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. When a class is defined within another class.






2. Use only through the interface of the object.






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






4. Input






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






6. CONSTANT






7. Simply a value.






8. Freed heap memory.






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






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






11. When GIT cannot merge your data.






12. Inheritance between object.






13. Code whatever it is you need to code.






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






15. Whats displayed to the screen






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






17. The process of deciding which function definition to link during run-time.






18. Weak relationship between two classes. Almost always results in a #include.






19. The linking is already done internally






20. Helps to eliminate unnecessary "include chaining."






21. Current line that is executing.






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






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






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






25. Views all previous changes.






26. Try to find the flaws in your code.






27. Removes files from the repository.






28. A function that can load a library






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






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






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






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






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






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






35. STOP!!






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






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






38. Breaks encapsulation boundaries.






39. Set of all pending changes.






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






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






42. One of the linking methods (pragma comment)






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






44. Uploads changes to your current branch.






45. Downloads without merging.






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






47. The default nickname for the remote repository.






48. When doing a - precise task.






49. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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