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. Separating out a section of code into a reusable function or class.






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






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






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






5. Classes build off of each other.






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






7. When GIT cannot merge your data.






8. NULL memory.






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






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






11. Create a test and then create a function.






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






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






14. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






15. Concept based on limiting the scope of modules to provide better structures.






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






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






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






19. Initialized heap memory.






20. Default branch within your repository.






21. Undo changes made since your last commit.






22. One of the linking methods (pragma comment)






23. When doing a - precise task.






24. Simply a value.






25. Functionality Tests.






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






27. Freed heap memory.






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






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






30. Set of all pending changes.






31. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






32. Variable doesn't exist.






33. Downloads without merging.






34. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






35. When a conflict is fixed.






36. A measure of logical dependency.






37. Will execute all code paths and boundary conditions.






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






39. Inheritance between object.






40. Code whatever it is you need to code.






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






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






43. Function doesn't exist.






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






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






46. Breaks encapsulation boundaries.






47. Stops when memory changes.






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






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






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