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. A type of library that is used by the code






2. 2 Eyes + 2 Minds = AWESOME!






3. Plan out your code.






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






5. STOP!!






6. Fix any problems and then repeat the process.






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






8. Inheritance between object.






9. A reference. Has and delete dynamic memory. implies ownership (Association does not).






10. The default nickname for the remote repository.






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






12. Meetings used to create a release plan - which will lay out the overall project.






13. Try to find the flaws in your code.






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






15. Initialized stack memory.






16. Current line that is executing.






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






18. Will execute all code paths and boundary conditions.






19. Default branch within your repository.






20. When a class is defined within another class.






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






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






23. Function doesn't exist.






24. Are what function classes should include.






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






26. Adds files to the repository.






27. Downloads without merging.






28. Simply a value.






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






30. NULL memory.






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






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






33. Do not optimize until the very end.






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






35. Input






36. When doing a - precise task.






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






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






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






40. Quick program.






41. When we remove redundant or obsolete designs and replace them with a new.






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






43. Classes build off of each other.






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






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






46. Formatted code standards.






47. When GIT cannot merge your data.






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






49. Views all previous changes.






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