Post on 14-Jun-2020
www.thalesgroup.comTHALES GROUP OPEN
Arcadia and Capella: Augmenting requirements with models to improve the articulation between systems engineering levels and optimize V&V practices
Stéphane Bonnet, Jean-Luc Voirin, Juan NavasTHALES
INCOSE SYMPOSIUM 2019MBSE BEST PAPER AWARD
2
1. Preamble: Arcadia method and Capella workbench
2. Model elements ARE requirements
3. Contracts between engineering levels: workflow
4. (Happy) consequences on V&V and incremental development strategy
This
doc
umen
t ma
y no
t be
rep
rod
uced
, mod
ified
, ad
ap
ted
, pub
lishe
d, t
rans
late
d, i
n a
ny w
ay,
in w
hole
or i
n p
art
or d
isclo
sed
to a
third
pa
rty w
ithou
t the
prio
r writ
ten
cons
ent o
f Tha
les
-©
Tha
les
2015
All
right
s res
erve
d.
5. Instantiated workflow
3 1. Arcadia and Capella
4
Methodology and high level concepts
and viewpoints
Purpose-built to provide the
notation and diagrams fitting the Arcadia approach
5
Arcadia : A “Simple” Engineering Language
6
Arcadia : A “Simple” Engineering Language
NEED
SOLUTION
7
A practitioner-driven journey started in Thales…
2006 2010 20142008 2012 2016
Practitioner-drivenCapella development
Multi-domain Thales working groups on language and method
8
… and now continuing beyond
92. Model elements ARE requirements
10
Textual requirements
are at the heart of the current engineering
practices
Solution model
helps validate feasibility,
elicit/justify new requirements for the system/subsystems
Need model
helps formalize and consolidate
customer and system requirements
11
C
CapabilityInterface
MS
Mode State
F
Function
Functionalexchange
involves
FC
FunctionalChain
Scenario
Is described by
implements
C
Actors, Components
Component exchange
involves
12
Visualize data in live during flight
Display acquired HD video in live
Display multi-spectral image in live
Display thermal image in live
Visualize all collected mission data
Visualize substance level in live
13
Models add rigor to need expression / solution description
Models enable automated processing
14
C
F
FC
F
F
R
R
Requirements Model elements
R
15
TextualRequirements
Model elementsRequirements
C
F
FC
F
F
R
R
R
16
A model requirement can formalize a textual requirement and explicit its effects and ramifications
17
Some expectations (environmental, regulations, etc. ) are easier to express with textual descriptions.
18
Some expectations on a model element at a given engineering level do not require a formal modeling (which is left to subsystem design)
19
Tooling supportCoupling models and textual requirements
20
RAT (The Reuse Company) authoring in Capella
21
Capella in Siemens TeamCenter via Obeo SMW
22
Certain model elements can be considered as requirements
23
3. Contracts between engineering levels: workflow
24
SolutionN
ee
dSo
lutio
n
Textual Requirements
Direct allocation
Leve
lN
25
Solution
Textual Requirements
Ne
ed
Solu
tion
Direct allocation
1
1. Elicitation of model
and textual requirements on the
systemLeve
lN
26
Solution
Textual Requirements
Direct allocation
1
2
2.Architecture description
specifies with the adequate level of detail
how the system works and what is expected from
each constituent
The goal here is to prepare the contracts for all
subsystems and guarantee their proper integration.
Leve
lN
Ne
ed
Solu
tion
27
SolutionN
ee
dSo
lutio
n
Textual Requirements
Direct allocation
Leve
lN1
2
C11
F21
F1
F6Textual
Requirements
3 4
Ne
ed
Leve
lN+1
4. Textual requirements are
created when needed, in addition to the model
requirements: legal, non-functional, additional
specification of internal expected behaviour
3. The context of a given system
constituent is entirely computed (anything
contributing to the definition of this constituent including
allocated Functions, interfacing Components, etc.)
28
Tablet is a constituent of a drone-basedsystem
Tablet is the (sub)system of interest
3
29
Model-based workflow favors co-engineering over the traditional differentiation between “customer” requirements and “system” requirements
30
4. (Happy) consequenceson V&V and incremental
development strategy
31
TextualRequirements
Model Requirements
C
F
F
F
R
R
R FC
(Derived, reconstructed link)
IVV Version(RV/DV)
Verification and validation
32
System-level V&V procedures
Visualize data in live during flight
Display acquired HD videoin live
Display multi-spectral image in live
Display thermal image in live
Visualize all collected mission data
Visualize substance level in live
Subsystems, software, etc.
System architectural design
MS
F
FC
C R MS
F
FC
C R
Vertical slices of architectural design across need and solution models
Definition of increments with expected functional chains (user stories)
INC 1
INC 2
33
5. Instanciated workflowTwo years, 30 persons
34THALES GROUP INTERNAL
This
do
cum
ent
ma
y no
t be
rep
rod
uce
d, m
od
ifie
d, a
da
pte
d, p
ublis
hed
, tra
nsla
ted
, in
any
wa
y, in
who
le o
r in
pa
rt o
r disc
lose
d to
a th
ird p
arty
with
out
the
prio
r writ
ten
co
nse
nt o
f Tha
les
-©
Tha
les
2016
All
right
s re
serv
ed
.
System Engineering data package
SYSTEM BLACK BOX
SYSTEMGLASS BOX
Classic scheme, rolled out by increments
Sub-System Engineering data package
SUB-SYSTEM BLACK BOX
SUB-SYSTEMGLASS BOX
System delivery
Sub-System delivery
SUB-SYSTEM COMPONENTS
SYSTEM VERIFIED
SYSTEMINTEGRATED
SUB-SYSTEM VERIFIED
SUB-SYSTEMINTEGRATED
x8
35THALES GROUP INTERNAL
This
do
cum
ent
ma
y no
t be
rep
rod
uce
d, m
od
ifie
d, a
da
pte
d, p
ublis
hed
, tra
nsla
ted
, in
any
wa
y, in
who
le o
r in
pa
rt o
r disc
lose
d to
a th
ird p
arty
with
out
the
prio
r writ
ten
co
nse
nt o
f Tha
les
-©
Tha
les
2016
All
right
s re
serv
ed
.
IVV procedure
Functional chain RequirementsFunctional Chains list Functional Chains release definition
IVV Test Suite Repository
Identical pattern at all levels
36THALES GROUP INTERNAL
This
do
cum
ent
ma
y no
t be
rep
rod
uce
d, m
od
ifie
d, a
da
pte
d, p
ublis
hed
, tra
nsla
ted
, in
any
wa
y, in
who
le o
r in
pa
rt o
r disc
lose
d to
a th
ird p
arty
with
out
the
prio
r writ
ten
co
nse
nt o
f Tha
les
-©
Tha
les
2016
All
right
s re
serv
ed
. RequirementsSA functional chains
SA Functions & exchanges
System Context
SYSTEM BLACK BOX
System Context
SYSTEM GLASS BOX
satisfiesLA functional
chainsLA functions &
exchanges
15 leaf components402 leaf-functions1856 funct. exchanges1676 requirements
Domain knowledge
Logical (LA) components
Requirements
Interface & Data
6 capabilities198 funct. Chains24 leaf-functions458 funct. exchanges641 requirements
37THALES GROUP INTERNAL
This
do
cum
ent
ma
y no
t be
rep
rod
uce
d, m
od
ifie
d, a
da
pte
d, p
ublis
hed
, tra
nsla
ted
, in
any
wa
y, in
who
le o
r in
pa
rt o
r disc
lose
d to
a th
ird p
arty
with
out
the
prio
r writ
ten
co
nse
nt o
f Tha
les
-©
Tha
les
2016
All
right
s re
serv
ed
.
SUB-SYSTEM BLACK BOX
SYSTEM GLASS BOX
System LogicalArchitecture
LA functional chains System Internal Data
Sub-system Context
Requirements
Requirements
SA functional chains External Data
READ ONLY input contract
Automated transitions
38THALES GROUP INTERNAL
This
do
cum
ent
ma
y no
t be
rep
rod
uce
d, m
od
ifie
d, a
da
pte
d, p
ublis
hed
, tra
nsla
ted
, in
any
wa
y, in
who
le o
r in
pa
rt o
r disc
lose
d to
a th
ird p
arty
with
out
the
prio
r writ
ten
co
nse
nt o
f Tha
les
-©
Tha
les
2016
All
right
s re
serv
ed
.
System verification: enhanced progress monitoring
Content removed
39THALES GROUP INTERNAL
This
do
cum
ent
ma
y no
t be
rep
rod
uce
d, m
od
ifie
d, a
da
pte
d, p
ublis
hed
, tra
nsla
ted
, in
any
wa
y, in
who
le o
r in
pa
rt o
r disc
lose
d to
a th
ird p
arty
with
out
the
prio
r writ
ten
co
nse
nt o
f Tha
les
-©
Tha
les
2016
All
right
s re
serv
ed
.
Test results: models facilitate analyses
Content removed
40THALES GROUP OPEN
This
doc
umen
t ma
y no
t be
rep
rod
uced
, mod
ified
, ad
ap
ted
, pub
lishe
d, t
rans
late
d, i
n a
ny w
ay,
in w
hole
or i
n p
art
or d
isclo
sed
to a
third
pa
rty w
ithou
t the
prio
r writ
ten
cons
ent o
f Tha
les
-©
Tha
les
2015
All
right
s res
erve
d.
Ref number- dateName of the company/ Template : 87204467-DOC-GRP-EN-002
Tooling supportManaging increments with Capella
41THALES GROUP INTERNAL
This
do
cum
ent
ma
y no
t be
rep
rod
uce
d, m
od
ifie
d, a
da
pte
d, p
ublis
hed
, tra
nsla
ted
, in
any
wa
y, in
who
le o
r in
pa
rt o
r disc
lose
d to
a th
ird p
arty
with
out
the
prio
r writ
ten
co
nse
nt o
f Tha
les
-©
Tha
les
2016
All
right
s re
serv
ed
.
Functional chain RequirementsFunctional Chains list Functional Chains release definition
Associate functional chains to increments
Compute, visualize and compare the footprints in terms of expected components and functions
42
Focus on the dedicated tooling
43
Release management viewpoint:Automated visualization of versions
Preview of functional increments footprints
44
Developed Version 1 Available elements in BLUE
Preview of functional increments footprints
45
Developed Version 2 Available elements in CYAN
Preview of functional increments footprints
46
Developed Versions 1 & 2 Common available elements in GREY
Preview of functional increments footprints
47Resources
48
Public forums, webinars and Youtube channel
https://polarsys.org/forums/index.php/f/10/
https://www.youtube.com/playlist?list=PLfrEYVpSGVLxEFR
ODSWUTP8N5i3NTG4o-
49
Capella website
https://polarsys.org/capella/index.html
50
bit.ly/CapellaDay2019Sept. 16th 2019
www.thalesgroup.comTHALES GROUP INTERNAL
Thank You! Questions?
Capella website: http://www.polarsys.org/capella/LinkedInhttps://www.linkedin.com/groups/8605600Twitterhttps://twitter.com/capella_arcadiaArcadia forum: https://polarsys.org/forums/index.php/f/12/Capella forum: https://polarsys.org/forums/index.php/f/13/IFE model & doc.: http://www.polarsys.org/capella/start.html