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. Copies all changes from one branch into another branch.






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






3. Fix any problems and then repeat the process.






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






5. Use only through the interface of the object.






6. The linking is already done internally






7. Link multiple projects together






8. Classes build off of each other.






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






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






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






12. Set of all pending changes.






13. CONSTANT






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






15. Adds files to the repository.






16. Freed heap memory.






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






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






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






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






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






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






23. Written by the customers as things that the system needs to do for them.






24. Stops when memory changes.






25. Plan out your code.






26. Variable doesn't exist.






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






28. Current line that is executing.






29. Input






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






31. Allows you to switch your working copy to another branch.






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






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






34. When GIT cannot merge your data.






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






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






37. Initialized stack memory.






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






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






40. Are what function classes should include.






41. Weak relationship between two classes. Almost always results in a #include.






42. When a conflict is fixed.






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






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






45. Ignores files when pushing.






46. One of the linking methods (pragma comment)






47. Create a test and then create a function.






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






49. Breaks encapsulation boundaries.






50. Application