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. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






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






3. When GIT cannot merge your data.






4. Allows you to switch your working copy to another branch.






5. Will execute all code paths and boundary conditions.






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






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






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






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






10. Helps to eliminate unnecessary "include chaining."






11. NULL memory.






12. Input






13. Ignores files when pushing.






14. Makes a copy of your repository.






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






16. Current view/ previous line.






17. Use only through the interface of the object.






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






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






20. What is part of the current scope.






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






22. Code whatever it is you need to code.






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






24. Plan out your code.






25. Are what function classes should include.






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






27. CONSTANT






28. Adds files to the repository.






29. Link multiple projects together






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






31. Stops when memory changes.






32. Application






33. Set of all pending changes.






34. Breaks encapsulation boundaries.






35. Treating a derived class's data members like it's base class's.






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






37. A function that can load a library






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






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






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






41. Uploads changes to your current branch.






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






43. Variable doesn't exist.






44. You have to tell it to link






45. Fix any problems and then repeat the process.






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






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






48. Quick program.






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






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