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. About the interface to an object. Data contained within.






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






3. Classes build off of each other.






4. Try to find the flaws in your code.






5. NULL memory.






6. When GIT cannot merge your data.






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






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






9. Plan out your code.






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






11. The linking is already done internally






12. Italicized in UML.






13. When a class is defined within another class.






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






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






16. You have to tell it to link






17. Input






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






19. Initialized stack memory.






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






21. Function doesn't exist.






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






23. Link multiple projects together






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






25. A measure of logical dependency.






26. Functionality Tests.






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






28. 2 Eyes + 2 Minds = AWESOME!






29. Removes files from the repository.






30. No more than 40 hours to stop burnouts.






31. Code whatever it is you need to code.






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






33. Downloads your changes and then merges.






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






35. Allows consumers to try a system earlier and give early feedback.






36. Do not optimize until the very end.






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






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






39. Freed heap memory.






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






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






42. Trying to access a location in memory that your computer cannot access.






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






44. Default branch within your repository.






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






46. Inheritance between object.






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






48. Whats displayed to the screen






49. Set of all pending changes.






50. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically