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 function that can load a library






2. Classes build off of each other.






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






4. Ignores files when pushing.






5. Inheritance between object.






6. Functionality Tests.






7. NULL memory.






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






9. Freed heap memory.






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






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






12. One of the linking methods (pragma comment)






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






14. Application






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






16. Valid input that the program is designed to process.






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






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






19. Code generation in a lib






20. Formatted code standards.






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






22. Current view/ previous line.






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






24. Downloads without merging.






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






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






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






28. When a concrete class inherits from a pure interface.






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






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






31. Fix any problems and then repeat the process.






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






33. When a class is defined within another class.






34. Input






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






36. Default branch within your repository.






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






38. Helps to eliminate unnecessary "include chaining."






39. Initialized stack memory.






40. A measure of logical dependency.






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. Ask questions and obtain the details and requirements given.






43. Undo changes made since your last commit.






44. Breaks encapsulation boundaries.






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






46. Makes a copy of your repository.






47. Downloads your changes and then merges.






48. Meetings used to create a release plan - which will lay out the overall project.






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






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