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. Classes build off of each other.






2. Helps to eliminate unnecessary "include chaining."






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






4. Use only through the interface of the object.






5. Uploads changes to your current branch.






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






7. 2 Eyes + 2 Minds = AWESOME!






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






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






10. When doing a - precise task.






11. Whats displayed to the screen






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






13. When you type in an object - you can see its attributes.






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






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






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






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






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






19. The default nickname for the remote repository.






20. Initialized heap memory.






21. Are what function classes should include.






22. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






23. STOP!!






24. Makes a copy of your repository.






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






26. A function that can load a library






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






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






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






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






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






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






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






34. Do not optimize until the very end.






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






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






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






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






39. CONSTANT






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






41. Link multiple projects together






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






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






44. Fix any problems and then repeat the process.






45. Function doesn't exist.






46. Current line that is executing.






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






48. Set of all pending changes.






49. When a class is defined within another class.






50. Ignores files when pushing.