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 exporting a dll - the names of the functions are changed. This is knwon as ____________.






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






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






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






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






6. Puts all headers into a master header.






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






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






9. Create a test and then create a function.






10. Simply a value.






11. Formatted code standards.






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






13. Removes files from the repository.






14. Stops when memory changes.






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






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






17. Classes build off of each other.






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






19. Undo changes made since your last commit.






20. Code whatever it is you need to code.






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






22. No more than 40 hours to stop burnouts.






23. Variable doesn't exist.






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






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






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






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






28. Are what function classes should include.






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






30. Current line that is executing.






31. 2 Eyes + 2 Minds = AWESOME!






32. Functionality Tests.






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






34. Portioning your changes to commit by inserting them into the index.






35. Quick program.






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






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






38. A measure of logical dependency.






39. Do not optimize until the very end.






40. Views all previous changes.






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






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






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






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






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






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






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






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






49. Creates a copy of your current branch into a remote branch.






50. Default branch within your repository.