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. Put this before a function name in a dll - and the function name will avoid name mangling






2. Link multiple projects together






3. A measure of logical dependency.






4. Classes build off of each other.






5. Removes files from the repository.






6. Current line that is executing.






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






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






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






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






11. Simply a value.






12. Breaks encapsulation boundaries.






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






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






15. Create a test and then create a function.






16. Puts all headers into a master header.






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






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






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






20. Symbols that can not be accessed by code in other units have __________. These symbols are usually static non-member functions/variables defined within.c/.cpp or defined in an anonymous namespace.






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






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






23. Use only through the interface of the object.






24. Uploads changes to your current branch.






25. Code generation in a lib






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






27. Initialized stack memory.






28. The default nickname for the remote repository.






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






30. Helps to eliminate unnecessary "include chaining."






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






32. Adds files to the repository.






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






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






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






36. Makes a copy of your repository.






37. Function doesn't exist.






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






39. Variable doesn't exist.






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






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






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






43. When GIT cannot merge your data.






44. Do not optimize until the very end.






45. Freed heap memory.






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






47. Are what function classes should include.






48. Quick program.






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






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