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. Copies all changes from one branch into another branch.






2. No more than 40 hours to stop burnouts.






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






4. Whats displayed to the screen






5. Current view/ previous line.






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






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






8. When GIT cannot merge your data.






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






10. A measure of logical dependency.






11. Initialized heap memory.






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






13. Simply a value.






14. Default branch within your repository.






15. Downloads your changes and then merges.






16. Are what function classes should include.






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






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






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






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






21. Function doesn't exist.






22. The linking is already done internally






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






24. Application






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






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






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






28. Makes a copy of your repository.






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






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






31. No man's land. Guard bytes before the after allocated heap memory.






32. Trying to access a location in memory that your computer cannot access.






33. 2 Eyes + 2 Minds = AWESOME!






34. A function that can load a library






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






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






37. Classes build off of each other.






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






39. Formatted code standards.






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






41. STOP!!






42. Views all previous changes.






43. Functionality Tests.






44. Try to find the flaws in your code.






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






46. A reference. Has and delete dynamic memory. implies ownership (Association does not).






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






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






49. When a conflict is fixed.






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