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. Uploads all changes staged in the index list into the repository database.






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






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






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






5. Adds files to the repository.






6. Initialized stack memory.






7. Whats displayed to the screen






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






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






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






11. Current view/ previous line.






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






13. No more than 40 hours to stop burnouts.






14. Simply a value.






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






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






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






18. Do not optimize until the very end.






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






20. Fix any problems and then repeat the process.






21. Italicized in UML.






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






23. Code whatever it is you need to code.






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






25. Variable doesn't exist.






26. Input






27. The linking is already done internally






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






29. Breaks encapsulation boundaries.






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






31. Default branch within your repository.






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






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






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






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






36. Puts all headers into a master header.






37. A measure of logical dependency.






38. Stops when memory changes.






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






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






41. Having power over inheritance with the flexibility of composition.






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






43. Plan out your code.






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






45. Application






46. What is part of the current scope.






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






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






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






50. One of the linking methods (pragma comment)