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. Bookmark of a revised set with a title. For easy checkouts.






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






3. Variable doesn't exist.






4. When GIT cannot merge your data.






5. About the interface to an object. Data contained within.






6. Initialized stack memory.






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






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






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






10. Input






11. Puts all headers into a master header.






12. Code generation in a lib






13. Makes a copy of your repository.






14. Simply a value.






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






16. Define a one-to-many dependency between objects so that when one object changes state - all its dependents are notified and updated automatically






17. Compose objects into tree structures to represent part-whole hierarchies. Lets clients treat individual objects and compositions of objects uniformly.






18. When a conflict is fixed.






19. Function doesn't exist.






20. Are what function classes should include.






21. One of the linking methods (pragma comment)






22. A function that can load a library






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






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






25. Set of all pending changes.






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






27. Link multiple projects together






28. Uploads changes to your current branch.






29. Functionality Tests.






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






31. Try to find the flaws in your code.






32. Undo changes made since your last commit.






33. STOP!!






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






35. Formatted code standards.






36. Will execute all code paths and boundary conditions.






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






38. Default branch within your repository.






39. When we remove redundant or obsolete designs and replace them with a new.






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






41. A group of code. unnamed can only be accessed within that translation unit - name can be accessed anywhere






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






43. Initialized heap memory.






44. Code whatever it is you need to code.






45. You have to tell it to link






46. Portioning your changes to commit by inserting them into the index.






47. CONSTANT






48. Breaks encapsulation boundaries.






49. What is part of the current scope.






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