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. Whats displayed to the screen






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






3. Downloads your changes and then merges.






4. Function doesn't exist.






5. Formatted code standards.






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






7. Downloads without merging.






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. Views all previous changes.






10. Are what function classes should include.






11. CONSTANT






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






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






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






15. Uploads changes to your current branch.






16. The linking is already done internally






17. When a conflict is fixed.






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






19. Italicized in UML.






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






21. Input






22. The default nickname for the remote repository.






23. No more than 40 hours to stop burnouts.






24. NULL memory.






25. Functionality Tests.






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






27. Do not optimize until the very end.






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






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






30. Undo changes made since your last commit.






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






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






33. When doing a - precise task.






34. Stops when memory changes.






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






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






37. Puts all headers into a master header.






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






39. Quick program.






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






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






42. Ignores files when pushing.






43. Keeps a team using a similar naming convention for things.






44. Use only through the interface of the object.






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






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






47. A function that can load a library






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






49. Try to find the flaws in your code.






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