model-based requirements engineering with autoraid/autofocus€¦ · model-based requirements...

Model-based Requirements Engineering with AutoRAID/AutoFocus

Dr. Eva Geisberger

Lehrstuhl für Software & Systems EngineeringInstitut für Informatik

Technische Universität München

GI AK TraceabilityDarmstadt, 7. Dezember 2007

Model-based Requirements Analysis with AutoRAID

AK Traceability – 07.12.2007Dr. Eva Geisberger 2

Iterative steps of REQ analysis and system construction

Dr.

Eva

Gei

sber

ger

Basic RE Cycle in AutoRAID



Integrated with system modeling tool AutoFocus

Mathematically well-founded system specification and development tool• System concept with functional system views and graph. description techniques• Test case & code generation, simulation and verification of components



An Example: Instrument Cluster for vehicles

An Example: Instrument Cluster for vehicles

0

10

20

3040 50

6070

x 100 U/ min

0

10

20

3040

5060

7080

90100

110120

160

miles/ h130

140

150

Speedometer Display

Indicator Lights Rev Meter



AutoRAID user interface



Identifying and capturing of requirements (1)

Requirement

ApplicationRequirementBusinessRequirement

* *

isJustifiedBy +SuperApplicationRequirement

*

+SubApplicationRequirement

*

Requirement



Identifying and capturing of requirements (2)



Refining and goal-oriented structuring of requirements (1)

Requirement


* *


*


*

Requirement



Requirement


* *


*


*

Requirement




Classifying and modeling of requirements



Classifying by functional system views



Constructing and modeling: Motivate



Constructing and modeling: Associate



Major method: UseCase and scenario analysis



Anayzing and modeling scenario steps by observations (1)

Knorr Bremse Workshop, 11. April 2007Eva Geisberger



Anayzing and modeling scenario steps by observations (2)



Analyzing and modeling requirements by system views



System model relations in AutoRAID/AutoFocus



IsJustifiedBySubApplicationReq.

SuperApplicationReq.

SubBusinessReq.

SuperBusinessReq.

BusinessRequirement

ApplicationRequirement

Requirement

UseCase

Scenario

SequenceStep

CommunicationObservation

ModeObservation

StateObservation

BusinessGoal

Feature

QualityGoal

ArchitecturalConstraint

ModalConstraint

DataConstraint

Component

State

DataType

Channel

Transition

Comm.Event

AutoRAID Data Model

Association

Mot

ivat

ion

Obs

erva

tion

Constraint

System ModelingRequirements Analysis & Definition





SubBusinessReq.

SuperBusinessReq.

BusinessRequirement


Requirement

UseCase

Scenario

SequenceStep


ModeObservation

StateObservation

BusinessGoal

Feature

QualityGoal


ModalConstraint

DataConstraint

Component

State

DataType

Channel

Transition

Comm.Event

AutoRAID Data Model

Association

Mot

ivat

ion

Obs

erva

tion

Constraint


Business Needs Requirements Specification System Specification



RE Artifact Model – model of work products in RE



Methodical structure of RE Artifact Model

Dr.

Eva

Gei

sber

ger

Refinement Relation

Verhaltensmodell

Logische Systemarchitektur

Funktions-hierarchie

SzenarienmodellProzessmodell

Interaktionsmuster

UmgebungsmodellLogische

Systemgrenzen

Behavior Model

System Service

Architecture

&

Hierachy

Process Model

Scenario Model

Interaction Model

Environment Model

Logical System

Boundaries

Functional Model Relations

Functional Requirements

Design Conditions/Decisions

Design Relation

Model relations Consistency constraints: Verification & Validation





SubBusinessReq.

SuperBusinessReq.

BusinessRequirement


Requirement

UseCase

Scenario

SequenceStep


ModeObservation

StateObservation

BusinessGoal

QualityGoal

Feature


ModalConstraint

DataConstraint

Component

State

DataType

Channel

Transition

Comm.Event

Obs

erva

tion

Association

Mot

ivat

ion


AutoRAID Data Model

Refinement:





SubBusinessReq.

SuperBusinessReq.

BusinessRequirement


Requirement

UseCase

