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 measure of logical dependency.






2. Link multiple projects together






3. Are what function classes should include.






4. Freed heap memory.






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






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






7. Plan out your code.






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






9. One of the linking methods (pragma comment)






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






11. No more than 40 hours to stop burnouts.






12. Undo changes made since your last commit.






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






14. A function that can load a library






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






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






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






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






19. Connection between a local brand and a remote branch.






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






21. Whats displayed to the screen






22. Ignores files when pushing.






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






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






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






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






27. A type of library that is used by the code






28. Code generation in a lib






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






30. Adds files to the repository.






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






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






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






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






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






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






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






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






39. Breaks encapsulation boundaries.






40. Application






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






42. When a class is defined within another class.






43. Helps to eliminate unnecessary "include chaining."






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






45. Initialized heap memory.






46. Current view/ previous line.






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






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






49. CONSTANT






50. Quick program.