1. Requirements Management Overview NIGMS Software Development

2. Agenda/Overview  Purpose and importance of requirements  Requirements management process  Project artifacts  Tools  Case study

3. What is Requirements Management? Requirements Management is a systematic approach to eliciting, organizing, documenting, and targeting system requirements

4.  Descriptions of necessary system functionality  Descriptions of how the system should respond to user interactions  Constraints on system design  Requirements vs. design decisions  Allows flexibility  Reduces overhead What Are Requirements?

5. To...  Establish agreement with the stakeholders on what the system must do  Provide system developers with an understanding of the functionality a system must provide  Provide a basis for planning development  Provide a means of measuring progress and success Purpose of Requirements

6. Kinds of Requirements

7. Use Cases  Provide description of system behavior  Give context to functional requirements  Supported by supplemental specs to capture non-functional requirements  Use case example (following page)

9. Importance of Managing Requirements  Common causes for failure  Poor stakeholder involvement  Unclear vision and objectives  Changing requirements  Requirements errors are costly  Need to reduce errors  Need to find errors sooner  Need to reduce cost of change

10. Approach and Traceability  Agree on scope for current release  Document and implement in-scope requirements  Changes may affect schedule  Record out of scope requirements for future releases  May be identified during any stage of development or operations

11. Process Flow

12. Mapping RUP to EPLC

13. Preliminary Draft Version Final BaselinedVersion Artifacts / PhaseIncElConTran Vision Use Case Summary Use Case Supplemental Specs UI Prototype Software Architecture Document Data Model (Logical & Physical) PIA System Executables Test Plans TAR ISDS Project Deliverables Artifacts / PhaseIncElConTran UAT Deploy Plan User Guide Training Material Security Plan CM Plan SVD Project Plan Project Schedule Risk Plan  Baselining vs. gate reviews

14.  Requisite Pro  Store current requirements  Store working documents  Rational Clear Quest  Track work flow  Store future requirements  Rational Clear Case  Manage versions  Publish baselined documents  Rational Rose  Modeling & Design Requirements Tools

15. CMR Meeting Support System (CMS 2 ) Case Study Putting it All Together

16. Requirements Management Success  Delivered critical functionality  On time  Within budget  Stakeholder satisfaction  Positioned for future enhancements

17. CMS 2 Inception  Stakeholder needs  Schedule driven  Agreement on scope  Vision & Use Case Summary

20. CMS 2 Elaboration  Gathering of detailed requirements  Mock-ups & wire-frames  Current requirements in Req Pro  Use case specifications  Supplemental specifications  Future requirements in Clear Quest

23. CMS 2 Construction  Documents baselined into Clear Case  Code created using Clear Case for CM  Initial functionality split  Core functionality readied for original date  Additional requirements targeted for enhancement release (in Clear Quest)

25. CMS 2 Transition  Testing using test manager  Link to Req Pro with new version  Demo to users and service desk  User acceptance testing (UAT)  Defects remedied immediately  New requirements entered in CQ  Operations and future releases  Enhancements vs. defects  Enhancement requests in CQ

26. Enhancements for Version 1.1 Future Enhancement Requests

27. Wrap Up... Q & A