Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
CMMI and REQM/RD<br />Introducing<br />
Outline<br />Why CMMI?<br />Why Requierments Development andManagement?<br />Process Overview<br />
Motivation<br />Developing the correct software with speed and quality from the first attempt is almost utopic;<br />In th...
How do most perform now?<br />Individual/team processes<br />Performance relies on heroic efforts<br />No common language<...
The context? CMMI.<br />Process improvement approach that help organizations improve performance<br />Capability Maturity ...
CMMI Process Areas<br />
CMMI Representations<br />Staged:<br />5 Levels of maturity:<br />Level 1 – Initial;<br />Level 2 - Managed;<br />Level 3 ...
Introducing<br />RequirementsDevelopmentandManagement<br />
Purpose? – avoid the typical story!<br />
Requirements Development<br />RD (Engineering, L3)<br />The purpose of Requirements Development (RD) is to produce and ana...
Requirements Management<br />REQM (Engineering, L2)<br />The purpose of REQM is to manage the requirements of the project'...
Summary<br />CMMI reduces risk<br />CMMI is a model, not a process<br />Correct REQM/RD can save up to 40% of the developm...
mihainadas.com<br />Contact<br />
Upcoming SlideShare
Loading in …5
×

Introducing CMMI and REQM/RD

4,098 views

Published on

Published in: Technology

Introducing CMMI and REQM/RD

  1. 1. CMMI and REQM/RD<br />Introducing<br />
  2. 2. Outline<br />Why CMMI?<br />Why Requierments Development andManagement?<br />Process Overview<br />
  3. 3. Motivation<br />Developing the correct software with speed and quality from the first attempt is almost utopic;<br />In the real world:<br />Many projects fail or become challenged because of poor requirements management;<br />40% of effort in software projects is spent on correcting errors;<br />Good requirements management avoid:<br />Extra costs associated to rework;<br />Project failure;<br />Unpredictablity;<br />Unplanned project delays;<br />Avoiddeveloperfrustrationduetorework<br />
  4. 4. How do most perform now?<br />Individual/team processes<br />Performance relies on heroic efforts<br />No common language<br />No company wide optimized process<br />Implies risks<br />Difficult to evolve<br />Difficult to manage<br />
  5. 5. The context? CMMI.<br />Process improvement approach that help organizations improve performance<br />Capability Maturity Model – Integration<br />Developed by the Carnegie Mellon University’s (CMU) Software Engineering Instutute (SEI)<br />18 “Process Areas” specifc to each functional grouping involved in product development:<br />Project Management (6 areas);<br />Engineering (6 areas);<br />Process Management (5 areas);<br />Support (5 areas);<br />
  6. 6. CMMI Process Areas<br />
  7. 7. CMMI Representations<br />Staged:<br />5 Levels of maturity:<br />Level 1 – Initial;<br />Level 2 - Managed;<br />Level 3 – Defined;<br />Level 4 – Quantitatively Managed;<br />Level 5 – Optimizing;<br />Continuous:<br />Designed to allow the user to focus on the specific processes that are important;<br />
  8. 8. Introducing<br />RequirementsDevelopmentandManagement<br />
  9. 9. Purpose? – avoid the typical story!<br />
  10. 10. Requirements Development<br />RD (Engineering, L3)<br />The purpose of Requirements Development (RD) is to produce and analyze customer, product, and product component requirements.<br />SG 1 Develop Customer Requirements<br />SP 1.1 Elicit Needs<br />SP 1.2 Develop the Customer Requirements<br />SG 2 Develop Product Requirements<br />SP 2.1 Establish Product and Product Component Requirements<br />SP 2.2 Allocate Product Component Requirements<br />SP 2.3 Identify Interface Requirements<br />SG 3 Analyze and Validate Requirements<br />SP 3.1 Establish Operational Concepts and Scenarios<br />SP 3.2 Establish a Definition of Required Functionality<br />SP 3.3 Analyze Requirements<br />SP 3.4 Analyze Requirements to Achieve Balance<br />SP 3.5 Validate Requirements<br />
  11. 11. Requirements Management<br />REQM (Engineering, L2)<br />The purpose of REQM is to manage the requirements of the project's components and to identify inconsistencies between those requirements and the work products<br />SG 1 Manage Requirements<br />SP 1.1 Obtain an Understanding of Requirements<br />SP 1.2 Obtain Commitment to Requirements<br />SP 1.3 Manage Requirements Changes<br />SP 1.4 Maintain Bidirectional Traceability of Requirements<br />SP 1.5 Identify Inconsistencies Between Project Work and Requirements<br />
  12. 12. Summary<br />CMMI reduces risk<br />CMMI is a model, not a process<br />Correct REQM/RD can save up to 40% of the development costs<br />
  13. 13. mihainadas.com<br />Contact<br />

×