Sanplex tracks Requirement changes using two fields: Status and Development Stage. The following section explains these two fields.

图1

I. Requirement Status

The Status field is used to track the workflow state of a Requirement. It includes five statuses: Draft, Under Review, Active, In Change, and Closed.

The corresponding workflow actions are Create, Review, Change, Close, and Activate. The status transition flow is shown below:

图2

图3

II. Requirement Stage

Requirements also have a Stage field, which is used to describe the current stage of an active Requirement during the development process.

For Development Requirements, the available stages are:

Not Started, Planned, Project Initiated, In Design, In Development, Development Completed, In Testing, Testing Completed, Accepted, Acceptance Failed, Released, Closed

For Business Requirements, User Requirements, and parent Development Requirements, the available stages are:

Not Started, Planned, Project Initiated, In Development, In Delivery, Delivered, Closed

图4

How does the stage of a Development Requirement change?

One option is to update the stage manually through editing. However, the recommended approach is to define Task types carefully when creating Tasks, such as Design, Development, and Testing. Sanplex can then automatically calculate the Development Stage of the Requirement based on changes in those Tasks, using the following rules:

1. If a Development Requirement is not linked to a Project and is not linked to a Plan, its stage is Not Started.

2. If a Development Requirement is linked to a Plan but not yet linked to a Project, its stage is Planned.

3. If a Development Requirement is linked to a Project but no Task has started yet, its stage is Project Initiated.

4. If a Development Requirement is linked to a Project and Tasks have been created:

   • If at least one Design Task is in progress, and all Development and Testing Tasks have not started, the stage is In Design.
   • If all Design Tasks are completed, and all Development and Testing Tasks have not started, the stage is Design Completed.
   • If at least one Development Task is in progress, and all Testing Tasks have not started, the stage is In Development.
   • If all Development Tasks are completed, and all Testing Tasks have not started, the stage is Development Completed.
   • If at least one Testing Task is in progress, the stage is In Testing.
   • If all Testing Tasks are finished, but some Development Tasks are still unfinished, the stage is still In Testing.
   • If all Testing Tasks and all Development Tasks are finished, the stage is Testing Completed.

5. The Acceptance stage must be confirmed manually by the product manager. After confirmation, the stage becomes Accepted or Acceptance Failed.

6. If a Development Requirement is linked to a Release under Product > Releases, and the Release status changes to Released, the Requirement stage becomes Released.

7. If a Development Requirement is manually closed, its stage becomes Closed.

Stage rules for Business Requirements / User Requirements / parent Development Requirements

The stages of Business Requirements, User Requirements, and parent Development Requirements cannot be edited manually. Sanplex automatically calculates their stage based on the status of the Requirement itself and the stages of its child Requirements, using the following rules:

1. If a Business Requirement, User Requirement, or parent Development Requirement is not linked to a Plan or Project, and none of its child Requirements is linked to a Plan or Project, its stage is Not Started.
2. If the Requirement itself or any of its child Requirements is linked to a Plan, and neither the Requirement nor its child Requirements is linked to a Project, its stage is Planned.
3. If the Requirement itself or any of its child Requirements is linked to a Project, and no child Requirement has started any Task yet, its stage is Project Initiated.
4. If any child Requirement has started a Task, the stage of the Business Requirement, User Requirement, or parent Development Requirement becomes In Development.
5. If any child Requirement is linked to a Release or has been completed and closed, the stage becomes In Delivery.
6. If all child Requirements are linked to a Release or have been completed and closed, the stage becomes Delivered.
7. If a Business Requirement, User Requirement, or parent Development Requirement is manually closed, its stage becomes Closed.