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. When you type in an object - you can see its attributes.






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






3. Quick program.






4. Application






5. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






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






7. Current line that is executing.






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






9. Do not optimize until the very end.






10. A function that can load a library






11. STOP!!






12. Simply a value.






13. Meetings at the beginning of each iteration to produce a plan of programming tasks.






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






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






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






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






18. Puts all headers into a master header.






19. Breaks encapsulation boundaries.






20. Code whatever it is you need to code.






21. Ignores files when pushing.






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






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






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






25. Portioning your changes to commit by inserting them into the index.






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






27. Set of all pending changes.






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






29. No more than 40 hours to stop burnouts.






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






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






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






33. Helps to eliminate unnecessary "include chaining."






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






35. Use only through the interface of the object.






36. Classes build off of each other.






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






38. Adds files to the repository.






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






40. Are what function classes should include.






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






42. Makes a copy of your repository.






43. Creates a spin-off of a repository for concurrent development.






44. A measure of logical dependency.






45. 2 Eyes + 2 Minds = AWESOME!






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






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. Views all previous changes.






49. Variable doesn't exist.






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