![Thanks! For details, please visit http://products.optimizory.com/rmsis For further questions or issues, contact [email_address]](https://image.slidesharecdn.com/rmsisrequirementlifecycle-20110914-110915093040-phpapp01/85/Managing-lifecycle-of-a-requirement-with-RMsis-1-2-x-17-320.jpg)
Managing lifecycle of a requirement with RMsis 1.2.x
- 1. RMsis 1.2.x Lifecycle of a Requirement in Product Development Scenario
- 2. Problem Statement To walk through the lifecycle of a specific Requirement in a product development scenario. A need is contributed by customer, eventually leading to inclusion as feature. Need is specified in unplanned table. Requirement is included in the planned set, analyzed and assigned to a release. Requirement is evolved and baselined. Requirement goes through a change request. It is implemented and tested. Forward traceability is established. Issues are associated and tracked to closure.
- 3. “ Customer Need B” is contributed by a customer / team member in “Unplanned Table”.
- 4. The need is elaborated by the contributor / Business Analyst / Product Manager.
- 5. Product Manager identifies this as a valuable input and decides to move it to the Planned Requirements list.
- 6. Product Management Team defines a “Feature B” and creates dependency on need. can also define a requirements hierarchy, like User Need >> Product Function >> Feature
- 7. This Feature is analyzed by the Product Management Team, who does an estimation and assigns values to various attributes.
- 8. The Feature is opened up to a multidimensional team (sales, developers, architects) for comments. The team’s feedback is incorporated.
- 9. When the evolution of “feature B” stops, it’s current version is committed.
- 10. The feature can be Baselined / Marked for Baseline.
- 11. The feature is assigned to product “Release 7”.
- 12. Development Team starts developing Feature B. Test Team starts preparing for testing of Feature B. They discover an issue and log a change request.
- 13. Change request is closed. Feature is updated and a new version (2) created. This version is assigned to Release 7.
- 14. Test Cases are mapped to the requirement.
- 15. Issues found during testing are mapped to the requirement. These issues are tracked to closure.
- 16. The “Product Feature B” is released as part of Release 7
- 17. Thanks! For details, please visit http://products.optimizory.com/rmsis For further questions or issues, contact [email_address]