#3715: Add Requirements Engineering chapter to RTEMS Software Engineering Handbook -----------------------------+------------------------------ Reporter: Sebastian Huber | Owner: Sebastian Huber Type: task | Status: accepted Priority: normal | Milestone: 6.1 Component: doc | Version: 6 Severity: normal | Resolution: Keywords: qualification | Blocked By: Blocking: 3703 | -----------------------------+------------------------------
Comment (by Chris Johns): How does the quality of RTEMS and it's requirements depend on the evaluation and selection of the tools for requirement management? I can understand the quality of the requirements effecting the quality of RTEMS but not the tools used to capture them? Why have the process, ie a sort of log book, in the engineering handbook? I would have expected this document to contain the out come of the discovery process and not the process itself. I am concerned adding these things just creates a liability for the project. Can an email archive can perform this task? -- Ticket URL: <http://devel.rtems.org/ticket/3715#comment:2> RTEMS Project <http://www.rtems.org/> RTEMS Project
_______________________________________________ bugs mailing list bugs@rtems.org http://lists.rtems.org/mailman/listinfo/bugs