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. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






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






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






4. You have to tell it to link






5. 2 Eyes + 2 Minds = AWESOME!






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






7. Downloads without merging.






8. Application






9. Removes files from the repository.






10. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






11. Creates a copy of your current branch into a remote branch.






12. Helps to eliminate unnecessary "include chaining."






13. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






14. Always do the simplest design that could possibly work.






15. Views all previous changes.






16. One of the linking methods (pragma comment)






17. 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






18. Figure out what is feasible. Decide whether to use API's or to write from scratch.






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






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






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






22. Stops when memory changes.






23. Current line that is executing.






24. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






25. Breaks encapsulation boundaries.






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






27. No man's land. Guard bytes before the after allocated heap memory.






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






29. Bookmark of a revised set with a title. For easy checkouts.






30. Italicized in UML.






31. Current view/ previous line.






32. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






33. Static in C++. Can span all instances of a class.






34. Allows consumers to try a system earlier and give early feedback.






35. Quick program.






36. A measure of logical dependency.






37. Makes a project compile in order of who is dependent on what






38. Are what function classes should include.






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






40. Adds files to the repository.






41. Simply a value.






42. Set of all pending changes.






43. Use only through the interface of the object.






44. When we remove redundant or obsolete designs and replace them with a new.






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






46. Having power over inheritance with the flexibility of composition.






47. Fix any problems and then repeat the process.






48. Whats displayed to the screen






49. Variable doesn't exist.






50. Ignores files when pushing.