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. Stops when memory changes.






2. Fix any problems and then repeat the process.






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






4. Plan out your code.






5. A collection of memory addresses for all virtual functions in an objects class hierarchy.






6. Breaks encapsulation boundaries.






7. Inheritance between object.






8. Puts all headers into a master header.






9. Functionality Tests.






10. Treating a derived class's data members like it's base class's.






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






12. Keeps a team using a similar naming convention for things.






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






14. Are what function classes should include.






15. When doing a - precise task.






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






17. Whats displayed to the screen






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






19. About the interface to an object. Data contained within.






20. Input






21. 2 Eyes + 2 Minds = AWESOME!






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






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






24. Developers should be integrated and releasing code into the code repository every few hours.






25. Bad! Don't ever use these types of variables!






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






27. You have to tell it to link






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






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






30. Classes build off of each other.






31. Use only through the interface of the object.






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






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






34. Initialized stack memory.






35. Code whatever it is you need to code.






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






37. A set of creation and initialization steps useful for a set of different related tests.






38. Current view/ previous line.






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






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






41. The default nickname for the remote repository.






42. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






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






44. Do not optimize until the very end.






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






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






47. Quick program.






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






49. Italicized in UML.






50. CONSTANT