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. Set of all pending changes.






2. Undo changes made since your last commit.






3. Link multiple projects together






4. Meetings used to create a release plan - which will lay out the overall project.






5. 2 Eyes + 2 Minds = AWESOME!






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






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






8. Are what function classes should include.






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






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






11. A function that can load a library






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






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






14. When GIT cannot merge your data.






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






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






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






18. Allows consumers to try a system earlier and give early feedback.






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






20. Initialized heap memory.






21. NULL memory.






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






23. Application






24. Italicized in UML.






25. Plan out your code.






26. Put this before a function name in a dll - and the function name will avoid name mangling






27. Uploads changes to your current branch.






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






29. Default branch within your repository.






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






31. Downloads without merging.






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






33. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






34. Whats displayed to the screen






35. The linking is already done internally






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






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






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






39. Current line that is executing.






40. Initialized stack memory.






41. Makes a copy of your repository.






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






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






44. Inheritance between object.






45. Valid input that the program is designed to process.






46. STOP!!






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






48. Helps to eliminate unnecessary "include chaining."






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






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