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. Takes information in the index and pushes it onto the stack.






2. Quick program.






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






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






5. Treating a derived class's data members like it's base class's.






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






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






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






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






10. Code generation in a lib






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






12. Freed heap memory.






13. When doing a - precise task.






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






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






16. Breaks encapsulation boundaries.






17. You have to tell it to link






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






19. Default branch within your repository.






20. Functionality Tests.






21. Uploads changes to your current branch.






22. STOP!!






23. Create a test and then create a function.






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






25. Formatted code standards.






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






27. Code whatever it is you need to code.






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






29. Makes a copy of your repository.






30. Puts all headers into a master header.






31. CONSTANT






32. A function that can load a library






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






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






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






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






37. When a conflict is fixed.






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






39. Fix any problems and then repeat the process.






40. Current line that is executing.






41. When a concrete class inherits from a pure interface.






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






43. Inheritance between object.






44. Adds files to the repository.






45. 2 Eyes + 2 Minds = AWESOME!






46. Input






47. Italicized in UML.






48. Helps to eliminate unnecessary "include chaining."






49. When exporting a dll - the names of the functions are changed. This is knwon as ____________.






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