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. When a conflict is fixed.






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






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






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






5. A measure of logical dependency.






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






7. Freed heap memory.






8. Variable doesn't exist.






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






10. When GIT cannot merge your data.






11. The linking is already done internally






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






13. Function doesn't exist.






14. Code whatever it is you need to code.






15. What is part of the current scope.






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






17. No more than 40 hours to stop burnouts.






18. Will execute all code paths and boundary conditions.






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






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






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






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






23. Default branch within your repository.






24. Views all previous changes.






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






26. When doing a - precise task.






27. Set of all pending changes.






28. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






29. Do not optimize until the very end.






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






31. Downloads without merging.






32. Inheritance between object.






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






34. Undo changes made since your last commit.






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






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






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






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






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






40. Input






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






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






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






44. Stops when memory changes.






45. Functionality Tests.






46. You have to tell it to link






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






48. When a class is defined within another class.






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






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