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. Weak relationship between two classes. Almost always results in a #include.






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






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






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






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






6. Plan out your code.






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






8. STOP!!






9. Use this to find a memory address or signiture in a dll






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






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






12. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






13. Allows you to switch your working copy to another branch.






14. Puts all headers into a master header.






15. Removes files from the repository.






16. Code generation in a lib






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






18. Link multiple projects together






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






20. Ignores files when pushing.






21. No more than 40 hours to stop burnouts.






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






23. NULL memory.






24. CONSTANT






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






26. Ability to treat a class object as a function by overloading the () operator.






27. Inheritance between object.






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






29. Variable doesn't exist.






30. Undo changes made since your last commit.






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






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






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






34. Breaks encapsulation boundaries.






35. Input






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






37. Try to find the flaws in your 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. Quick program.






40. Initialized stack memory.






41. Fix any problems and then repeat the process.






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






43. Are what function classes should include.






44. When doing a - precise task.






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






46. Do not optimize until the very end.






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






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






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






50. Copies all changes from one branch into another branch.