CS4311 Spring 2011 Process Improvement Dr

Slides:



Advertisements
Similar presentations
More CMM Part Two : Details.
Advertisements

How ISO9001 Compares with CMM Mark C. Paulk JAN,1995 CMM version 1.1 ISO9001 July 1994 presented by Zhilan Zhou.
Chapter 2 The Software Process
Stepan Potiyenko ISS Sr.SW Developer.
R R R CSE870: Advanced Software Engineering (Cheng): Intro to Software Engineering1 Advanced Software Engineering Dr. Cheng Overview of Software Engineering.
SE 470 Software Development Processes James Nowotarski 12 May 2003.
Capability Maturity Model (CMM) in SW design
1 R&D SDM 1 Software Project Management Capability Maturity Model 2009 Theo Schouten.
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
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Standardization. Introduction A standard is a document. It is a set of rules that control how people should develop and manage materials, products, services,
Capability Maturity Model
SOFTWARE QUALITY ASSURANCE Asst. Prof. Dr. Selim BAYRAKLI Maltepe University Faculty of Engineering SE 410.
Chapter : Software Process
Integrated Capability Maturity Model (CMMI)
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
Chapter 2 Software Process: A Generic View
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
Software Qualities. Unique Properties of Software (Teams: What are the properties of software that make it unique from other engineering disciplines?)
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.
J. R. Burns, Texas Tech University Capability Maturity Model -- CMM n Developed by the Software Engineering Institute (SEI) in 1989 –SEI is a spinoff.
CMMi What is CMMi? Basic terms Levels Common Features Assessment process List of KPAs for each level.
College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 1 (Ch. 1, 2, & 3)
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 31 Slide 1 Process Improvement u Understanding, Modelling and Improving the Software Process.
PART ONE The Product and the Process Chapter 2 The Process  Software Engineering: A Layered Technology a “quality” focus process model methods tools.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
SQA System Overview Chapter 4. Where we have been so far, Where we are going Where do software errors come from? What is quality? How can quality be measured?
Chapter 2 Process: A Generic View
Software Engineering - Spring 2003 (C) Vasudeva Varma, IIITHClass of 39 CS3600: Software Engineering: Standards in Process Modeling CMM and PSP.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
Software Engineering Lecture # 17
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
Software Process Models
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
Quality Concepts within CMM and PMI G.C.Reddy
Georgia Institute of Technology CS 4320 Fall 2003.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
Software Engineering - I
CS Process Improvement CMM Hans Van Vliet, Software Engineering, Principles and Practice, 3 rd edition, John Wiley & Sons, Chapter 6. W. Humphrey,
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Requirements Development in CMMI
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.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Page 1 The Capability Maturity Model (CMM) distinguishes between immature and mature software organizations. Immature software organizations are typically.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming.
An Introduction. Objective - Understand the difference between CMM & CMMI - Understand the Structure of CMMI.
SOFTWARE PROCESS IMPROVEMENT
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
Certification: CMMI Emerson Murphy-Hill. Capability Maturity Model Integration (CMMI) Creation of the Software Engineering Institute (SEI) at Carnegie.
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
1 Week 3 Software Engineering Spring Term 2016 Marymount University School of Business Administration Professor Suydam.
Advanced Software Engineering Dr. Cheng
School of Business Administration
CMMI Overview Quality Frameworks.
Software Engineering (CSI 321)
Information Technology Project Management – Fifth Edition
Level 1 Level 1 – Initial: The software process is characterized as ad hoc and occasionally even chaotic. Few processes are defined, and success depends.
A possible solution: Personal Software Process (PSP)
CMMI – Staged Representation
THE SOFTWARE PROCESS (revisited)
Software Engineering Lecture 16.
Software Engineering I
Capability Maturity Model
Capability Maturity Model
Requirements Development in CMMI
Chapter 4: Software Process Models
Presentation transcript:

CS4311 Spring 2011 Process Improvement Dr CS4311 Spring 2011 Process Improvement Dr. Guoqiang Hu Department of Computer Science UTEP

Basic Concepts Process: Is about how to go about things. More strictly, it is the sequence of steps required to do a job, whether that process guides a medical procedure, a military operation, or the development and maintenance of software. When properly designed and defined, a process will guide you in doing your work: for example, help you plan your work, coordinate the activities, manage the progress; If not, your work will most probably follow a random and chaos process. More specifically, the software process establishes the technical and management framework for applying methods, tools, and people to the software tasks. The process definition identifies roles, specifies tasks, establishes measures, and provide entry and exit criteria for the major steps. It ensures that every work item is properly assigned and its status consistently tracked. It also provides an orderly mechanism for learning and improving. Software process vs. software lifecycle models

Basic Concepts Basic model of improvement: Process improvement model: Observe the difficulties and problems Collect some data Identify the root causes (hypothesis) Develop reasonable solutions Plan and implement the changes Continue this process Process improvement model: Process improvement model provides a common set of process requirements that capture the best practices and knowledge in a format that can be used to guide the process improvement. Both change and stability are fundamental to process improvement CMM (Capability Maturity Model)

Capability Maturity Model (CMM) for Software Process capability: The ability of a process to produce planned results Software Engineering Institute (SEI): Carnegie Mellon 5 Levels Certification is based on audits

CMM Maturity Level 1: Initial Characteristics: No sound SE management principles in place Ad hoc practices May be successful because of competent manager and team Activities are not preplanned, but response to crisis Unpredictable process Cannot predict time and cost of development To get to next level: Initiate Project Management

Elements of Basic Project Management Software Configuration Management Software Quality Assurance Software Acquisition Management Software Project Control Software Project Planning Software Requirements Management

CMM Maturity Level 2: Repeatable Characteristics: Basic SE management practices in place Planning and management are based on experience with similar products (repeatable) Track costs and schedules Identify problems as arise and take immediate corrective action To get to next level: Standardize Processes

Process Standardization Peer Reviews Project Interface Coordination Software Product Engineering Methods and technologies Software development process architecture Integrated Software Management Organization-level Awareness Organization training program Organization process definition Organization process focus

CMM Maturity Level 3: Defined Characteristics: Process for development fully documented Reviews used to achieve software quality Introduce CASE Tools To get to next level: Quantitative Management

Quantitative Management Statistical process management Quantify quality and cost parameters Process database to maintain process data Assess relative quality of each product

CMM Maturity Level 4: Managed Characteristics: Organization sets quality and productivity goals for each project Continually measure Statistical quality control in place To get to next level: Support automatic gathering of process data Use data to analyze and modify the process Defect Prevention

CMM Maturity Level 5: Optimizing Characteristics: Statistical quality and process control techniques are used and guide the organization Process has positive feedback loop To maintain level: Continue improvement and optimization of the process

Four Process Categories Process Management Process Definition Training Project Management Project Planning Monitoring and Control Risk Management Engineering Requirements Development and Management Product Engineering V&V Support Configuration Management Measurement and Analysis Decision Analysis and Resolution