RTEMS Requirement Management Tools

Jose Valdez Jose.Valdez at edisoft.pt
Mon Mar 25 10:09:35 UTC 2019


Hello All,

Sorry for my late reply and thanks to the people who answered these questions. I believe these positive answers reinforces the choice for doorstop.

For the requirement analysis, I meant that this feature is descoped (too much complexity to make it) and it will be the responsibility of the user to define good requirements. Of course, in future, if a good requirement analysis tool shows up, it could be integrated in the Qualification Toolchain.

Best regards

José

From: devel [mailto:devel-bounces at rtems.org] On Behalf Of Joel Sherrill
Sent: sexta-feira, 22 de março de 2019 20:18
To: sebastian huber
Cc: RTEMS
Subject: Re: RTEMS Requirement Management Tools



On Fri, Mar 22, 2019 at 5:28 AM Sebastian Huber <sebastian.huber at embedded-brains.de<mailto:sebastian.huber at embedded-brains.de>> wrote:
Hello,

I searched a bit for Doorstop use cases. I found this:

https://arxiv.org/abs/1807.05422

It was used for this NASA mission:

https://wfirst.gsfc.nasa.gov/observatory.html

Ironically enough, WFIRST uses RTEMS for at least one subsystem.

Plus we have the report on the list from DLR.

--joel



--
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190325/01210253/attachment-0002.html>


More information about the devel mailing list