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. Functionality Tests.






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






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






4. Views all previous changes.






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






6. Variable doesn't exist.






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






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






9. Plan out your code.






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






11. You have to tell it to link






12. A reference. Has and delete dynamic memory. implies ownership (Association does not).






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






14. The process of deciding which function definition to link during run-time.






15. NULL memory.






16. Use this to find a memory address or signiture in a dll






17. Freed heap memory.






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






19. Invalid or unexpected input that the program is not designed to process.






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






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






22. A measure of logical dependency.






23. Do not optimize until the very end.






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






25. One of the linking methods (pragma comment)






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






27. When a class is defined within another class.






28. Makes a copy of your repository.






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






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






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






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






33. The linking is already done internally






34. Ignores files when pushing.






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






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






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






38. Will execute all code paths and boundary conditions.






39. When doing a - precise task.






40. Set of all pending changes.






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






42. Whats displayed to the screen






43. Adds files to the repository.






44. Undo changes made since your last commit.






45. Downloads your changes and then merges.






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






47. Classes build off of each other.






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






49. Application






50. Meetings at the beginning of each iteration to produce a plan of programming tasks.