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. Views all previous changes.






2. Downloads without merging.






3. Link multiple projects together






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






5. Functionality Tests.






6. Code generation in a lib






7. Removes files from the repository.






8. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






9. Classes build off of each other.






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






11. No more than 40 hours to stop burnouts.






12. Trying to access a location in memory that your computer cannot access.






13. Initialized heap memory.






14. Inheritance between object.






15. STOP!!






16. Use only through the interface of the object.






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






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






19. Uploads changes to your current branch.






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






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






22. Stops when memory changes.






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






24. Will execute all code paths and boundary conditions.






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






26. What is part of the current scope.






27. Input






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






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






30. Default branch within your repository.






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






32. One of the linking methods (pragma comment)






33. Fix any problems and then repeat the process.






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






35. Code whatever it is you need to code.






36. Whats displayed to the screen






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






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






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






40. 2 Eyes + 2 Minds = AWESOME!






41. When GIT cannot merge your data.






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






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






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






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






46. Set of all pending changes.






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






48. Puts all headers into a master header.






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






50. Formatted code standards.