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 concrete class inherits from a pure interface.






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






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






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






5. NULL memory.






6. The default nickname for the remote repository.






7. Portioning your changes to commit by inserting them into the index.






8. Input






9. Italicized in UML.






10. No man's land. Guard bytes before the after allocated heap memory.






11. Uploads changes to your current branch.






12. When doing a - precise task.






13. Downloads without merging.






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






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






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






17. Set of all pending changes.






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






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






20. Freed heap memory.






21. Breaks encapsulation boundaries.






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






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






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






25. You have to tell it to link






26. STOP!!






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






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






29. Undo changes made since your last commit.






30. What is part of the current scope.






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






32. Downloads your changes and then merges.






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






34. Stops when memory changes.






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






36. Makes a project compile in order of who is dependent on what






37. Formatted code standards.






38. Functionality Tests.






39. The linking is already done internally






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






41. Will execute all code paths and boundary conditions.






42. Simply a value.






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






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






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






46. One of the linking methods (pragma comment)






47. Create a test and then create a function.






48. Application






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






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