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. Are what function classes should include.






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






3. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






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






5. Freed heap memory.






6. Ignores files when pushing.






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






8. When GIT cannot merge your data.






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






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






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






12. Removes files from the repository.






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






14. Uploads all changes staged in the index list into the repository database.






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






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






17. Functionality Tests.






18. Adds files to the repository.






19. 2 Eyes + 2 Minds = AWESOME!






20. A measure of logical dependency.






21. Helps to eliminate unnecessary "include chaining."






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






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






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






25. Current line that is executing.






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






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






28. Current view/ previous line.






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






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






31. NULL memory.






32. Create a test and then create a function.






33. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






34. Set of all pending changes.






35. Formatted code standards.






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






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






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






39. Plan out your code.






40. Will execute all code paths and boundary conditions.






41. Breaks encapsulation boundaries.






42. The linking is already done internally






43. Try to find the flaws in your code.






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






45. Classes build off of each other.






46. Puts all headers into a master header.






47. A collection of memory addresses for all virtual functions in an objects class hierarchy.






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






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






50. Downloads your changes and then merges.