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. Use this to find a memory address or signiture in a dll






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






3. Formatted code standards.






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






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






6. Current view/ previous line.






7. Use only through the interface of the object.






8. Initialized stack memory.






9. Plan out your code.






10. No more than 40 hours to stop burnouts.






11. Adds files to the repository.






12. When doing a - precise task.






13. Simply a value.






14. Downloads without merging.






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






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






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






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






19. A function that can load a library






20. Undo changes made since your last commit.






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






22. Try to find the flaws in your code.






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






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






25. One of the linking methods (pragma comment)






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






27. Are what function classes should include.






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






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






30. Link multiple projects together






31. What is part of the current scope.






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






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. Cross training is an important consideration to try and prevent islands of knowledge - which can cause loss.






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






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






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






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






39. Variable doesn't exist.






40. Stand up meetings show who will be valuable and needed.






41. Code generation in a lib






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






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






44. Classes build off of each other.






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






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






47. Set of all pending changes.






48. Default branch within your repository.






49. The default nickname for the remote repository.






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