ARTIST II November 2007 Presented by Gert Döhmen Airbus Deutschland GmbH Embedded System Development for Distributed Networked Computing Platforms ARTIST2 meeting on Integrated Modular Avionics
Content 1. The SPEEDS Project 2. Distributed Networked Computing Platform 3. Using SPEEDS for IMA Development ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 2
The SPEEDS Project SPEculative and Exploratory Design in System s Engineering SPEEDS is funded by the European Commission under Contract IST-033471 ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 3
SPEEDS technological contribution Fool-proof" representations of Systems [HRC: Heterogeneous Rich Components]. Formal technical analyses to verify compatibility, consistency, of Systems [ADT; Analysis Design Techniques]. Process Control/Monitoring Techniques to evaluate the progress, maturity, of Systems Projects. [SDS; Speculative Design and Seamless Access; Process Adviser]. Integrated development with transparent access to information and transfer of data between tools [Speeds Bus]. ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 4
Heterogeneous Rich Components Objectives To provide a characterization of components of electronic components supporting all phases, levels, and viewpoints of electronic system design Allowing complete re-use (across multiple platforms, across multiple organizations, and/or as part of design libraries) Allowing characterization of allowed/assumed environments of component (for all viewpoints) Basis for (de-facto) standardization, compatible with Autosar Component Model As basis for tool-independent meta-model for capturing and validating function networks Supporting semantic based integration of industry standard System & SW design tools (UML, Matlab-Simulink/Stateflow, ASCET, ) Supporting view-point specific and cross viewpoint requirement capturing, modeling, analysis and design ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 5
Heterogeneous Rich Component HRC Follows Design by Contract Paradigm : Assumptions reflect current degree of knowledge of anticipated design context Determine boundary conditions on actual design context for each viewpoint under which component is promising its services are decorated with confidence levels horizontal and vertical Promises Are guaranteed if component is used in assumed design context horizontal and vertical Is organized per viewpoint : Behavior, Coordination, Safety, Real-Time,. Assumed ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 6 SL FL EL HL But allow specification of cross viewpoint dependencies from neighbors From/by higher design levels From/by lower design levels Promised to neighbors
SPEEDS Design Entities User s View: COTS modeling tools RT Builder TM Simulink TM Rhapsody TM SCADE TM Speeds Metamodel Speeds Semantic Foundation b? a c AK ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 7 BR GR LR SK component C begin interface I begin. end view functional begin end view safety begin end view Real-time begin end.. end C A 1 A 2 for all viewpoints v: b! L(A(OutI.v.pr c j )) L(A(InI.v.assm i ))
HRC Meta-model Based on SysML Added Features (Assumptions, Promises) Various Viewpoints Linking layers (Functional Network, LRU/ECU, Physical Architecture,...) Available as Standalone Meta-model or SysML Profile Heterogeneous Modelling Integration of Design Tools Multiple Viewpoints (Functional, Real-Time, Safety,...) Analysis Functional and non-functional characteristics Interaction between viewpoints Design Space Exploration ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 8
SPEEDS Engineering Bus SCADE Rhapsody Simulink Modeling Y Modeling X SCADE Simulink DOORS Rhapsody Tool Z RT-Builder Adapter Adapter SPEEDS Engineering Bus Process Advisor Model Repository Analysis Y Analysis X ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 9
November 2007 Distributed Networked Computing Platform ARTIST2 meeting on Integrated Modular Avionics
Distributed Networked Computing Platform IMA-Core ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 11 RDC IOM CPM IOM CPM CPM CPM CPM CPM Global Functions: Consolidation, BITE, Diagnostic IMA-core-bricks AFDX Function A Function B Function C Field-Bus: TT-Bus, A429, CAN, ) RDC Smart Smart Smart Smart Smart Smart Smart Smart Smart Smart Smart Smart Smart Common: - HW Components - Development Process - Tools
Different IMA Topologies Rear Bay DC1, Ess DC1, Ess DC1, DC2 DC1, DC2 LDG Bay AFDX Avionic Bay Avionic Bay Analogue, Analogue, Discret, Discret, Digital Busses Analogue, Analogue, Discret, Discret, Digital Busses AFDX Cabin Network DC Bus DC Bus Fully integrated and centralized CPIOMs CPM centralized IOM/ RDC distributed... and the right Function to Resource Allocation? DC1, Ess DC1, DC2 AFDX Avionic Bay Analogue, Analogue, Discret, Discret, Digital Busses AFDX Cabin Network DC Bus CPM centralized IOMs/ RDCs per section ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 12
A380 IMA Development Process Aspects Classification of Configuration Parameter (Module, Global, Local). Hardware/OS specific configuration parameter. Manual assignment of resources supported by databases. Automated tool-chain to produce the load. Module Supplier A Function Supplier 1 Module Supplier B Function Supplier 2 Function Supplier 3 Information & Data Flow for one Module Type System Depart. 1 System Depart. 2 System Depart. 3 ATA XX Module Integrator ADCN & IMA ATA 42-10 IMA ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 13 Airbus
Specification architecture & validation Aircraft Level ATA 42-10 IMA ATA XX TLAR, TLSRD TLAR, TLSRD System Level SRD preliminary sizing SRD common requirements Module PTS specific requirements MICS SDD, SID CCD PTS Equipment Level Bare mod. supplier development V&V SES UG UD Bare module MCCT SES XX application ALCS MACT ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 14
November 2007 Using SPEEDS for IMA development ARTIST2 meeting on Integrated Modular Avionics
Needed Improvements of Development Process Ubiquitous seamless model-based design access hiding heterogeneity and semantic diversity of representations and methods, and providing a design-centric access to all design activities. During all design phases, process steps must be guided by an estimation how far overall requirements (e.g. safety, costs) are fulfilled. This speculative design can be based on HRC analysis methods. High flexibility and robustness with respect to late changes and overlapping design activities. More guidance and tool support is required for systematic and structured: system requirements analysis system concept evaluation system design & system equipment specification ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 16
Rich Component Models RCM with Get status information IN 1 IN 2 Comp Out Assumption : Status available every t ms Promise : Status == enabled implies Out == V within t ms Get information based on sensor values Provide control commands Contract Specification : Textual: Pattern Language Graphical: Extended State Machines ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 17
1 1 «block» 1 RCM-based Process for a Single Function Formalized Communication btw. OEM and Supplier: Concept and Definition Phases (new System policy) Functional System Specification Documents: Definition Non-functional aspects Use of design assumptions Complexity FRD / TLSRD (Top Level System Req.) SRD ATA XX (System Req. Document) SDD / SID ATA XX (System Description / Interfaces) PTS PTS (Equipment (Equipment XX) TBD) Formal Specifications by HRCs: ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 18 LLS_CAN 8 1 TA_CAN LLS LLS_CAN TA_CAN[ 8] Toilet_Assembly :Toilet_ MPI_WF WF_MPI 1 CAN_Bus Waste_Sy stem Toilet_Ass embly_class Water_Faucet MPI:MPI_Clas s VGMC_CAN GWDU_CAN[2] 2 GWDU_CAN VGMC VGMC_CAN Galley _Waste_Disposal_Unit:Ga A/C System Black-box Model MPI_CAN A/C System White-box Model (A, P) TA_CAN (A, P)
Alignment of IMA and System Specifications Abstract Fkt. A Integrated Performance & Resources Model based on. Evaluation and optimization of different IMA architectures. Abstract Fkt. B Abstract Fkt. C Abstract IMA Platform Integrated Performance & Resources Model Requirements IMA Model IMA Configuration Aircraft Architecture Design ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 19 Optimization Evaluation
RCM for IMA development Overview Requirements Performance & Resources Model (A, P) IMA System X System Specification Design Space Exploration System Design Decomposition of (Ai, Pi) ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 20
RCM for IMA development Requirements Model Requirements Performance & Resources Model (A, P) OEM Supplier (A, P) Design Space Exploration (A, P) Decomposition Of Guaranteed by OEM (resp. other suppliers) (A, P) (Ai, Pi) (A, P) To be Guaranteed by Supplier ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 21
RCM for IMA development Architecture Analysis Requirements Performance & Resources Model (A, P) OEM Supplier Design Space Exploration Decomposition Of Guaranteed by OEM (resp. other suppliers) (Ai, Pi) To be Guaranteed by Supplier ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 22
RCM for IMA develop. Architecture Optimization Requirements Performance & Resources Model (A, P) OEM Supplier Component Design Design Space Exploration Decomposition Of Guaranteed by OEM (resp. other suppliers) (Ai, Pi) To be Guaranteed by Supplier ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 23
RCM for IMA develop. Contract Decomposition Requirements Performance & Resources Model (A, P) OEM Supplier Design Space Exploration Decomposition Of Guaranteed by OEM (resp. other suppliers) (Ai, Pi) To be Guaranteed by Supplier ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 24
RCM for IMA development Overview Requirements Performance & Resources Model (A, P) IMA System X System Specification Design Space Exploration System Design Decomposition of (Ai, Pi) ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 25
System Design on IMA looking ahead SPEEDS Methodology supports: Formal system specifications including non-functional aspects. Early identification of errors in the specification due to formal analysis. Multi-System Integration in early phases based on contracts. Increased transparency of system functionality during implementation at the supplier. ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 26
AIRBUS DEUTSCHLAND GMBH. All rights reserved. Confidential and proprietary document. This document and all information contained herein is the sole property of AIRBUS DEUTSCHLAND GMBH. No intellectual property rights are granted by the delivery of this document or the disclosure of its content. This document shall not be reproduced or disclosed to a third party without the express written consent of AIRBUS DEUTSCHLAND GMBH. This document and its content shall not be used for any purpose other than that for which it is supplied. The statements made herein do not constitute an offer. They are based on the mentioned assumptions and are expressed in good faith. Where the supporting grounds for these statements are not shown, AIRBUS DEUTSCHLAND GMBH will be pleased to explain the basis thereof. AIRBUS, its logo, A300, A310, A318, A319, A320, A321, A330, A340, A350, A380, A400M are registered trademarks. ARTIST2 meeting on Integrated Modular Avionics November 2007 Page 27