journée des doctorants 2011-06-28 v0urtado/slides/cornu_28_06_2011.pdf · 2 etzr / clémentine...

ETZ

R /

C.C

OR

NU

/ Jo

urné

e de

s do

ctor

ants

201

1-06

-28

/ v.

0.1

/ 12/

07/2

011/

©

Eur

ocop

ter r

ight

s re

serv

ed

Journée annuelle de présentation des travaux des doctorants du LGI2P

28/06/2011 – Clémentine CORNUCo-Directeurs de thèse : Vincent CHAPURLAT (EMA) et François IRIGOIN (ENSMP)

2

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Agenda

1. Introduction to the thesis question and context

2. Our proposition to help companies in their SE deployment

3. Conclusion

3

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Introduction to the thesis question and its context

3211. Introduction to the thesis

question and context

4

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Thesis question

How to deploy System Engineering processesin a multi cultural and multi sites industry, in a multi-disciplinary context,dealing with different factors like interoperability



5

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Systems Engineering Overview

Companies need to reduce• Customer dissatisfaction • Product lack of profitability• Cost and deadlines overruns• Etc.

Origins: lack of systems’ control• Needs not sufficiently expressed / listened• Lifecycle not considered entirely• Resources not available at the right time• Miscommunication• Etc.



6

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed


Definition“General methodological approach that includes all the appropriate activities to design, develop and test a system which both provides an economical and competitive solution to the needs of a customer and also satisfies all stakeholders.”

SE Stakes• Better complexity control • Better match between products needs/quality

• Better cost control • Better anticipation of problems and risks

• Better respect of deadlines • Better multi-disciplinary and multi-actors cooperation

• Shorter development time • Increasing the satisfaction of all stakeholders



7

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Systems Engineering

Position of SE on the Vee cycle

Realization : business engineering

Needs Endproduct

System integration

Tailored from an AFIS pattern

To qualify the systemTo qualify the system

To verify the integration

To verify the integration

To assemblyTo assembly

To get the components

To get the components

To developpTo developp To manufactureTo manufacture To reuseTo reuse To buyTo buy

To analyze & define the need

To analyze & define the need

To define technical requirements

To define technical requirements

To design organicarchitecture

To design organicarchitecture

To design functionnalarchitecture

To design functionnalarchitecture

To verify & validate & optimize

To verify & validate & optimize




8

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed


SE principles are defined using processes • High level of abstraction • Example taken from [ISO 15288:2008]

[…]6.4.1 Stakeholder Requirements Definition Process

a) Elicit stakeholder requirements. 1) Identify the individual stakeholders or stakeholder classes who have a legitimate interest in the system throughout its life cycle.2) Elicit stakeholder requirements from the identified stakeholders.

[…]



9

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Main obstacles to Systems Engineering deployment

How to know if the company is mature enough to face a SE deployment? Is it ready for processes ?

What computer tool could be used to support the

deployment?

How to deploy SE? How to identify and keep

the enterprise design good practices?How to limit the

resistance to change?

What shall be deployed pragmatically?

What document shall be used to get SE best practices?



10

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Thesis question

How to deploy System Engineering processesin a multi cultural and multi sites industry, in a multi-disciplinary context,dealing with different factors like interoperability



11

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Entreprise

Hypothesis : Interoperability is a deployment key factor

Systems Engineering = interdisciplinary approach

Our hypothesis: • Interoperability is a key factor in

the deployment• Interoperability = “Ability of

companies and entities within those companies to communicate and interact effectively” *

Each deliverable of this thesis aims to promote enterprise interoperability



SE processSE processSE processSE process

SE processesSE processes

SESE

Realization

Integration

actorsactors

methods

toolstools

methods

……

= INTEROPERABILITY MATTERS

*ISO/DIS 11354-1 - Advanced automation technologies and their applications - Part 1: Framework for enterprise interoperability, ISO, 2010

12

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Our proposition to help companies in their SE deployment

321Our proposition to help companies in their SE

deployment

13

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed




deployment?





deployment



14

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

State of the Art in Systems Engineering applied to Avionics

Comparison and analysis of SE standards• Goals

• Provide deployment team with elements required to pick a reference standard• Indicate where information on specific topics can be found

• Standards studied • generic • aeronautics/aerospace specific


deployment

15

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed




deployment?





deployment



16

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Processes to deploy

SE principles are defined using processes • High level of abstraction

• They must be tailored to the company and to its business area specificities• They are rarely described with process models…

• Deployment process and Managmenent process are not addressed

[…]6.4.1 Stakeholder Requirements Definition

Processa) Elicit stakeholder requirements.

1) Identify the individual stakeholders or stakeholder classes who have a legitimate interest in the system throughout its life cycle.2) Elicit stakeholder requirements from the identified stakeholders.

[…]



Picture taken from: On Principles of Complex Systems Engineering―B. E. White, Ph.D. INCOSE Symposium, 20-23 Jun 2011, Denver, CO

17

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Models of the processes to deploy

Process model has been developped for the “Stakeholder requirements definition” process described in the ISO 15288:2008

Specific tailoring has been done for Eurocopter

Generic models for deployment process and management process have also been built


