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. Portioning your changes to commit by inserting them into the index.






2. Do not optimize until the very end.






3. Link multiple projects together






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






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






6. Current view/ previous line.






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






8. Initialized heap memory.






9. Function doesn't exist.






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






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






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






13. Functionality Tests.






14. When GIT cannot merge your data.






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






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






17. When a conflict is fixed.






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






19. Italicized in UML.






20. Fix any problems and then repeat the process.






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






22. A function that can load a library






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






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






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






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






27. Simply a value.






28. Are what function classes should include.






29. Use only through the interface of the object.






30. Stops when memory changes.






31. Whats displayed to the screen






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






33. Will execute all code paths and boundary conditions.






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






35. When a class is defined within another class.






36. Adds files to the repository.






37. Uploads changes to your current branch.






38. Set of all pending changes.






39. When doing a - precise task.






40. Ability to withstand change and what the effects are.






41. Ability to treat a class object as a function by overloading the () operator.






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






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






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






45. Code whatever it is you need to code.






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






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






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






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






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