4 Review Class Diagram: § Keep It Simple § Double-check isolated parts § Inheritance: a Child improves its parent. § Aggregation/Composition vs Association/Realization § Do not worry about Dependency § Remember * (multiplicity)
7 § Validation. It is about requirements. Are we building the right product? Does this software do what it needs to do? § Verification. It is about design. Are we building the product right? § Testing. Examination of the behavior of a program by executing it on sample data sets. Definition
8 a) May state what (reactions, behaviours, or services) the system should not do. b) services the system should provide, c) how the system should react to particular inputs, and d) how the system should behave in particular situations. Functional Requirement
9 § Independent – loosely coupled with one another § Negotiable – Stories are what and why , not how ( 99% ). § Valuable – for the customer! § Estimatable – Effort/Cost of design, build, and test. § Small (sized appropriately) § Testable – pass or fail INVEST in good requirements
Winter 2023 Copyright. These slides can only be used as study material for the class CSC308 at Cal Poly. They cannot be distributed or used for another purpose.