ARINC 653P3B 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 (Application Programming Interface (API)) between the application programs and the Operating System (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 catgories

• Partition management

• Process management

• Time management

•  Inter partition communication

• Intra partition communication

• Health Monitoring

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 3A provides conformity test specifications for ARINC 653 Required Services that are defined in Part 1.

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 the ARINC Specification 653. Any application, which 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.