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. Stops when memory changes.






2. What is part of the current scope.






3. Inheritance between object.






4. Current line that is executing.






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






6. When a conflict is fixed.






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






8. Functionality Tests.






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






10. Italicized in UML.






11. NULL memory.






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






13. The linking is already done internally






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






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






16. Breaks encapsulation boundaries.






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






18. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






19. A measure of logical dependency.






20. A function that can load a library






21. STOP!!






22. Simply a value.






23. One of the linking methods (pragma comment)






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






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






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






27. Figure out what is feasible. Decide whether to use API's or to write from scratch.






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






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






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






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






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






33. Try to find the flaws in your code.






34. Fix any problems and then repeat the process.






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






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






37. Puts all headers into a master header.






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






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






40. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






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






42. Removes files from the repository.






43. Function doesn't exist.






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






45. Whats displayed to the screen






46. Application






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






48. Views all previous changes.






49. Initialized stack memory.






50. Code whatever it is you need to code.