Lecture - 04. Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.

Slides:



Advertisements
Similar presentations
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 25 Slide 1 Chapter 25 Process Improvement.
Advertisements

IS301 – Software Engineering V:
PROCESS FRAMEWORK Lecture - 3. Topics covered PROCESS FRAMEWORK PROCESS MODELS DIFFERENCE.
Chapter 2 Process Models
May 14, May 14, 2015May 14, 2015May 14, 2015 Azusa, CA Sheldon X. Liang Ph. D. Software Engineering in CS at APU Azusa Pacific University, Azusa,
Process Improvement.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
Capability Maturity Model Integration (CMMI). CMMI Enterprise-wide process improvement framework Focuses on processes for improved product Process areas:
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Quality Assurance. CS351 - Software Engineering (AY2004)2 Software engineering processes Systems vs. Software –Terms often used interchangeably.
CMMI Overview Quality Frameworks.
Software Process CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology December 17, 2002.
Lecture 11 CMM CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement 2.
Chapter : Software Process
Process: A Generic View
Process: A Generic View n A software process  is a roadmap to building high quality software products.  provides a framework for managing activities.
1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.
CMMI Course Summary CMMI course Module 9..
1 The Continuous Representation. 2 UNIT 2 Topics covered in this unit include Additional terminology Practices – The fundamental building blocks Process.
Integrated Capability Maturity Model (CMMI)
Chapter 2 Software Process: A Generic View
Chapter 2 The process Process, Methods, and Tools
1 The Continuous Representation. 2 UNIT 2 Topics covered in this unit include Additional terminology Practices – The fundamental building blocks Process.
Chapter 2 Process: A Generic View
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.
©Ian Sommerville 1995 Software Engineering, 5th edition. Chapter 31 Slide 1 Process Improvement u Understanding, Modelling and Improving the Software Process.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Chapter 2 Process: A Generic View
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 25 Slide 1 Process Improvement l Understanding, Modelling and Improving the Software Process.
Software process improvement Framework for SPI SPI support groups, maturity and immaturity models Assessment and gap analysis Education and training Selection.
Software Engineering Principles Principles form the basis of methods, techniques, methodologies and tools Principles form the basis of methods, techniques,
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 2 The Software Process Discussion of the Software Process: Process Framework,
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Software Engineering - I
©Ian Sommerville 2004 Software Engineering. Chapter 28Slide 1 Chapter 28 Process Improvement.
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
Process: A Generic View
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Capability Maturity Model by Hardeep Atwal (hsa06u)
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Making knowledge work harder Process Improvement.
1 Chapter 2 A Generic View of Process Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
1 2.1 Software Engineering Software engineering is a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software;
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
SOFTWARE PROCESS IMPROVEMENT
Software Engineering (CSI 321) Software Process: A Generic View 1.
Software Engineering CE 501 Prepared by : Ashwin Raiyani.
CMMI1 Capability Maturity Model Integration Eyal Ben-Ari 8/2006.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 6/e Chapter 2.
1 Software Engineering Muhammad Fahad Khan Software Engineering Muhammad Fahad Khan University Of Engineering.
Statistical process model Workshop in Ukraine October 2015 Karin Blix Quality coordinator
PROCESS ASSESSMENT AND IMPROVEMENT. Process Assessment  A formal assessment did not seem financially feasible at the onset of the company’s process improvement.
Chapter 25 Process Improvement.
School of Business Administration
CMMI Q & A.
Software Engineering (CSI 321)
CMMI Overview.
CMMI – Staged Representation
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.
Chapter 2 Process Models.
Presentation transcript:

Lecture - 04

Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements

The Capability Maturity Model Integration SEI has developed a process meta-model on a set of system & software engg. capabilities that should be present as organization reaches diff. levels of process capability and maturity. “The quality of a product is largely determined by the quality of the process that is used to develop and maintain it.”

