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. Bad! Don't ever use these types of variables!






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






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






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






5. Link multiple projects together






6. CONSTANT






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






8. Do not optimize until the very end.






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






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






11. Functionality Tests.






12. Current view/ previous line.






13. When GIT cannot merge your data.






14. Current line that is executing.






15. Plan out your code.






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






17. Uploads changes to your current branch.






18. Input






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






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






21. Downloads without merging.






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






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






24. A pointer or reference. One object needs to know about the other object to work.






25. Italicized in UML.






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






27. What is part of the current scope.






28. Freed heap memory.






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






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






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






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






33. Variable doesn't exist.






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






35. Code generation in a lib






36. The default nickname for the remote repository.






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






38. Undo changes made since your last commit.






39. Try to find the flaws in your code.






40. Breaks encapsulation boundaries.






41. Set of all pending changes.






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






43. Application






44. Create a test and then create a function.






45. Downloads your changes and then merges.






46. Puts all headers into a master header.






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






48. Initialized stack memory.






49. Removes files from the repository.






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