Model Based System Engineering with Capella · 2016-06-03 · 83230347-DOC-TAS-FR-002 02/06/2016 Ref.: Model Based System Engineering with Capella Laetitia Saoud TAS/ CTO / SSEPG

8323

0347

-DO

C-T

AS

-FR

-002

02/06/2016

Ref.:

Model Based System Engineeringwith Capella

Laetitia SaoudTAS/ CTO / SSEPG - System Modelling expertise

Ce document ne peut être reproduit, modifié, adapté, publié, traduit d'une quelconque façon en tout ou partie,ni divulgué à un tiers sans l'accord préalable et écrit de Thales Alenia Space - © 2015, Thales Alenia Space

SCOPE of the presentation

Introduction

Arcadia & Capella overview

Co-architecting & multi criteria trade-off

Example

Additional information

02/06/2016

2

Ref.:

Introduction


Spatial systems: functional complexity & variety of criteria

A wide range of needs combined with a lot of criteria and variety of technology lead to more and more complex system architectures

From Requirements Allocation to Architecture Mastering

�late discovery of design issues during IVV

Requirements

« Requirement to Boxallocation »

Non-functionalConstraints

Architecture building & Justification

OperationalNeed

FunctionalNeed

Reqs

Trade-off

Architecture

�Early validation of the Architecture �Mastering and optimisation of product & IVV

And from Document driven to MBSE practices

Moving from Document Centric to Data Centric

SpecificationsInterface specificationsSystem DesignAnalysis & Trade-offTest plans & procedures

Document Driven Model Driven


Need for a collaborative architecting solution

02/06/2016

Ref.:

A global engineering approach, not limited to System engineers.

To enable:

HW and SW teams to:

- work In co-engineering with system engineering team

- take benefits for their own architecting activities

IVVQ & Operations to:

- express specific IVV needs,

- build an IVVQ strategy driven by functions & architecture

Domain analyses / specialty engineering to:

- contribute to architecture early validation and optimization,

- introduce architecture constraints from analyses

Specialty

engineers

Customer

System

Architects

SW/HW designers

& developpers

IVVQ

manager

Operations

engineers

…

Arcadia & Capella Overview


Thales MBE solution : Capella

02/06/2016

Ref.:

It embeds a Model Based Engineering method called ARCADIA :

• Customer need & operational concepts

refinement

• System Functional analysis

• Solution architecture definition :

• Logical Architecture (sub-systems specification and internal interfaces)

• Physical Architecture (architecture as developed and deployed,

incl. SW/HW allocation)


Capella core concepts

Ref.:

Functions & dataflows Structure

Interfaces & data

Behaviour: scenario

Behaviour: modes


Thales MBE solution : Capella

02/06/2016

Ref.:

Capella:

• Provides graphical views for major

engineering concerns

• Based on a central design database

(model) => consistency and impact

analysis

Physical architecture

Scenarios (operations, IVV,

protocols …)

Functional analysis

Interfaces definition

Modes & States

Logical Architecture

System mission

Interfaces Data model

MODEL


System modelling approach

02/06/2016

12

Ref.:

Operational

Analysis

System

Analysis

Logical

Architecture

Physical

Architecture

• Mission Operational processes description

• ‘Voice of the customer’

• Functional analysis / mapping to upper level

• System external interfaces

• System lifecycle and scenarios

• System internal architecture:

• Ground centers allocation and interfaces

• Space segment architecture (PL/PF alloc)

• Refined operational scenarios, additional FDIR

scenarios

• Physical design consolidation:

• Network and redundancies considerations

• Physical constraints / perfo assessment

• Refined satellite FDIR

• End-to-end system analysis

Co-architecting & multi criteria trade-off


Engineering disciplines constraints sharing

6/2/2016Ref.:

Architecture constraints

System Engineer -ArchitectCustomer

Requirements

System model

Domain constraints and req.

Domain teams

SW / HW engineer

Domain engineering tools (perfo, RAM,

safety)

