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. Valid input that the program is designed to process.






2. Classes build off of each other.






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






4. Current view/ previous line.






5. Freed heap memory.






6. A measure of logical dependency.






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






8. Fix any problems and then repeat the process.






9. A function that can load a library






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. A set of creation and initialization steps useful for a set of different related tests.






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






13. Link multiple projects together






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






15. Variable doesn't exist.






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






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






18. Put this before a function name in a dll - and the function name will avoid name mangling






19. Quick program.






20. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






21. You have to tell it to link






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






23. Whats displayed to the screen






24. Makes a copy of your repository.






25. Default branch within your repository.






26. Downloads your changes and then merges.






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






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






29. The default nickname for the remote repository.






30. Input






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






32. Stops when memory changes.






33. The linking is already done internally






34. When GIT cannot merge your data.






35. Adds files to the repository.






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






37. Breaks encapsulation boundaries.






38. Use only through the interface of the object.






39. Downloads without merging.






40. No more than 40 hours to stop burnouts.






41. Do not optimize until the very end.






42. Simply a value.






43. Connection between a local brand and a remote branch.






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






45. Helps to eliminate unnecessary "include chaining."






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






47. 2 Eyes + 2 Minds = AWESOME!






48. Will execute all code paths and boundary conditions.






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






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