Qualification of RTEMS SMP (ECSS)

[Amaan Cheval]

This is great news!

- Is there a way for other interested parties to join the effort
(volunteers from the community)?
- Will all the work also be planned on public channels (devel@, public WIP
branches, etc.)?

On Tue, Dec 4, 2018 at 6:49 PM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> Hello,
>
> I would like to announce to the RTEMS community a 24 month project
> sponsored by the European Space Agency (ESA).
>
> The main goal of the project is to enable European space missions to use
> RTEMS as a software product in criticality category C (this is basically
> category B without independent software verification and validation,
> ISVV). Criticality category C means:
>
>
> http://ecss.nl/standard/ecss-q-st-80c-rev-1-software-product-assurance-15-february-2017/
>
> "Software that if not executed, or if not correctly executed, or whose
> anomalous behaviour can cause or contribute to a system failure
> resulting in: Major consequences"
>
> In ECSS-Q-ST-40C  major consequences are characterized in Table 6-1 as a
> major mission degradation without effects to the outside world of the
> system. A future activity may perform ISVV to enable a use in category B
> settings.
>
> The qualification will be done according to ECSS standards
> (ECSS-E-ST-40C and ECSS-Q-ST-80C). The standards are available at
>
> http://ecss.nl/
>
> free of charge after registration.
>
> The project consists of four tasks.
>
> 1. Qualification toolchain
>
> This task aims to produce a tool chain so that qualification related
> work can be carried out efficiently. For example: document generation,
> test suite runs (including code coverage), test reporting, test result
> archiving, code metrics, static code analysis, traceability (e.g.
> requirements to tests), etc.
>
> 2. RTEMS SMP qualification data package
>
> This task covers the main RTEMS components (source code, tests,
> documentation; new: requirements document, ECSS standard tailoring) so
> that a data package for space mission consumers can be generated.
>
> 3. RTEMS SMP formal verification
>
> This is a research project. The aim is to apply formal methods for the
> verification of a subset of the RTEMS SMP algorithms.
>
> 4. RTEMS SMP application porting
>
> The goal of this task is to port an existing uniprocessor space software
> from RTEMS 4.8 (RTEMS Improvement by Edisoft) to RTEMS SMP. The
> algorithms used by the software needs to be parallelized.
>
> The project partners are:
>
> * Edisoft (prime)
>
> * Lero (https://www.lero.ie/) with Lero researchers from Trinity College
> Dublin and University of Limerick
>
> * Jena-Optronik GmbH and embedded brains GmbH
>
> The results of this activity should be open source and available to the
> RTEMS community. The actual planning needs to be discussed at
> devel at rtems.org in the next couple of weeks. One of the first topics is
> the definition of a space profile which defines the feature set subject
> to this project.
>
> --
> Sebastian Huber, embedded brains GmbH
>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany
> Phone   : +49 89 189 47 41-16
> Fax     : +49 89 189 47 41-09
> E-Mail  : sebastian.huber at embedded-brains.de
> PGP     : Public key available on request.
>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>
>
> _______________________________________________
> users mailing list
> users at rtems.org
> http://lists.rtems.org/mailman/listinfo/users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20181204/6b49c932/attachment-0002.html>