A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution...

20
Thales Communications MyCCM A Component Based Approach for Real-Time & Critical Systems Olivier Hachet [email protected]

Transcript of A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution...

Page 1: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

Thales Communications

MyCCMA Component Based Approach for Real-Time & Critical

Systems

Olivier Hachet

[email protected]

Page 2: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

2 /2 / Agenda

1) Path toward CBSE for RTE

2) The MyCCM Framework

3) Future orientation

Réf

éren

ce /

date

Thales Communications

Page 3: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

Path Toward CBSE

Thales Communications

Page 4: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

4 /4 / RTE Systems Context

RTE Systems Characteristics

� Execution platform heterogenity

� Complex internal communication and interaction sche mes

� Reuse of code is not obvious

� Intricated with underlying technologies

� Complex to integrate and tune

� Difficult to test

Réf

éren

ce /

date

� Difficult to test

� Domain specific method and tools

Thales Communications

Certification Reconfigurable

Determinism Ressource optimisation

Page 5: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

5 /5 / Targeted Improvements for RTE Systems

� Capitalize on software archi tectures

� Better structuration of software

� Reuse of business code

� Common approach for several targets (HW, OS, MW)

� Software Design tooled up process

� One source running on multi-target

Réf

éren

ce /

date

� For near-real-time to hi-integrity runtime environments

� Complementary IVV tooled up process

� Standalone to highly distributed

� Static to Reconfigurable

Thales Communications

CBSE with Component/Container/Connector principles

allows to reach these goals

Page 6: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

6 /6 / From R&T to industrial adoption

Research Projects Domain Needs

� Space

� Software Radio

�Optronic

� Electronic Warfare

�…

MyCCM

Réf

éren

ce /

date

CBSE dedicated to

Real Time Embedded Systems

� Component Framework Basis

� Real Time constraints

� Safety and Security

� Connection with MDE

MyCCM

�C++ (optro, vetro, SDR)

�Ada (space, radar)

� Java (ECS)

�C (railway)

Standardisation l

� lwCCM (2003)

�DDS4CCM (2008)

�QoS4CCM (RTF 2007)

�…UCM (2013 …)

Page 7: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

MyCCM Framework

Thales Communications

Page 8: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

8 /8 / Component Based Approach

BusinessCode

BusinessCode

Non-structured code

ArctifactBusiness

CodeArctifactBusiness

Code

Structured code, with abstraction API

Réf

éren

ce /

date

Thales Communications

BusinessCode

Tooled Process (MDE)

BusinessCode

MyCCM Approach enables the generation of technical

code (communications, deployment, etc…)

Page 9: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

9 /9 / MyCCM Architecture Model

A common Architecture Description Formalism

� Based on the Lightweight CCM Abstract Component Mod el

� Standard interaction patterns + Programming model

� D&C for deployment

� Specific Adaptations for RTE

� Non CORBA environments, static deployment

Very low footprint

Réf

éren

ce /

date

� Very low footprint

� Built-in Extension mechanisms (Connectors)

� Ability to define new interaction patterns and implementations

Connector

Interaction pattern &

middleware encapsulation

Business Code

BusinessCode

Page 10: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

10 /10 / MyCCM Framework Architecture

Back-end …

EMF

Engagement Systems

SDR/SCA

Space / Weapon Systems

Software Architecture NF Code Generation & Deployment on Targets

SharedArchitectural

Principles

Rhapsody

Réf

éren

ce /

date

Thales Communications & Security

Domain or

Environment

specific

Extensions

Component

Model

MetaData

Structure

Optronic /Vetro/ EWR…

N FGenerated

Code+

Deployment facilities

CommonGenerationRules

Platform SpecificGenerationRules

NFGenerated

Code +

Deployment facilities

CommonGenerationRules

Platform SpecificGenerationRules

RSA / CX

MelodyCCM

Page 11: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

11 /11 / MyCCM applied to SDR Signal processing

DomainSpecific

Metadata

Component Model

MetaData

Structure

EMF

Back-end C++ for SDR Digital Signal Processors

GeneratedCodeCommon

GenerationRules

Platform SpecificGeneration

Rules

GeneratedCode

CommonGeneration

Rules

Platform SpecificGeneration

Rules

Front-end

Graphical DSL(Melody,

Advance)

Textual DSL(IDL, XML, COAL)

UML Modeler

Réf

éren

ce /

date

11

RTOS

Domain Specific Middleware and Services

Specific Processor

Libs

Thales DSP OE

threads

Method objects

allocators

Error management

MHAL Com

Broker

POSIX AEP

SCA Lib

MyCCM runtime (Abstraction layer)

Page 12: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

12 /12 / MyCCM applied to Space Domain

DomainSpecific

Metadata

