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. Do not optimize until the very end.






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






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






4. Set of all pending changes.






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






6. Link multiple projects together






7. Current view/ previous line.






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






9. When GIT cannot merge your data.






10. Removes files from the repository.






11. Fix any problems and then repeat the process.






12. Code whatever it is you need to code.






13. Breaks encapsulation boundaries.






14. Will execute all code paths and boundary conditions.






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






16. When a class is defined within another class.






17. NULL memory.






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






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






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






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






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






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






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






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






26. One of the linking methods (pragma comment)






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






28. Simply a value.






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






30. What is part of the current scope.






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






32. When doing a - precise task.






33. Input






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






35. Undo changes made since your last commit.






36. Try to find the flaws in your code.






37. Quick program.






38. Are what function classes should include.






39. A collection of memory addresses for all virtual functions in an objects class hierarchy.






40. Function doesn't exist.






41. A function that can load a library






42. Inheritance between object.






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






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






45. How many objects that a source object can legitimately reference.






46. Variable doesn't exist.






47. Classes build off of each other.






48. Formatted code standards.






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






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