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. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






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






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






5. Plan out your code.






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






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






8. Do not optimize until the very end.






9. No more than 40 hours to stop burnouts.






10. Input






11. STOP!!






12. Breaks encapsulation boundaries.






13. When a conflict is fixed.






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






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






16. 2 Eyes + 2 Minds = AWESOME!






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






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






19. Static in C++. Can span all instances of a class.






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






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






22. Use only through the interface of the object.






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






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






25. A function that can load a library






26. Makes a copy of your repository.






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






28. Stops when memory changes.






29. CONSTANT






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






31. Whats displayed to the screen






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






33. Simply a value.






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






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






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






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






38. Undo changes made since your last commit.






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






40. Application






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






42. A measure of logical dependency.






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






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






45. Classes build off of each other.






46. Freed heap memory.






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






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






49. Quick program.






50. One of the linking methods (pragma comment)