Industrial Avionics Working Group 19/04/07 Architecture Integration

Industrial Avionics Working Group

19/04/07

Architecture Integration


19/04/07

Integration Arguments

•Split design and arguments at the APOS

•Application Layer Integration Argument

•Architecture Integration Argument


19/04/07

Objectives of Architecture Integration Argument

• Argument that the elements of ‘The Architecture’, together provide the guaranteed behaviour and properties, that require close interaction between the layers.

• Argument about system management functions, including error handling.

• Link the various services provided by the architecture components in such a way that they provide integrated architectural services.

• Argument that all dependencies for the OSL and MSL have been satisfied.

• Structure the Integration argument to minimise impact of change.


19/04/07

Linked modules

Architecture Integration

Application Layer Integration

RunTime BluePrint

OSL

MSL

System Issues


19/04/07

Behaviour

• To claim, argue and provide evidence that the behaviour of the integrated components assures the set of required Architecture level functions, namely:

– Scheduling– Partitioning – Initialisation – Data transfer with integrity

Goal: Arch_Integrated_Behaviour

Integration of Architectural elements provides assured behaviour properties.

Strat: Arch_Level_FunctionArgument over required Architecture behaviour at the integrated level

Goal: Architecture_Partitioning

Architecture constrains and protects process interactions

Goal: Architecture_Scheduling

Architecture controls scheduling of multiple processes and TCs


19/04/07

SchedulingGoal: Architecture_Scheduling


Goal: Temporal_Partitioning

The architecture supports a guaranteed allocation of time to individual items

Strat: Scheduling_Support

Argument over the scheduling mechanism and its correct configuration.

Goal: Scheduling_Configuration

RTBP configuration of scheduling (validity and consistency) is assured.

Con: Sched_Items

Schedulable Items consist of both Processes, and Transfer Connections (TCs). TCs have no memory component other than that assigned to the OS process. Refer to Project Specific Software Requirment Specifications for the Architectural Components.

Goal: Configuration

The Architecture and Applications are properly configured / re-configured according to the RTBP









19/04/07

Partitioning - Top









19/04/07

Services

• To claim, argue and provide evidence that services provided by the OSL are re-published as from the Architecture level

– GSM functions (event driven) (Fault Management, Configuration)

– OS services (to Applications, via APOS) Strat: Init_And_ConfigArgument over functional components of System Management and initialisation.

Goal: Configuration

The Architecture and Applications are properly configured / re-configured according to the RTBP

Goal: GSM_Fault_Management

Faults are detected and handled as required

Goal: Arch_Init

The Architecture software is correctly initialised for {stack a}

Goal: Arch_System_Management

The Architecture implements required system management functions correctly


19/04/07

Dependencies

• To claim, argue and provide evidence that all dependencies for the OSL and MSL have been satisfied.

Match OSL Dependenciesto MSL Guarantees–One way of doing

this is to use a Safety Case Contract.

Documents

Industrial Avionics Working Group 19/04/07 Architecture Integration