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. When doing a - precise task.






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






3. Ignores files when pushing.






4. Inheritance between object.






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






6. Input






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






8. 2 Eyes + 2 Minds = AWESOME!






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






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






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






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






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






14. Create a test and then create a function.






15. When GIT cannot merge your data.






16. Link multiple projects together






17. What is part of the current scope.






18. Code whatever it is you need to code.






19. Views all previous changes.






20. Meetings used to create a release plan - which will lay out the overall project.






21. Initialized stack memory.






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






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






24. When a class is defined within another class.






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






26. Removes files from the repository.






27. No more than 40 hours to stop burnouts.






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






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






30. Makes a copy of your repository.






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






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






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






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






35. Code generation in a lib






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






37. Try to find the flaws in your code.






38. Freed heap memory.






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






40. Use only through the interface of the object.






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






42. Do not optimize until the very end.






43. Having power over inheritance with the flexibility of composition.






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






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






46. NULL memory.






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






48. Uploads changes to your current branch.






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






50. Set of all pending changes.