Analysis Parameters

+ constraints

Architecture Building & Design: the Art of Compromise

Product Architecture must deal with potentially contradictory Constraints, which impact Breakdown, e.g. :

SafetyPerformancesComplexity of internal interfacesEase of System IntegrationCost, sub-contracting…

SolutionArchitecture

RAMS, ILS, IVV

Architect

Product line

Performance Non-Functional Viewpoint

1°°°° Automatic analysis:-CPU overloaded-Bus overloaded-Latency in excess

2°°°° Causal analysis-Tool locates problems-Quantitative analysis

3°°°° Architecture improvement:-Lighter protocols-Higher bandwidth-Hardware processing

3°°°° Architecture improvement:-Second redundant server

2°°°° Causal analysis-Tool locates problems-Failure propagation algorithm

Safety Non-Functional Viewpoint

1°°°° Automatic analysis:-Rule: “No single source for major failure condition”-Not met for video

Multi-Viewpoints Trade-off

Confrontation rules for multi-viewpoints trade-off

Exemple of functional allocation trade-off


Functional allocation trade-off example : the problem

Allocationtrade-off

on referencearchitecture

cost

security

complexibility

TM/TC bandwidth

flexibility

CPU

Autonomy

Maturity

s/s Specification derivation

Operationprocedure

specification

Ground/boardIRD

OBCP specification

PL managementspecification

PL IRD

safety

Timing


Functional allocation trade-off example : candidate architectures

Autonomous payload

Dumb payload managed from ground


Functional allocation trade-off example : candidate architectures & automated evaluation.Dumb payload managed from OBCP

Automated evaluation of criteriaSome of the criteria may be automatically evaluated by the modeling environment:

TM/TC bandwith,Sub-system complexity (from function complexity),Timing performances …

Compromise to be found for the precision of modeling (behaviours, timing, …) to obtain a representative model and the benefits wrt to manual evaluation.

Additional information


Open sourcing as Capella

Melody Advance has been open sourced in 2015 as CAPELLA

Clarity project: - Experimentation @ Airbus D&S, Areva,

Continental Automotive, OHB...- Collaboration/Contribution with external

companies to develop extensions or tools integration

https://www.polarsys.org/capella /


What is Open Source?

Technical

platform

Domain

platform

Expertise,

Know-how,

Core business

Domain

end-user

solutions

Va

lue

Share

-

Co-develop

-

Contribute

-

Use

Focus on

one’s value

-

Keep as

competitive

Advantage

Viewpoints

• IVV• Product Line• Safety• Performance• Etc.

Advanced add-ons

• Teamworking• Model maintenance• Non functional• Etc.


ANY QUESTION ?

02/06/2016

26

Ref.:


02/06/2016

Ref.:

Commercial Tools Experiments

The Thales MBE Odyssey

2000 2002 2004 2006 2008 2010 20142012

NatoAF

Corporate Research Program

Engineering PracticesTransformation Plan

MethodBuilding

Short-LoopValidation & Adjustment

Pilot Deployments

Real Operational Use

ToolOpen Sourcing

Dedicated ToolDevelopment

Early Experiments


Unique and shared reference

SYSTEM MODEL

CUSTOMER

RAMS

ILS & operations

Specification & design

Sub-contractors

END USER

AIV

Perfo

Managing the system complexity:

� Breakdown according to system layers,

� Mastering the product behaviour,

� Asking the right questions at the right time.

Support requirement and design engineering wrt

to customer inputs :

� Logical derivation from customer need

analysis down to solution,

� Design data formalisation and organization

A unique and shared reference for system

definition:

� Viewpoints integration and sharing,

� Early validation

� Early preparation of ILS, AIV

Support to analyses (trade-off, change impacts…)

Documents

Model Based System Engineering with Capella · 2016-06-03 · 83230347-DOC-TAS-FR-002 02/06/2016 Ref.: Model Based System Engineering with Capella Laetitia Saoud TAS/ CTO / SSEPG