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. Classes build off of each other.






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






3. Quick program.






4. Code whatever it is you need to code.






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






6. Use only through the interface of the object.






7. CONSTANT






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






9. Downloads your changes and then merges.






10. Removes files from the repository.






11. A function that can load a library






12. When a conflict is fixed.






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






14. Create a test and then create a function.






15. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






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






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






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






19. Code generation in a lib






20. A measure of logical dependency.






21. Fix any problems and then repeat the process.






22. Whats displayed to the screen






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






24. Default branch within your repository.






25. Are what function classes should include.






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






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






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






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






30. Plan out your code.






31. Ignores files when pushing.






32. Formatted code standards.






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






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






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






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






37. One of the linking methods (pragma comment)






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






39. The process of deciding which function definition to link during run-time.






40. The default nickname for the remote repository.






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






42. Inheritance between object.






43. When a class is defined within another class.






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






45. STOP!!






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






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






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






49. Puts all headers into a master header.






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