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. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






4. Helps to eliminate unnecessary "include chaining."






5. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






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






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






8. Code generation in a lib






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






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






11. Whats displayed to the screen






12. One of the linking methods (pragma comment)






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






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






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






16. CONSTANT






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






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






19. Makes a copy of your repository.






20. Adds files to the repository.






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






22. Views all previous changes.






23. Will execute all code paths and boundary conditions.






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






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. When a concrete class inherits from a pure interface.






27. Quick program.






28. Removes files from the repository.






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






30. The linking is already done internally






31. Breaks encapsulation boundaries.






32. Stops when memory changes.






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






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






35. Puts all headers into a master header.






36. Italicized in UML.






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






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






39. Input






40. When a class is defined within another class.






41. Formatted code standards.






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






43. No more than 40 hours to stop burnouts.






44. Initialized heap memory.






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






46. When GIT cannot merge your data.






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






48. Black Box - The way the program works is internally unknown.






49. Undo changes made since your last commit.






50. Initialized stack memory.