CMMI Carlos Mario Zapata J. 4/13/2017 Calidad de Software.

Presentación del tema: "CMMI Carlos Mario Zapata J. 4/13/2017 Calidad de Software."— Transcripción de la presentación:

1 CMMI Carlos Mario Zapata J. 4/13/2017 Calidad de Software

2 IMPORTANCIA DEL MEJORAMIENTO EN UNA ORGANIZACIÓN
Compromiso de las personas Planificación Presupuestos y Cronogramas Eficiencia individual y colectiva Lecciones aprendidas Calidad de las aplicaciones Motivación Inversión Relación con el cliente 4/13/2017 Calidad de Software

3 CMMI Integración de modelos de capacidad y madurez
Busca el mejoramiento en organizaciones de software: Mejorando los procesos Mejorando las habilidades de la organización Se centra en el desarrollo, adquisición y mantenimiento de productos y servicios Posee tres constelaciones planificadas: desarrollo, adquisición y servicios El enfoque más conocido es CMMI-Dev, incluyendo, adicionalmente, IPPD (Integrated Product and process development) 4/13/2017 Calidad de Software

4 4/13/2017 Calidad de Software

5 MODELO ESCALONADO: MADUREZ ORGANIZACIONAL
Optimizing Focus on process improvement Quantitatively Managed L4 Process measured and controlled Defined L3 Process characterized for the organization and is proactive Managed L2 Process characterized for projects and is often reactive Initial L1 Process unpredictable poorly controlled, & Reactive. 4/13/2017 Calidad de Software

6 MODELO CONTINUO: CAPACIDAD EN LOS PROCESOS
4/13/2017 Calidad de Software

7 ESTRUCTURA DE CMMI CATEGORY 4/13/2017 Calidad de Software

8 MODELO DE MADUREZ Y ÁREAS DE PROCESO
4/13/2017 Calidad de Software

9 ÁREAS DE PROCESO POR CATEGORÍA
1. Engineering REQM - Requirements Management RD - Requirements Development TS - Technical Solution PI - Product Integration VER - Verification VAL - Validation 2. Project Management PP - Project Planning PMC - Project Monitoring & Control SAM - Supplier Agreement Mgmt. IPM - Integrated Project Mgmt. RSKM - Risk Management QPM - Quantitative Project Mgmt. 3. Process Management OPF - Org. Process Focus OPD - Org. Process Definition OT - Org. Training OPP - Org. Process Performance OID - Org. Innovation & Deployment 4. Support CM - Configuration Mgmt. PPQA - Process & Product Quality- Assurance MA - Measurement & Analysis DAR - Decision Analysis & Resolution CAR - Causal Analysis & Resolution 4/13/2017 Calidad de Software

10 CATEGORÍA: INGENIERÍA
4/13/2017 Calidad de Software

11 ÁREA DE PROCESO: DESARROLLO DE REQUISITOS
Purpose: Produce and analyze customer, product, and product component requirements. SG 1: Develop Customer Requirements: Stakeholder needs, expectations, constraints, and interfaces are collected and translated into customer requirements. SG 2: Develop Product Requirements: Customer requirements are refined and elaborated to develop product and product component requirements. SG 3: Analyze and Validate Requirements: The requirements are analyzed and validated, and a definition of required functionality is developed. 4/13/2017 Calidad de Software

12 ÁREA DE PROCESO: DESARROLLO DE REQUISITOS
GG 1 Achieve Specific Goals: The process supports and enables achievement of the specific goals of the process area by transforming identifiable input work products to produce identifiable output work products. GG 2 Institutionalize a Managed Process: The process is institutionalized as a managed process. GG 3 Institutionalize a Defined Process: The process is institutionalized as a defined process. GG 4 Institutionalize a Quantitatively Managed Process: The process is institutionalized as a quantitatively managed process. GG 5 Institutionalize an Optimizing Process: The process is institutionalized as an optimizing process. 4/13/2017 Calidad de Software

13 DESARROLLO DE REQUISITOS: METAS ESPECÍFICAS
Develop Customer Requirements Develop Product Requirements Analyze and Validate Requirements Stakeholders’ Needs Validated Customer Requirements Validated Product, Product Component, and Interface Requirements 4/13/2017 Calidad de Software

14 DESARROLLAR LOS REQUISITOS DEL CLIENTE: PRÁCTICAS ESPECÍFICAS
Develop Customer Requirements Develop the Customer Requirements Stakeholders’ Needs Elicit Needs Customer Requirements 4/13/2017 Calidad de Software

15 DESARROLLAR LOS REQUISITOS DEL PRODUCTO: PRÁCTICAS ESPECÍFICAS
Develop Product Requirements TS Establish Product & Product Component Requirements Selected Solutions Allocate Product Component Requirements Identify Interface Requirements Product, Product Component, and Interface Requirements Customer Requirements 4/13/2017 Calidad de Software

16 ANALIZAR Y VALIDAR REQUISITOS: PRÁCTICAS ESPECÍFICAS
Analyze and Validate Requirements Establish Operational Concepts & Scenarios Establish a Definition of Required Functionality Analyze Requirements to Achieve Balance Analyze Requirements Validate Requirements Validated Requirements Customer, Product, Product Component, and Interface Requirements 4/13/2017 Calidad de Software

17 DESARROLLO DE REQUISITOS: METAS GENÉRICAS
Achieve Specific Goals Institutionalize a Managed Process Institutionalize a Defined Process Institutionalize a Quantitatively Managed Process Institutionalize an Optimizing Process Establish Quantitative Objectives for the Process Ensure Continuous Process Improvement Perform Base Practices Establish a Defined Process Establish an Organizational Policy . Collect Improvement Information Stabilize Subprocess Performance Correct Root Causes of Problems Review Status with Higher Level Management 4/13/2017 Calidad de Software