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. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






2. Initialized stack memory.






3. Simply a value.






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






5. Classes build off of each other.






6. The linking is already done internally






7. You have to tell it to link






8. When a class is defined within another class.






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






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






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






12. Invalid or unexpected input that the program is not designed to process.






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






14. Current view/ previous line.






15. Breaks encapsulation boundaries.






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






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






18. A function that can load a library






19. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






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






21. Views all previous changes.






22. 2 Eyes + 2 Minds = AWESOME!






23. Uploads all changes staged in the index list into the repository database.






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






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






26. The default nickname for the remote repository.






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






28. When GIT cannot merge your data.






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






30. Stops when memory changes.






31. Quick program.






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






33. Puts all headers into a master header.






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






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






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






37. A collection of memory addresses for all virtual functions in an objects class hierarchy.






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






39. A measure of logical dependency.






40. Downloads without merging.






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






42. Makes a project compile in order of who is dependent on what






43. Are what function classes should include.






44. No man's land. Guard bytes before the after allocated heap memory.






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






46. When a conflict is fixed.






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






48. Function doesn't exist.






49. Helps to eliminate unnecessary "include chaining."






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