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. Black Box - The way the program works is internally unknown.






2. Quick program.






3. Set of all pending changes.






4. Code whatever it is you need to code.






5. Views all previous changes.






6. Breaks encapsulation boundaries.






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






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






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






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






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






12. CONSTANT






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






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






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






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






17. Makes a copy of your repository.






18. Whats displayed to the screen






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






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






21. Classes build off of each other.






22. Functionality Tests.






23. NULL memory.






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






25. One of the linking methods (pragma comment)






26. Function doesn't exist.






27. Link multiple projects together






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






29. Adds files to the repository.






30. Removes files from the repository.






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






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






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






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






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






36. Are what function classes should include.






37. Stops when memory changes.






38. Formatted code standards.






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






40. Undo changes made since your last commit.






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






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






43. STOP!!






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






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






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






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






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






49. Code generation in a lib






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