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. Link multiple projects together






3. Stops when memory changes.






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






5. Application






6. Classes build off of each other.






7. Initialized stack memory.






8. 2 Eyes + 2 Minds = AWESOME!






9. Create a test and then create a function.






10. Functionality Tests.






11. When GIT cannot merge your data.






12. STOP!!






13. Quick program.






14. Italicized in UML.






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






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






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






18. Function doesn't exist.






19. NULL memory.






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






21. When a class is defined within another class.






22. Meetings used to create a release plan - which will lay out the overall project.






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






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






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






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






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






28. Uploads changes to your current branch.






29. No man's land. Guard bytes before the after allocated heap memory.






30. Puts all headers into a master header.






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






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






33. Do not optimize until the very end.






34. Fix any problems and then repeat the process.






35. No more than 40 hours to stop burnouts.






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






37. Makes a copy of your repository.






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






39. Are what function classes should include.






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






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






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






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






44. Undo changes made since your last commit.






45. Code whatever it is you need to code.






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






47. Downloads without merging.






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






49. When doing a - precise task.






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