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. Will execute all code paths and boundary conditions.






2. When doing a - precise task.






3. Quick program.






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






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






6. When GIT cannot merge your data.






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






8. Views all previous changes.






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






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






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






12. Puts all headers into a master header.






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






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






15. Ensure a class only has one instance - and provide a global point of access to it






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






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






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






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






20. Inheritance between object.






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






22. When a class is defined within another class.






23. CONSTANT






24. Undo changes made since your last commit.






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






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






27. The linking is already done internally






28. Current view/ previous line.






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






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






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






32. Removes files from the repository.






33. NULL memory.






34. Whats displayed to the screen






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






36. Function doesn't exist.






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






38. Try to find the flaws in your code.






39. Creates a copy of your current branch into a remote branch.






40. Breaks encapsulation boundaries.






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






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






43. Fix any problems and then repeat the process.






44. 2 Eyes + 2 Minds = AWESOME!






45. Set of all pending changes.






46. Classes build off of each other.






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






48. Code whatever it is you need to code.






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






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