Page Comparison

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

1. Informal, where a requirement is analyzed for it's value.
2. Assigned, where it is allocated an owner (Analyst / Manager) and is analyzed and developed further.
3. Approved, where it is reviewed and approved by the Manager / Requirements Owner.

In the context of RMsis, it is also important to state the difference between Approval and Baseline; which is done through the following description:

• 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
  1. Requirement is elaborated.
  2. It is reviewed and updated.
  3. The approved version is committed.
  4. It is released for review by all the stakeholders.
  5. The agreed upon version is committed.
  6. Chosen set of committed requirements are baselined.

States of a Requirement

A Requirement can have the following states, as shown in the Status column:

...

1. Review State is just indicated by the attribute value and can be used by any viewer to filter out the requirements in Review State.
2. When an Owner is assigned to a requirement, the state automatically changes to Assigned.
   1. If the user tries to change the state to Assigned, he/she should be given an error asking to assign a user in order to change state.

Notes on Review State

• In the initial release of this workflow, there are no explicit operations involved with the "Review State".
• The Owner / Manager is expected to informally manage the review process.

Ownership

The ownership will fall into three categories

...