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. When GIT cannot merge your data.






2. CONSTANT






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






4. Quick program.






5. You have to tell it to link






6. Simply a value.






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






8. Do not optimize until the very end.






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






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






11. Initialized heap memory.






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






13. When a class is defined within another class.






14. When a conflict is fixed.






15. Use only through the interface of the object.






16. STOP!!






17. Whats displayed to the screen






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






19. Removes files from the repository.






20. The default nickname for the remote repository.






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






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






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






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






25. Figure out what is feasible. Decide whether to use API's or to write from scratch.






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






27. Plan out your code.






28. Will execute all code paths and boundary conditions.






29. Current view/ previous line.






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






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






32. Link multiple projects together






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






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






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






36. Inheritance between object.






37. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






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






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






40. Classes build off of each other.






41. Formatted code standards.






42. NULL memory.






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






44. Create a test and then create a function.






45. Downloads your changes and then merges.






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






47. Are what function classes should include.






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






49. Set of all pending changes.






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