cesar - cost-efficient methods and processes for...

23
CESAR - Cost-efficient methods and processes for safety relevant embedded systems Roland Mader, AVL List GmbH [email protected]

Upload: vuongcong

Post on 26-Jun-2018

212 views

Category:

Documents


0 download

TRANSCRIPT

CESAR - Cost-efficient methods and processes

for safety relevant embedded systems

Roland Mader, AVL List GmbH

[email protected]

2

Roland Mader, AVL List GmbH

2010-10-05

Outline

� CESAR (Cost-efficient methods and processes for safety relevant embedded systems) Project

� European project

� 55 partners

� 4 domains

� Reference technology platform (RTP)

� Tailoring

� Integration

� Tool adapters

� Metamodels

� Prototypical instance of the RTP

� Papyrus for EAST-ADL2, AVL InMotion

3

Roland Mader, AVL List GmbH

2010-10-05

PAST TODAY FUTURE ?

Motivation – E.g. Automotive

� Vehicles a decade ago

� A few embedded systems per vehicle

� Vehicles nowadays

� Up to a few hundred of computing devices

per vehicle

� Multiple networks per vehicle

� Advantage

� Safety-critical embedded systems have

been key innovation drivers� E.g. by-wire systems

� Disadvantage

� Enormous complexity is challenging

industry (automotive, aerospace, rail,

automation)

� Increasing costs

� Affected product quality � safety-critical

Source: AVL List

4

Roland Mader, AVL List GmbH

2010-10-05

NacellesNacelles and components

(thrust reversers,…)

Engine equipment and parts• Integrated engine control systems

• Power transmissions

• Engine modules and components

• Composite engine parts

Engines• CFM56 family (50/50 with GE)

• SAM146 engine for the Russian

Regional Jet (50/50 with NPO Saturn)

• Participation in programs: CF6, GE90,

GE90-115B, GP7000, PW4000, AS900, CF34

Landing & braking systems• Landing gear for all types of aircraft

• Braking/landing control systems

• Wheels and carbon brakes

• Control systems and hydraulics

• Maintenance, repair and overhaul

Aircraft equipment• Network server systems

• Back-up flight control

• Secure data link

• Cockpit control systems

• Electrical wiring systems

• Aircraft condition monitoring systems

Engine services• Maintenance, repair and overhaul

• Engine testing and test equipment

• Composite aerostructures

• Auxiliary power units

• Hydraulic systems

• Sensors and actuators

• Ventilation/filtration

• Inertial references

Motivation – E.g. Aerospace

5

Roland Mader, AVL List GmbH

2010-10-05

The CESAR Project

Objectives

� Improvement of processes and

methods for safety-critical embedded

systems development

� Development of the Reference

Technology Platform (RTP) for safety-

critical embedded systems development

� Motivate technology providers and

SMEs to contribute to the RTP

� Bring innovations in two most

improvable engineering disciplines

� Requirements engineering

� Component-based engineering

Key Data

� EU Project (Artemis JU)

� 55 Partners from 4 domains

(Automotive, Aerospace, Rail &

Automation)

� Total Budget: 58 Mill. €

� 3 Years (03.2009 – 02.2012)

� Project Coordinator:

AVL List GmbH

Parts of slide basing on CESAR General Presentation

6

Roland Mader, AVL List GmbH

2010-10-05

� Multidomain approach

� 3 Innovation Cycles

� Industrial needs

(requirements)

� Solutions provided by Industry and academics

� Implemented in RTP

� Evaluation and feedback

Project Strategy

7

Roland Mader, AVL List GmbH

2010-10-05

� 3 Innovation Subprojects

� SP1 – Reference Technology

Platform - RTP

� SP2 – Requirement-engineering

� SP3 – Component-based

development

� 3 User Subprojects

� SP5, SP6, SP7

� Domain dependent processes and

methodology

� Validation by industrial Pilot

Applications

� 2 Task ForcesTask Forces

Project Organization

8

