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. Undo changes made since your last commit.






2. A measure of logical dependency.






3. Variable doesn't exist.






4. Downloads without merging.






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






6. Plan out your code.






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






8. Whats displayed to the screen






9. A function that can load a library






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






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






12. Create a test and then create a function.






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






14. Stops when memory changes.






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






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






17. Current line that is executing.






18. Inheritance between object.






19. Classes build off of each other.






20. When GIT cannot merge your data.






21. Linking to dynamic libraries is usually handled by linking to an ____________.






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






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






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






25. The linking is already done internally






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






27. Developers should be integrated and releasing code into the code repository every few hours.






28. Fix any problems and then repeat the process.






29. Downloads your changes and then merges.






30. Uploads changes to your current branch.






31. Helps to eliminate unnecessary "include chaining."






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






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






34. Makes a copy of your repository.






35. Code generation in a lib






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






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






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






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






40. What is part of the current scope.






41. Try to find the flaws in your code.






42. Puts all headers into a master header.






43. Ignores files when pushing.






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






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






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






47. Set of all pending changes.






48. Quick program.






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






50. Will execute all code paths and boundary conditions.