taking the Interrupt Manager Extension as an example for the qualification process

Joel Sherrill joel at rtems.org
Wed May 22 14:11:07 UTC 2019

On Wed, May 22, 2019 at 3:37 AM Ting Peng <ting.peng at embedded-brains.de>

> Hello,
> 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
> (
> https://docs.rtems.org/doxygen/branches/master/group__rtems__interrupt__extension.html)
> 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).

What other candidates are up for consideration?

This may or may not  be a good candidate but at first glance it avoids a
lot of the
areas with complexity like thread management and services based on open
Both of which are special areas we need to solve. I always worry that a
first candidate
or example avoids addressing issues. which will be encountered elsewhere.

Is it possible to define the challenging areas in RTEMS for the process and
identify the first few components that cover the challenging areas?


> Thank you for reading this email.
> Best regards,
> Ting Peng
> _______________________________________________
> devel mailing list
> 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/20190522/d6204b89/attachment-0002.html>

More information about the devel mailing list