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. Quick program.






2. Are what function classes should include.






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






4. Freed heap memory.






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






6. Input






7. Inheritance between object.






8. Creates a spin-off of a repository for concurrent development.






9. Formatted code standards.






10. Downloads your changes and then merges.






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






12. When GIT cannot merge your data.






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






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






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






16. Stops when memory changes.






17. Downloads without merging.






18. NULL memory.






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






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






21. Bookmark of a revised set with a title. For easy checkouts.






22. Linking to dynamic libraries is usually handled by linking to an ____________.






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






24. Uploads changes to your current branch.






25. Try to find the flaws in your code.






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






27. Breaks encapsulation boundaries.






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






29. STOP!!






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






31. Create a test and then create a function.






32. What is part of the current scope.






33. You have to tell it to link






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






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






36. Stand up meetings show who will be valuable and needed.






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






38. Ignores files when pushing.






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






40. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






41. Plan out your code.






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






43. Simply a value.






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






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






46. 2 Eyes + 2 Minds = AWESOME!






47. Do not optimize until the very end.






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






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






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