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. Formatted code standards.






2. Input






3. Try to find the flaws in your code.






4. Simply a value.






5. A measure of logical dependency.






6. Whats displayed to the screen






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






8. Quick program.






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






10. Link multiple projects together






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






12. Helps to eliminate unnecessary "include chaining."






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






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






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






16. Inheritance between object.






17. 2 Eyes + 2 Minds = AWESOME!






18. Classes build off of each other.






19. Code whatever it is you need to code.






20. When a class is defined within another class.






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. Current view/ previous line.






23. Create a test and then create a function.






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






25. Removes files from the repository.






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






27. Set of all pending changes.






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






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






30. Undo changes made since your last commit.






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






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






33. When you type in an object - you can see its attributes.






34. Ignores files when pushing.






35. No more than 40 hours to stop burnouts.






36. Functionality Tests.






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






38. Linking to dynamic libraries is usually handled by linking to an ____________.






39. Function doesn't exist.






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






41. Ability to accept different types of parameters to bind to different implementations at run-time.






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






43. Variable doesn't exist.






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






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






46. Puts all headers into a master header.






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






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






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






50. The default nickname for the remote repository.