deployment

Elicit stakeholder requirements

+Identify stakeholders

+Elicit stakeholders

requirements

Accountable for the activity

Responsible for the activity

needs needs

List of stakeholders orstakeholders classes

List of stakeholders requirements

Accountable for the activity

Responsible for the activity

needs needs

Stakeholder

needs

18

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed




deployment?





deployment



19

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Assessment of the readiness of the company to face a SE deployment

Before to deploy SE processes, the deployment team must assess the readiness of the company for it.

To this end, a maturity model (tested within Eurocopter) is proposed


deployment

Collaboration topics have been included

20

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Two scenarios for the deployment

According to the result of the maturity model evaluation, two deployment scenarios can be envisaged


deployment

Assessment of the maturity of the company to face

the deployment

Deployment of SE processes

Deployment of SE good practices

1st scenario 2nd scenario

Method discribing how to deploy processes

Method discribing how to start new design project meeting SE requirements

21

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed




deployment?





deployment



22

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Two scenarios for the deployment 321Our proposition to help companies in their SE

deployment


the deployment






23

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Two scenarios for the deploymentIntroduction to first scenario

1st scenario : Deployment of SE processes (Declared deployment)


deployment

AS-IS

IDEAL

TO-BEI : InputsI : Inputs

- Mission, purpose and objectives of the deployment and thus of the modelling- Enabling systems- Systems at Interfaces- Needs

f(I(t), AS-IS(t), IDEAL(t))=TO-BE(t+dt)

24

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Two scenarios for the deploymentIntroduction to first scenario

This scenario requires: • A culture of processes and modelling• A standard design process within the company • A good image of SE within the company• Etc.

It cannot be applied in every company.

A second deployment scenario is needed


deployment

25

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Two scenarios for the deploymentIntroduction to second scenario


deployment


the deployment






26

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Two scenarios for the deploymentIntroduction to second scenario

2nd scenario: Deployment of SE good practices (Descreet deployment)

• Principle• To use the kick-off of new design projects to introduce progressively new

design activities meeting SE and interoperability requirements• Two main objectives

• Practically • A method

– Providing all required activities to start a project applying SE principles – Based on modelling

• A documentation platform– Enabling to generate project documents from models built– Aims to limit resistance to change


deployment

Resources neededActivities to be performed

Tools to useStandards to meet

ObjectivesMissionFinality

Enabling systems Systems at interface

Help project team to organize the project

Help project team to define the object of the project

i.e. the system of Interest

27

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Formalization of concepts needed: From a meta-model…

Whatever the deployment scenario chosen, models are used.

So we need• A framework for the modelling

– What concept/relationships can used in models? – What are their allowed attributes?

• A definition of concepts used to improve semantic interoperability between deployment and design stakeholders

To this end, we have first built a meta-model


deployment

28

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Formalization of concepts needed: From a meta-model…


deployment

29

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Formalization of concepts needed: From a meta-model…to an ontology

However, it appears that the meta-model was not self-sufficient. We sure need classes and relationships between them but we also need:

• To define of classes and relationships in natural language and in a formal way to share deployment semantics

• To check the consistency of the classes and relationships according to specific rules

We have therefore choosen to design an ontology that extend the previously defined meta-model

• Ontology = "an explicit and formal specification of a conceptualisation"*• To design it, we have choosen OWL and Protégé

*T.R. Gruber. Toward principles for the design of ontologies used for knowledge sharing. International Journal of Human Computer Studies, 43(5):907–928, 1995

30

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Formalization of concepts needed: From a meta-model…to an ontology


deployment

The ontology currently developed is here

31

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed




deployment?





deployment



32

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Main computer tools proposed (to be developed) to support the deployment


deployment

Model processes, activities, actors, roles, etc.

Put contents togetherEnable the creation of documents templates Manage users profiles Etc.

Manually add classes and instances to the ontologyDetect inconsistencies Provide a graphical representaionetc.

To automatically generate ontology classes instances

BPMN 2.0Modelling

environment

TransformationT

GMF ATL

BPMN 2.0Models

Ontology DocumentsDocuments

Ontology manager

Protégé

Documentation plateform

JavaXML

Document structure and

format

XML

OWL

Verification reports

Includes rules

33

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Conclusion

321Conclusion

To conclude

Scientific locks we aim to remove• Creation of a System Engineering

deployment approach which is applicable even if the company is not ready for it

• Creation of an ontology covering various scientific fields (SE, Enterprise Modelling, etc.) together with Eurocopter business area concepts

• Creation of a modelling environment dedicated to the description and the organisation of the design project

• Creation of a documentation platform implying verification, transformation and alignment of models

34

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

321Conclusion

35

ETZ

R /

Clé

men

tine

CO

RN

U /

Jour

née

des

doct

oran

ts 2

011-

06-2

8 /

v.0.

1 / 1

2/07

/201

1/

©

Eur

ocop

ter r

ight

s re

serv

ed

Thank you for you attention ! Questions are welcolme ☺

321Conclusion

Contact

Clémentine Cornu Eurocopter (ETZR)Aéroport International Marseille Provence, 13725 Marignane Cedex – France [email protected]