TASTE is ESA’s established toolchain targeting heterogeneous systems implementing a model-based system/software engineering approach. At its core, it utilizes AADL and ASN.1 models for architecture and data description respectively. System behaviour can be described via various methods, including, but not limited to, SDL, Simulink models, C or Ada. TASTE can be used both for system design, analysis, simulation and actual implementation targeting embedded devices.

Recently TASTE has been enriched with the support for CCSDS SOIS EDS (SEDS, or simply EDS further within this document), an XML based standard for specifying data interfaces offered by flight hardware such as sensors and actuators. The support is provided via conversion of SEDS to Interface View, ASN.1/ACN and SDL.

Currently TASTE users can design the logical system architecture and its logical behaviour using Interface View and applicable Function source language editors. When the logical architecture is deployed onto physical architecture using Deployment View, TASTE generates all the necessary glue and communication code. Such an approach is quite convenient, but is has two major drawbacks:

• users lack control over the protocol details, which may hinder interoperability and make it impossible to meet certain interface requirements

• the actual communication drivers have to be provided for the runtime in a traditional, non-MBSE fashion, making the final, complete software not fully modelled

The objective of this project is to resolve this issues, reinforcing software re-use and interoperability by providing the capabilities to:

• choose between different packetization schemes for communication interfaces

• design communication device drivers using MBSE

• use SEDS in modelling of the communication device drivers

• use the designed communication device drivers with traditional code, outside of TASTE