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. Always do the simplest design that could possibly work.






2. 2 Eyes + 2 Minds = AWESOME!






3. Are what function classes should include.






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






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






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






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






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






9. Do not optimize until the very end.






10. Code generation in a lib






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






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






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






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






15. CONSTANT






16. Input






17. No more than 40 hours to stop burnouts.






18. Current line that is executing.






19. Italicized in UML.






20. NULL memory.






21. A measure of logical dependency.






22. Adds files to the repository.






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






24. One of the linking methods (pragma comment)






25. Create a test and then create a function.






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






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






28. Simply a value.






29. Application






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






31. Puts all headers into a master header.






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






33. When a conflict is fixed.






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






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






36. Stops when memory changes.






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






38. Inheritance between object.






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






40. The linking is already done internally






41. Helps to eliminate unnecessary "include chaining."






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






43. Put this before a function name in a dll - and the function name will avoid name mangling






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






45. Removes files from the repository.






46. Quick program.






47. The default nickname for the remote repository.






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






49. What is part of the current scope.






50. Fix any problems and then repeat the process.