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. Variable doesn't exist.






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






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






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






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






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






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






8. Function doesn't exist.






9. Ignores files when pushing.






10. A set of creation and initialization steps useful for a set of different related tests.






11. Meetings at the beginning of each iteration to produce a plan of programming tasks.






12. Code generation in a lib






13. Initialized stack memory.






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






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






16. Use only through the interface of the object.






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






18. What is part of the current scope.






19. The default nickname for the remote repository.






20. When GIT cannot merge your data.






21. Will execute all code paths and boundary conditions.






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






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






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






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






26. Views all previous changes.






27. Puts all headers into a master header.






28. Undo changes made since your last commit.






29. When a conflict is fixed.






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






31. Makes a copy of your repository.






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






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






34. Link multiple projects together






35. A measure of logical dependency.






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






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






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






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






40. Application






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






42. Whats displayed to the screen






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






44. CONSTANT






45. 2 Eyes + 2 Minds = AWESOME!






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






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






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






49. Breaks encapsulation boundaries.






50. One of the linking methods (pragma comment)