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. When you type in an object - you can see its attributes.






2. 2 Eyes + 2 Minds = AWESOME!






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






4. Views all previous changes.






5. Quick program.






6. Do not optimize until the very end.






7. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






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






9. What is part of the current scope.






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






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






12. Set of all pending changes.






13. Initialized heap memory.






14. Variable doesn't exist.






15. Code generation in a lib






16. Stops when memory changes.






17. Portioning your changes to commit by inserting them into the index.






18. Try to find the flaws in your code.






19. Functionality Tests.






20. Function doesn't exist.






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






22. You have to tell it to link






23. No more than 40 hours to stop burnouts.






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






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






26. Whats displayed to the screen






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






28. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






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






30. Italicized in UML.






31. Simply a value.






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






33. Application






34. CONSTANT






35. Input






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






37. Downloads your changes and then merges.






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






39. A function that can load a library






40. Freed heap memory.






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






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






43. Puts all headers into a master header.






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






45. Fix any problems and then repeat the process.






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






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






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






49. When GIT cannot merge your data.






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