The CMMI framework The CMMI framework is the current stage of work on process assessment and improvement that started at the Software Engineering Institute in the 1980s. The SEI’s mission is to promote software technology transfer particularly to US defence contractors. It has had a profound influence on process improvement Capability Maturity Model introduced in the early 1990s. Revised maturity framework (CMMI) introduced in 2001.

Process capability assessment Intended as a means to assess the extent to which an organisation’s processes follow best practice. My providing a means for assessment, it is possible to identify areas of weakness for process improvement. There have been various process assessment and improvement models but the SEI work has been most influential.

Initial Essentially uncontrolled Repeatable Product management procedures defined and used Defined Process management procedures and strategies defined and used Managed Quality management strategies defined and used Optimising Process improvement strategies defined and used The SEI capability maturity model

Problems with the CMM Practices associated with model levels Companies could be using practices from different levels at the same time but if all practices from a lower level were not used, it was not possible to move beyond that level Discrete rather than continuous Did not recognise distinctions between the top and the bottom of levels Practice-oriented Concerned with how things were done (the practices) rather than the goals to be achieved.

The CMMI model An integrated capability model that includes software and systems engineering capability assessment. The model has two instantiations Staged where the model is expressed in terms of capability levels; Continuous where a capability rating is computed.

CMMI model components Process areas 24 process areas that are relevant to process capability and improvement are identified. These are organised into 4 groups. Goals Goals are descriptions of desirable organisational states. Each process area has associated goals. Practices Practices are ways of achieving a goal - however, they are advisory and other approaches to achieve the goal may be used.

CMMI process areas 1

CMMI process areas 2

CMMI goals

CMMI practices

CMMI assessment Examines the processes used in an organisation and assesses their maturity in each process area. Based on a 6-point scale: Not performed; Performed; Managed; Defined; Quantitatively managed; Optimizing.

Continuous CMMI meta model It describes a process in 2 dimensions as shown in fig. capability level & process area

Continuous model.. PROCESS AREAS : PP- project planning REQM- requirement management MA- measurement & analysis CM- configuration management PPQA- process & product quality assurance Each process area is formally assessed against specific goals & practices and rated according to following capability levels

Capability Levels Level 0 - Incomplete Process area is not performed or does not achieve all goals of level 1 Level 1 – Performed achieved all goals of level 1 Work tasks conducted or performed Level 2 – Managed All level 1 criteria satisfied In addition tasks & work products are monitored, controlled, reviewed & evaluated

Capability Levels Level 3 – Defined All level 2 criteria satisfied In addition process is tailored from organizational standards of process to organizational process assets Level 4 – Quantitatively managed All level 3 criteria satisfied In addition process is improved & controlled using measurements & quantitative assessment Level 5 – Optimized All capability 4 criteria have been achieved In addition process area is adapted & optimized to meet changing customers need

CMMI staged Model The CMMI defines each process area in terms of specific goals & specific practices required to achieve those goals Specific Goals – establish the characteristics that must exist if the activities implied by a process area are to be effective Specific practices- refine goal into a set of process related activities

Process Patterns Software process can be defined as a collection of patterns Templates or methods for describing important characteristics of software processes Software teams can combine software patterns to construct processes that best meet the needs of specific projects

21 Process Patterns.. Process patterns define a set of activities, actions, work tasks, work products and/or related behaviors A template is used to define a pattern Typical examples: Customer communication (a process activity) Analysis (an action) Requirements gathering (a process task) Reviewing a work product (a process task) Design model (a work product)

22 Generic Process pattern elements Meaningful pattern name Intent (objective of pattern) Type Task pattern (defines engineering action or work task) Stage pattern (defines framework activity for the process) Phase pattern (defines sequence or flow of framework activities that occur within process) Initial context (describes conditions that must be present prior to using pattern) Problem (describes the problem to be solved by process pattern) Solution (describes how to implement pattern correctly) Resulting context (describes conditions that result when pattern has been implemented successfully) Related patterns (links to patterns directly related to this one) Known uses/examples (instances in which pattern is applicable)