This document presents a data extraction process for avionics systems' interface specifications. It aims to provide innovative tools to efficiently integrate equipment from different suppliers using interface control documents (ICDs). The process leverages model-driven engineering approaches. It was developed based on an analysis of common avionics architecture standards and interface specifications. The extraction process provides a better understanding of interface specifications and is a first step towards a complete model-driven solution for modeling avionics system interfaces. Future work includes completing an industrial partner's model-driven solution and enabling semi-automated verification of interfaces.

1. A Data Extraction Process for Avionics Systems’
Interface Specifications
Hassna Louadah1
, Roger Champagne1
, and Yvan Labiche2
,
Yann-Ga¨el Gu´eh´eneuc 3
1 ´Ecole de technologie sup´erieure (´ETS), 2Carleton University,
3 ´Ecole Polytechnique de Montr´eal, Canada
4th International Conference on Model-Driven Engineering and Software Development
(MODELSWARD 2016), Rome, Italy
February 21, 2016

2. Outline
1 Motivation
Context & challenges
Objective
2 Background
Avionics systems interfaces
Main sources of information
3 Data extraction process
Illustration
4 Conclusion

3. Motivation
Background
Data extraction process
Conclusion
Context & challenges
Objective
Avionics systems
More and more complex
(35 to 40%) of civil aircraft costs and over (50%) of military
aircraft costs
Architectures
Federated (one function = one computer)
IMA (multiple funtions, shared ressources)
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 3 / 14

4. Motivation
Background
Data extraction process
Conclusion
Context & challenges
Objective
Context
Moving to IMA architecture
Interoperability =⇒ well defined interfaces
Interface specification :
Physical and electrical characteristics
Communication protocols
Exchanged data
Documented in interface control documents (ICD)
Heterogenious
Integration based on ICDs is tedious and error prone
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 4 / 14

5. Motivation
Background
Data extraction process
Conclusion
Context & challenges
Objective
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 5 / 14
Objective
To provide innovative tools enabling an efficient way of integrating
equipment from different suppliers, described by their ICDs, to build
avionic systems.

6. Motivation
Background
Data extraction process
Conclusion
Context & challenges
Objective
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 5 / 14
Objective
To provide innovative tools enabling an efficient way of integrating
equipment from different suppliers, described by their ICDs, to build
avionic systems.
⇓
Leverage the strengths of model-driven engineering for the
development, use and verification of ICDs, in order to :
Enable unambiguous description and representation of interfaces
and ICDs
Enable automatic verification and analysis of interfaces
Enable automatic generation of human-readable ICDs in different
formats

7. Motivation
Background
Data extraction process
Conclusion
Context & challenges
Objective
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 5 / 14

8. Motivation
Background
Data extraction process
Conclusion
Avionics systems interfaces
Main sources of information
Avionics systems
Architectures and interfaces
FIGURE – federated vs. IMA architectures interfaces
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 6 / 14

9. Motivation
Background
Data extraction process
Conclusion
Avionics systems interfaces
Main sources of information
Main sources of information
ARINCs and RTCA
1 Federated systems
ARINC 7xx & ARINC-429
2 IMA systems
ARINC 7xx & ARINC-429
RTCA/DO-297, RTCA/DO-255, and ARINC-651
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 7 / 14

12. Motivation
Background
Data extraction process
Conclusion
Illustration
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 9 / 14

13. Motivation
Background
Data extraction process
Conclusion
Illustration
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 9 / 14

21. Motivation
Background
Data extraction process
Conclusion
Illustration
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 11 / 14

23. Motivation
Background
Data extraction process
Conclusion
Conclusion
New data extraction process for avionics systems’ interface
specification
Better understanding and more efficient data extraction process of
open avionics systems interface specifications
Clear vision on what an interface specification should include
First step towards designing a complete model-driven solution
for modelling avionics systems interfaces
Future works :
Complete our industrial partners model-driven solution with the
missing information needed for modelling interfaces of both
federated and IMA systems
Enable semi-automated verification process of the interfaces
MODELSWARD (2016) A Data Extraction Process for Avionics Systems’ Interface Specifications 21/02/2016 13 / 14