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. Initialized heap memory.






2. When a class is defined within another class.






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






4. NULL memory.






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






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






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






8. Ask questions and obtain the details and requirements given.






9. Function doesn't exist.






10. Uploads changes to your current branch.






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






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






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






14. Try to find the flaws in your code.






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






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






17. Bookmark of a revised set with a title. For easy checkouts.






18. Set of all pending changes.






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






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






21. Concept based on limiting the scope of modules to provide better structures.






22. Classes build off of each other.






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






24. Default branch within your repository.






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






26. Always do the simplest design that could possibly work.






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






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






29. Whats displayed to the screen






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






31. Create a test and then create a function.






32. CONSTANT






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






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






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






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






37. No more than 40 hours to stop burnouts.






38. Variable doesn't exist.






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






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






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






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






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






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






45. When doing a - precise task.






46. STOP!!






47. Puts all headers into a master header.






48. Fix any problems and then repeat the process.






49. A measure of logical dependency.






50. Formatted code standards.