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. Static in C++. Can span all instances of a class.






2. Puts all headers into a master header.






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






4. Formatted code standards.






5. What is part of the current scope.






6. Code whatever it is you need to code.






7. Set of all pending changes.






8. One of the linking methods (pragma comment)






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






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






11. When doing a - precise task.






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






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






14. A measure of logical dependency.






15. Do not optimize until the very end.






16. Classes build off of each other.






17. No more than 40 hours to stop burnouts.






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






19. Connection between a local brand and a remote branch.






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






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






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






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






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






25. 2 Eyes + 2 Minds = AWESOME!






26. NULL memory.






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






28. Initialized stack memory.






29. Breaks encapsulation boundaries.






30. Use only through the interface of the object.






31. Downloads without merging.






32. Plan out your code.






33. Default branch within your repository.






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






35. A function that can load a library






36. Helps to eliminate unnecessary "include chaining."






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






38. STOP!!






39. Fix any problems and then repeat the process.






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






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






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






43. Quick program.






44. Code generation in a lib






45. CONSTANT






46. Will execute all code paths and boundary conditions.






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






48. Link multiple projects together






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






50. Inheritance between object.