Odd Qualification Related Documentation

[Joel Sherrill]

Hi

I am in the tail end of a customer's Level C (headed to B) project and we
are tidying up documents that I don't recall having had a lot of
discussion. With all the work on the Software Engineering Guide and
automated generation, most of this likely already is addressed to some
extent but we may want to review what we have or have planned versus
expectations.

Is there a plan with all the generation of code and documentation to
generate Software Test Plan ? I would suspect that a traditional Software
Test Plan falls nicely as a chapter inside the Engineering Guide.

What about a Software Test Description? Usually a Software Test Description
is more painful as it focuses on what's in each test executable and,
sometimes, each specific unit test.

What about Software Test Reports? The rtems-tester output is the starting
point but I don't know how that compares against the qualification
expectations for this report.

Then there is the Software Version Description that goes along with a
release. We would need to compare that also.

Just curious since these are things we do but may not have laid out even
plans for what should be the goal. If we need to seek outside guidance
again, it would be good to know that and prepare a plan/checklist for what
is missing.

Thanks.

--joel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200820/9e76d5d8/attachment.html>