Level - 3 Process Areas (CMMI-DEV)

Slides:



Advertisements
Similar presentations
Process and Product Quality Assurance (PPQA)
Advertisements

Kai H. Chang COMP 6710 Course NotesSlide CMMI-1 Auburn University Computer Science and Software Engineering Capability Maturity Model Integration - CMMI.
S Y S T E M S E N G I N E E R I N G.
Chapter 2 – Software Processes
PROCESS AND PRODUCT QUALITY ASSURANCE
School of Computing, Dublin Institute of Technology.
Capability Maturity Model Integration (CMMI). CMMI Enterprise-wide process improvement framework Focuses on processes for improved product Process areas:
Adaptive Processes Comparing CMMI 1.2 vs. CMMI 1.1 LN Mishra Adaptive Processes Consulting.
Verification and Validation Mark C. Paulk July 16, 2003 SEEK 2003
Effective Methods for Software and Systems Integration
Chapter : Software Process
QUALITY MANAGEMENT SYSTEM ACCORDING TO ISO
Understanding (and Untangling) Verification and Validation Requirements ISO 9001 vs. CMMI-Dev 1.2.
CMMI Course Summary CMMI course Module 9..
Capability Maturity Model Integration
1 The Continuous Representation. 2 UNIT 2 Topics covered in this unit include Additional terminology Practices – The fundamental building blocks Process.
8. CMMI Standards and Certifications
Integrated Capability Maturity Model (CMMI)
Training on “CMMI for Development – ver 1.2”
Light-Weight CMMI (Capability Maturity Model Integration ) Stage 1: Requirement Development and Project Planning For NSC Open Source Projects Dr. Chaw-Kwei.
Otto Vinter Software Engineering Mentor Otto Vinter Software Engineering Mentor Tel/Fax: , Mobile:
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
CLEANROOM SOFTWARE ENGINEERING.
1 The Continuous Representation. 2 UNIT 2 Topics covered in this unit include Additional terminology Practices – The fundamental building blocks Process.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
NIST Special Publication Revision 1
Software Engineering Lecture # 17
Product Development Chapter 6. Definitions needed: Verification: The process of evaluating compliance to regulations, standards, or specifications.
Project Planning Author : Software Engineering Institute Carnegie Mellon University 學生 : 吳與倫 老師:李健興 教授.
10/16/2015Bahill1 Organizational Innovation and Deployment Causal Analysis and Resolution 5 Optimizing 4 Quantitatively Managed 3 Defined 2 Managed Continuous.
Gary Natwick & Jim Cocci November 2003 Understanding the CMMI ® Validation Process Area CMMI ® Technology Conference & User Group 2003 assured.
Georgia Institute of Technology CS 4320 Fall 2003.
Software Engineering - I
Requirements Development in CMMI
Federal Aviation Administration 2011 V&V Summit: Verification & Validation Overview Presented by: John Frederick Date:10/19/11.
1 Agenda for measurement r1. CMMI r2. Other thrusts.
Chapter 2 – Software Processes Lecture 1 Chapter 2 Software Processes1.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
An Introduction. Objective - Understand the difference between CMM & CMMI - Understand the Structure of CMMI.
Copyright © | Trade secret and confidential Page 1 Innovative, Professional, Fact Based and Eustressed© Maruthi Quality Management Services Ptv. Ltd..,
Space and Airborne Systems Prepared For 3rd Annual CMMI Technology Conference Presented In Denver, CO Tom Cowles November 19, 2003 Peer Reviews For CMMI.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
COMPGZ07 Project Management CMMI Project Planning Lecture 5b Graham Collins, UCL.
CMMI1 Capability Maturity Model Integration Eyal Ben-Ari 8/2006.
MSA Orientation – v203a 1 What’s RIGHT with the CMMI?!? Pat O’Toole
Project Management Strategies Hidden in the CMMI Rick Hefner, Northrop Grumman CMMI Technology Conference & User Group November.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
CMMI Model overview Practical experience. Copyright © 2014 Accenture All rights reserved. 2 Education 2004 graduated LU, Faculty of Physics and Mathematics,
Certification: CMMI Emerson Murphy-Hill. Capability Maturity Model Integration (CMMI) Creation of the Software Engineering Institute (SEI) at Carnegie.
A Comparison of CMMI & SPICE
1 Week 3 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
CMMI for Services, Version 1.3 Speaker: Business Excellence Date:
PRODUCT VERIFICATION Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Software Quality Control and Quality Assurance: Introduction
School of Business Administration
CS4311 Spring 2011 Process Improvement Dr
Software Engineering (CSI 321)
Development Projects / Analysis Projects / On-site Service Projects
Software Requirements
CS 577b Software Engineering II -- Introduction
CMMI – Staged Representation
Engineering Processes
Software Quality Engineering
Technical Management Processes
Engineering Processes
Software Reviews.
Requirements Development in CMMI
Presentation transcript:

Level - 3 Process Areas (CMMI-DEV) Defined Quantitatively Managed Initial © SEI Optimizing

Staged View of Process Areas : CMMI-DEV Organizational Training Organizational Process Definition Organizational Process Focus Organizational Process Performance Project Monitoring and Control Project Planning Supplier Agreement Management Requirements Management Integrated Project Management Risk Management Quantitative Project Management Requirements Development Technical Solution Product Integration Verification Validation Organizational Performance Management Configuration Management Process & Product QA Measurement & Analysis Decision Analysis & Resolution Causal Analysis & Resolution Engineering Project Management Process Management Support 2 3 4 5

