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






2. Freed heap memory.






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






4. Always do the simplest design that could possibly work.






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






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






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






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






9. Will execute all code paths and boundary conditions.






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






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






12. You have to tell it to link






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






14. Current view/ previous line.






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






16. Undo changes made since your last commit.






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






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






19. Variable doesn't exist.






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






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






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






23. CONSTANT






24. Simply a value.






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






26. Portioning your changes to commit by inserting them into the index.






27. Function doesn't exist.






28. A set of creation and initialization steps useful for a set of different related tests.






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






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






31. Ability to accept different types of parameters to bind to different implementations at run-time.






32. 2 Eyes + 2 Minds = AWESOME!






33. Downloads without merging.






34. Meetings at the beginning of each iteration to produce a plan of programming tasks.






35. Stand up meetings show who will be valuable and needed.






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






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






38. Fix any problems and then repeat the process.






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






40. Classes build off of each other.






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






42. Helps to eliminate unnecessary "include chaining."






43. Try to find the flaws in your code.






44. Figure out what is feasible. Decide whether to use API's or to write from scratch.






45. Whats displayed to the screen






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






47. Default branch within your repository.






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






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






50. Italicized in UML.