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. Having power over inheritance with the flexibility of composition.






2. Formatted code standards.






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






4. When doing a - precise task.






5. Code whatever it is you need to code.






6. Whats displayed to the screen






7. CONSTANT






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






9. Views all previous changes.






10. Are what function classes should include.






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






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






13. When GIT cannot merge your data.






14. 2 Eyes + 2 Minds = AWESOME!






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






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






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






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






19. Ignores files when pushing.






20. Downloads without merging.






21. Function doesn't exist.






22. You have to tell it to link






23. A function that can load a library






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






25. The default nickname for the remote repository.






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






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






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






29. Input






30. Do not optimize until the very end.






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






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






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






34. A measure of logical dependency.






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






36. Initialized heap memory.






37. The linking is already done internally






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






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






40. Fix any problems and then repeat the process.






41. Current line that is executing.






42. Create a test and then create a function.






43. NULL memory.






44. Variable doesn't exist.






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






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






47. A pointer or reference. One object needs to know about the other object to work.






48. Quick program.






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






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