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. Treating a derived class's data members like it's base class's.






2. A function that can load a library






3. Set of all pending changes.






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






5. Views all previous changes.






6. When GIT cannot merge your data.






7. A measure of logical dependency.






8. Inheritance between object.






9. Uploads changes to your current branch.






10. Breaks encapsulation boundaries.






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






12. Undo changes made since your last commit.






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






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






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






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






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






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






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






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






21. Code whatever it is you need to code.






22. Stops when memory changes.






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






24. Classes build off of each other.






25. Fix any problems and then repeat the process.






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






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






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






29. Current line that is executing.






30. A reference. Has and delete dynamic memory. implies ownership (Association does not).






31. Do not optimize until the very end.






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






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






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






35. STOP!!






36. Removes files from the repository.






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






38. Current view/ previous line.






39. When a .cpp file is compiled - the header files are first included (recursively) by the pre-processor. This block of code is called a ______________.






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






41. Takes information in the index and pushes it onto the stack.






42. Try to find the flaws in your code.






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






44. Quick program.






45. Simply a value.






46. Code generation in a lib






47. Default branch within your repository.






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






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






50. Initialized stack memory.