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. Trying to access a location in memory that your computer cannot access.






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






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






4. When GIT cannot merge your data.






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






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






7. STOP!!






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






9. Will execute all code paths and boundary conditions.






10. Concept based on limiting the scope of modules to provide better structures.






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






12. Link multiple projects together






13. Copies all changes from one branch into another branch.






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






15. A function that can load a library






16. Helps to eliminate unnecessary "include chaining."






17. Functionality Tests.






18. Simply a value.






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






20. When doing a - precise task.






21. Developers should be integrated and releasing code into the code repository every few hours.






22. Function doesn't exist.






23. Puts all headers into a master header.






24. The linking is already done internally






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






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






27. Bookmark of a revised set with a title. For easy checkouts.






28. Quick program.






29. 2 Eyes + 2 Minds = AWESOME!






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






31. Initialized heap memory.






32. When a class is defined within another class.






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






34. No more than 40 hours to stop burnouts.






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






36. Freed heap memory.






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






38. Removes files from the repository.






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






40. Initialized stack memory.






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






42. Stops when memory changes.






43. Linking to dynamic libraries is usually handled by linking to an ____________.






44. Fix any problems and then repeat the process.






45. Try to find the flaws in your code.






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






47. Downloads your changes and then merges.






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






49. NULL memory.






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