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. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






2. Makes a copy of your repository.






3. Stops when memory changes.






4. Formatted code standards.






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






6. Makes a project compile in order of who is dependent on what






7. A function that can load a library






8. Link multiple projects together






9. Whats displayed to the screen






10. Inheritance between object.






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






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






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






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






15. Adds files to the repository.






16. No more than 40 hours to stop burnouts.






17. Current line that is executing.






18. Uploads changes to your current branch.






19. When a class is defined within another class.






20. One of the linking methods (pragma comment)






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






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






23. Are what function classes should include.






24. Plan out your code.






25. Initialized stack memory.






26. Portioning your changes to commit by inserting them into the index.






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






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






29. Downloads your changes and then merges.






30. Current view/ previous line.






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






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






33. Removes files from the repository.






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






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






36. Code whatever it is you need to code.






37. Quick program.






38. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






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






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






41. Ability to accept different types of parameters to bind to different implementations at run-time.






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






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






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






45. NULL memory.






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






47. Simply a value.






48. Downloads without merging.






49. Breaks encapsulation boundaries.






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