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. Views all previous changes.






2. Makes a copy of your repository.






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






4. What is part of the current scope.






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






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






7. CONSTANT






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






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






10. Default branch within your repository.






11. Ignores files when pushing.






12. Italicized in UML.






13. Portioning your changes to commit by inserting them into the index.






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






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






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






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






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






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






20. Functionality Tests.






21. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






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






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






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






25. Current view/ previous line.






26. When GIT cannot merge your data.






27. One of the linking methods (pragma comment)






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






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






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






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






32. Formatted code standards.






33. A measure of logical dependency.






34. Code whatever it is you need to code.






35. Classes build off of each other.






36. Breaks encapsulation boundaries.






37. Are what function classes should include.






38. Inheritance between object.






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






40. When a class is defined within another class.






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






42. Downloads without merging.






43. Fix any problems and then repeat the process.






44. Current line that is executing.






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






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






47. Freed heap memory.






48. Whats displayed to the screen






49. 2 Eyes + 2 Minds = AWESOME!






50. Application