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. Downloads your changes and then merges.






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






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






4. Do not optimize until the very end.






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






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






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






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






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






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






11. Function doesn't exist.






12. Italicized in UML.






13. Application






14. Puts all headers into a master header.






15. Fix any problems and then repeat the process.






16. Whats displayed to the screen






17. Try to find the flaws in your code.






18. Quick program.






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






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






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






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






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






24. Undo changes made since your last commit.






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






26. Breaks encapsulation boundaries.






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






28. CONSTANT






29. What is part of the current scope.






30. A collection of memory addresses for all virtual functions in an objects class hierarchy.






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






32. Input






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






34. A measure of logical dependency.






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






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






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






38. Views all previous changes.






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






40. Code generation in a lib






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






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






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






44. Link multiple projects together






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






46. Plan out your code.






47. Initialized heap memory.






48. Stops when memory changes.






49. You have to tell it to link






50. When a class is defined within another class.