Date post: | 23-Jan-2016 |
Category: |
Documents |
Upload: | victor-rivas |
View: | 221 times |
Download: | 0 times |
04/21/23 Calidad de Software 1
CMMI
Carlos Mario Zapata J.
04/21/23 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
04/21/23 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)
04/21/23 Calidad de Software 4
04/21/23 Calidad de Software 5
MODELO ESCALONADO: MADUREZ ORGANIZACIONAL
InitialInitial
ManagedManaged
DefinedDefined
QuantitativelyQuantitatively
ManagedManaged
OptimizingOptimizingL5
L3
L2
L1
L4
Process unpredictable poorly controlled, & Reactive.
Process characterized for projects and is often reactive
Process characterized for the organization and is proactive
Process measured and controlled
Focus on process improvement
04/21/23 Calidad de Software 6
MODELO CONTINUO: CAPACIDAD EN LOS PROCESOS
04/21/23 Calidad de Software 7
ESTRUCTURA DE CMMICATEGORY
04/21/23 Calidad de Software 8
MODELO DE MADUREZ Y ÁREAS DE PROCESO
04/21/23 Calidad de Software 9
ÁREAS DE PROCESO POR CATEGORÍA
3. Process Management • OPF - Org. Process Focus• OPD - Org. Process Definition• OT - Org. Training• OPP - Org. Process Performance• OID - Org. Innovation & Deployment
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.
1. Engineering• REQM - Requirements Management • RD - Requirements Development• TS - Technical Solution• PI - Product Integration• VER - Verification• VAL - Validation
4. Support • CM - Configuration Mgmt.• PPQA - Process & Product Quality- Assurance• MA - Measurement & Analysis• DAR - Decision Analysis & Resolution• CAR - Causal Analysis & Resolution
04/21/23 Calidad de Software 10
CATEGORÍA: INGENIERÍA
04/21/23 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.
04/21/23 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.
04/21/23 Calidad de Software 13
DESARROLLO DE REQUISITOS: METAS ESPECÍFICAS
Analyze andValidate
Requirements
Develop Customer
Requirements
Validated CustomerRequirements
Validated Product, Product Component, andInterface Requirements
DevelopProduct
RequirementsStakeholders’Needs
04/21/23 Calidad de Software 14
DESARROLLAR LOS REQUISITOS DEL CLIENTE: PRÁCTICAS ESPECÍFICAS
Develop the Customer
Requirements
CustomerRequirements
Develop Customer Requirements
Elicit NeedsStakeholders’Needs
04/21/23 Calidad de Software 15
DESARROLLAR LOS REQUISITOS DEL PRODUCTO: PRÁCTICAS ESPECÍFICAS
EstablishProduct &Product
ComponentRequirements
Product, Product Component, and Interface Requirements
Develop Product Requirements
AllocateProduct
ComponentRequirements
IdentifyInterface
Requirements
CustomerRequirements
TS
SelectedSolutions
04/21/23 Calidad de Software 16
ANALIZAR Y VALIDAR REQUISITOS: PRÁCTICAS ESPECÍFICAS
EstablishOperationalConcepts
& Scenarios
Establish a Definition of
RequiredFunctionality
AnalyzeRequirements
to AchieveBalance
Analyze Requirements
Customer, Product, Product Component, andInterface Requirements
ValidatedRequirements
Analyze and Validate Requirements
ValidateRequirements
04/21/23 Calidad de Software 17
DESARROLLO DE REQUISITOS: METAS GENÉRICAS
Institutionalize a Defined Process
Achieve Specific Goals
Institutionalize a Managed Process
Institutionalize a Quantitatively
Managed Process
Institutionalize an Optimizing Process
Perform Base Practices
Establish a Defined Process
Collect Improvement Information
Establish Quantitative
Objectives for the Process
Stabilize Subprocess
Performance
Ensure Continuous
Process Improvement
Correct Root Causes of Problems
Establish an Organizational
Policy
Review Status with Higher
Level Management
.
.
.