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. Set of all pending changes.






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






3. Input






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






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






6. Stops when memory changes.






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






8. Uploads changes to your current branch.






9. Are what function classes should include.






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






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






12. Whats displayed to the screen






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






14. Undo changes made since your last commit.






15. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






16. One of the linking methods (pragma comment)






17. Inheritance between object.






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






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






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






21. Downloads without merging.






22. Application






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






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






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






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






27. Create a test and then create a function.






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






29. Formatted code standards.






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






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






32. When a conflict is fixed.






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






34. A function that can load a library






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






36. You have to tell it to link






37. Fix any problems and then repeat the process.






38. Code generation in a lib






39. What is part of the current scope.






40. Quick program.






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






42. Do not optimize until the very end.






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






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






45. When you type in an object - you can see its attributes.






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






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






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






49. Puts all headers into a master header.






50. Will execute all code paths and boundary conditions.