scope:

This document specifies extensions (i.e., optional services) to the API specified in ARINC Specification 653 Part 1. This document specifies both the interface, and the behavior of the services. Behavior is specified to the extent needed to describe behavior relevant to calling applications. In defining the extensions herein, it is assumed that the required services of the API comply with ARINC Specification 653 Part 1. Readers of this document should be fully acquainted with the content of Part 1.

Where necessary, assumptions are made as to the support or behavior provided by the core Operating System (O/S) and module. This should not be construed as a specification for the core O/S or module hardware. However, where the core O/S or module hardware does not coincide with the stated assumptions, the API behaviors specified herein may not match the actual behavior.

ARINC 653 is intended for use in a partitioned software environment. In order to assure a high degree of portability, aspects of the partitioned environment are discussed and assumed. However, this standard does not define the complete system, hardware or software requirements for partitioning, nor does it provide guidance on proper implementation of partitioning and in particular, robust partitioning. It must not be construed that compliance to this standard in any way assures robust partitioning.

Purpose

This document defines Extended Services for the Application Program Interface (API) specified by ARINC Specification 653: Part 1, Required Services and Part 4, Subset Services. Each of these extensions may be implemented individually, or collectively. When implemented, it is expected that the interface and behavior will comply with this standard as outlined in Section 4, Compliance.