AIDA Model Description V4.5

AIDA study case
Architecture model in Capella

System version : V4.5
© IRT Saint Exupéry • All rights reserved • Confidential and proprietary document
p
a
Table of content
g
e
0 Before opening the Capella model
1 Capella model overview
2 OA : Operational Analysis
3 SA : System Analysis
4 LA : Logical Architecture
5 PA : Physical Architecture
22/08/2022
p
a
Copyright
g
e
Copyright (c) 2016-2025 IRT AESE (IRT Saint Exupéry).

All rights reserved. This program and the accompanying materials are made available under
the terms of the
Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
which accompanies this distribution, and is available at
https://creativecommons.org/licenses/by-sa/4.0/
Contributors:
Pierre Virelizier, Tatiana Prosvirnova, Estelle Saez – Initial contribution
Romaric Demachy – System version V4.4 and V4.5
22/08/2022
p
a
Capella Tool
g
e
is modelled with
Capella is an Open Source MBSE tool (Model Based System Engineering). This tool
implement the Arcadia method.
Capella software and documentation about the tool and the method are available here :
https://www.polarsys.org/capella/
The AIDA architecture system version V4.5 is modelled with the version V5.1 of Capella.
22/08/2022
p
a
AIDA system introduction
g
e
5 AIDA : Aircraft Inspection by Drone Assistant

Assistance during walk around. AIDA seeks Aircraft defects
22/08/2022
p
a
AIDA system description
g
e Drone Environment
6
Drone Pilot Drone Control Desk Drone Aircraft
Remote
Control
AIDA
Power
Supply Data
22/08/2022
base
p
a
AIDA experimentation
g
e
7 • AIDA system was first designed and modelled by the MOISE project (IRT Saint
Exupery, Toulouse, France). The S2C project, a MOISE sequel, also uses AIDA and
continues the development of the use case.
• This system is a full study case, covering several fields of system design assisted by
models.
Topics: system
Topics: system safety simulation, control law,
Topics: system analysis, MBSA, Altarica cosimulation
architecture, MBSE Tool: Cecilia Ocas, Tools: simulationX,
Tool: Capella SimfiaNeo OpenModelica, ProSivic,
Cosimate
• This document describes the model of the AIDA Architecture package.

22/08/2022
p
a
Table of content
g
e
22/08/2022
p
a
Capella model overview
g
e
9 The AIDA model follows the Arcadia method. All the modelling layers proposed by this method are exploited,
except for the EPBS layer.
Capella layers/visions AIDA model description

Activity explorer Content Comments
Arcadia note: Description of Walk-Around process – identification of

The system does not appear in this layer
Visions for high level capabilities and activities
environment
description and need Vision with need analysis and system context analysis
Gathers technical exchanges between system
analysis. (high level scenarios and functional architecture,
supplier and customer
external interfaces)
Vision for classification and traceability between need Architecture breakdown taking into account non-
Arcadia note: analysis and solution functional considerations (safety,…)
Visions for solution
description Vision with the solution of the system supplier (with System supplier proposal taking into account
functions of physical objects) technological choices
22/08/2022
p
a
Capella model overview
g
e
A full documentation of the model has been created, see the document “AIDA Architecture synthesis
1
0 V4.5”.
Important remark : amongst other evolutions, the V4.4 system version aimed at completing Capella
layers that were not, or only partially populated in previous versions. Currently, all the layers (except for
EPBS) are populated, but inconsistencies remain between the upper level layers (OA, SA and LA) and
the Physical Architecture layer. V4.5 provides minor additional modelling improvements.
Previously Step 1 (performed Step 2 Step 3.1 (performed T4

available T3 2020) (performed T3 2020) Step 3.2
2020)
Operational and Operational and

system analysis system analysis Operational and system Operational and system
properly properly analysis properly analysis properly
documented in documented in documented in the documented in the
the model the model model (following model (following
Preliminary (following (following ARCADIA top down ARCADIA top down
content : system ARCADIA top ARCADIA top approach) approach)
view down approach) down approach)
Logical architecture
Logical architecture Logical architecture
taking into account
taking into account safety taking into account safety
safety
requirements requirements
requirements
Baseline version Baseline version Baseline version First system evolution Physical layer update
(V4.3) of functional (V4.3) of functional (V4.3) of functional with partial taking into account new
and physical and physical and physical reconciliation (V4.4 and System and Logical
22/08/2022
architecture architecture architecture V4.5) architecture
: Consistency not ensured : Consistency ensured

Current state
: Consistency not ensured
p
a
Table of content
g
e
1
1
22/08/2022
p
a
OA : Operational Analysis layer description
g
e
1 The Operational Analysis layer aims at identifying the users needs and objectives. It describes the
2 missions, activities and involved capabilities from the user and stakeholders point of view, without
focusing on the system itself.
The objects and diagrams used for AIDA are described in the table below.
Point of view Capella Diagrams Capella Objects

