Requirements Format

[Joel Sherrill]

On Tue, Feb 26, 2019 at 8:57 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

> Hello Joel,
>
> On 26/02/2019 15:44, Joel Sherrill wrote:
> > Hi
> >
> > I have mentioned this before but reading ticket 3703, you obviously
> > didn't remember it.
>
> I remember it and I think I proposed to use ReqIF.
>
> > ReqIF is an OMG standard for representing
> > requirements in XML format. It was designed to facilitate requirements
> > exchange between partnering organizations.
> >
> > https://www.omg.org/spec/ReqIF/About-ReqIF/
> >
> > It appears to be supported by all the major requirement tools including
> > DOORS and LDRA's toolset. Importantly, it is supported by the Eclipse
> > Requirements Management Framework (RMF) and the ProR tool
> >
> > https://en.wikipedia.org/wiki/Requirements_Modeling_Framework
> > https://www.eclipse.org/rmf/
> > https://www.eclipse.org/rmf/pror/
> >
> > This is a solved problem. We should not define our own XML format.
> > One exists and there is a set of open source tools we can use to work
> > with requirements.
>
> Did you try to use these tools? It is a nightmare.
>

We were starting to look at some requirements tools for another project.
Some of the feedback will be from people with experience with other
requirements tools. My impression is that requirements tools generally
suck.


>
> We evaluated also Papyrus:
>
> https://www.eclipse.org/papyrus/
>
> I will try to summarize the problems we encountered using ReqIF in the
> next days.
>

The format or the Eclipse tools? The format is separate from the tools.

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