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 GIT cannot merge your data.






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






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






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






5. A function that can load a library






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






7. Do not optimize until the very end.






8. Quick program.






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






10. Variable doesn't exist.






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






12. One of the linking methods (pragma comment)






13. Downloads your changes and then merges.






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






15. Formatted code standards.






16. Code whatever it is you need to code.






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






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






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






20. Allows consumers to try a system earlier and give early feedback.






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






22. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






23. Application






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






25. Stops when memory changes.






26. Views all previous changes.






27. Fix any problems and then repeat the process.






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






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






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






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






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






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






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






35. Code generation in a lib






36. Treating a derived class's data members like it's base class's.






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






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






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






40. The default nickname for the remote repository.






41. Meetings at the beginning of each iteration to produce a plan of programming tasks.






42. Breaks encapsulation boundaries.






43. Freed heap memory.






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






45. When a class is defined within another class.






46. Functionality Tests.






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






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






49. CONSTANT






50. Whats displayed to the screen