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. Uploads all changes staged in the index list into the repository database.






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






3. Formatted code standards.






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






5. CONSTANT






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






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






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






9. Initialized stack memory.






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






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






12. Linking to dynamic libraries is usually handled by linking to an ____________.






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






14. The linking is already done internally






15. Do not optimize until the very end.






16. What is part of the current scope.






17. When GIT cannot merge your data.






18. NULL memory.






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






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






21. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






22. Concept based on limiting the scope of modules to provide better structures.






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






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






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






26. Are what function classes should include.






27. Helps to eliminate unnecessary "include chaining."






28. Link multiple projects together






29. Freed heap memory.






30. A measure of logical dependency.






31. You have to tell it to link






32. One of the linking methods (pragma comment)






33. Fix any problems and then repeat the process.






34. Italicized in UML.






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






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






37. Puts all headers into a master header.






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






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






40. Classes build off of each other.






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






42. Black Box - The way the program works is internally unknown.






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






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






45. Downloads without merging.






46. When a class is defined within another class.






47. Makes a copy of your repository.






48. Breaks encapsulation boundaries.






49. Uploads changes to your current branch.






50. Takes information in the index and pushes it onto the stack.