Requirements Management: Approve And Baseline (include E-Signature)
Problem to solve
For many teams doing requirements management, the need to be able to define specific baseline configurations of the 'approved' requirements. This is important when the requirements are used to drive software development that is part of larger hardware systems are integrated with the software.
In regulated industries, the need to have trusted and immutable electronic signatures is a requirement for them to manage their requirements.
Further details
(Include use cases, benefits, and/or goals)
- Be able to track version changes of requirements
- Be able to 'freeze' a set of requirements based on a specific version
- Be able to identify the person who 'approved' a single or a group of requirements (Date, title, etc)
Proposal
What does success look like, and how can we measure that?
(If no way to measure success, link to an issue that will implement a way to measure this)
Links / references
This issue/need emerged in a discussion w/ a health care IT leader, and their specific need to capture and track 'esignatures' and approvals of their requirements.