Implementierung der Systemkon-trolle und Systemsteuerung gem äß ASAAC

1. Informationstag zur Informatik, TU Chemnitz 8.11.2005 Burkhard Balser, Michael Förster, EADS, MT321 Implementierung der Systemkon-trolle und Systemsteuerung gemäß ASAAC

2. Inhalt ASAAC Overview ASAAC Software and System Concept Blueprints Generic System Management Design and Implementation Details

3. ASAAC: involved Nations and Companies Germany • Dasa Military Aircraft • Dasa Defence and Civil Systems • ESG Elektroniksystem- undLogistik GmbH • LITEF GmbH U.K. • GEC - Marconi Avionics • British AerospaceMilitary Aircraft & Aerostructures • Smith Industries Aerospace Budget: France • Dassault Aviation • Thomson CSF - Radar & Contremesures • Thomson CSF - Communications • Dassault Electronique • Sextant Avionique DEM 110,000,000

4. 2004 2000 Stage 1 (15 Months) Stage 2 (45 Months) T0 Time Demonstrations + Standards Validation Concept 1 Concept 2 Concept n Con-cepts Std. Arch Core Arch Std. NET Std. S/W Core + Applications Demo Specs 1st draft Stan-dards StdH/W 104 Documents The ASAAC Program ASAAC: State of Work The three national ASAAC Program was finished in time

5. Inhalt ASAAC Overview ASAAC Software and System Concept Blueprints Generic System Management Design and Implementation Details

6. Application Layer Functional Applications Application Management Operating System Layer Generic System Management Run Time Blueprint Operating System Aircraft Independent, Hardware Dependent Module Support Layer ASAAC Software Model SystemManagement Aircraft Dependent,Hardware Independent APOS Aircraft Independent,Hardware Independent SMBP SMOS MOS

7. ASAAC System Concept: Management Operations System Manager Mission Mode Management Pilot/Application Fault Tolerance Fault Valid Avionic System State Reconfiguration Ground Crew ITM Blueprints Power Initialisation + Shutdown System Design

8. Inhalt ASAAC Overview ASAAC Software and System Concept Blueprints Generic System Management Design and Implementation Details

9. Blueprints • Blueprints are used at all Development Steps: • Designtime: Designtime Blueprints • Resource Blueprints • Application Blueprints • Runtime: Runtime Blueprints • Blueprints provide a formal context free Description of the related Elements • The Content of the Blueprints is defined by a Grammar • for Runtime Blueprints the Grammar is expressed in eBNF in the Standards for Software

10. Inhalt ASAAC Overview ASAAC Software and System Concept Blueprints Generic System Management Design and Implementation Details

11. APOS (incl. Communication) S M O S GSM FM CM SMBP BPM HM RTBP MOS/NII Hardware GSM embedded in ASAAC Standards and Guidelines • Standards • APOS • SMOS • SMBP • MOS/NII • Guidelines: Definition of the component’s behaviour • GSM with HM, FM, CM and BPM

12. GSM embedded in the Generic ASAAC Design Application APOS APOS APOS-Lib GSM R T O S - A P I S M O S FM CM Process Management SMBP BPM HM RTBP RTOS Virtual Channel Management Legend: MOS/NII ASAAC Standards ASAAC Components MSL RTOS Components APOS Adaptation Layer BSP Application Code

13. GSM Task: Configuration of Communication Application Application RTBP APOS APOS APOSLib APOSLib S M O S - L i b S M O S VCM GSM VCDrv VCMgt NII MSL Virtual Channel Managementimplements Configuration Services • Configure Interfaces • Create TC • Create VC • Attach VC to TC • Attach VC to Process • Destroy TC • Destroy VC • Detach VC from TC • Detach VC from Process

14. GSM Task: Configuration of Processes Application RTBP APOS APOSLib R T O S - A P I S M O S - L i b S M O S GSM Process Manager ProcMgt MOS MSL Process Managementimplements Configuration Services • Create Process • Setup Scheduling • Run Process • Stop Process • Destroy Process

15. GSM Task: Health Monitoring and Fault Management Application RTBP APOS APOSLib R T O S - A P I S M O S - L i b S M O S GSM Process Manager ProcMgt MOS MSL Process Management implementsServices for Fault Management • Log Error • Raise Application Error • Get Error Information • Destroy Process • Get Fault • Get Thread State

16. ASAAC System Concept: Hierarchy of the GSM’s Aircraft Level Integration Area Level Integration Area Level Integration Area Level Integration Area Level GSM Resource Element Level Resource Element Level Resource Element Level Exchange of Messages between GSM’s • Delegation of Responsability: • Notification (of State or Error) is sent to the next higher Level • Command is sent to the next lower Level • for each Level the Blueprints define the Generation and Handling of Notifications and Command • All Messages between the Levels are routed over VC's

17. Inhalt • ASAAC Overview • ASAAC Software and System Concept • Blueprints • Generic System Management • Design and Implementation Details

18. The GSM Project • System Requirement • Implementation to be used in future EADS M Projects • Minimalisation of Dependencies of O/S Interfaces • Design flexible to be incorporated in existing Environments with ASAAC or none ASAAC Behaviour • Design flexible to incorporate existing Components of HM/FM/CM • Implementation Requirements • Using UML for Design and Code Generation • Using Design Pattern for better Understanding • Using ADA as the Target Language

19. Elements of the GSM GSM FM CM BPM HM • The GSM consists of • Health Monitor • Fault Manager • Configuration Manager • and 1 Interface • SMBP • and its Implementation • Blueprint Manager

20. Generic GSM Component Design APOS Communication S M O S S M B P Conversion Threads of Control • Generic Design of all GSM Components • SMOS at RE Level only: • Configuration of the RE, including GSM Elements • Controling of Processes, Communication and Hardware • Receiving Faults of Hardware and Software • Using Interfaces of the Standard only • Instantiation of the real Component via a Factory

21. Configuration via CM-RE APOS APOS GSM Broker Communication Communication S M O S S M B P S M O S S M B P Conversion Conversion Threads of Control Threads of Control Inter GSM Component Communication • Simplifies Implementation of Components • only one Channel for receiving ore sending messages • Routing wil be done by an external Component • Configuration of the GSM Broker is defined in the Blueprints • GSM Broker can translate Messages to communicate with GSM implemented differently

22. Comprehension (1) • Implementation gives a full ASAAC System Hierarchy for other Projects with • Resource Element Level • Integration Area Level • Aircraft Level as described in the ASAAC Standards and Guidelines

23. Comprehension (2) • Inheritance and Design Pattern allow a flexible Implementation and Reuse of Elements • GSM Broker: Adaptor to external System Managers • Converter: Adaptor to existing System Management Components for Health Monitoring, Fault Management or Configuration Services

24. Comprehension (3) • O/S Dependencies are dedicated to explicite Elements: • Process Management for O/S specific Process Instantiation and Control • Virtual Channel Management for O/S specific Communication Instantiation and Control • ADA hides O/S specific Tasking and Synchronisation to the GSM Implementation