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. Use only through the interface of the object.






2. Downloads without merging.






3. Input






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






5. Freed heap memory.






6. Downloads your changes and then merges.






7. When a class is defined within another class.






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






9. Breaks encapsulation boundaries.






10. Inheritance between object.






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






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






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






14. Adds files to the repository.






15. A measure of logical dependency.






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






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






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






19. Makes a copy of your repository.






20. Ignores files when pushing.






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






22. When a conflict is fixed.






23. A function that can load a library






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






25. Variable doesn't exist.






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






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






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






29. No more than 40 hours to stop burnouts.






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






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






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






33. Functionality Tests.






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






35. 2 Eyes + 2 Minds = AWESOME!






36. Quick program.






37. Italicized in UML.






38. Simply a value.






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






40. Set of all pending changes.






41. Whats displayed to the screen






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






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






45. Current line that is executing.






46. Function doesn't exist.






47. Will execute all code paths and boundary conditions.






48. NULL memory.






49. Fix any problems and then repeat the process.






50. Create a test and then create a function.