Roland Mader, AVL List GmbH

2010-10-05

The RTP Vision

Embedded Software Development Process

Safety StandardsDomain Requirements Tools

Data Formats

Meta ModelsData Standards

RepositoryRepositoryManagement

Console

Management Console

Application Domains

Specific Tool Chain (Instance of RTP)

Generic Model Based Integration Platform

for safety-critical embedded systems

development

RTP = Reference Technology

Platform

Parts of pictures from A.Keis/EADS

Configuration Tailoring

SPEM

Exemplary Tools

9

Roland Mader, AVL List GmbH

2010-10-05

DB DB

� Service Oriented Architecture (SOA)

� Tool-Adapters and internal Services realized as Web-Services, connected via model-aware Middleware, called ModelBus

� Integration Platform has model-based core data model, builds up upon abstract models of integrated tools, processes, standards

� Model-Repository, services for e.g. model compare, transformation, check

CESAR Tool Integration Concept

Provide an Integration Platform for the exchange of model based data

Application

GUI

Application

GUI

DB

Application

GUI

ModelBus

Model based Core Data Model of Integration Platform

Process Engine

Model Check Service

Process Management

Rules GUI

Transformation Service

Model Mapping GUI

RepositoryRepository

Tool 1 Tool 2 Tool 3

ToolAdapter

ToolAdapter

Platform integrated Services (Examples)

10

Roland Mader, AVL List GmbH

2010-10-05

CESAR Tool Adapter Concept

� Syntactic Transformation, translate data format

� Provide exchange of XML model fragments

Speak the same language

� Service Integration - Abstract Interface Level

� Connecting Tool-API or data file format to platform Interface (e.g. Java RPC) via HTTP/SOAP requests

Establish a communication channel

� Semantic Transformation - map elements with the same meaning (test cases, software architecture elements…)

� Manage links between different elements (e.g. requirements to software architecture blocks)

� Usually mapping of tool elements to meta-model elements provided by platform

� Supported by meta models building an meta model layer scheme

� Done by transformation services which are part of the platform

Speak about the same thingsRTP

Transformation Services

RTP Transformation

Services

11

Roland Mader, AVL List GmbH

2010-10-05

CESAR Meta Model Concept

Integration Platform

Model based Core Data Model of Integration Platform consists of several layers

Requirements Tool 1

Tool Adapter with syntactic and

semantic Transformation

Software Specification

Tool 1

ApplicationData Model

CESAR Common Meta ModelCESAR Common Meta Model

RQ Tool 1 Model

RQ Tool 1 Model

RQ Tool 2 Model

CESAR Requirements

Meta Model

Spec. Tool 1 Model

Spec. Tool 1 Model

Spec. Tool 2 Model

Software Architecture Meta Model

EAST-ADL Meta ModelEAST-ADL Meta Model

generic

specific

ApplicationData Model

Basing on picture from Ch. Hein/Fraunhofer

12

Roland Mader, AVL List GmbH

2010-10-05

Industrial Use Case showing the results achieved so far

� Specify requirements using EAST-ADL meta model

� Setup necessary V&V by defining test cases linked to requirements

� Parameterize simulation and carry out simulation runs

RQ

EngineerV&V

Manager

Test

Engineer

2 Tools

3 Roles

Eclipse based modeling tool

supporting UML2-based

languages (e.g. EAST-ADL2)

Simulation software with HIL

capabilities for maneuver-

and event-based testing

Open Source from www.papyrusuml.org

Benefits

AVL InMotion is powered by IPG CarMaker

PapyrusPapyrus InMotionInMotion

� Traces between requirements and test cases

� Multi-site, multi-user environment

Activities

13

Roland Mader, AVL List GmbH

2010-10-05

EAST-ADL2 Metamodel

� Semi-formal language

� Means to describe automotive embedded systems on different abstraction levels

� Covers various levels of abstraction

� Traceability, analysis and synthesis are supported

14

Roland Mader, AVL List GmbH

2010-10-05

