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. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






3. Quick program.






4. One of the linking methods (pragma comment)






5. Code whatever it is you need to code.






6. Current line that is executing.






7. A measure of logical dependency.






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






9. Puts all headers into a master header.






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






11. Allows you to switch your working copy to another branch.






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






13. What is part of the current scope.






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






15. Initialized stack memory.






16. Italicized in UML.






17. When doing a - precise task.






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






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






20. Classes build off of each other.






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






22. No more than 40 hours to stop burnouts.






23. Uploads changes to your current branch.






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






25. Simply a value.






26. Downloads your changes and then merges.






27. Link multiple projects together






28. Undo changes made since your last commit.






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






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






31. Fix any problems and then repeat the process.






32. Makes a copy of your repository.






33. Try to find the flaws in your code.






34. NULL memory.






35. Plan out your code.






36. Formatted code standards.






37. Input






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






39. Ignores files when pushing.






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






41. Set of all pending changes.






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






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






44. When a conflict is fixed.






45. Function doesn't exist.






46. Default branch within your repository.






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






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






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






50. Code generation in a lib