#3715 accepted task

Add Requirements Engineering chapter to RTEMS Software Engineering Handbook

Reported by: Sebastian Huber Owned by: Sebastian Huber
Priority: normal Milestone: 6.1
Component: doc Version: 6
Severity: normal Keywords: qualification
Cc: Blocked By:
Blocking: #3703

Description

The chapter should cover the following topics:

  • Overview and introduction
  • Evaluation of tools for requirements management
  • Selected tool for requirements management
  • Evaluation of data models and formats for the requirements
  • Definition of data model and format actually used for the project (may overlap with tool)
  • Requirements management workflow used in the project
  • Requirements on requirements, e.g. derived from standards such as ECSS-E-ST-10-06C
  • Requirement identifiers used to ensure traceability

Change History (5)

comment:1 Changed on Mar 4, 2019 at 1:10:43 PM by Sebastian Huber

Status: assignedaccepted
Summary: Add Requirements Engineering chaper to RTEMS Software Engineering HandbookAdd Requirements Engineering chapter to RTEMS Software Engineering Handbook

comment:2 Changed on Mar 4, 2019 at 11:02:03 PM 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?

comment:3 Changed on Mar 4, 2019 at 11:06:15 PM by Joel Sherrill

I agree with Chris. A trade study of requirements tools shouldn't end up in the handbook. Perhaps our requirements for a tool.

  • open source
  • supports format XXX for interchange
  • supports links for requirement derivation
  • ...

comment:4 Changed on Mar 7, 2019 at 7:34:38 AM by Sebastian Huber

Yes, maybe this is not the best place for the tool overview. I though it would be helpful in case someone asks in two years, why did you use this, have you considered that, etc.? Should I add a ticket for the tool selection instead?

comment:5 in reply to:  4 Changed on Mar 7, 2019 at 9:00:27 PM by Chris Johns

Replying to Sebastian Huber:

Yes, maybe this is not the best place for the tool overview. I though it would be helpful in case someone asks in two years, why did you use this, have you considered that, etc.?

A brief rational can be helpful, but the details can be distracting. I feel the simpler and more direct this document is the more effective it will be.

Should I add a ticket for the tool selection instead?

Yes, it can links to mailing lists discussions and attachments and it is easy to link too.

Note: See TracTickets for help on using tickets.