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. A collection of memory addresses for all virtual functions in an objects class hierarchy.






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






3. Code whatever it is you need to code.






4. Puts all headers into a master header.






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






6. When a conflict is fixed.






7. A measure of logical dependency.






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






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






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






11. Whats displayed to the screen






12. Try to find the flaws in your code.






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






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






15. No more than 40 hours to stop burnouts.






16. Default branch within your repository.






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






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






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






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






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






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






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






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






25. Set of all pending changes.






26. STOP!!






27. Makes a copy of your repository.






28. Breaks encapsulation boundaries.






29. Initialized stack memory.






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






31. When doing a - precise task.






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






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






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






35. Link multiple projects together






36. Ignores files when pushing.






37. Plan out your code.






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






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






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






41. Variable doesn't exist.






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






43. Adds files to the repository.






44. Are what function classes should include.






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






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






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






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






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






50. When a concrete class inherits from a pure interface.