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. Initialized heap memory.






2. Helps to eliminate unnecessary "include chaining."






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






4. Variable doesn't exist.






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






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






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






8. Always do the simplest design that could possibly work.






9. No more than 40 hours to stop burnouts.






10. Default branch within your repository.






11. When a class is defined within another class.






12. Try to find the flaws in your code.






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






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






15. Current view/ previous line.






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






17. Black Box - The way the program works is internally unknown.






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






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






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






21. Classes build off of each other.






22. Application






23. Puts all headers into a master header.






24. Functionality Tests.






25. Inheritance between object.






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






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






28. Will execute all code paths and boundary conditions.






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






30. Undo changes made since your last commit.






31. Uploads changes to your current branch.






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






33. Makes a copy of your repository.






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






35. The default nickname for the remote repository.






36. When doing a - precise task.






37. Quick program.






38. Code whatever it is you need to code.






39. Symbols that can be invoked or used by other code in a different unit. All non inline class member functions and variables - non-static non-member functions and variables defined within a .cpp file






40. Freed heap memory.






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






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






43. Input






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






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






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






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






48. Do not optimize until the very end.






49. Use only through the interface of the object.






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