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. Ability to accept different types of parameters to bind to different implementations at run-time.






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






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






4. Are what function classes should include.






5. A function that can load a library






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






7. Separating out a section of code into a reusable function or class.






8. Undo changes made since your last commit.






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






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






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






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






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






14. The default nickname for the remote repository.






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






16. Initialized stack memory.






17. Helps to eliminate unnecessary "include chaining."






18. Ignores files when pushing.






19. Formatted code standards.






20. NULL memory.






21. Fix any problems and then repeat the process.






22. Code generation in a lib






23. One of the linking methods (pragma comment)






24. Initialized heap memory.






25. Whats displayed to the screen






26. CONSTANT






27. Create a test and then create a function.






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






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






30. Functionality Tests.






31. Views all previous changes.






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






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






34. The linking is already done internally






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






36. Link multiple projects together






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






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






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. STOP!!






41. When doing a - precise task.






42. What is part of the current scope.






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






44. Adds files to the repository.






45. Linking to dynamic libraries is usually handled by linking to an ____________.






46. When a class is defined within another class.






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. You have to tell it to link






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






50. Simply a value.