Test your basic knowledge |

SWA - Software Architecture

Instructions:
  • Answer 50 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. Bookmark of a revised set with a title. For easy checkouts.






2. The process of deciding which function definition to link during run-time.






3. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






4. When you type in an object - you can see its attributes.






5. Adds files to the repository.






6. Stand up meetings show who will be valuable and needed.






7. Initialized heap memory.






8. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






9. Separating out a section of code into a reusable function or class.






10. The linking is already done internally






11. Meetings at the beginning of each iteration to produce a plan of programming tasks.






12. Code generation in a lib






13. Valid input that the program is designed to process.






14. A type of library that is used by the code






15. How many objects that a source object can legitimately reference.






16. Ability to withstand change and what the effects are.






17. Written by the customers as things that the system needs to do for them.






18. Removes files from the repository.






19. Views all previous changes.






20. Undo changes made since your last commit.






21. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






22. Ability to accept different types of parameters to bind to different implementations at run-time.






23. Variable doesn't exist.






24. Puts all headers into a master header.






25. Set of all pending changes.






26. Function doesn't exist.






27. Functionality Tests.






28. Application






29. Do not optimize until the very end.






30. Invalid or unexpected input that the program is not designed to process.






31. Stops when memory changes.






32. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






33. Copies all changes from one branch into another branch.






34. Weak relationship between two classes. Almost always results in a #include.






35. Allows you to switch your working copy to another branch.






36. Creates a spin-off of a repository for concurrent development.






37. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






38. CONSTANT






39. Portioning your changes to commit by inserting them into the index.






40. Meetings used to create a release plan - which will lay out the overall project.






41. When a class is defined within another class.






42. You have to tell it to link






43. Default branch within your repository.






44. Ability to treat a class object as a function by overloading the () operator.






45. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






46. Ask questions and obtain the details and requirements given.






47. Formatted code standards.






48. Create a test and then create a function.






49. A function that can load a library






50. A pointer or reference. One object needs to know about the other object to work.