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. Makes a project compile in order of who is dependent on what






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






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






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






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






6. Simply a value.






7. Italicized in UML.






8. No more than 40 hours to stop burnouts.






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






10. Removes files from the repository.






11. Downloads without merging.






12. Do not optimize until the very end.






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






14. Inheritance between object.






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






16. Quick program.






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






18. Always do the simplest design that could possibly work.






19. Set of all pending changes.






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






21. Whats displayed to the screen






22. Ignores files when pushing.






23. Current view/ previous line.






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






25. Function doesn't exist.






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






27. NULL memory.






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






29. Initialized heap memory.






30. Default branch within your repository.






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






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






33. Breaks encapsulation boundaries.






34. When GIT cannot merge your data.






35. You have to tell it to link






36. Makes a copy of your repository.






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






38. Input






39. Current line that is executing.






40. Downloads your changes and then merges.






41. Create a test and then create a function.






42. When a class is defined within another class.






43. Link multiple projects together






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






45. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






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






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






48. Uploads changes to your current branch.






49. Initialized stack memory.






50. CONSTANT