1 / 12

Requirements Development in CMMI

Requirements Development in CMMI. Presented by: Anna Nash October 22, 2007. Agenda. CMMI Background Definition History CMMI Maturity Levels CMMI Process Areas Requirements Development Definition Goals Importance Concerns References. CMMI - Background.

rhian
Télécharger la présentation

Requirements Development in CMMI

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 Development in CMMI Presented by: Anna Nash October 22, 2007

  2. Agenda • CMMI Background • Definition • History • CMMI Maturity Levels • CMMI Process Areas • Requirements Development • Definition • Goals • Importance • Concerns • References

  3. CMMI - Background • The Capability Maturity Model Integration (CMMI) is a process improvement method that integrates disparate organizational functions, sets improvement goals and priorities and provides guidance for quality and a point of reference for reviewing current processes • CMMI is predecessor to the Capability Maturity Model (CMM), first released in 1989, sponsored by DoD and developed by the Software Engineering Institute (SEI) at Carnegie Mellon University. • CMMI is currently maintained by a team comprised of DoD, industry and SEI members • CMMI Version 1.2 is slated for release in November 2007

  4. CMMI Benefits • Is a conglomerate of internationally recognized best practices • Internationally recognized and adhered to organizational maturity model • Aids in linking management and engineering activities to business goals • Aids in implementing a robust maturity practice • Applicable to any product producing project, particularly large or Enterprise wide projects

  5. CMMI Maturity Levels Level 1: Performed • Process is unpredictable, reactive in nature and uncontrolled Level 2: Managed • Process characterized for projects and is managed Level 3 Defined • Process characterized for the organization and is proactive Level 4: Quantitatively Managed • Process quantitatively measured and controlled Level 5: Optimizing • Process focused on continuous process improvement

  6. CMMI Process Areas Level 2: Manager Configuration Management Measurement & Analysis Project Monitoring & Control Project Planning Process & Product Quality Assurance Requirements Management Supplier Agreement Management Level 3: Defined Decision Analysis & Resolution Integrated Project Management Organizational Process Definition Organizational Process Focus Organizational Training Product Integration Requirements Development Risk Management Technical Solution Validation Verification Level 4: Quantitatively Managed Quantitative Project Management Organizational Process Performance Level 5: Optimizing Casual Analysis & Resolution Organizational Innovation and Development

  7. Requirements Development • The Requirements Development process area is defined to produce and analyze customer, product and product-component requirements • Requirements should address the needs of all relevant stakeholders and constraints resulting from the design solution • Requirements Development as defined by CMMI is relevant to any project in which a product is developed

  8. Requirements Development Requirements Development is comprised of the following events: • Gathering and organizing stakeholder needs • Developing the product’s life-cycle specifications • Establishing customer requirements • Establishing product and product-component requirements

  9. Requirements Development Requirements Development can be broken into 3 specific goals: • Develop Customer Requirements • Establish needs • Establish requirements • Develop Product Requirements • Develop Product and Product-Component Requirements • Allocate Product-Component Requirements • Discern Interface Requirements • Analyze and Validate Requirements • Develop Operational Concepts and Scenarios • Define Required Functionality • Validate Requirements with Comprehensive Methods

  10. Requirements Development Requirements Development is important because: • Requirements are the backbone of design • The process helps ensure customer satisfaction • Adherence to the process signals CMMI Level 3 Maturity

  11. Requirements Development Concerns surrounding Requirements Development include: • Process may be too long or cumbersome for smaller projects • Heavy reliance on outside organizations • Assumes that stakeholders understand what they want

  12. References • www.sei.cmu.edu/cmmi/ • en.wikipedia.org/wiki/CMMI/ • www.borland.com/us/services/cmmi.html • www.galorath.com/tool.softcmmi.html • en.wikipedia.org/wiki/Process_area_%28CMMI%29#Requirements_Development_.28RD.29

More Related