SysInt 2014 » A Multi-Disciplinary Modeling Technique for Requirements Management in Mechatronic...

Post on 06-Jul-2015

510 views 0 download

Tags:

description

Presentation @ SysInt 2014 in Bremen

Transcript of SysInt 2014 » A Multi-Disciplinary Modeling Technique for Requirements Management in Mechatronic...

A Multi-Disciplinary Modeling Techniquefor Requirements Management in Mechatronic Systems Engineering

Georg Hackenberg, Christoph Richter and Michael Zäh

1. Introduction

2. Modeling Technique

3. Case Study

4. Discussion and

Introduction » Motivation

02.07.2014 2nd International Conference on System-integrated Intelligence 3

Gau

sem

eier

‘13

Rei

nh

art

et a

l.

‘07

But: Development processes still are dominated by mechanical

engineering

Sequential development with discipline-specific engineering processes

Insufficient understanding of dependencies and lack of coordination

Integration problems and high change management and coordination

effort

Introduction » State of the Art (1/2)

02.07.2014 2nd International Conference on System-integrated Intelligence 4

Software engineering [9, 10]

Mechatronic systems engineering

[6]

• Simplifies collaboration [11]

• Function orientation [13]

• SysML and V-Modell [4, 12]

• Föderal information architecture

[15]

• AQUIMO formal modeling [16]

• Views and abstraction layers [17,

18]

• Modularization [19]

Software engineering

• Management activities [21]

• Requirements documentation [22]

• Iterative process [23]

Mechatronic systems engineering

• Interface to systems engineering

[24]

• Three-phase procedure [20]

• Requirements analysis [25]

• Workflow [26, 27]

Model-Based Development Requirements Management

Introduction » State of the Art (2/2)

02.07.2014 2nd International Conference on System-integrated Intelligence 5

But the approaches do not focus …

formal and integrated requirements and solution modeling along with

stepwise refinement and automated verification,

which would allow one to …

stay solution independent as long as possible and

enable frequent (because automated) solution examination.

1. Introduction

2. Modeling Technique

3. Case Study

4. Discussion and Outlook

Modeling Technique » Concepts and Terms

02.07.2014 2nd International Conference on System-integrated Intelligence 7

Spatio-temporal modeling technique [5,28,29]

Modeling Technique » Workflows

02.07.2014 2nd International Conference on System-integrated Intelligence 8

Requirements modeling

Stepwiserefinement

Solution modeling

Automatedverification

1. Introduction

2. Modeling Technique

3. Case Study

4. Discussion and Outlook

Case Study » Conception (1/4)

02.07.2014 2nd International Conference on System-integrated Intelligence 10

1. In

terf

ace

2. S

cen

ario

Case Study » Conception (2/4)

02.07.2014 2nd International Conference on System-integrated Intelligence 11

3. F

un

ctio

n

4.

Dec

om

po

siti

on

Case Study » Conception (3/4)

02.07.2014 2nd International Conference on System-integrated Intelligence 12

4.1.

Inte

rfac

e

4.2.

Ela

bo

rati

on

Case Study » Conception (4/4)

02.07.2014 2nd International Conference on System-integrated Intelligence 13

4.3.

Ela

bo

rati

on

5. E

lab

ora

tio

n

Case Study » Simulation

02.07.2014 2nd International Conference on System-integrated Intelligence 14

Maven Build Management

State and Data Flow Framework

JBullet Framework

• Ports as collision geometries

• Parts as rigid bodies

• Joints as constraints

JUnit Framework

• Model as test suite

• Scenarios as test cases

• Constraints as assertions

Weak Motor

Strong Motor

1. Introduction

2. Modeling Technique

3. Case Study

4. Discussion and Outlook

Discussion and Outlook

02.07.2014 2nd International Conference on System-integrated Intelligence 16

Academic case study with limited

requirements complexity only

Binary solution assessment according

to constraints only

Develop industrial case study and

evaluate acceptance in practice

Integrate numeric quality concept and

adapt test execution reports

Discussion (Cons)

Outlook

Cross-discipline requirements model

enables early collaboration

Stepwise refinement enables successive

solution space restriction

Decomposition enables derivation of

mechatronic subproblems

Solution independent requirements model

enables solution plugin and

comparison

Standard software test framework

enables advanced tool integration

Discussion (Pros)

A Multi-Disciplinary Modeling Techniquefor Requirements Management in Mechatronic Systems Engineering

Georg Hackenberg, Christoph Richter and Michael Zäh