Stakeholders identification [OAB] Operational entities
Capabilities identification [OCB] Operational entities, operational
capabilities
Operational activities and [OAIB], [OAB] Operational entities, operational activities
workflows
22/08/2022
p
a
Table of content
g
e
1
3
22/08/2022
p
a
SA : System Analysis layer description
g
e
1 The System Analysis layer aims at identifying the system functions and associated requirements, and the
4 system externals interfaces. It describes the missions and associated capabilities, the scenarios associated to
each capability, the identified system level functions and the exchanges with external systems and actors

Actors identification [CSA] Components/Actors
Mission and capabilities [MB], [MCB] Missions, capabilities, system components/actors
identification
Lifecycle [MSM] States and transitions
System modes [MSM] Modes and transitions
Functional behavior and [SDFB], [SFS] System functions and functional exchanges, functional
exchanges scenarios
External exchanges [SAV], [SES] System components and components exchanges,
exchanges scenarios
System level requirements N/A Native Capella requirements
22/08/2022
p
a
Table of content
g
e
1
5
22/08/2022
p
a
LA : Logical Architecture layer description
g
e
1 The Logical Architecture layer aims at defining “how the system works”, without focusing on the technological
6 choices. It describes the behavior of the various sub-systems and components and their functional interactions.
System level functions [LDFB], [LFBD] Logical functions, functional exchanges
breakdown
Modes allocation to sub- [MSM] Modes and transitions
systems
Logical architecture [LAB] Logical components, components exchanges
Functional allocation to [LAB] Logical components, components exchanges
sub-systems Logical functions, functional exchanges
Internal behavior [LFS], [LES] Functional and exchanges scenarios
22/08/2022
p
a
Table of content
g
e
1
7
22/08/2022
p
a
PA : Physical Architecture layer description
g
e
1 The Physical Architecture layer aims at defining “how the system is built”, taking into account the constraints
8 generated by the technological choices. It describes the real components that constitute the AIDA system, in
two steps : allocation of functions to the behavior components, and deployment of the behavior components on
the physical node components (see Arcadia documentation for more details).
System level functions [PDFB], [PFBD] Physical functions, functional exchanges
breakdown
Modes allocation to sub- [MSM] Modes and transitions
systems
Functional allocation to [LAB] Physical functions, functional exchanges
behavior components
Deployment on node [LAB] Node components, physical links and paths
components Behavior components, components exchanges
Internal behavior [PFS], [PES] Functional and exchanges scenarios
Physical architecture [PAB] Node components, physical links and paths
22/08/2022
Component level N/A Native Capella requirements

requirements
p
a
PA : Physical Architecture layer features
g
e
1 Additionally to the main objects, the PA layer contains some features that complete the information contained in
9 the model. They are described in the table below.
Features Capella objects Purpose
Main functional chains Functional chains Identify the functional chains related to the various control
related to drone control [PFCD] functionalities : control mode selection, automatic
and data transmission navigation control, attitude control, payload control,…
Communication buses Physical paths Identify the implementation of the communication buses
and power supply wiring and the power supply principles
Physical links type Property value + Identify the type of the physical links : electrical, wireless,
diagram styler mechanical, IHM,…
(necessitate the PVMT
add-on)
FDAL and IDAL Property value + Identify the DAL level associated to functions and
diagram styler components (resulting from safety analysis)
(necessitate the PVMT
add-on)
22/08/2022

AIDA Model Description V4.5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

AIDA Model Description V4.5

Uploaded by

Copyright:

Available Formats

AIDA study case

Architecture model in Capella

0 Before opening the Capella model

1 Capella model overview

Copyright (c) 2016-2025 IRT AESE (IRT Saint Exupéry).

5 AIDA : Aircraft Inspection by Drone Assistant

Drone Pilot Drone Control Desk Drone Aircraft

• This document describes the model of the AIDA Architecture package.

0 Before opening the Capella model

1 Capella model overview

Capella layers/visions AIDA model description

Arcadia note: Description of Walk-Around process – identification of

Previously Step 1 (performed Step 2 Step 3.1 (performed T4

Operational and Operational and

architecture architecture architecture V4.5) architecture

: Consistency not ensured : Consistency ensured

0 Before opening the Capella model

1 Capella model overview

Point of view Capella Diagrams Capella Objects

0 Before opening the Capella model

1 Capella model overview

Point of view Capella Diagrams Capella Objects

0 Before opening the Capella model

1 Capella model overview

0 Before opening the Capella model

1 Capella model overview

Component level N/A Native Capella requirements

You might also like