Increasing complexity of Software Systems necessitates the focus on system function and behaviour, abstracting from lower-level implementation details of the programming languages. Modelling languages start to find their way into the development process, from requirements specification and system-software co-engineering, up to operations, through development and verification. Use of models increases the level of specification formality and provides a possibility for model simulation and formal analysis to verify certain aspects of the system from the early lifecycle phases.

Performance of European processors for space applications have been increasing over the years, from the ERC32 (25MHz, current missions) to the single-core Leon2/3 (100MHz, upcoming missions) to the next generation processor (multicore, Leon4, future missions). Simulators are needed throughout the software, spacecraft and operations development. Simulator performance needs to keep the pace with the processors. Instruction set simulators for the ERC32 could keep up with real-time simulation of the overall spacecraft.

An ESA study is starting considering the system aspects of the use of the multi-core for our applications, and this study will define the final technical solutions. However, the trend seems to be towards the use of a hypervisor. If this is confirmed, there could be a convergence between the various hypervisors used for partitioning, for security and for multi-core. An environment for hypervisor could therefore be reused, which is the focus of the the proposed activity.

The Integrated Modular Avionics for Space (IMA-SP) concept introduces the role of System Architect to the spacecraft avionics domain. The System Architect has the key responsibility for negotiating the avionics resource allocation with the hosted application suppliers and then performing a system-level verification to ensure that the configured system is capable to host the applications and meet the system requirements. The allocation of the platform resources is an iterative process between the Architect and the application suppliers.

Address the open points raised in COrDeT2: i) open points in final report, ii) integrate OBCP building block interface specification from parallel GSTP5 element 2 activities, iii) define unique meta-model of component model and add semantic description, iv) incorporate feedback from OBSW reference architecture consolidation activities (GSTP5 element 2 activities).Harmonize the OBSW reference architecture specification with the outcomes from IMA-SP activity by implementing the recommendations from SISTORA activity.

N/A

The model based software engineering consists in expressing the software functional requirements with models. In order to get the requirements right as early as possible, system-software co-engineering is necessary, in this case avionics-software co-engineering, where the software functional models are placed consistently into an avionics model.The avionics model represents the physical architecture on which the software will run (deployment view).

Currently employed approaches to FDIR development are poorly phased with regard to the main Software Development activities. They have tendency of starting late, awaiting for the system Failure Mode Effects and Criticality Analysis (FMECA) data. If functional FMECA is sometimes available, its update into the physical FMECA is seldom ready for software development. FDIR definition is not adequately synchronised with the nominal Software System behaviour.

GRAVMOD-2 is a software tool developed by Astos Solutions and GMV for ESA.

It adds guidance analysis and on-board manoeuver capabilities to the gravitational modelling core of GRAVMOD-1 originally developed by DEIMOS. The unique mathematical models and architecture make it particularly suitable for the modelling of the gravity field of highly irregular bodies such as small moons, asteroids or comets. GRAVMOD-2 is composed of two main modules: