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. Variable doesn't exist.






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






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






4. Code whatever it is you need to code.






5. Views all previous changes.






6. When a conflict is fixed.






7. CONSTANT






8. Input






9. Helps to eliminate unnecessary "include chaining."






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






11. The linking is already done internally






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






13. Freed heap memory.






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






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






16. Formatted code standards.






17. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






18. Simply a value.






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






20. Create a test and then create a function.






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






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






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






24. Functionality Tests.






25. No more than 40 hours to stop burnouts.






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






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






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






29. Plan out your code.






30. Current line that is executing.






31. A measure of logical dependency.






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






33. The default nickname for the remote repository.






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






35. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






36. 2 Eyes + 2 Minds = AWESOME!






37. Use only through the interface of the object.






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






39. Fix any problems and then repeat the process.






40. A function that can load a library






41. Whats displayed to the screen






42. Undo changes made since your last commit.






43. Separating out a section of code into a reusable function or class.






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






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






46. When GIT cannot merge your data.






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






48. Classes build off of each other.






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






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