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