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. Makes a copy of your repository.






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






3. Function doesn't exist.






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






5. Initialized heap memory.






6. Inheritance between object.






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






8. Ignores files when pushing.






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






10. Will execute all code paths and boundary conditions.






11. One of the linking methods (pragma comment)






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






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






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






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






16. Use only through the interface of the object.






17. The linking is already done internally






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






19. CONSTANT






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






21. Downloads without merging.






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






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






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






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






26. Removes files from the repository.






27. Are what function classes should include.






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






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






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






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






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






33. Breaks encapsulation boundaries.






34. Adds files to the repository.






35. A pointer or reference. One object needs to know about the other object to work.






36. Input






37. When doing a - precise task.






38. Puts all headers into a master header.






39. Functionality Tests.






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






41. Undo changes made since your last commit.






42. Formatted code standards.






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






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






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






46. Uploads changes to your current branch.






47. Create a test and then create a function.






48. When GIT cannot merge your data.






49. Variable doesn't exist.






50. Initialized stack memory.