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 GIT cannot merge your data.






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






3. Current view/ previous line.






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






5. Italicized in UML.






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






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






8. A function that can load a library






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






10. 2 Eyes + 2 Minds = AWESOME!






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






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






13. Set of all pending changes.






14. Freed heap memory.






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






16. Meetings used to create a release plan - which will lay out the overall project.






17. Try to find the flaws in your code.






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






19. When doing a - precise task.






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






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






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






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






24. Initialized stack memory.






25. A measure of logical dependency.






26. Classes build off of each other.






27. Breaks encapsulation boundaries.






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






29. NULL memory.






30. Whats displayed to the screen






31. Functionality Tests.






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






33. Current line that is executing.






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






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






36. Formatted code standards.






37. Create a test and then create a function.






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






39. Initialized heap memory.






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






41. Makes a project compile in order of who is dependent on what






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






43. Inheritance between object.






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






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






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






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






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






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






50. Variable doesn't exist.