RMsis implements a simple workflow for approving requirements, which does not compromise with the system usability, while providing the required functionality. Essentially there are 3 major stages for a requirement s:
- Informal, where a requirement is analyzed for it's value.
- Assigned, where it is allocated an owner (Analyst / Manager) and is analyzed and developed further.
- Approved, where it is reviewed and approved by the Manager / Requirements Owner.
...
- Definitions
- Approval: approval is typically at the Project Level, with the Manager taking the final call to say that the requirement is adequately specified.
- Baseline: On the other hand, Baseline is an agreement between all stakeholders, that they agree to a specific version of one or more Requirements.
- Sequence of Operations
- Requirement is elaborated.
- It is reviewed and updated.
- The approved version is committed.
- It is released for review by all the stakeholders.
- The agreed upon version is committed.
- Chosen set of committed requirements are baselined.
States of a Requirement
A When the Requirements Approval Workflow is enabled, a Requirement can have the following states, as shown in the Status column:
...
State Transition Diagram
Transitions
For Unplanned Table transitions
| From Status | Target Status | Permissions |
|---|---|---|
| New | Valid, Invalid, Deferred | Edit All Unplanned Requirements |
| Valid | Invalid, Deferred | Edit All Unplanned Requirements |
| Invalid | Valid, Deferred | Edit All Unplanned Requirements |
| Deferred | Valid, Invalid | Edit All Unplanned Requirements |
...