[RTEMS Project] #3701: RTEMS SMP Pre-Qualification (ECSS)

Tue Feb 26 13:42:08 UTC 2019

#3701: RTEMS SMP Pre-Qualification (ECSS)
-----------------------------+-------------------------------
 Reporter:  Sebastian Huber  |       Owner:  Sebastian Huber
     Type:  project          |      Status:  accepted
 Priority:  normal           |   Milestone:  6.1
Component:  unspecified      |     Version:  6
 Severity:  normal           |  Resolution:
 Keywords:  qualification    |  Blocked By:  3702, 3703, 3705
 Blocking:                   |
-----------------------------+-------------------------------
Description changed by Sebastian Huber:

Old description:

> This ticket summarises activities carried out by a 24 month project
> sponsored by the European Space Agency (ESA). The project start was
> February 2019.
>
> 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 according to
> [http://ecss.nl/standard/ecss-q-st-80c-rev-1-software-product-
> assurance-15-february-2017/ ECSS-Q-ST-80C]:
>
> "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 [https://ecss.nl/standard/ecss-e-st-40c-software-general-requirements/
> 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 major 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:
>
> * [http://www.edisoft.pt/ Edisoft] (prime) and
> [http://www.cister.isep.ipp.pt/ CISTER] from Portugal
>
> * [https://www.lero.ie/ Lero] with Lero researchers from Trinity College
> Dublin and University of Limerick from Ireland
>
> * [https://www.jena-optronik.de/ Jena-Optronik GmbH] and [https
> ://embedded-brains.de/ embedded brains GmbH] from Germany
>
> The results of this activity should be open source and available to the
> RTEMS community.

New description:

 This ticket summarises activities carried out by a 24 month project
 sponsored by the European Space Agency (ESA). The project start was
 February 2019.

 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 according to
 [http://ecss.nl/standard/ecss-q-st-80c-rev-1-software-product-
 assurance-15-february-2017/ ECSS-Q-ST-80C]:

 "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 [https://ecss.nl/standard/ecss-e-st-40c-software-general-requirements/
 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 major tasks.

 1. Qualification toolchain[[BR]][[BR]]
    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[[BR]][[BR]]
    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.[[BR]][[BR]]
    * #3702: Space profile for RTEMS SMP
    * #3703: Technical Specification (TS) for space profile
    * #3705: Software Design Document (SDD) for space profile
       * #3704: Review and update Doxygen recommendations
       * #3706: Create a hierarchy of RTEMS software components using
 Doxygen groups
       * #3707: Assign each code file to a Doxygen group

 3. RTEMS SMP formal verification[[BR]][[BR]]
    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[[BR]][[BR]]
    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:

 * [http://www.edisoft.pt/ Edisoft] (prime) and
 [http://www.cister.isep.ipp.pt/ CISTER] from Portugal

 * [https://www.lero.ie/ Lero] with Lero researchers from Trinity College
 Dublin and University of Limerick from Ireland

 * [https://www.jena-optronik.de/ Jena-Optronik GmbH] and [https
 ://embedded-brains.de/ embedded brains GmbH] from Germany

 The results of this activity should be open source and available to the
 RTEMS community.

--

--
Ticket URL: <http://devel.rtems.org/ticket/3701#comment:7>
RTEMS Project <http://www.rtems.org/>
RTEMS Project