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. Uploads all changes staged in the index list into the repository database.






2. Bookmark of a revised set with a title. For easy checkouts.






3. Makes a copy of your repository.






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






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






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






7. Written by the customers as things that the system needs to do for them.






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






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






10. Do not optimize until the very end.






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






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






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






14. Italicized in UML.






15. When GIT cannot merge your data.






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






17. Application






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






19. CONSTANT






20. Code generation in a lib






21. STOP!!






22. When a conflict is fixed.






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






24. Classes build off of each other.






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






26. Downloads without merging.






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






28. Current view/ previous line.






29. Are what function classes should include.






30. The default nickname for the remote repository.






31. Quick program.






32. Breaks encapsulation boundaries.






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






34. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






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






36. What is part of the current scope.






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






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






39. The linking is already done internally






40. No more than 40 hours to stop burnouts.






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






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






43. Fix any problems and then repeat the process.






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






45. When a class is defined within another class.






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






47. Uploads changes to your current branch.






48. Inheritance between object.






49. A measure of logical dependency.






50. Helps to eliminate unnecessary "include chaining."