RTEMS Requirement Management Tools

[Joel Sherrill]

On Fri, Mar 22, 2019 at 8:03 AM Sebastian Huber <
sebastian.huber at embedded-brains.de> wrote:

>
>
> On 21/03/2019 14:32, Joel Sherrill wrote:
> > 5. Is it possible to have custom fields? I worked on a project where
> > requirements were
> > tagged with project phase and HW/SW. Alternatively, can we add
> > comments to the YAML
> > files. Or who cares since the author information is in git.
>
> According to the Doorstep documentation:
>
> https://doorstop.readthedocs.io/en/latest/reference/items/
>
> "Extended attributes
>
> In addition to the standard attributes, Doorstop will allow any number
> of custom attributes (key-value pairs) in the YAML file. The extended
> attributes will not be part of a published document, but they can be
> queried by a 3rd party application through the REST interface or the
> Python API.
> Example:
>
> In this example, an extended attribute invented-by is added to the item.
>
> invented-by: some.guy at email.com"
>
> Use of a standard format such as YAML is nice since it enables us to
> read these requirements files quite easily.
>

This is awesome! Chris and I discussed that it would be desirable to
generate
our requirement documents in Rest. If this is implemented, then that tool
could
know the extended attributes.

>
> [...]
> > Is the documentation and/or tutorial sufficient to get us started?
> > Whatever tool is adopted,
> > common tasks will have to be documented like we do with git use.
>
> Similar to the Git overview in
>
> https://docs.rtems.org/branches/master/eng/vc-authors.html
>
> we need something similar for the requirements tool.
>

+1

>
> --
> 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/20190322/aab7c48e/attachment-0002.html>