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. Put this before a function name in a dll - and the function name will avoid name mangling






2. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






3. Italicized in UML.






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






5. Functionality Tests.






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






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






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






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






10. When a class is defined within another class.






11. The default nickname for the remote repository.






12. Are what function classes should include.






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






14. Use this to find a memory address or signiture in a dll






15. Makes a copy of your repository.






16. 2 Eyes + 2 Minds = AWESOME!






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






18. Inheritance between object.






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






20. CONSTANT






21. Use only through the interface of the object.






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






23. No more than 40 hours to stop burnouts.






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






25. Do not optimize until the very end.






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






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






28. Quick program.






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






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






31. Classes build off of each other.






32. Views all previous changes.






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






34. Current view/ previous line.






35. Will execute all code paths and boundary conditions.






36. You have to tell it to link






37. Code generation in a lib






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






39. Try to find the flaws in your code.






40. Adds files to the repository.






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






42. Helps to eliminate unnecessary "include chaining."






43. Fix any problems and then repeat the process.






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






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






46. The linking is already done internally






47. When a conflict is fixed.






48. A measure of logical dependency.






49. A function that can load a library






50. Function doesn't exist.