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. No more than 40 hours to stop burnouts.






2. What is part of the current scope.






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






4. Initialized heap memory.






5. Adds files to the repository.






6. Inheritance between object.






7. The linking is already done internally






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






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






10. Create a test and then create a function.






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






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






13. Puts all headers into a master header.






14. Use only through the interface of the object.






15. Breaks encapsulation boundaries.






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






17. Uploads changes to your current branch.






18. Helps to eliminate unnecessary "include chaining."






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






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. Code generation in a lib






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






23. CONSTANT






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






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






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






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






28. Whats displayed to the screen






29. Views all previous changes.






30. Default branch within your repository.






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






32. Initialized stack memory.






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






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






35. Formatted code standards.






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






37. STOP!!






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






39. Downloads without merging.






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






41. Variable doesn't exist.






42. Link multiple projects together






43. Do not optimize until the very end.






44. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






45. Are what function classes should include.






46. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






48. Function doesn't exist.






49. Functionality Tests.






50. When GIT cannot merge your data.