taking the Interrupt Manager Extension as an example for the qualification process
ting.peng at embedded-brains.de
Wed May 22 12:29:39 UTC 2019
As to the requirements documentation, we need to decide a place to store
those requirements documentation. One suggestion is to store in
rtems/reqs folder, the other is to store in rtems-docs/reqs folder. We
suggest to put the requirements related files (by Doorstop) inside
rtems/reqs so that the versions of both source code and the requirements
could be consistent. If you wouldn't express any disagreement, then we
will use /rtems/reqs. Thank you for your attention.
On 5/22/19 10:37 AM, Ting Peng wrote:
> As we need to choose one RTEMS software component as an example to
> have an overview of the qualification process, Sebastian Huber
> suggests to take the Interrupt Manager Extension
> as the example. The goal is to integrate the Interrupt Manager
> Extension in the Interrupt Manager. The example will cover the topics
> of requirements, test plans, test code, test reports, code coverage,
> other metrics, software architecture, software detailed design,
> traceability items (open issue) and Interface control document (ICD)
> vs. RTEMS Classic API Guide (open issue).
> Thank you for reading this email.
> Best regards,
> Ting Peng
More information about the devel