Conferences and supporting programme
A Lean Process for Ariane 6 Flight Software Development
The current context of Space Systems development (more competitors, less budget) requires to put in place innovative engineering processes and methods which permit to be efficient all along the development while keeping these products to the necessary quality level; not forgetting of course the System specificities (high reactivity, high availability, mission critical, safety). The method which has been put in place to realize the Ariane 6 Functional Design and Flight Software development aims at reducing the gap between System and Software, improving the System consistency, reactivity in change implementation and early problems discovering. The Ariane 6 Functional Design is strongly based on a formalised co-engineering approach, to decompose the System level Function, down to “Functional Units”. A Functional Unit is a set of both Hardware items (electrical and/or fluidic) and Software items organised so as to provide the common set of services needed to the launcher and its mission (including also “Assembly Integration & Test” aspects); in addition to the identified Functional Units (as much as 25 for Ariane 6), a central On board function called Launcher Management gathers the Mission Management and the Launcher Modes Management. The Mission Management is responsible for scheduling and synchronizing the different orders necessary to execute the mission, the Launcher Modes Management has to execute the different launcher configuration changes requested by the Mission Management. The modelling artefacts used to formalize the Design of a Functional Unit have been chosen to be easily implemented in the Flight Software (from specification to code) while keeping an adequate level of abstraction, appropriate for a System Functional definition (there is no Software level Design element in the Functional Unit Design). At Software level, all elements defined during the Functional Unit Design activity are directly used to structure the Software specification reusing the same modelling artefacts (to improve consistency and traceability between System and Software). Dedicated tools have been put in place to generate automatically part of the Flight code from Functional Unit Design elements (SysML) and the Software Design elements (Ada 2012). The presentation will cover: • Presentation of the launcher Main Functions and their specificities, • Functional Unit approach: guidelines (from Functions to Functional Units definition), implementation of the method at System level (involving System and Software team in co-engineering), • Flight Software Design main drivers which fit with the System Design approach, • Process applied in Software team to define the Flight Software specification, Design and code (modelling, automatic code generation) from Functional Unit System Design details, • Tools to support the method from System to Flight code (COTS, in house tools and in house reusable library), • Feedback after one year of effective operational use of the method.
--- Date: 27.02.2018 Time: 2:30 PM - 3:00 PM Location: Conference Counter NCC Ost