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. Ignores files when pushing.






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






3. Freed heap memory.






4. Downloads without merging.






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






6. Classes build off of each other.






7. One of the linking methods (pragma comment)






8. Formatted code standards.






9. Current view/ previous line.






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






11. Fix any problems and then repeat the process.






12. When GIT cannot merge your data.






13. Create a test and then create a function.






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






15. Code whatever it is you need to code.






16. Current line that is executing.






17. Do not optimize until the very end.






18. Removes files from the repository.






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






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






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






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






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






24. A function that can load a library






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






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






27. Makes a copy of your repository.






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






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






30. Views all previous changes.






31. Helps to eliminate unnecessary "include chaining."






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






33. Provide a unified interface to a set of interfaces in a subsystem. Defines a higher-level interface that makes the subsystem easier to use.






34. Keeps a team using a similar naming convention for things.






35. Variable doesn't exist.






36. Try to find the flaws in your code.






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






38. Functionality Tests.






39. Adds files to the repository.






40. Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.






41. The linking is already done internally






42. When a conflict is fixed.






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






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






45. Static in C++. Can span all instances of a class.






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






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






48. Connection between a local brand and a remote branch.






49. Initialized heap memory.






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