Status Transition

The life cycle of an RR consists of the Analyzing, Planning, Implementing, Delivering, Accepting, and Closed states.

Table 1 describes operations in each state.

**Table 1** Operation description
State	Description	Operation
To submit	When an RR is created, the state is To submit by default. The requirement proposer is by default the person who creates the requirement.	Creating RRs
Analyzing	After the RR is submitted, the state changes to Analyzing. The requirement recipient can analyze whether to accept the requirement based on the requirement content. If not, the requirement can be returned or suspended. After the requirement is returned, the state changes to Confirming. The requirement proposer can directly cancel the requirement or submit the requirement again.	Analyzing an RR
Planning	After the RR is accepted, the state changes to Planning. The requirement recipient makes development plan on the requirement. If the requirement does not involve R&D, select R&D not required, and the state of the requirement changes to Accepting.	Planning an RR
Implementing	After the R&D of the RR starts, the state changes to Implementing. If there is any problem with the implementation solution, the requirement recipient can return the requirement to the planning phase.	Implementing an RR
Delivering	After the R&D of the RR is completed, the state changes to Delivering. If the delivery cannot meet the expectation, the requirement recipient can return the requirement to the planning or implementing phase.	Delivering an RR
Accepting	After the RR is submitted for acceptance, the state changes to Accepting. The requirement proposer checks whether the content of the requirement meets acceptance conditions. If not, select Acceptance failed and the state of the requirement goes back to Delivering.	Accepting an RR
Closed	After the RR is accepted, the state changes to Closed.	-