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. Code generation in a lib






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






3. CONSTANT






4. The linking is already done internally






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






6. Plan out your code.






7. NULL memory.






8. 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.






9. No more than 40 hours to stop burnouts.






10. Undo changes made since your last commit.






11. Simply a value.






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






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






14. Inheritance between object.






15. Adds files to the repository.






16. Formatted code standards.






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






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






19. Italicized in UML.






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






21. A function that can load a library






22. Puts all headers into a master header.






23. Set of all pending changes.






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






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






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






27. Initialized stack memory.






28. Create a test and then create a function.






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






30. Whats displayed to the screen






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






32. Use only through the interface of the object.






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






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






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






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






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






38. Views all previous changes.






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






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






41. Code whatever it is you need to code.






42. Link multiple projects together






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






44. 2 Eyes + 2 Minds = AWESOME!






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






46. One of the linking methods (pragma comment)






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






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






49. When doing a - precise task.






50. Stops when memory changes.