EAST-ADL2 Example

15

Roland Mader, AVL List GmbH

2010-10-05

Papyrus

� Eclipse-based tool

� UML modeling

� EAST-ADL extensions available

� Dedicated palette

� Modeling of requirements

� Traces to test cases

� Modeling of test cases

� Validation planning

� Traces to requirements

� Target (InMotion)

16

Roland Mader, AVL List GmbH

2010-10-05

AVL InMotion

� Simulation tool

� Virtual test driving

� Maneuver based testing

� Vehicle simulation model

� Car, engine, electric motor,

battery, transmission,

differential, tires,

suspension, brake, clutch…

� Maneuver simulation model

� Driver, passenger, trailer,

obstacles, traffic signs,

multi lane roads, junctions,

other vehicles…

17

Roland Mader, AVL List GmbH

2010-10-05

AVL InMotion

� Optimization of fuel economy

� Driver influence

� Influence of adaptive cruise control

� Hardware in the loop (HiL)

� Electronics, Engine,

Powertrain, vehicle test

beds

� Contemporary industry tool

� Many reference customers

18

Roland Mader, AVL List GmbH

2010-10-05

InMotion Metamodel

� InMotion contains complex and

extendable simulation model

� Needs parameterization

� Parameterization

� Car, powertrain, tires, brakes…

� Driver, track, trailer

� Simulation results

� Signal traces as samples

recorded during simulation

time

� Allow for further processing

and analysis

19

Roland Mader, AVL List GmbH

2010-10-05

� Mapping from elements of EAST-ADL meta model to elements of InMotion meta model

� Necessary to facilitate transformations between Papyrus and InMotion

� Necessary to facilitate information exchange between Papyrus and InMotion

� High-level InMotion elements, EAST-ADL elements for V&V

EAST-ADL / InMotion Transformation

EAST-ADL InMotion

ConcreteVVProcedure + VVTarget InMotionTestCase

VLog + VVTarget SimulationResult

VStimuli + VVTarget GenericConfigurationParameterGroup

20

Roland Mader, AVL List GmbH

2010-10-05

Use Case

Workflow

1. Requirement is created (Papyrus EAST-ADL2) by

Requirements Engineer

2. EAST-ADL model is checked in (Papyrus EAST-ADL2)

3. Automated notification to V&V Manager because

requirements have been updated

4. V&V Manger checks out Requirement Model and

specifies System under Test and Test cases (Papyrus

EAST-ADL2)

5. V&V Manger checks in the refined Requirement Model

(with InMotion stereotype)

6. Automatic execution of Transformation EAST-ADL2 to

InMotion

7. Notification of Test Engineer

8. Test Engineer checks out transformed initial test cases

9. Test Engineer specifies test data (InMotion)

10.Test Engineer executes Test-Cases (InMotion)

11.Results are checked into the repository

12.Notification of Requirements Engineer, V&V Manager

InMotion

Initial Test

case

Initial Test

case

RQRQ

Papyrus

ModelBusModelBus

RQ +

Test case

RQ +

Test case

Papyrus

EAST-ADL2 -> InMotion

EAST-ADL2 -> InMotion

Test dataTest data

Execute testExecute test

RQ Engineer

V&V Manager

Test Engineer

= role in project

RepositoryRepository

21

Roland Mader, AVL List GmbH

2010-10-05

Use Case

Live RTP Prototype Demonstration

22

Roland Mader, AVL List GmbH

2010-10-05

Summary

� CESAR is an European Consortium of 55 partners over 4

domains

� Aim: provide cost-efficient processes and methods for the

development of safety relevant embedded systems

� Support model based embedded software development

by model aware integration concept

� Prototype concept for improved traceability between

models, requirements and test cases

� Working towards a Interoperability Standard for model

based integration

23

Roland Mader, AVL List GmbH

2010-10-05

Contact

Roland MaderAVL List [email protected]

Thank you for your attention!

www.cesarproject.eu

CESAR project partners