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. A reference. Has and delete dynamic memory. implies ownership (Association does not).






2. Set of all pending changes.






3. The linking is already done internally






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






5. Makes a copy of your repository.






6. CONSTANT






7. About the interface to an object. Data contained within.






8. Ignores files when pushing.






9. Adds files to the repository.






10. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






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






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






13. Link multiple projects together






14. Current view/ previous line.






15. Helps to eliminate unnecessary "include chaining."






16. Variable doesn't exist.






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






18. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






19. Portioning your changes to commit by inserting them into the index.






20. No more than 40 hours to stop burnouts.






21. Formatted code standards.






22. Static in C++. Can span all instances of a class.






23. Ask questions and obtain the details and requirements given.






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






25. NULL memory.






26. Downloads your changes and then merges.






27. Will execute all code paths and boundary conditions.






28. Fix any problems and then repeat the process.






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






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






31. Removes files from the repository.






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






33. Breaks encapsulation boundaries.






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






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






36. What is part of the current scope.






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






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






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






40. Plan out your code.






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






42. Views all previous changes.






43. Quick program.






44. Default branch within your repository.






45. Are what function classes should include.






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






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






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






49. Current line that is executing.






50. Stops when memory changes.