by Juan Navas (Thales) Complex systems engineering programs not only deal with the inherent complexity of the systems they develop but also shall be able to adapt very quickly to changes. This requires adapting existing well-proven engineering practices in order to support shorter time-to-market, more frequent variations in operational contexts and usages, and more complex engineering organizations. In this talk, Juan Navas will present the latest methodological progress on Arcadia and Capella that tackle these stakes.

1. www.thalesgroup.com
OPEN
Thisdocumentmaynotbereproduced,modified,adapted,published,translated,inanyway,inwholeorin
partordisclosedtoathirdpartywithoutthepriorwrittenconsentofThales-©Thales2018Allrightsreserved.
MBSE with Arcadia and Capella
Reconciling with the past and moving
towards the future
Juan Navas
Thales Corporate Engineering
juan.navas@thalesgroup.com

2. 2
participants registered for the Capella Days 2020
650

3. 3
Increasing number of
disciplines involved on
complex systems
engineering
More recently – Cybersecurity,
Resilience, User Experience, …

4. 4
We are not all like the Wright Brothers!

5. 5
Complex Systems
Engineering today requires a
collective intelligence

6. 6
Enable production/consumption of the right information
by the right person for the right use at the right time

7. 7
Models are key enablers of Digital Engineering
Provide
consistent
sources of truth
Provide digital
representations of the system
across life-cycle stages
Enable
communication
and collaboration
across stakeholders

8. 8
It is not the most
intellectual of the
species that survives; it is
not the strongest that
survives; but the species
that survives is the one
that is able best to
adapt and adjust to the
changing environment
in which it finds itself

9. 9
Reconciling with the past Embracing the future

10. 10
Reconciling with the past:
Models & Textual Requirements
Embracing the future:
Models and Agility

11. 11
Reconciling with the past:
Models & Textual Requirements

12. 12
Textual
requirements
are at the heart of
the current
engineering
practices
Solution model
helps validate
feasibility,
elicit/justify new
requirements for the
system/subsystems
Needs & Context
model
helps formalize and
consolidate
stakeholders and
system requirements

13. 13
Models add rigor to needs expression / solution description
Models can be processed to ensure completeness and consistency
… Why not considering that models ARE requirements?

14. 14
Requirements can either be
textual “shall” statements, either
model elements: textual and
model requirements actually
complete each other

15. 15
Model requirements Model + textual requirements
Some of the Arcadia concepts can be
considered as Functional and Interfaces
requirements, eventually with related
Performance requirements.
Models formalize stakeholders requirements
Some expectations (Environmental, Regulations,
etc. ) are easier to express with textual
descriptions with traceability links to model
elements

16. 16
N-Level:
Tablet is a
constituent of a
drone-based
system
N+1 Level:
Tablet is the
(sub)system
of interest
Textual
Requirements
Models + Textual
requirements bring
clarity and rigor to
“contracts” between
engineering levels

17. 17
Textual
Requirements
Model
Requirements
R
R
R
(Derived,
reconstructed link)
IVV
Version
(RV/DV)
Verification and
validation
Models + Textual requirements
enable a better coordination and
planning of IVV activities

18. 18
Embracing the future:
Models and Agility

19. 19
Models add rigor to needs expression / solution description
Agility on systems engineering is required to cope with customers’
expectations
… Why not implementing Model-Based Agility?

20. 20
Model-based practices are
effective enablers of systems
engineering agility
Build the solution in an
incremental way based on
value creation, using system-
level Capabilities and end-to-
end Functional Chains and
Scenarios

21. 21
Time
Gate Gate Gate Gate
Iterations
X.1 to X.n
“Warm-up” “Run” “Evaluation”
Concept
Development
… …
Iteration
review
Iteration X:
production
of macro-
increment X
Release
Stakeholder needs
Architecture definition
Design
Implementation
IVV
Between 2
Gates, teams
go through
phases that can
be iterated:
increments at
the team level
Warm-up - collaborative definition
of the detailed scope, goals an
schedule of the increment and of
the necessary resources
Run - iterative effort
punctuated by
iteration reviews
Evaluate - assess how the
engineering was performed, that the
expected outcomes are there and
that conditions for pursuing are met

22. 22
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
Vertical slices of architectural
design across need and
solution models
INC
1
INC
2
Definition of increments with
expected Functional Chains
RR

23. 23
Better collaboration,
organization and
progress monitoring
by using architectural
models as the
common “blueprint”

24. 24
Model elements such
as Capabilities and
Functional Chains
provide meaning to
what SW developers
are doing

25. 25
The road to Digital Engineering is in front of us

26. 26
LABS 4
Tomorrow, Tuesday October 13th, 4:45 pm CET: