<div dir="auto">Thanks for the tool tip Jan.<div dir="auto"><br></div><div dir="auto">Does this import into Doors? Is there a converter to ReqIF for importing to other tools?</div><div dir="auto"><br></div><div dir="auto">Would you be willing to submit the scripts and tools you have around it?</div><div dir="auto"><br></div><div dir="auto">Any horrible gotchas?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Feb 27, 2019, 4:59 AM <<a href="mailto:Jan.Sommer@dlr.de">Jan.Sommer@dlr.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In one project we use Doorstop (<a href="https://doorstop.readthedocs.io/en/latest/reference/items/" rel="noreferrer noreferrer" target="_blank">https://doorstop.readthedocs.io/en/latest/reference/items/</a>) due to a lack of an actual DOORS license for every partner.<br>
For software developers it is quite easy to handle as it has a CLI and can be easily integrated with git as everything is a text file.<br>
However, it only gives you the basics. With some scripting we used it to generate our Latex-requirements documents with traceability matrices.<br>
<br>
Best regards,<br>
<br>
Jan<br>
<br>
<br>
> -----Ursprüngliche Nachricht-----<br>
> Von: devel [mailto:<a href="mailto:devel-bounces@rtems.org" target="_blank" rel="noreferrer">devel-bounces@rtems.org</a>] Im Auftrag von Sebastian<br>
> Huber<br>
> Gesendet: Mittwoch, 27. Februar 2019 08:43<br>
> An: <a href="mailto:joel@rtems.org" target="_blank" rel="noreferrer">joel@rtems.org</a><br>
> Cc: <a href="mailto:rtems-devel@rtems.org" target="_blank" rel="noreferrer">rtems-devel@rtems.org</a><br>
> Betreff: Re: Requirements Format<br>
> <br>
> On 26/02/2019 16:15, Joel Sherrill wrote:<br>
> ><br>
> ><br>
> > On Tue, Feb 26, 2019 at 8:57 AM Sebastian Huber<br>
> > <<a href="mailto:sebastian.huber@embedded-brains.de" target="_blank" rel="noreferrer">sebastian.huber@embedded-brains.de</a><br>
> > <mailto:<a href="mailto:sebastian.huber@embedded-brains.de" target="_blank" rel="noreferrer">sebastian.huber@embedded-brains.de</a>>> wrote:<br>
> ><br>
> > Hello Joel,<br>
> ><br>
> > On 26/02/2019 15:44, Joel Sherrill wrote:<br>
> > > Hi<br>
> > ><br>
> > > I have mentioned this before but reading ticket 3703, you obviously<br>
> > > didn't remember it.<br>
> ><br>
> > I remember it and I think I proposed to use ReqIF.<br>
> ><br>
> > > ReqIF is an OMG standard for representing<br>
> > > requirements in XML format. It was designed to facilitate<br>
> > requirements<br>
> > > exchange between partnering organizations.<br>
> > ><br>
> > > <a href="https://www.omg.org/spec/ReqIF/About-ReqIF/" rel="noreferrer noreferrer" target="_blank">https://www.omg.org/spec/ReqIF/About-ReqIF/</a><br>
> > ><br>
> > > It appears to be supported by all the major requirement tools<br>
> > including<br>
> > > DOORS and LDRA's toolset. Importantly, it is supported by the<br>
> > Eclipse<br>
> > > Requirements Management Framework (RMF) and the ProR tool<br>
> > ><br>
> > > <a href="https://en.wikipedia.org/wiki/Requirements_Modeling_Framework" rel="noreferrer noreferrer" target="_blank">https://en.wikipedia.org/wiki/Requirements_Modeling_Framework</a><br>
> > > <a href="https://www.eclipse.org/rmf/" rel="noreferrer noreferrer" target="_blank">https://www.eclipse.org/rmf/</a><br>
> > > <a href="https://www.eclipse.org/rmf/pror/" rel="noreferrer noreferrer" target="_blank">https://www.eclipse.org/rmf/pror/</a><br>
> ><br>
> <br>
> The ProR and ReqIF Studio look like mostly dead projects to me. They<br>
> didn't manage to build a reasonable user base and community in the last<br>
> couple of years. I experienced stability problems with both tools (e.g.<br>
> NULL pointer exceptions). The documentation is not really great and if<br>
> you start to try things beyond simple examples it gets hairy. I don't<br>
> want to work with such tools and waste my time.<br>
> <br>
> > ><br>
> > > This is a solved problem. We should not define our own XML format.<br>
> > > One exists and there is a set of open source tools we can use to<br>
> > work<br>
> > > with requirements.<br>
> ><br>
> > Did you try to use these tools? It is a nightmare.<br>
> ><br>
> ><br>
> > We were starting to look at some requirements tools for another project.<br>
> > Some of the feedback will be from people with experience with other<br>
> > requirements tools. My impression is that requirements tools generally<br>
> > suck.<br>
> ><br>
> ><br>
> > We evaluated also Papyrus:<br>
> ><br>
> > <a href="https://www.eclipse.org/papyrus/" rel="noreferrer noreferrer" target="_blank">https://www.eclipse.org/papyrus/</a><br>
> ><br>
> <br>
> My experience and one of our trainees with Papyrus are not really great.<br>
> This is a complex tool you have to use intensively in your day to day<br>
> work to be productive. There are some videos available, but getting<br>
> started is quite difficult. I guess most people learn it with the help<br>
> of colleagues. I also guess that it is used via in-house versions and<br>
> not all known bugs are fixed in the public version. It is overkill just<br>
> to manage requirements with it.<br>
> <br>
> ><br>
> > I will try to summarize the problems we encountered using ReqIF in<br>
> > the<br>
> > next days.<br>
> ><br>
> ><br>
> > The format or the Eclipse tools? The format is separate from the tools.<br>
> <br>
> First, we need a data model for the requirements in the scope of RTEMS.<br>
> You need this model also for ReqIF. ReqIF is the Requirements<br>
> Interchange Format, the emphasis is on interchange. It is an open<br>
> question, if it is suitable as a project internal representation for our<br>
> requirements. At the moment I tend to use some sort of XML file and use<br>
> a simple text editor.<br>
> <br>
> --<br>
> Sebastian Huber, embedded brains GmbH<br>
> <br>
> Address : Dornierstr. 4, D-82178 Puchheim, Germany<br>
> Phone : +49 89 189 47 41-16<br>
> Fax : +49 89 189 47 41-09<br>
> E-Mail : <a href="mailto:sebastian.huber@embedded-brains.de" target="_blank" rel="noreferrer">sebastian.huber@embedded-brains.de</a><br>
> PGP : Public key available on request.<br>
> <br>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br>
> <br>
> _______________________________________________<br>
> devel mailing list<br>
> <a href="mailto:devel@rtems.org" target="_blank" rel="noreferrer">devel@rtems.org</a><br>
> <a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a><br>
</blockquote></div>