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. Downloads your changes and then merges.






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






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






4. Makes a copy of your repository.






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






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






7. Breaks encapsulation boundaries.






8. Current view/ previous line.






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






10. Formatted code standards.






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






12. Create a test and then create a function.






13. No more than 40 hours to stop burnouts.






14. Do not optimize until the very end.






15. When GIT cannot merge your data.






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






17. Ignores files when pushing.






18. How many objects that a source object can legitimately reference.






19. Set of all pending changes.






20. 2 Eyes + 2 Minds = AWESOME!






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






22. Italicized in UML.






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






24. Try to find the flaws in your code.






25. What is part of the current scope.






26. Function doesn't exist.






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






28. Uploads changes to your current branch.






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






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






31. CONSTANT






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






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






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






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






36. Inheritance between object.






37. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






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






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






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






41. Puts all headers into a master header.






42. Stops when memory changes.






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






44. When a conflict is fixed.






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






46. Classes build off of each other.






47. Input






48. NULL memory.






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






50. Code whatever it is you need to code.