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. Fix any problems and then repeat the process.






3. Create a test and then create a function.






4. When doing a - precise task.






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






6. Downloads your changes and then merges.






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






8. Freed heap memory.






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






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






11. Input






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






13. Undo changes made since your last commit.






14. What is part of the current scope.






15. (Door-----Spell) BI_DIRECTIONAL because both classes can reference each other. (Door--->Spell) DIRECTIONAL because only the door knows and can reference Spell.






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






17. Stops when memory changes.






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






19. Quick program.






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






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






22. Adds files to the repository.






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






24. Formatted code standards.






25. Link multiple projects together






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






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






28. Whats displayed to the screen






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






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






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






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






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






34. Makes a copy of your repository.






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






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






37. STOP!!






38. Code whatever it is you need to code.






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






40. No more than 40 hours to stop burnouts.






41. When GIT cannot merge your data.






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






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






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






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






46. Functionality Tests.






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






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






49. Function doesn't exist.






50. Simply a value.