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. 2 Eyes + 2 Minds = AWESOME!






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






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






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






5. Uploads changes to your current branch.






6. Functionality Tests.






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






8. NULL memory.






9. Plan out your code.






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






11. Function doesn't exist.






12. Are what function classes should include.






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






14. Ensure a class only has one instance - and provide a global point of access to it






15. A measure of logical dependency.






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






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






18. When a class is defined within another class.






19. Formatted code standards.






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






21. Inheritance between object.






22. Classes build off of each other.






23. Will execute all code paths and boundary conditions.






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






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






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






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






28. A reference. Has and delete dynamic memory. implies ownership (Association does not).






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






30. When a conflict is fixed.






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






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






33. Use this to find a memory address or signiture in a dll






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






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






36. Try to find the flaws in your code.






37. CONSTANT






38. Set of all pending changes.






39. Downloads without merging.






40. Whats displayed to the screen






41. You have to tell it to link






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






43. Removes files from the repository.






44. Use only through the interface of the object.






45. Freed heap memory.






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






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






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






49. What is part of the current scope.






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