1 / 27

Requirements Management Overview

Requirements Management Overview. NIGMS Software Development. Agenda/Overview. Purpose and importance of requirements Requirements management process Project artifacts Tools Case study. What is Requirements Management?.

fabian
Download Presentation

Requirements Management Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 Managementis a systematic approach to eliciting, organizing, documenting, and targeting system requirements

  4. What Are Requirements? • 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

  5. Purpose of Requirements 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

  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)

  8. 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

  9. 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

  10. Process Flow

  11. Mapping RUP to EPLC

  12. ISDS Project Deliverables • Baselining vs. gate reviews

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

  14. CMR Meeting Support System (CMS2) Case Study Putting it All Together

  15. Requirements Management Success • Delivered critical functionality • On time • Within budget • Stakeholder satisfaction • Positioned for future enhancements

  16. CMS2 Inception • Stakeholder needs • Schedule driven • Agreement on scope • Vision & Use Case Summary

  17. CMS2 Elaboration • Gathering of detailed requirements • Mock-ups & wire-frames • Current requirements in Req Pro • Use case specifications • Supplemental specifications • Future requirements in Clear Quest

  18. CMS2 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)

  19. CMS2 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

  20. Enhancements for Version 1.1 Future Enhancement Requests

  21. Wrap Up ... Q & A

More Related