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. A reference. Has and delete dynamic memory. implies ownership (Association does not).






2. Uploads all changes staged in the index list into the repository database.






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






4. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






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






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






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






8. Helps to eliminate unnecessary "include chaining."






9. Code whatever it is you need to code.






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






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






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






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






14. Functionality Tests.






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






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






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






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






19. What is part of the current scope.






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






21. Default branch within your repository.






22. Current line that is executing.






23. Inheritance between object.






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






25. Puts all headers into a master header.






26. When a class is defined within another class.






27. Link multiple projects together






28. Input






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






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






31. Uploads changes to your current branch.






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






33. NULL memory.






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






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






36. Quick program.






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






38. No more than 40 hours to stop burnouts.






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






40. Set of all pending changes.






41. A measure of logical dependency.






42. Formatted code standards.






43. Freed heap memory.






44. A function that can load a library






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






46. You have to tell it to link






47. Try to find the flaws in your code.






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






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






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