A key goal of the ARINC 653 (APEX) specification is the achievement of software re-use through provision of a standard operating environment for applications software. Reuse of software can be achieved in two ways: (i) by re-using operating systems, which provide common functions across the application spectrum, e.g., health monitoring, process management, communications mechanisms; and (ii) by re-using the applications software which provides avionics applications functions. By provision of a standardised interface between applications and operating system, ARINC 653 facilitates both forms of re-use. Operating systems are by nature tightly coupled to the underlying hardware platform, re-use of operating systems is therefore limited to modules employing the same hardware unless a new standard such as COEX (Core Executive Interface) can be tightly defined. Applications software is often dependent on the actual aircraft implementation. Direct re-use of applications will not always be possible; however, by use of ARINC 653, it will be possible to re-use individual partitions of an application in other applications. ARINC 653 is language-dependent and within languages such as Ada there is scope for functionally identical implementations which are syntactically different. Unless definitive language implementations of ARINC 653 are adhered to, language issues will become a major hurdle to re-use. A large cost of avionics development (particularly software) is the cost of certification.
ARINC 653-achieving software re-use
Das Digitalkommunikationssystem ARINC 653 und das Problem der Software-Wiederverwendbarkeit
Microprocessors and Microsystems ; 20 , 8 ; 479-483
1997
5 Seiten, 3 Quellen
Article (Journal)
English
`ARINC 653 - achieving software re-use'
British Library Conference Proceedings | 1996
|Software Fault Protection with ARINC 653
IEEE | 2007
|Field Repairable Arinc 404 and Arinc 600 Filter Connectors
Emerald Group Publishing | 1990
|Guidelines for Modelling the ARINC 653 Software Architecture
British Library Conference Proceedings | 2008
|IEEE | 2017
|