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. Code generation in a lib






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






3. Simply a value.






4. A function that can load a library






5. Views all previous changes.






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






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






8. Try to find the flaws in your code.






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






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






11. Link multiple projects together






12. CONSTANT






13. A measure of logical dependency.






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






15. When a class is defined within another class.






16. Function doesn't exist.






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






18. Set of all pending changes.






19. 2 Eyes + 2 Minds = AWESOME!






20. Italicized in UML.






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






22. When a conflict is fixed.






23. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






24. The default nickname for the remote repository.






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






26. The linking is already done internally






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






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






29. Stops when memory changes.






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






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






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






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






34. Will execute all code paths and boundary conditions.






35. Do not optimize until the very end.






36. Downloads your changes and then merges.






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






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






39. Initialized heap memory.






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






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






42. NULL memory.






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






44. Use only through the interface of the object.






45. STOP!!






46. Create a test and then create a function.






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






48. Adds files to the repository.






49. Puts all headers into a master header.






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