Software Engineering I - Chair for Applied Software Engineering

More documents

Recommendations

Info

Requirements Validation Requirements validation is a quality assurance step, usually performed after requirements elicitation or after analysis • Correctness: • The requirements represent the client’s view • Completeness: • All possible scenarios, in which the system can be used, are described • Consistency: • There are no requirements that contradict each other. © 2008 Bernd Bruegge Introduction into Software Engineering Summer 2008 52
Requirements Validation (2) • Clarity: • Requirements can only be interpreted in one way • Realism: • Requirements can be implemented and delivered • Traceability: • Each system behavior can be traced to a set of functional requirements • Problems with requirements validation: • Requirements change quickly during requirements elicitation • Inconsistencies are easily added with each change • Tool support is needed! © 2008 Bernd Bruegge Introduction into Software Engineering Summer 2008 53
Page 1 and 2: Software Engineering I: Software Te
Page 3 and 4: Software Lifecycle Definition • S
Page 5 and 6: Software Lifecycle Activities ...an
Page 11 and 12: What is the best Software Lifecycle
Page 13 and 14: What does the Customer say? © 2008
Page 15 and 16: Techniques to elicit Requirements
Page 17 and 18: More Definitions • Scenario: “A
Page 19 and 20: Scenario-based Design • Focuses o
Page 21 and 22: A Visionary Scenario (1954): The Ho
Page 23 and 24: How do we find scenarios? • Don
Page 25 and 26: Scenario example: Warehouse on Fire
Page 27 and 28: After the scenarios are formulated
Page 29 and 30: How to find Use Cases • Select a
Page 31 and 32: Use Case Example: ReportEmergency F
Page 33 and 34: Allocate a Resource (cont’d) •
Page 35 and 36: Requirements Elicitation: Difficult
Page 37 and 38: Defining the System Boundary is dif
Page 39 and 40: Example of an Ambiguous Specificati
Page 41 and 42: Requirements Process :problem state
Page 43 and 44: Types of Requirements • Functiona
Page 45 and 46: Types of Nonfunctional Requirements
Page 47 and 48: Types of Nonfunctional Requirements
Page 49 and 50: Some Quality Requirements Definitio
Page 51: What should not be in the Requireme
Page 55 and 56: Tools for Requirements Management (
Page 57 and 58: Prioritizing requirements • High
Page 59 and 60: Nonfunctional Requirements (Questio
Page 61 and 62: Nonfunctional Requirements (3) Syst
Page 63 and 64: Nonfunctional Requirements (5) Reso
Page 65 and 66: Exercise • Reverse engineer the r
Page 67 and 68: Exercise Solution • Available inf

Software Engineering I - Chair for Applied Software Engineering

Create successful ePaper yourself

Delete template?

Save as template?