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. Helps to eliminate unnecessary "include chaining."






2. The linking is already done internally






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






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






5. Views all previous changes.






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






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






8. When GIT cannot merge your data.






9. Connection between a local brand and a remote branch.






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






11. Will execute all code paths and boundary conditions.






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






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






14. Makes a copy of your repository.






15. STOP!!






16. 2 Eyes + 2 Minds = AWESOME!






17. What is part of the current scope.






18. Variable doesn't exist.






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






20. Set of all pending changes.






21. Are what function classes should include.






22. Simply a value.






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






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






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






26. Functionality Tests.






27. Function doesn't exist.






28. CONSTANT






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






30. Default branch within your repository.






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






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






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






34. One of the linking methods (pragma comment)






35. Stand up meetings show who will be valuable and needed.






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






37. When a class is defined within another class.






38. Downloads without merging.






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






40. Freed heap memory.






41. Current view/ previous line.






42. Create a test and then create a function.






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






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






45. A measure of logical dependency.






46. Ask questions and obtain the details and requirements given.






47. The default nickname for the remote repository.






48. When a conflict is fixed.






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






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