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. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






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






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






4. Whats displayed to the screen






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






6. Try to find the flaws in your code.






7. Variable doesn't exist.






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






9. One of the linking methods (pragma comment)






10. 2 Eyes + 2 Minds = AWESOME!






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






12. Link multiple projects together






13. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






15. Function doesn't exist.






16. Code generation in a lib






17. Use only through the interface of the object.






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






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






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






21. The linking is already done internally






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






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






24. Invalid or unexpected input that the program is not designed to process.






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






26. No man's land. Guard bytes before the after allocated heap memory.






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






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






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






30. About the interface to an object. Data contained within.






31. Freed heap memory.






32. Current line that is executing.






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






34. Removes files from the repository.






35. Downloads your changes and then merges.






36. The default nickname for the remote repository.






37. Fix any problems and then repeat the process.






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






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






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






41. Current view/ previous line.






42. A function that can load a library






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






44. Set of all pending changes.






45. The process of deciding which function definition to link during run-time.






46. Input






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






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






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






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