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. NULL memory.






3. Uploads changes to your current branch.






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






5. Current view/ previous line.






6. Current line that is executing.






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






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






9. The linking is already done internally






10. Whats displayed to the screen






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






12. Default branch within your repository.






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






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






15. Initialized heap memory.






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






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






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






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






20. Undo changes made since your last commit.






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






22. Adds files to the repository.






23. Try to find the flaws in your code.






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






25. The default nickname for the remote repository.






26. Function doesn't exist.






27. Views all previous changes.






28. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






29. Breaks encapsulation boundaries.






30. Stops when memory changes.






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






32. Developers should be integrated and releasing code into the code repository every few hours.






33. Code generation in a lib






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






35. Formatted code standards.






36. When a conflict is fixed.






37. Are what function classes should include.






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






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






40. Ensure a class only has one instance - and provide a global point of access to it






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






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






43. Will execute all code paths and boundary conditions.






44. 2 Eyes + 2 Minds = AWESOME!






45. Ignores files when pushing.






46. You have to tell it to link






47. Italicized in UML.






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






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






50. Treating a derived class's data members like it's base class's.