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






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






3. When a conflict is fixed.






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






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






6. Are what function classes should include.






7. Allows consumers to try a system earlier and give early feedback.






8. The linking is already done internally






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






10. Removes files from the repository.






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






12. Italicized in UML.






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






14. A measure of logical dependency.






15. Fix any problems and then repeat the process.






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






17. A function that can load a library






18. STOP!!






19. Freed heap memory.






20. CONSTANT






21. Downloads your changes and then merges.






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






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






24. Meetings at the beginning of each iteration to produce a plan of programming tasks.






25. Adds files to the repository.






26. Puts all headers into a master header.






27. Makes a copy of your repository.






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






29. The default nickname for the remote repository.






30. Classes build off of each other.






31. NULL memory.






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






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






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






35. Default branch within your repository.






36. Initialized stack memory.






37. Copies all changes from one branch into another branch.






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






39. Simply a value.






40. Helps to eliminate unnecessary "include chaining."






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






42. 2 Eyes + 2 Minds = AWESOME!






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






44. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






45. When GIT cannot merge your data.






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






47. Creates a spin-off of a repository for concurrent development.






48. Undo changes made since your last commit.






49. Link multiple projects together






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