ARINC 653P3A-1 PDF

Purpose of Compliance Demonstration

ARINC Specification 653, Part 1 defines the basic set of services that addresses the necessary functionalities for core services, as well as the necessary facilities that have to be provided through the interface (API Application Programming Interface) between the application programs and the OS. It describes the invocation of those services and the data structures with specified semantics to ensure the accurate binding and running of the applications on the OS.

These core services are grouped into the following major service categories:

• Partition management, which allows partitions with different criticality levels to execute in the same core module without affecting one another spatially or temporally.

• Process management and control, which includes all the resources necessary to manage the different processes. For example, process control and process scheduling, taking into account the specific processes attributes, and process state transitions.

• Time management is one of the most critical features to be provided by the OS within multiple application systems. In accordance with ARINC 653 philosophy, time is independent of process or partition execution. All time values are related to the core module time and not relative to the partition or process.

• Inter partition communication mechanisms, which allow the communication of messages between two or more partitions executing either on the same core module or on different core modules.

• Intra partition communication mechanisms, which allow the communication of messages between processes within the same partition without the overhead of the global message passing processing.

• Health Monitoring functions, which monitor and report platform/application/software faults and failures and help to isolate faults and to prevent failures from propagating.

ARINC Specification 653, Part 2 complements the basic set of services defined in Part 1, with extensions to the core services as well as some additional services deemed optional.

These optional services are grouped in the following categories:

• File System

• Sampling Port Data Structures

• Multiple Module Schedules

• Logbook System

• Sampling Port Extensions

• Service Access Points

• Name Service

• Memory Blocks

• Health Monitoring Extensions

• Queuing Port List Service

ARINC Specification 653, Part 3B provides conformity test specifications for ARINC 653 Extended Services that are defined in Part 2.

ARINC Specification 653, Part 4 defines a subset of the services defined in Part 1, constrained by some restrictions:

• No Health Monitoring extension services are available.

• The only timeout value accepted is zero.

The goal to take a compliance test process as specified within this ARINC standard for an implemented OS is to demonstrate and to prove that the interface behavior is in compliance with ARINC Specification 653. Any application that will be installed upon this OS, can rely on this compliance and the portability of applications is more supported. A compliance demonstration finally gives more confidence to both sides, to the OS providers, as well as to the organization responsible to integrate the applications. A standard specification for compliance test procedures provides a unique test scenario with predetermined conditions for all test candidates, which increases significantly the level of confidence.