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. Takes information in the index and pushes it onto the stack.






2. Downloads without merging.






3. When a class is defined within another class.






4. Views all previous changes.






5. Freed heap memory.






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






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






8. NULL memory.






9. Puts all headers into a master header.






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






11. A set of creation and initialization steps useful for a set of different related tests.






12. Plan out your code.






13. No more than 40 hours to stop burnouts.






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






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






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






17. Use only through the interface of the object.






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






19. One of the linking methods (pragma comment)






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






21. Removes files from the repository.






22. 2 Eyes + 2 Minds = AWESOME!






23. CONSTANT






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






25. Set of all pending changes.






26. Ignores files when pushing.






27. Default branch within your repository.






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






29. The linking is already done internally






30. A measure of logical dependency.






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






32. A function that can load a library






33. Create a test and then create a function.






34. Quick program.






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






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






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






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






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






40. Helps to eliminate unnecessary "include chaining."






41. Downloads your changes and then merges.






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






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






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






45. When GIT cannot merge your data.






46. When a conflict is fixed.






47. Functionality Tests.






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






49. Function doesn't exist.






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