Model-based systems engineering has developed significantly over the last few years, resulting in an increased usage of models in systems specification and architecture description. The question of the positioning of requirement engineering versus MBSE is a recurrent one.
This talk describes one vision of this articulation where textual and model requirements actually complete each other. The results are improved contracts across engineering levels and more formalized V&V practices.
Stéphane Bonnet, Thales Corporate Engineering
Stéphane Bonnet is in charge of Thales Corporate MBSE Coaching and Design Authority of the Capella open source modeling solution. For the last ten years, he has led the development of Capella and has been an active contributor to the Arcadia model-based method for systems, hardware and software architectural design. In Thales, he is animating a wide community of modeling experts from all domains and countries to investigate low-maturity modeling topics, capture end-user needs, and orient method and workbench roadmaps.
Similaire à [ Capella Day 2019 ] Augmenting requirements with models to improve the articulation between system engineering levels and optimize V&V practices
Similaire à [ Capella Day 2019 ] Augmenting requirements with models to improve the articulation between system engineering levels and optimize V&V practices (20)
[ Capella Day 2019 ] Augmenting requirements with models to improve the articulation between system engineering levels and optimize V&V practices
1. www.thalesgroup.com
THALES GROUP OPEN
Arcadia and Capella: As much as I can
tell and demonstrate in a bit less than
one hour, from core concepts to
advanced practices and perspectives
Stéphane Bonnet
THALES
CAPELLA DAY, MUNICH, SEPT. 16TH 2019
2. 2
THALES GROUP OPEN
A focused journey
in a Capella model
Extremely quick and simple example
to introduce both the method and the tool
4. 4
THALES GROUP OPEN
Understand the customer/user need
Define and share the solution among stakeholders
Secure SYS/SW/HW engineering, prepare subcontracting
Early evaluate and justify architectural design
Prepare and master V&V
6. 6
THALES GROUP OPEN
Capability
Interface
Mode State
Function
Functional
exchange
involves
Functional
Chain
Scenario
Is described by
implements Actors,
Components
Component
exchange
involves
8. 8
THALES GROUP OPEN
A1
A3
A2
Operational Analysis
WHAT THE USERS/STAKEHOLDERS
NEED TO ACCOMPLISH
Support of discussions
with the customer, objectives,
activities and processes,
pains, gains, etc.
11. 11
THALES GROUP OPEN
Not relevant here
Anything solution-related: how things work, which technologies, etc.
12. 12
THALES GROUP OPEN
F2
F1
F3
F4
F5
A1
A3
A2
ViewPoints
C1
C2
C3
F21
F1
F6 F3
F22
Conceptual solution
HOW THE SYSTEM WILL WORK SO
AS TO FULFIL EXPECTATIONS
High-level architecture
description, functional
refinement, architectural
drivers, functional allocation,
first trade-offs,
modes and states analysis
13. 13
THALES GROUP OPEN
Not relevant here
Which specific sensors, which command device, communication
media between the drone and the base station, detailed interfaces
14. 14
THALES GROUP OPEN
F2
F1
F3
F4
F5
A1
A3
A2
HOW THE SYSTEM WILL BE
DEVELOPED AND BUILT
Implementation constraints,
reuse, refined trade-offs,
M/T/B strategy,
finalized detailed interfaces
ViewPoints
C1
C2
C3
F21
F1
F6 F3
F22
ViewPoints
C11
C12
C1’
C2
C3
C4
F21
F1
F6 F7
F22
e.g. Processors
e.g. Buses
e.g. SW, HW
components
Finalized Architecture
HOW THE SYSTEM WILL BE
DEVELOPED AND BUILT
Implementation constraints,
reuse, refined trade-offs,
M/T/B strategy,
finalized detailed interfaces
18. 18
THALES GROUP OPEN
1. Functional chains
4. Property Values Management Tool (add-on)
2. Replication of elements
3. Filtering (add-on)
19. 19
THALES GROUP OPEN
1. Functional chains
What?
Creation and composition of functional chains
Why?
To capture system usage examples, to enforce design
completeness and consistence, to drive engineering activities
(e.g., V&V or development strategy)
20. 20
THALES GROUP OPEN
2. Replication of elements
What?
Automated synchronization of model parts, automated
reconnections
Why?
Enabler for instance-level modeling (cloning of a prototype
instance), enabler for reuse of building blocks
21. 21
THALES GROUP OPEN
U U
UU
D
P
Prototype pattern
the « type » is also an instance
Definition and usages
« types » are defined separately
22. 22
THALES GROUP OPEN
3. Filtering (add-on)
What?
Definition of criteria on model elements, automated preview
and derivation of filtered models
Why?
Master system increments, master the data exchanged with
customer or sub-contractors, etc.
25. 25
THALES GROUP OPEN
4. Property Values Management Tool (add-on)
What?
Easy creation of model extensions and customization of
diagram graphical rendering
Why?
Charactization of models with meaningful, domain-specific
information, instant perception of added-value for models
26. 26
THALES GROUP OPEN
Augmenting requirements
with models
to improve the articulation between engineering levels
and optimize verification and validation activities
28. 28
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
30. 30
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
31. 31
Models add rigor to need expression / solution description
Models enable automated processing
46. 46
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
R R
Vertical slices of architectural design
across need and solution models
Definition of increments with expected
functional chains (user stories)
INC 1
INC 2
56. 56
THALES GROUP OPEN
Assets & Threats Modeling for supporting cyber security risk management
Describe the threats, threat
sources, primary assets being
threatened
Identify the critical data and the
functions and components
manipulating this data
Identify the trust boundaries
Visualize the security levels of
the solution (Confidentiality,
Integrity, Availability and
Traceability security levels
57. 57
THALES GROUP OPEN
Assets & Threats Modeling for supporting cyber security risk management
Describe the threats, threat
sources, primary assets being
threatened
Identify the critical data and the
functions and components
manipulating this data
Identify the trust boundaries
Visualize the security levels of
the solution (Confidentiality,
Integrity, Availability and
Traceability security levels
58. 58
THALES GROUP OPEN
Assets & Threats Modeling for supporting cyber security risk management
Describe the threats, threat
sources, primary assets being
threatened
Identify the critical data and the
functions and components
manipulating this data
Identify the trust boundaries
Visualize the security levels of
the solution (Confidentiality,
Integrity, Availability and
Traceability security levels
59. 59
THALES GROUP OPEN
A place to share open source
prototypes, experiments, small
non-industrialized developments.
Coming soon…
(hopefully by the end of 2019)