Scenario

SequenceStep


ModeObservation

StateObservation

BusinessGoal

QualityGoal

Feature


ModalConstraint

DataConstraint

Component

State

DataType

Channel

Transition

Comm.Event

Obs

erva

tion

Association

Mot

ivat

ion


AutoRAID Data Model

Design decision:





SubBusinessReq.

SuperBusinessReq.

BusinessRequirement


Requirement

UseCase

Scenario

SequenceStep


ModeObservation

StateObservation

BusinessGoal

QualityGoal

Feature


ModalConstraint

DataConstraint

Component

State

DataType

Channel

Transition

Comm.Event

Obs

erva

tion

Association

Mot

ivat

ion


AutoRAID Data Model

Model relation:



System model relations in AutoRAID/AutoFocus



Summary and outlook

Model-based RE with AutoRAID/AutoFocus:• Common core model of RE work products: RE Artifact Model • Goal-oriented refinement and consolidation of requirements• Basic functional system concept and views

– Model relations define construction and consistency rules– Guide analysis, development and completion of requirements

• Integrated requirements analysis and functional system design• Interdisciplinary communication and appropriate decison making• Supports measurable quality and progress control

Requirements Engineering Reference Model (REM):• Testing and advancing a comprehensive RE approach

– REM: Common core model of RE work products– Artifact-oriented process definition– tailoring concept and tool support



Literature and links

AutoRAID/AutoFocus:

Modellbasierte Anforderungsanalyse mit AutoRAID.Eva Geisberger, Bernhard SchätzGI - Informatik Forschung und Entwicklung, Bd. 3, Springer Verlag, 2007.

AutoFocus 2 – Das Bilderbuch. Doris WildTechnische Universität München, Technical Report: TUM-I0610, May 2006.

Homepage AutoFocus2: http://www4.in.tum.de/~af2/

Requirements Engineering Referenzmodell (REM):

Ein Requirements Engineering Referenzmodell.Klaus Beetz, Manfred Broy, Eva Geisberger, Jürgen Kazmeier, Arnold RudorferGI Informatik Spektrum, Bd. 3, Springer Verlag, 2007.

Requirements Engineering Reference Model (REM).Eva Geisberger, Manfred Broy, Brian Berenbach, Jürgen Kazmeier, Daniel Paulish, Arnold RudorferTechnische Universität München, Technical Report TUM-I0618, 2006.



back up



AutoFocus2• integrierter, erweiterbarer CASE Prototyp• Kontinuierliche Entwicklung seit 1995

Modellierung Analyse, Test & QSSimulation

ModelChecking

Control Systems

Requirements

Process-support

Constraints CodeGen

TestGen



REM Artifact Model – Business Needs artifacts

Business Needs ArtifactsBusiness Needs

Business ObjectivesCustomer REQ

System Vision

General ConditionsScope & Limitations

ROIBusiness Risk

Sys. Success Factors

System SuccessFactors

Key Features/ Requirements

Priority of Requirements



REM Artifact Model – Requirements Specification artifacts

Requirements Specification ArtifactsRequirements Specification

Functional AnalysisModel

Domain Model

Quality REQAssumptions &Dependencies

Design Constraints

Acceptance Criteria

Functional Analysis Model

Product Functions

Use Modes

SystemInteraction

Application Scenarios

User Classes &Characteristics

Functions/Services

UserInterface

ReleaseStrategy

NFR AnalysisModel

Quality Requirements

Assumptions &Dependencies

DesignConstraints

Performance

Safety

Further IEEE Quality REQ

Security

Modifiability

Standards

GlobalRequirements

Business Rules

GeneralConditions

HW Design Constraints

SW Design Constraints



REM Product Model – System Specification artifacts

System Specification ArtifactsSystem Specification

FunctionalSystem Concept

User Documentation

System Test Criteria

Design Constraints

Ext

erna

lInt

erfa

ces

/ UI

Design Constraints

Hardware Design Constraints

Software Design Constraints

Electrics

Mechanics Architecture Constraints

Deployment Constraints

Coding Standards

model-based requirements engineering with autoraid/autofocus€¦ · model-based requirements...

Documents