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 pointer or reference. One object needs to know about the other object to work.






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






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






4. Downloads without merging.






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






6. One of the linking methods (pragma comment)






7. A reference. Has and delete dynamic memory. implies ownership (Association does not).






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






9. You have to tell it to link






10. What is part of the current scope.






11. Do not optimize until the very end.






12. Functionality Tests.






13. Initialized stack memory.






14. 2 Eyes + 2 Minds = AWESOME!






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






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






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






18. Fix any problems and then repeat the process.






19. STOP!!






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






21. Function doesn't exist.






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






23. Code whatever it is you need to code.






24. Simply a value.






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






26. Current view/ previous line.






27. Makes a copy of your repository.






28. Puts all headers into a master header.






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






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






31. NULL memory.






32. Treating a derived class's data members like it's base class's.






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






34. Current line that is executing.






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






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






37. Quick program.






38. A function that can load a library






39. Try to find the flaws in your code.






40. Create a test and then create a function.






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






42. Trying to access a location in memory that your computer cannot access.






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






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






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






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






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






48. Uploads changes to your current branch.






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






50. Developers should be integrated and releasing code into the code repository every few hours.