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. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






2. Will execute all code paths and boundary conditions.






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






4. A measure of logical dependency.






5. Downloads without merging.






6. Weak relationship between two classes. Almost always results in a #include.






7. How many objects that a source object can legitimately reference.






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






9. Ignores files when pushing.






10. Variable doesn't exist.






11. Whats displayed to the screen






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






13. Connection between a local brand and a remote branch.






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






15. Makes a copy of your repository.






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






17. Uploads changes to your current branch.






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






19. Views all previous changes.






20. When GIT cannot merge your data.






21. Ability to treat a class object as a function by overloading the () operator.






22. When doing a - precise task.






23. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






24. NULL memory.






25. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






26. When a conflict is fixed.






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






28. Formatted code standards.






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






30. Stops when memory changes.






31. Fix any problems and then repeat the process.






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






33. Default branch within your repository.






34. Functionality Tests.






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






36. Adds files to the repository.






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






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






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






40. Puts all headers into a master header.






41. Italicized in UML.






42. CONSTANT






43. Link multiple projects together






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






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






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






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






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






49. Try to find the flaws in your code.






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