Private
Only the Owner or requirement owner can view and edit the requirement in the "Private" state. The requirement is not visible to other members of the Collaborative Space when it is in this state. The Owner or requirement owner can promote requirements from the "Private" state to the "In Work Approval" state (if it exists), then to the "In Work" state; or to the "In Work" state directly (if the "In Work Approval" state does not exist). In Work Approval
Note:
This is a legacy lifecycle state that exists only for requirements on systems upgraded from releases earlier than 3DEXPERIENCE R2017x. It will not exist for requirements on systems with a new installation of 3DEXPERIENCE R2017x or later releases.
In Work
When a Product Manager or Requirement Manager creates a new requirement either stand-alone or in the context of a product or feature, it is created in the "In Work" state. The Owner or requirement owner can demote requirements to the "In Work Approval" state (if it exists) then to the "Private" state; or to the "Private" state directly (if the "In Work Approval" state does not exist). A Product Manager or Requirement Manager can define use cases and test cases for the requirement, assign the requirement for impact analysis, perform a gap analysis against existing products, and define an approval route for the requirement while it is in the "In Work" state. Note:
Any requirements created in releases earlier than 3DEXPERIENCE R2017x that were in the "In Work Validation" state are in the "In Work" state after upgrading to 3DEXPERIENCE R2017x.
Frozen
Once the requirement is validated, its content is frozen. The requirement is reviewed by those assigned in the approval route while it is in the "Frozen" state. Before a requirement can be promoted from the "Frozen" to the "Released" state, any sub requirements must be in the "Released" state. Released
Once the requirement is valid and can be planned, it is promoted to the "Released" state. A feature can then be created to satisfy the requirement. When requirements are promoted to the "Released" state, any unreleased parent products, features, and requirements are connected to a new revision of the requirement. Email notification is sent to the owners of the parent objects stating that the requirement has been replaced with its latest revision. Obsolete
When the requirement is no longer needed, it is promoted to the "Obsolete" state. You cannot demote the requirement from the "Obsolete" state back to the "Released" state. | |||||||