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. The linking is already done internally






2. Default branch within your repository.






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






4. Downloads your changes and then merges.






5. Uploads changes to your current branch.






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






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






8. Removes files from the repository.






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






10. One of the linking methods (pragma comment)






11. Input






12. The default nickname for the remote repository.






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






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






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






16. Set of all pending changes.






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






18. 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






19. When a conflict is fixed.






20. 2 Eyes + 2 Minds = AWESOME!






21. Views all previous changes.






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






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






24. Stops when memory changes.






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






26. A measure of logical dependency.






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






28. Downloads without merging.






29. Do not optimize until the very end.






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






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






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






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






34. Initialized stack memory.






35. Quick program.






36. Ignores files when pushing.






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






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






39. Adds files to the repository.






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






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






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






43. Initialized heap memory.






44. Bad! Don't ever use these types of variables!






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






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






47. When a class is defined within another class.






48. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






49. Formatted code standards.






50. STOP!!