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. A type of library that is used by the code






2. What is part of the current scope.






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






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






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






6. Plan out your code.






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






8. Puts all headers into a master header.






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






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






11. Input






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






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






14. A function that can load a library






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






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






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






18. Freed heap memory.






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






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






21. Helps to eliminate unnecessary "include chaining."






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






23. The default nickname for the remote repository.






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






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






26. Try to find the flaws in your code.






27. Fix any problems and then repeat the process.






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






29. When GIT cannot merge your data.






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






31. A collection of memory addresses for all virtual functions in an objects class hierarchy.






32. A measure of logical dependency.






33. Inheritance between object.






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






35. Code whatever it is you need to code.






36. Initialized stack memory.






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






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






39. Link multiple projects together






40. Figure out what is feasible. Decide whether to use API's or to write from scratch.






41. When a conflict is fixed.






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






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






44. Current view/ previous line.






45. A pointer or reference. One object needs to know about the other object to work.






46. Adds files to the repository.






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






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






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






50. NULL memory.