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. Stand up meetings show who will be valuable and needed.






2. What is part of the current scope.






3. Create a test and then create a function.






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






5. A measure of logical dependency.






6. Function doesn't exist.






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






8. 2 Eyes + 2 Minds = AWESOME!






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






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






11. Adds files to the repository.






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






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






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






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






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






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






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






19. When doing a - precise task.






20. Link multiple projects together






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






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






23. Undo changes made since your last commit.






24. STOP!!






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






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






27. Uploads changes to your current branch.






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






29. No more than 40 hours to stop burnouts.






30. Use only through the interface of the object.






31. The linking is already done internally






32. Input






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. Invalid or unexpected input that the program is not designed to process.






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






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






37. Code generation in a lib






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






39. Initialized stack memory.






40. Default branch within your repository.






41. Simply a value.






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






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






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






45. One of the linking methods (pragma comment)






46. Try to find the flaws in your code.






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






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






49. Will execute all code paths and boundary conditions.






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