Industrial Avionics Working Group 19/04/07 Architecture Integration

Industrial Avionics Working Group 19/04/07 Integration Arguments Split design and arguments at the APOS Application Layer Integration Argument Architecture Integration Argument

Industrial Avionics Working Group 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.

Industrial Avionics Working Group 19/04/07 Linked modules

Industrial Avionics Working Group 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

Industrial Avionics Working Group 19/04/07 Scheduling

Industrial Avionics Working Group 19/04/07 Partitioning

Industrial Avionics Working Group 19/04/07 Partitioning - Top

Industrial Avionics Working Group 19/04/07 Partitioning – next level

Industrial Avionics Working Group 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)

Industrial Avionics Working Group 19/04/07 Dependencies To claim, argue and provide evidence that all dependencies for the OSL and MSL have been satisfied. Match OSL Dependencies to MSL Guarantees –One way of doing this is to use a Safety Case Contract.