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. Helps to eliminate unnecessary "include chaining."






2. Adds files to the repository.






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






4. Create a test and then create a function.






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






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






7. When a class is defined within another class.






8. Are what function classes should include.






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






10. Link multiple projects together






11. Downloads your changes and then merges.






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






13. When a concrete class inherits from a pure interface.






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






15. Function doesn't exist.






16. Will execute all code paths and boundary conditions.






17. The linking is already done internally






18. No more than 40 hours to stop burnouts.






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






20. Inheritance between object.






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






22. Try to find the flaws in your code.






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






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






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






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






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






28. The default nickname for the remote repository.






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






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






31. Functionality Tests.






32. Variable doesn't exist.






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






34. What is part of the current scope.






35. Whats displayed to the screen






36. Makes a copy of your repository.






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






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






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






40. CONSTANT






41. Puts all headers into a master header.






42. A measure of logical dependency.






43. When a conflict is fixed.






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






45. Stops when memory changes.






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






47. Current view/ previous line.






48. Put this before a function name in a dll - and the function name will avoid name mangling






49. Downloads without merging.






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