Model-Based Requirements Engineering with Auto-RAID

1
Model-Based Requirements Engineering with
Auto-RAID

• Bernhard Schätz
• Technische Universität München
• Institut für Informatik
• 08.03.2005 - ReConf 2005

2
Best 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

3
Describing Embedded Systems
4
Quality Criteria

• Quality criteria for system specifications (IEEE
  830-1998)

• Changeability
• Traceability
• Comprehensibility

• Consistency
• Completeness
• Unambiguity

5
Modeling Requirements
Weak-Structure Model Built-In Flexibility
Facilitates comprehensability, changeability -
Enables ambiguities, inconsistencies - Restricts
completeness, feasibility
6
Modeling Designs
Structured Model Built-In Preciseness
Restricts ambiguities, inconsistencies Supports
completeness, feasibility - Restricts
comprehensability, changeability
7
Structured Information
Precision
Flexibility
Flexibility
Precision
Analysis
Design
8
Quality Assurance Mechanisms
Precision
Flexibility
Analysis
Design
9
Improving Quality and Efficiency
Precision
Flexibility
View Construction
Classification
Refinement
Analysis
Analysis
Design
10
User-Support

• Efficient and quality-oriented transition from
  analysis to design
• Based on activities as performed in a review
• Focusing on constructive activities
• Supporting each activity by tool-interaction

Requires a deep integration of models for
analysis and design
11
Weak Integration Unstructured Requirements

• Model Elements
• Generic Requirements
• Domain-Specific Design
• Weak Integration
• Hierarchic Requirement Model
• View-Based Design Model
• Generic Links
• Generic Requirement Structure
• Description
• Title, ID
• Rationale
• Priority, Status

12
Weak Integration Homogeneous Links
13
Weak Integration Identify Requirements
14
Weak Integration Refine Requirements
15
Weak Integration Link Models
16
Weak Integration Support

• Support mechanisms
• Management Import, Refinement, Linking
• Analysis Coverage/Completeness (Refinement,
  Linking)
• Synthesis Documentation

17
Deep Integration Embedding Specific Requirements

• Model Elements
• Domain-specific requirements
• Domain-specific views
• Deep Integration
• View-based requirements
• View-based design model
• Homogeneous requirements/design model
• Requirements as an additional view
• Requirements as structured text
• Requirements as domain-specific structure
• Requirements as collection of model views

18
Deep Integration Structuring Information
Quelle IEEE Standard 1998-830
19
Deep Integration Embedded Requirements
20
Deep Integration Classify Constraint
21
Deep Integration Motivate Models
22
Deep Integration Construct Model Views
23
Deep Integration Support

• Support Mechanisms
• Management Review-based View Generation,
  Multiple Views
• Analysis Consistency/Completeness (Refinement,
  Motivation)
• Synthesis View Generation (Motivation,
  Construction)

24
User-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

25
AutoRAID Partners and Contact
Contact www4.in.tum.de/autoraid