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






2. Breaks encapsulation boundaries.






3. Inheritance between object.






4. Function doesn't exist.






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






6. Initialized heap memory.






7. Treating a derived class's data members like it's base class's.






8. Stops when memory changes.






9. Downloads your changes and then merges.






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






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






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






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






14. Try to find the flaws in your code.






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






16. Use only through the interface of the object.






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






18. When doing a - precise task.






19. Removes files from the repository.






20. Adds files to the repository.






21. Input






22. Italicized in UML.






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






24. A measure of logical dependency.






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






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






27. Ability to withstand change and what the effects are.






28. Current line that is executing.






29. Code whatever it is you need to code.






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






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






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






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






34. Variable doesn't exist.






35. Ignores files when pushing.






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






37. Default branch within your repository.






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






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






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






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






42. Concept based on limiting the scope of modules to provide better structures.






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






44. Are what function classes should include.






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






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






47. One of the linking methods (pragma comment)






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






49. A set of creation and initialization steps useful for a set of different related tests.






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