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. Separating out a section of code into a reusable function or class.






2. CONSTANT






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






4. Uploads all changes staged in the index list into the repository database.






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






6. Breaks encapsulation boundaries.






7. Variable doesn't exist.






8. Ignores files when pushing.






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






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






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






12. Undo changes made since your last commit.






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






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






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






16. Initialized heap memory.






17. STOP!!






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






19. Inheritance between object.






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






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






22. Weak relationship between two classes. Almost always results in a #include.






23. Use only through the interface of the object.






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






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






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






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






28. When GIT cannot merge your data.






29. Italicized in UML.






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






31. Code whatever it is you need to code.






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






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






34. Puts all headers into a master header.






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






36. Views all previous changes.






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






38. Formatted code standards.






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






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






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






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






43. No more than 40 hours to stop burnouts.






44. Removes files from the repository.






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






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






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






48. When a conflict is fixed.






49. Whats displayed to the screen






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