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. What is part of the current scope.






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






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






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






5. When a conflict is fixed.






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






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






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






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






10. Freed heap memory.






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






12. Meetings used to create a release plan - which will lay out the overall project.






13. You have to tell it to link






14. Current line that is executing.






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






16. Whats displayed to the screen






17. Views all previous changes.






18. No more than 40 hours to stop burnouts.






19. Stops when memory changes.






20. Breaks encapsulation boundaries.






21. Puts all headers into a master header.






22. Plan out your code.






23. Downloads your changes and then merges.






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






25. Will execute all code paths and boundary conditions.






26. Inheritance between object.






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






28. One of the linking methods (pragma comment)






29. A measure of logical dependency.






30. Link multiple projects together






31. The default nickname for the remote repository.






32. Set of all pending changes.






33. Input






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






35. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






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






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






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






40. NULL memory.






41. Variable doesn't exist.






42. CONSTANT






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






44. Formatted code standards.






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






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






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






48. Fix any problems and then repeat the process.






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






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