Qualification of RTEMS SMP (ECSS)

Wed Dec 5 14:56:52 UTC 2018

Yes, ESA and we are going to get as much as possible feedback from the space community just to try to agree and define the RTEMS Space Profile. The RTEMS Space profile will be the subset of RTEMS that will be subject to Space Qualification. Any interested party that would like to participate in the pre-qualification, is invited.

We understand. We also do not intend to “overflow” the community. We intend to have the major discussions in the qualification@ but everyone is invited to participate in the mailing list. With the execution of the project we could also change, if we need.

We believe that we could need to ask some questions around in order to start to define the plans of the qualification.

Thank you in advance for the support, kind regards,
Helder

From: users [mailto:users-bounces at rtems.org] On Behalf Of Joel Sherrill
Sent: terça-feira, 4 de dezembro de 2018 16:59
To: Amaan Cheval
Cc: rtems-users at rtems.org
Subject: Re: Qualification of RTEMS SMP (ECSS)

On Tue, Dec 4, 2018 at 10:53 AM Amaan Cheval <amaan.cheval at gmail.com<mailto:amaan.cheval at gmail.com>> wrote:
This is great news!

- Is there a way for other interested parties to join the effort (volunteers from the community)?

I am at hte Flight Software Workshop and the ESA person here says they will get input from the space community.

From an RTEMS perspective, some will happen on devel@ but there is a qualification@ mailing list. As a community, we MUST figure out how to provide and maintain as much of the technical information as possible needed for qualification and certification efforts. But we must not crush an open source project with weight. Ensuring our processes are well-defined, tests are repeatable, continuous integration testing, etc are all important. Doing things better is one push.

The other push may ended up with things only applicable to qualification efforts. Those must be maintained by those interested in qualification. The formal analysis may be in this bucket.

This is an opportunity to do things better and do ground-breaking work for an open source project. We all just need to do our bit.

FWIW I am presenting tomorrow at the FSW and have 3 slides on qualification efforts including this one.

--joel

- 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<mailto: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<mailto: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<mailto: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<mailto:users at rtems.org>
http://lists.rtems.org/mailman/listinfo/users
_______________________________________________
users mailing list
users at rtems.org<mailto: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/20181205/6f4589a1/attachment-0002.html>