Requirement Specification Lifecycle

This lifecycle controls the states through which a requirement specification progresses as its requirements are satisfied by implemented features.

The Requirement Specification lifecycle includes these states:

This page discusses:

Private

Only the Owner or object owner can see and edit the requirement specification in the "Private" state. It is not visible to other members of the Collaborative Space. The object owner can create and check in the files for the requirement specification in this state.

In Work

A requirement specification is created in the "In Work" state. When the requirement specification is in this state, comments, chapters, and requirements can be added and edited as needed, and it can be reviewed by the appropriate people. The requirement specification can be promoted to the "Frozen" state when all needed information has been incorporated.

Frozen

When a requirement specification is in the "Frozen" state, its content is frozen. In this state, the Leader can modify the requirement specification or the object owner can demote it to the "In Work" state.

Released

Each requirement in the requirement specification structure must be in the "Released" state before the requirement specification itself can be promoted to the "Released" state. If the requirement specification is demoted from the "Released" state, all chapters and comments, and any child chapters and comments in the structure that comprise the requirement specification are also demoted at the same time to their "In Work" states.

If all child chapters and comments are in the "Released" state, then the chapter will automatically be promoted to the "Released" state; however, if a branch in the requirement specification tree contains a requirement, the requirement will not be promoted to the "Released" state (since it must be specifically promoted to that state) and the requirement specification is not promoted to the "Released" state.

Obsolete

In the "Obsolete" state, the requirement specification is considered no longer usable and cannot be connected to any requirement objects. When promoted to the "Obsolete" state, the requirement specification is not a baseline anymore—you should have a different requirement specification to use as the baseline. The requirement specification cannot be demoted from the "Obsolete" state back to the "Released" state.