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. Static in C++. Can span all instances of a class.






2. Makes a project compile in order of who is dependent on what






3. Undo changes made since your last commit.






4. Are what function classes should include.






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






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






7. When doing a - precise task.






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






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






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






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






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






13. Link multiple projects together






14. Simply a value.






15. Downloads without merging.






16. Try to find the flaws in your code.






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






18. The linking is already done internally






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






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






21. When a conflict is fixed.






22. The default nickname for the remote repository.






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






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






25. Default branch within your repository.






26. Allows consumers to try a system earlier and give early feedback.






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






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






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






30. CONSTANT






31. Helps to eliminate unnecessary "include chaining."






32. Do not optimize until the very end.






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






34. Current line that is executing.






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






36. Set of all pending changes.






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






38. 2 Eyes + 2 Minds = AWESOME!






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






40. Current view/ previous line.






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






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






43. NULL memory.






44. Inheritance between object.






45. Whats displayed to the screen






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






47. Application






48. Downloads your changes and then merges.






49. Stops when memory changes.






50. Removes files from the repository.