Title: Model-Based Requirements Engineering with Auto-RAID
1Model-Based Requirements Engineering with
Auto-RAID
- Andreas Fleischmann, Eva Geisberger, Bernhard
Schätz - Technische Universität München
- Institut für Informatik
- 22.09.2005 - QUAM - Informatik 2005
2Best Practices
- Best Requirements Practices for System Software
- Formal Requirements
- Requirements Inspection
- Requirements Tracing
- Performance Requirements
- Quality/Reliability Requirements
- Requirements Notations
- Requirements Segmentation
- Function Point Measurement
- Defect tracking
Source Jones, 2000, Software Assessments,
Benchmarks and Best Practices
- Adding Detailed Structure to Requirements
3Modeling Requirements
Weak-Structure Model Built-In Flexibility
Facilitates comprehensability, changeability -
Enables ambiguities, inconsistencies - Restricts
completeness, feasibility
4Modeling Designs
Structured Model Built-In Preciseness
Restricts ambiguities, inconsistencies Supports
completeness, feasibility - Restricts
comprehensability, changeability
5Structured Information
Precision
Flexibility
Flexibility
Precision
Analysis
Design
6Weak Integration Unstructured Requirements
7Weak Integration Homogeneous Links
8Weak Integration Identify Requirements
9Weak Integration Refine Requirements
10Weak Integration Link Models
11Weak Integration Quality Assurance Mechanisms
12Deep Integration Structuring Information
Quelle IEEE Standard 1998-830
13Deep Integration Embedded Requirements
14Deep Integration Classify Constraint
15Deep Integration Motivate Models
16Deep Integration Construct Model Views
17Deep Integration Quality Assurance Mechanisms
Structuring Impact Analysis
Tracing
Impact Analysis
18User-Support
- Deep Integration of Analysis and Design
- Smooth Based on activities as already performed,
e.g., in a review - Quality-oriented Focusing on constructive,
enabling analytic activities - Efficient Supporting each activity by convenient
tool-interaction
19AutoRAID Partners and Contact
Contact www4.in.tum.de/autoraid