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. Ability to accept different types of parameters to bind to different implementations at run-time.






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






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






4. Put this before a function name in a dll - and the function name will avoid name mangling






5. Initialized stack memory.






6. Current view/ previous line.






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






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






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






10. Application






11. Whats displayed to the screen






12. What is part of the current scope.






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






14. Undo changes made since your last commit.






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






16. Views all previous changes.






17. You have to tell it to link






18. The default nickname for the remote repository.






19. When doing a - precise task.






20. Stand up meetings show who will be valuable and needed.






21. NULL memory.






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






23. Are what function classes should include.






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






25. Quick program.






26. Set of all pending changes.






27. Fix any problems and then repeat the process.






28. Taking code and moving it to a function that usually returns an object. They are always virtual functions.






29. Input






30. Downloads your changes and then merges.






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






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






33. Stops when memory changes.






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






35. Try to find the flaws in your code.






36. Italicized in UML.






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






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






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






40. Use only through the interface of the object.






41. When GIT cannot merge your data.






42. Create a test and then create a function.






43. 2 Eyes + 2 Minds = AWESOME!






44. Freed heap memory.






45. One of the linking methods (pragma comment)






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






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






48. Classes build off of each other.






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






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