Component Model

MetaData

Structure

EMF

Back-end Ada for Space Domain

GeneratedCodeCommon

GenerationRules

Platform SpecificGeneration

Rules

GeneratedCode

CommonGeneration

Rules

Platform SpecificGeneration

Rules

Front-end

Graphical DSL(Melody,

Advance)

Textual DSL(IDL, XML, COAL)

UML Modeler

Réf

éren

ce /

date

RTOS- Proprietary

Domain Specific Middleware and Services

Task Mngt

MyCCM runtime (Abstraction layer)

Message Passing

Software Bus

Comm. Space PUS

Semaphore Mngt

Page 13: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

13 /13 / MyCCM in Short

A tooled approach to software engineering

� Model Driven

� Component-Based Architecture Approach

� Promotes the use of Automatic code Generation

Focus on value added code

� Reduce the amount of time and effort on non value-a dded code

Improve reusability

Réf

éren

ce /

date

Thales Communications

Improve reusability

� Identify reusable application blocks

� Integration of legacy code

Reduce integration costs

� Ensure Interfaces are properly defined

� Ease testing activities

Do not impose a framework but integrate domain expertise

in a CBSE tooled approach “Make Your CCM”

Page 14: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

14 /14 / MyCCM in THALES Programs

Optronic (C++)

� Since 2007

� 3 programs

Vetronic (C++)

� Since 2009

� 2 programs

Electronic Warfare (C++)

Software Defined Radio (C++)

� Since 2012

� Support for GPP and DSP targets

Space Domain (Ada)

� since 2010

� Used in 5 programs

Weapon systems (Ada)

Réf

éren

ce /

date

Thales Communications

Tec

hnod

ay 2

009

-co

nfer

ence

Electronic Warfare (C++)

� Since 2011

� 2 programs

Control Station (Java)

� Since 2008

� 1 program

Weapon systems (Ada)

� To be deployed in 2013

Railway Domain (C)

� Under evaluation

� Targeted deployment in 2014

Page 15: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

Future Orientations

Thales Communications

Page 16: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

16 /16 / Thales Requirements

A CBSE based on Component / Container / Connector

� A MDE component-based design

� Based on a meta-model capturing CBSE main concepts

� Extensible (capability to add new features for specific needs)

� Target several execution frameworks

� Middleware agnostic

� Interactions fully managed by connectors

Réf

éren

ce /

date

� Interaction patterns instead of specific interfaces

� Optional compatibility with IDL/IDL3

� Support native languages for component implementati on� Remove CORBA specific language mappings (or Optional)

� C++11 or subset supported by current compilers

� Java

� Reduce dramatically the complexity of the programmi ng model

Page 17: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

17 /17 / Future Component Framework Vision

Composant ComposantInteraction pattern (Pub/Sub, synchronours Data flow, …

Software Architectural View

Réf

éren

ce /

date

Ope

ratin

g E

nviro

nmen

t

Thales Communications & Security

Hardware 1

Operating System 1

Com MW

Hardware 2

Domain SpecificServices (Thread,

memory, mutex,….) Ope

ratin

g E

nviro

nmen

t

Operating System 2

Com MW Domain Specific

Services (Thread, memory, mutex,….)

Page 18: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

18 /18 / Future Component Framework Vision

SCA containerComponent SCA containerComponentConnectorFragment

ConnectorFragment

Services access points

Execution Framework View

Services access points

Réf

éren

ce /

date

Ope

ratin

g E

nviro

nmen

t

Thales Communications & Security

Hardware 1

Operating System 1

Cmp Fwk runtime & Services

Com MW

Hardware 2

Domain SpecificServices (Thread,

memory, mutex,….) Ope

ratin

g E

nviro

nmen

t

Operating System 2

Cmp Fwk runtime & Services

Com MW Domain Specific

Services (Thread, memory, mutex,….)

Page 19: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

19 /19 / MyCCM Open Source Initiative

Promote an Open Source core MyCCM (C++ first)

� Select the core building blocks

� Meta model, runtime, code generators, deployment

� Ensure modularity on meta models, generators, deployment

� Allowing to add new features as « plug-in »

� Identify the appropriate Open Source community

Réf

éren

ce /

date

Thales Communications

� Providing facilities to host and promote the project

� With LGPL or EPL license policies style

Contribute to its evolution toward UCM Standard

� COMET project (French R&T) with Prismtech

� Make MyCCM middleware agnostic and contribute to lwCCM evolution

� Commit new services and connectors when necessary

Page 20: A Component BasedApproachfor Real-Time & Critical Systems · RTE Systems Characteristics Execution platform heterogenity Complex internal communication and interaction schemes Reuse

20 /20 /

Réf

éren

ce /

date

Thales Communications