CMM Level 3 KPA’s CS4320 Fall 2003. Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across.

Slides:



Advertisements
Similar presentations
1 Dr. Ashraf El-Farghly SECC. 2 Level 3 focus on the organization - Best practices are gathered across the organization. - Processes are tailored depending.
Advertisements

Group 7 - Chapter 3 Steven Shroyer - Introduction, ad hoc, level 2 Xiao Jingshan - Levels 3 and 4 Dusting Marker - Level 5 and example companies Definintions.
S3-1 © 2001 Carnegie Mellon University OCTAVE SM Process 3 Identify Staff Knowledge Software Engineering Institute Carnegie Mellon University Pittsburgh,
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
More CMM Part Two : Details.
1 Brief Descriptions of CMM KPAs CEN 6070 Summer 2004.
1 State of Michigan Achieving Software Process Improvement with Capability Maturity Model (CMM)
S2-1 © 2001 Carnegie Mellon University OCTAVE SM Process 2 Identify Operational Area Management Knowledge Software Engineering Institute Carnegie Mellon.
Stepan Potiyenko ISS Sr.SW Developer.
Planning a measurement program What is a metrics plan? A metrics plan must describe the who, what, where, when, how, and why of metrics. It begins with.
Capability Maturity Model (CMM) in SW design
Computer Engineering 203 R Smith Process/Plan Model 7/ Development Process Models Development Process Models are different ways to look at the processes.
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
CMM Overview - 1 © Paul Sorenson CMPUT Software Engineering refs. IEEE Software, March 1988, 73-79, and IEEE Software, July 1993, (Capability.
Chapter 3 The Structure of the CMM
Capability Maturity Method (CMM)
CMMI Overview Quality Frameworks.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Capability Maturity Model
Release & Deployment ITIL Version 3
© 1999 Prentice-Hall, Inc. Chap Level 3: Key Processes Defined Group 9: LaTanya Moore Ali Imajat Asim Eldaroty.
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
What ISO 9000 Mandates The requirements for a quality system have been standardized - but many organizations like to think of themselves as unique. So.
Integrated Capability Maturity Model (CMMI)
Chapter 4 Interpreting the CMM. Group (3) Fahmi Alkhalifi Pam Page Pardha Mugunda.
Org Name Org Site CMM Assessment Kick-off Meeting Dates of assessment.
PART 2: A FRAMEWORK FOR SOFTWARE PROCESS IMPROVEMENT (SPI) Jean Charles Salvin Markus Erlandsson Jan-Peter Nilsson.
EMgt 4110 Engineering Professionalism and Practice
Capability Maturity Model Part One - Overview. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First.
N By: Md Rezaul Huda Reza n
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
CMM Level 2 KPA’s CS 4320 Fall Requirements Management 1 Goals: – System requirements allocated to software are controlled using a baseline for.
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
A Project ’ s Tale: Transitioning From SW-CMM to CMMI-SE/SW Warren Scheinin Systems Engineer, NG Mission Systems CMMI Technology Conference & User Group.
GENERAL DYNAMICS Communication Systems “Process Maturity: Things that Work” Boston SPIN Panel April 18, 2000 Presenter: Carol Pilch.
Capability Maturity Model. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First version published in.
Building Capability.  In order to successfully operate an architecture function within an enterprise, it is necessary to put in place appropriate organization.
Software process improvement Framework for SPI SPI support groups, maturity and immaturity models Assessment and gap analysis Education and training Selection.
CMM Level 2: Repeatable Copyright, 2000 © Jerzy R. Nawrocki Quality Management.
Georgia Institute of Technology CS 4320 Fall 2003.
Software Process Improvement: SEI Capability Maturity Model
Implementing the CMM Level 2 Creating Level 2 Structures Creating Level 2 Processes Creating a Level 2 Training Program Creating Level 2 Policies Subcontract.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
QUALITY MANAGEMENT STATEMENT
Ch-1 Introduction The processes used for executing a software project have major effect on quality of s/w produced and productivity achieved in project…
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
Page 1 The Capability Maturity Model (CMM) distinguishes between immature and mature software organizations. Immature software organizations are typically.
Software Testing and Software Quality Assurance Process.
SEN 460 Software Quality Assurance. Bahria University Karachi Campus Waseem Akhtar Mufti B.E(C.S.E) UIT, M.S(S.E) AAU Denmark Assistant Professor Department.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
Pertemuan 14 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Software Project Management Lecture 3. What is Project Management?  Project management is “the application of knowledge, skills, tools and techniques.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Managing Multiple Projects Steve Westerman California Department of Motor Vehicles Steve Young Mathtech, Inc.
CSC 480 Software Engineering Team Issues. Essence of a Successful Team To be successful, teams must  Plan their projects  Track their progress  Coordinate.
P ERSONAL & TEAM PROCESS MODELS Lecture 05 Part -2.
The Project Team. Major Ideas Software Projects are Cultural Events Management ≠ Leadership Team’s ability is based more on its personality than its skill.
Software Quality Control and Quality Assurance: Introduction
CS4311 Spring 2011 Process Improvement Dr
H. Overview of Capability Maturity Model (CMM)
CSC 480 Software Engineering
CMMI Overview Quality Frameworks.
Information Technology Project Management – Fifth Edition
A possible solution: Personal Software Process (PSP)
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering Lecture 16.
Capability Maturity Model
Capability Maturity Model
Team Software Process (TSP)
Project Management Method and PMI ® PMBOK ® Roles
Presentation transcript:

CMM Level 3 KPA’s CS4320 Fall 2003

Organizational Process Focus (Goals) Software process development and improvement activities are coordinated across the organization. The strengths and weaknesses of the software processes used are identified relative to a process standard. Organization-level process development and improvement activities are planned.

Org Process Focus Commitment to perform: – The organization follows a written organizational policy for coordinating software process development and improvement activities across the organization. – Senior management sponsors the organization's activities for software process development and improvement. – Senior management oversees the organization's activities for software process development and improvement.

Org Process Focus Ability to Perform: – A group that is responsible for the organization's software process activities exists. – Adequate resources and funding are provided for the organization's software process activities. – Members of the group responsible for the organization's software process activities receive required training to perform these activities. – Members of the software engineering group and other software related groups receive orientation on the organization's software process activities and their roles in those activities.

SEPG Software Engineering Process Group – Often a full-time group in large orgs. – Often part-time members with full-time leader in medium orgs. – All part-time in smaller orgs. – Cross-section of organization. – Members are experienced members of organization. – Has to have support from upper-level management (Management Steering Group) – Don’t make it us vs. them, has to be a cross-section of company – At Infosys- a dedicated group of QA people, but processes are defined via a user group task force.

SEPG Effort distribution at Infosys Process Management 22% Process Implementation 28% Miscellaneous 30% Audit 8% Training 12%

Organization Process Definition Goals: – A standard software process for the organization is developed and maintained. – Information related to the use of the organization's standard software process by the software projects is collected, reviewed and made available.

Commitment to perform: – The organization follows a written policy for developing and maintaining a standard software process and related process assets. Ability to perform: – Adequate resources and funding are provided for developing and maintaining the organization's standard software process and related process assets. – The individuals who develop and maintain the organization's standard software process and related process assets receive required training to perform these activities. Organization Process Definition

Training Program Goals: – Training activities are planned. – Training for developing the skills and knowledge needed to perform software management and technical roles is provided. – Individuals in the software engineering group and software related groups receive the training necessary to perform their roles.

Training Program Commitment to perform: – The organization follows a written policy for meeting its training needs. Ability to perform: – A group responsible for fulfilling the training needs of the organization exists. – Adequate resources and funding are provided for implementing the training program. – Members of the training group have the necessary skills and knowledge to perform their training activities. – Software managers receive orientation on the training program.

Integrated Software Management Goals: – The project's defined software process is a tailored version of the organization's standard software process. – The project is planned and managed according to the project's defined software process. Commitment to perform: – The project follows a written organizational policy requiring that the software project be planned and managed using the organization's standard software process and related process assets.

Integrated Software Management Ability to perform: – Adequate resources and funding are provided for managing the software project using the project's defined software process. – The individuals responsible for developing the project's defined software process receive required training in how to tailor the organization's standard software process and use the related process assets. – The software managers receive required training in managing the technical, administrative, and personnel aspects of the software project based on the project's defined software process.

Software Product Engineering Goals: – The software engineering tasks are defined, integrated, and consistently performed to produce the software. – Software work products are kept consistent with each other. Commitment to perform: – The project follows a written organizational policy for performing the software engineering activities.

Ability to perform: – Adequate resources and funding are provided for performing the software engineering tasks. – Members of the software engineering technical staff receive required training to perform their technical assignments. – Members of the software engineering technical staff receive orientation in related software engineering disciplines. – The project manager and all software managers receive orientation in the technical aspects of the software project. Software Product Engineering

Intergroup Coordination Goals: – The customer's requirements are agreed to by all affected groups. – The commitments between the engineering groups are agreed to by the affected groups. – The engineering groups identify, track, and resolve intergroup issues.

Intergroup Coordination Commitment to perform: – The project follows a written organizational policy for establishing interdisciplinary engineering teams. Ability to perform: – Adequate resources and funding are provided for coordinating the software engineering activities with other engineering groups. – The support tools used by the different engineering groups are compatible to enable effective communication and coordination. – All managers in the organization receive required training in teamwork. – All task leaders in each engineering group receive orientation in the processes, methods, and standards used by the other engineering groups. – The members of the engineering groups receive orientation in working as a team.

Peer Reviews Goal: – Peer review activities are planned. – Defects in the software work products are identified and removed. Commitment to perform: – The project follows a written organizational policy for performing peer reviews.

Peer Reviews Ability to perform: – Adequate resources and funding are provided for performing peer reviews on each software work product to be reviewed. – Peer review leaders receive required training in how to lead peer reviews. – Reviewers who participate in peer reviews receive required training in the objectives, principles, and methods of peer reviews.

Based on CMM… How would you assess: – TSP – PSP