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. Makes a copy of your repository.






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






3. When we remove redundant or obsolete designs and replace them with a new.






4. Will execute all code paths and boundary conditions.






5. When doing a - precise task.






6. One of the linking methods (pragma comment)






7. Downloads without merging.






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






9. 2 Eyes + 2 Minds = AWESOME!






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






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






12. Do not optimize until the very end.






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. Fix any problems and then repeat the process.






15. NULL memory.






16. Use only through the interface of the object.






17. Formatted code standards.






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






19. A measure of logical dependency.






20. Plan out your code.






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






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






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






24. Classes build off of each other.






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






26. Ignores files when pushing.






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






28. Code generation in a lib






29. Removes files from the repository.






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






31. Breaks encapsulation boundaries.






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






33. Quick program.






34. Views all previous changes.






35. Input






36. A function that can load a library






37. When you type in an object - you can see its attributes.






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






39. Bad! Don't ever use these types of variables!






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






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






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






43. Adds files to the repository.






44. Undo changes made since your last commit.






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






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






47. Variable doesn't exist.






48. Try to find the flaws in your code.






49. Set of all pending changes.






50. Initialized stack memory.