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. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






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






3. Freed heap memory.






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






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






6. Variable doesn't exist.






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






8. Plan out your code.






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






10. Static in C++. Can span all instances of a class.






11. Input






12. Helps to eliminate unnecessary "include chaining."






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






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






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






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






17. Link multiple projects together






18. Simply a value.






19. Formatted code standards.






20. Create a test and then create a function.






21. Keeps a team using a similar naming convention for things.






22. When doing a - precise task.






23. Inheritance between object.






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






25. What is part of the current scope.






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






27. Default branch within your repository.






28. CONSTANT






29. Removes files from the repository.






30. When GIT cannot merge your data.






31. STOP!!






32. Try to find the flaws in your code.






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






34. Initialized stack memory.






35. Takes information in the index and pushes it onto the stack.






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






37. Puts all headers into a master header.






38. The default nickname for the remote repository.






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






40. Fix any problems and then repeat the process.






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






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






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






44. Breaks encapsulation boundaries.






45. Function doesn't exist.






46. 2 Eyes + 2 Minds = AWESOME!






47. You have to tell it to link






48. Undo changes made since your last commit.






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






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