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. The process of deciding which function definition to link during run-time.






2. Input






3. Quick program.






4. When a conflict is fixed.






5. You have to tell it to link






6. Current view/ previous line.






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






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






9. Removes files from the repository.






10. When you type in an object - you can see its attributes.






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






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






13. Uploads changes to your current branch.






14. Plan out your code.






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






16. Simply a value.






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






18. Initialized heap memory.






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






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






21. Views all previous changes.






22. Downloads without merging.






23. A measure of logical dependency.






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






25. Undo changes made since your last commit.






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






27. Are what function classes should include.






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






29. What is part of the current scope.






30. Application






31. Code whatever it is you need to code.






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






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






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






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






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






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






38. The default nickname for the remote repository.






39. Uploads all changes staged in the index list into the repository database.






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






41. Functionality Tests.






42. Italicized in UML.






43. Whats displayed to the screen






44. Formatted code standards.






45. Link multiple projects together






46. Current line that is executing.






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






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






49. Create a test and then create a function.






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