Authors:
Hassna Louadah
1
;
Roger Champagne
1
;
Yvan Labiche
2
and
Yann-Gaël Guéhéneuc
3
Affiliations:
1
École de Technologie Supérieure (ÉTS), Canada
;
2
Carleton University, Canada
;
3
École Polytechnique Montréal, Canada
Keyword(s):
Interface, Interface Control Documents, Avionics Systems, IMA.
Related
Ontology
Subjects/Areas/Topics:
Domain-Specific Modeling and Domain-Specific Languages
;
Languages, Tools and Architectures
;
Methodologies, Processes and Platforms
;
Model-Driven Software Development
;
Reasoning about Models
;
Software Engineering
;
Systems Engineering
Abstract:
Avionics systems, along with their internal hardware and software components interfaces, must be well defined and specified (e.g., unambiguous, complete, verifiable, consistent, and traceable specification). Such a specification is usually written in the form of an Interface Control Document (ICD), and represents the cornerstone of the avionics system integration activities. However, there is no commonly accepted language to define and use these ICDs and no common definition of what an ICD is or should contain. Indeed, avionics companies define their own, proprietary ICDs and processes. In this paper, we first identify the pieces of information that an ICD should contain for both federated and IMA open systems. Then, we propose a data extraction process that enables better understanding and more efficient extraction of open avionics systems interface specifications, and provides a clearer vision on the information needed to build a model driven solution for modeling avionics system i
nterfaces, our long-term goal. We validate this process by applying it on a set of open avionics sub-system standards and the results have shown its feasibility.
(More)