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. A type of library that is used by the code






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






3. Classes build off of each other.






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






5. Will execute all code paths and boundary conditions.






6. No more than 40 hours to stop burnouts.






7. Set of all pending changes.






8. Application






9. When GIT cannot merge your data.






10. Uploads changes to your current branch.






11. Do not optimize until the very end.






12. Freed heap memory.






13. Views all previous changes.






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






15. A measure of logical dependency.






16. Removes files from the repository.






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






18. Simply a value.






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






20. Code generation in a lib






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






22. Whats displayed to the screen






23. STOP!!






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






25. CONSTANT






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






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






28. Use only through the interface of the object.






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






30. Fix any problems and then repeat the process.






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






32. When a class is defined within another class.






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






34. Ensure a class only has one instance - and provide a global point of access to it






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






36. Formatted code standards.






37. Create a test and then create a function.






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






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






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






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






42. Try to find the flaws in your code.






43. Uploads all changes staged in the index list into the repository database.






44. 2 Eyes + 2 Minds = AWESOME!






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






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






47. Undo changes made since your last commit.






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






49. Bad! Don't ever use these types of variables!






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