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. Ensure a class only has one instance - and provide a global point of access to it






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






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






4. One of the linking methods (pragma comment)






5. Functionality Tests.






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






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






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






9. Simply a value.






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






11. Breaks encapsulation boundaries.






12. Uploads changes to your current branch.






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






14. Downloads your changes and then merges.






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






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






17. Current view/ previous line.






18. Stops when memory changes.






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






20. Link multiple projects together






21. Try to find the flaws in your code.






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






23. Formatted code standards.






24. Helps to eliminate unnecessary "include chaining."






25. Code whatever it is you need to code.






26. Fix any problems and then repeat the process.






27. Function doesn't exist.






28. Freed heap memory.






29. Undo changes made since your last commit.






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






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






32. Reusing existing functionality by defining a relationship between two classes : Inheritance or containment.






33. The linking is already done internally






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






35. Plan out your code.






36. Italicized in UML.






37. Classes build off of each other.






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






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






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






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






42. Removes files from the repository.






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






44. STOP!!






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






46. Ignores files when pushing.






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






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






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






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