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. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






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






3. No more than 40 hours to stop burnouts.






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






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






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






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






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






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






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






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






12. Do not optimize until the very end.






13. Input






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






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






16. Uploads changes to your current branch.






17. Use only through the interface of the object.






18. Stops when memory changes.






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






20. Function doesn't exist.






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






22. Formatted code standards.






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






24. The default nickname for the remote repository.






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






26. Downloads without merging.






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






28. Views all previous changes.






29. STOP!!






30. Makes a copy of your repository.






31. Functionality Tests.






32. Quick program.






33. When doing a - precise task.






34. Default branch within your repository.






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






36. Initialized heap memory.






37. Classes build off of each other.






38. 2 Eyes + 2 Minds = AWESOME!






39. A function that can load a library






40. Current view/ previous line.






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






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






43. Will execute all code paths and boundary conditions.






44. Puts all headers into a master header.






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






46. When a class is defined within another class.






47. When a conflict is fixed.






48. Link multiple projects together






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






50. Taking code and moving it to a function that usually returns an object. They are always virtual functions.