Requirement Management tools

[Jose Valdez]

Hello Joel,

Indeed the project intends to implement the traceabilities to source code and to the tests. Please see below what we have in mind currently for the tool (note that the diagram is not complete and also this architecture is not final).

[cid:image002.png at 01D4D822.984ABEB0]

Best regards

José


From: Joel Sherrill [mailto:joel at rtems.org]
Sent: segunda-feira, 11 de março de 2019 13:36
To: Jose Valdez
Cc: devel at rtems.org; Qualification RTEMS SMP Tech
Subject: Re: Requirement Management tools

Thanks Jose.

I think we would like reports to be in Rest so we can use Sphinx and include them with the RTEMS Documentation Suite. I doubt any of the tools will meet this requirement.  I posted just before this that if we go with Doorstop, I can see adding this capability.

I like the concept of managing supporting artifacts the same way the code is. This means we want the files managed in git, able to be version controlled and ideally diffed. This puts a negative factor on binary formats. Binary formats also have a tendency to lock you into tools.

I assume we will want to be able to submit fixes. Make sure the tool is really open source.  If I looked at the right repo, the eclipse.org<http://eclipse.org> ProR source looks stagnant while a commercial product which appears to be open source is active. I am unsure where recent changes go. Just be a bit cynical.

I know it is premature but are there any thoughts yet on how to implement fully traceable requirements? To source and then to tests?

--joel

On Mon, Mar 11, 2019 at 8:24 AM Jose Valdez <Jose.Valdez at edisoft.pt<mailto:Jose.Valdez at edisoft.pt>> wrote:
Hello all,

I am José Valdez from EDISOFT.

I am working for the RTEMS SMP project which aims to pre-qualify RTEMS SMP for space missions.

I am investigating tools which may partially automate the software development process, i.e: Requirements Management, Design and Unit test tools and source code analysis and metrics tools.

Currently I have been investigating myself and also requested Sebastian Huber for some tools he knows. With this information I am building an excel sheet with the summarized information about the tools (not yet complete). Could you please help in this discussion, indicating, as far as you know:

==> if do you know other open source Requirement Management Tools

==> if do you know the tools provided and if they are/are not suitable for RTEMS SMP

==> if do you remember any tool feature not listed in excel sheet, that is relevant or if do you know any feature not listed that may block its selection for RTEMS SMP

As far as I have currently discussed with Sebastian Huber, we have the following ideas:

==> Tools which use databases are to be avoided

==> Deprecated tools (“dead projects”) are to be avoided

==> Could be interesting to have a tool which can import/export ReqIf standard file

Looking forward for your suggestions

Best regards

José
_______________________________________________
devel mailing list
devel at rtems.org<mailto:devel at rtems.org>
http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190311/a3fc4c26/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.emz
Type: application/octet-stream
Size: 25351 bytes
Desc: image001.emz
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190311/a3fc4c26/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 72132 bytes
Desc: image002.png
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190311/a3fc4c26/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oledata.mso
Type: application/octet-stream
Size: 31783 bytes
Desc: oledata.mso
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190311/a3fc4c26/attachment-0003.obj>