Requirements Development The purpose of Requirements Development is to produce and analyze customer, product, and product-component requirements.

Requirements Development There are 3 specific goals in the process area - Develop Customer Requirements(SG1) Develop Product Requirements (SG2) Analyze and Validate Requirements(SG3)

Requirements Development Elicit Needs SP 1.1 Transform Stakeholder Needs into Customer Requirements SP 1.2 Requirements SG1: Develop Customer Requirements

Requirements Development Establish Product & Product Component Requirements SP 2.1 Allocate Product Component Requirements 2.2 Allocated Requirements Identify Interface Requirements SP 2.3 SG2: Develop Product Requirements

Requirements Development Establish Operational Concepts and Scenarios SP 3.1 Establish a Definition of Required Functionality & Quality Atttributes 3.2 Analyze Requirements 3.3 Validate Requirements 3.5 Analyze Requirements to achieve Balance 3.4 SG3: Analyze and Validate Requirements

Technical Solution

Technical Solution The purpose of Technical Solution is to design, develop, and implement solutions to requirements. Solutions, designs, and implementations encompass products, product components, and product-related life-cycle processes either singly or in combinations as appropriate.

There are 3 specific goals in the process area - Technical Solution There are 3 specific goals in the process area - Select Product-Component Solutions(SG1) Develop the Design(SG2) Implement the Product Design(SG3)

Technical Solution SG1: Select Product-Component Solutions Develop Alternative Solutions & Selection Criteria SP 1.1 Select Product Component Solutions SP 1.2 SG1: Select Product-Component Solutions

? Technical Solution SG2: Develop the Design Design the Product or Product Component SP 2.1 Establish a Technical Data Package 2.2 Design Interfaces using Criteria SP 2.3 ? Perform Make, Buy, or Reuse Analyses SP 2.4 SG2: Develop the Design

Technical Solution SG3: Implement the Product Design Implement the Design SP 3.1 Develop Product Support Documentation SP 3.2 SG3: Implement the Product Design

Product Integration

Product Integration The purpose of Product Integration is to assemble the product from the product components, ensure that the product, as integrated, functions properly, and deliver the product. This process area addresses the integration of product components into more complex product components or into complete products.

There are 3 specific goals in the process area - Product Integration There are 3 specific goals in the process area - Prepare for Product Integration(SG1) Ensure Interface Compatibility(SG2) SG 3 Assemble Product Components and Deliver the Product (SG3)

Product Integration SG1: Prepare for Product Integration Establish an Integration Strategy SP 1.1 Establish the Product Integration Environment SP 1.2 Establish Product Integration Procedures and Criteria SP 1.3 SG1: Prepare for Product Integration

Product Integration SG2: Ensure Interface Compatibility Review Interface Descriptions for Completeness SP 2.1 Manage Interfaces 2.2 SG2: Ensure Interface Compatibility

Product Integration Confirm Readiness of Product Components for Integration SP 3.1 Assemble Product Components 3.2 Evaluate Assembled Product Components 3.3 Package and Deliver the Product or Product Component 3.4 SG3: Assemble Product Components and Deliver the Product

Verification

Verification The purpose of Verification is to ensure that selected work products meet their specified requirements. Verification includes verification of the product and intermediate work products against all selected requirements, including customer, product, and product component requirements The Verification process area involves the following: verification preparation, verification performance, and identification of corrective action.

There are 3 specific goals in the process area - Verification There are 3 specific goals in the process area - Prepare for Verification(SG1) Perform Peer Reviews(SG2) Verify Selected Work Products (SG3)

Verification SG1: Prepare for Verification SP Select Work Products for Verification SP 1.1 Establish the Verification Environment SP 1.2 Establish Verification Procedures and Criteria SP 1.3 QC Plan SG1: Prepare for Verification

Verification SG2: Perform Peer Reviews SP Prepare for Peer Reviews 2.1 Plan Conduct Peer Reviews SP 2.2 Analyze Peer Review Data SP 2.3 SG2: Perform Peer Reviews

Verification SG3: Verify Selected Work Products SP Perform Verification SP 3.1 Analyze Verification Results SP 3.2 Test Reports SG3: Verify Selected Work Products

Validation

Validation The purpose of Validation is to demonstrate that a product or product component fulfills its intended use when placed in its intended environment. Validation demonstrates that the product, as provided, will fulfill its intended use; whereas, verification addresses whether the work product properly reflects the specified requirements. In other words, verification ensures that “you built it right”; whereas, validation ensures that “you built the right thing.” Validation activities use approaches similar to verification (e.g., test, analysis, inspection, demonstration, simulation).

There are 2 specific goals in the process area - Validation There are 2 specific goals in the process area - Prepare for Validation(SG1) Validate Product or Product Components(SG2)

Validation SG1: Prepare for Validation Select Products for Validation SP 1.1 Establish the Validation Environment SP 1.2 Define Validation Procedures and Criteria SP 1.3 SG1: Prepare for Validation

Validation SG2: Validate Product or Product Components Perform Validation SP 2.1 Analyze Validation Results SP 2.2 SG2: Validate Product or Product Components

Questions