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 group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






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






3. When a class is defined within another class.






4. Function doesn't exist.






5. Freed heap memory.






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






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






8. Link multiple projects together






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






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






11. Initialized stack memory.






12. Are what function classes should include.






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






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






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






16. Uploads changes to your current branch.






17. A pointer or reference. One object needs to know about the other object to work.






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






19. A function that can load a library






20. Functionality Tests.






21. Puts all headers into a master header.






22. Makes a copy of your repository.






23. STOP!!






24. Application






25. Stops when memory changes.






26. Whats displayed to the screen






27. Downloads your changes and then merges.






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






29. Breaks encapsulation boundaries.






30. When GIT cannot merge your data.






31. Adds files to the repository.






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






33. Default branch within your repository.






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






35. Do not optimize until the very end.






36. Ignores files when pushing.






37. Downloads without merging.






38. One of the linking methods (pragma comment)






39. Plan out your code.






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






41. Code whatever it is you need to code.






42. Will execute all code paths and boundary conditions.






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






44. Use only through the interface of the object.






45. Inheritance between object.






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






47. Helps to eliminate unnecessary "include chaining."






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






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






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