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. Italicized in UML.






2. Simply a value.






3. Default branch within your repository.






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






5. Will execute all code paths and boundary conditions.






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






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






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






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






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






11. Stops when memory changes.






12. No more than 40 hours to stop burnouts.






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






14. Views all previous changes.






15. Function doesn't exist.






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






17. Undo changes made since your last commit.






18. A measure of logical dependency.






19. Set of all pending changes.






20. Code generation in a lib






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






22. Classes build off of each other.






23. CONSTANT






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






25. Use only through the interface of the object.






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






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






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






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






30. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






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






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






33. Freed heap memory.






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






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






36. Application






37. Current line that is executing.






38. The default nickname for the remote repository.






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






40. Ignores files when pushing.






41. Adds files to the repository.






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






43. NULL memory.






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






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






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






47. You have to tell it to link






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






49. When a class is defined within another class.






50. Are what function classes should include.