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. About the interface to an object. Data contained within.






2. When a conflict is fixed.






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






4. Having power over inheritance with the flexibility of composition.






5. You have to tell it to link






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






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






8. Invalid or unexpected input that the program is not designed to process.






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






10. Initialized heap memory.






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






12. Stops when memory changes.






13. Do not optimize until the very end.






14. Simply a value.






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






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






17. Makes a copy of your repository.






18. Will execute all code paths and boundary conditions.






19. Uploads changes to your current branch.






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






21. Variable doesn't exist.






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






23. The linking is already done internally






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






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






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






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






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






29. When GIT cannot merge your data.






30. A type of library that is used by the code






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






32. Freed heap memory.






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






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






35. Application






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






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






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






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






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






41. Inheritance between object.






42. When a class is defined within another class.






43. Current view/ previous line.






44. NULL memory.






45. Classes build off of each other.






46. Adds files to the repository.






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






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






49. Downloads without merging.






50. Breaks encapsulation boundaries.