SWE 3633 Lecture Notes - Lecture 15: Iterative And Incremental Development, Use Case, Product Design
17 Feb 2017
School
Department
Course
Professor
Document Summary
Use case models do not provide atomized requirements statements. Data and non-functional requirements are not explicit. Use case models sometimes serve as surrogates for requirements. Extracting requirements from use case models: helps designers understand their designs better, helps find errors and improve designs, produces a useful artifact for engineering design. Choose several use cases for implementation in an iteration; Do engineering design, code, test, and (perhaps) deploy; Evaluate the result for the next iteration; Start with a complete use case diagram. Choose use cases for each iteration according the following criteria: important to stakeholders, requires a core system function, requires the essentials of the system architecture, the implementation is technically challenging. A use cases description is structured text that specifies the details of a use case. Templates, processes, and heuristics guide use case description writers. Use case descriptions, though not requirements, can be a source for them. Use case diagrams and descriptions together form use case models.
