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. Breaks encapsulation boundaries.






2. Current line that is executing.






3. 2 Eyes + 2 Minds = AWESOME!






4. Downloads your changes and then merges.






5. A reference. Has and delete dynamic memory. implies ownership (Association does not).






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






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






8. Default branch within your repository.






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






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






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






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






13. Application






14. When GIT cannot merge your data.






15. A measure of logical dependency.






16. Inheritance between object.






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






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






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






20. Encapsulates a request as an object - thereby letting you parameterize clients with different requests - queue or log requests - and support undoable operations.






21. Ignores files when pushing.






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






23. Variable doesn't exist.






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






25. Try to find the flaws in your code.






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






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






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






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






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






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






32. Helps to eliminate unnecessary "include chaining."






33. A function that can load a library






34. Use only through the interface of the object.






35. Fix any problems and then repeat the process.






36. The default nickname for the remote repository.






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






38. Formatted code standards.






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






40. Freed heap memory.






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






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






43. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






45. Always do the simplest design that could possibly work.






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






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






48. Functionality Tests.






49. What is part of the current scope.






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