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. Separating out a section of code into a reusable function or class.






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






3. Uploads changes to your current branch.






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






5. Code whatever it is you need to code.






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






7. 2 Eyes + 2 Minds = AWESOME!






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






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






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






11. Are what function classes should include.






12. Uploads all changes staged in the index list into the repository database.






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






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






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






16. Application






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






18. You have to tell it to link






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






20. Ability to treat a class object as a function by overloading the () operator.






21. Quick program.






22. Do not optimize until the very end.






23. Downloads without merging.






24. Ignores files when pushing.






25. Use only through the interface of the object.






26. Create a test and then create a function.






27. What is part of the current scope.






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






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






30. Function doesn't exist.






31. Classes build off of each other.






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






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






34. Variable doesn't exist.






35. Creates a copy of your current branch into a remote branch.






36. Code generation in a lib






37. Initialized heap memory.






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






39. Inheritance between object.






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






41. Will execute all code paths and boundary conditions.






42. Try to find the flaws in your code.






43. The linking is already done internally






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






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






46. Stops when memory changes.






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






48. NULL memory.






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






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