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. A measure of logical dependency.






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






3. Input






4. Current view/ previous line.






5. Stops when memory changes.






6. Are what function classes should include.






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






8. Views all previous changes.






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






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






11. Adds files to the repository.






12. Formatted code standards.






13. Application






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






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






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






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






18. Fix any problems and then repeat the process.






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






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






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






22. Downloads without merging.






23. Downloads your changes and then merges.






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






25. Freed heap memory.






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






27. No man's land. Guard bytes before the after allocated heap memory.






28. Simply a value.






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






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






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






32. When a conflict is fixed.






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






34. Will execute all code paths and boundary conditions.






35. Italicized in UML.






36. The linking is already done internally






37. Ignores files when pushing.






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






39. Do not optimize until the very end.






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






41. About the interface to an object. Data contained within.






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






43. You have to tell it to link






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






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






46. Default branch within your repository.






47. The default nickname for the remote repository.






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






49. Makes a copy of your repository.






50. CONSTANT