quirements tool evaluation is nearing an end, posting that as a
patch in Rest for the Guide would be a good start. This will then be
another section in the same chapter.
--joel
>
>
> Best regards
>
>
>
> José
>
>
>
>
>
> *From:* Joel Sherrill [mailto:j...@rt
...@rtems.org]
Sent: terça-feira, 26 de março de 2019 14:32
To: Jose Valdez
Cc: rtems-de...@rtems.org
Subject: Re: Design Tools for RTEMS Qualification Toolchain
On Mon, Mar 25, 2019 at 12:20 PM Jose Valdez
mailto:jose.val...@edisoft.pt>> wrote:
Hello Joel,
Thank you for your reply.
I me
Hello José,
since the RTEMS software architecture, detailed design and
implementation exists already we don't need a design tool. We need
documentation tools for the software architecture and detailed design. I
would simply use what we have and this is Doxygen + Graphviz + MSC +
PlantUML.
F
ation Suite. Today, I am sure the rtems-docs build system
supports both PlantUML and ditaa. If it doesn't support graphviz/dot and
mscgen
(used by our Doxygen), then that's has to be addressed.
--joel
>
>
> Best regards
>
>
>
> José
>
>
>
> *From:* Joel S
)
architectural components source code (that’s why defining architectural
components in text files will be useful).
Best regards
José
From: Joel Sherrill [mailto:j...@rtems.org]
Sent: segunda-feira, 25 de março de 2019 16:31
To: Jose Valdez
Cc: rtems-de...@rtems.org
Subject: Re: Design Tools for
You haven't defined what you mean by design tool. The implication seems to
be
something to do UML-ish things in.
PlantUML with DITAA, mscgen, and dot (e.g. graphviz) as backups is a pretty
good combination for drawing diagrams.
But they are not design tools IMO. They are tools to produce diagrams
Hello,
I have been doing the Design Tools investigation. I had investigated several
tools with the following features in mind:
è Open Source and active project
è Text-file based tool, which allows git control and manipulation of the files
with other tools (to add extra functionality)
è Diagr
