Lero© 2010 Software Process & Quality Improvement Dr. Ita Richardson Lero – the Irish Software Engineering Research Centre and Department of Computer Science.

Slides:



Advertisements
Similar presentations
Copyright © 2003 by Cooliemon TM, LLC 1 Causal Analysis & Resolution (CAR) at Level 1 Presenter: Ralph Williams, President SEI Authorized CBA IPI Lead.
Advertisements

Formal Process of QA and quality related certifications Formal Process of QA and quality related certifications MIM 3 rd year – Sem V Abhishek Mishra –
Chapter 2 The Software Process
Copyright 2005 CMMI and ITIL Alison Adams & Kieran Doyle.
Copyright 2003 CMMI: Executive Briefing Presented by Kieran Doyle
Software Process Improvement Robin B. Hunter, Ph.D. Vol 2., p Presented by: Andrew Wheeler.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Lero© 2010 Software Quality & Process Improvement Dr. Ita Richardson Lero – the Irish Software Engineering Research Centre and Department of Computer Science.
Lero © Slide 1Lero–the Irish Software Engineering Research Centre Lero © 2011 Slide 1 Requirements Engineering – a Process viewpoint Dr. Ita Richardson,
Lero© 2010 Software Quality & Process Improvement Dr. Ita Richardson Lero – the Irish Software Engineering Research Centre and Department of Computer Science.
Software Quality Processes – Part I CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 16, 2007.
Software Quality Processes – Part II CSSE 376, Software Quality Assurance Rose-Hulman Institute of Technology March 19, 2007.
CMM Overview - 1 © Paul Sorenson CMPUT Software Engineering refs. IEEE Software, March 1988, 73-79, and IEEE Software, July 1993, (Capability.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement.
CMMI Overview Quality Frameworks.
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,
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.
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.
Lero© 2010 Software Quality & Process Improvement Dr. Ita Richardson Lero – the Irish Software Engineering Research Centre and Department of Computer Science.
UNIT-II Chapter : Software Quality Assurance(SQA)
Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?
Comparing CMMI® and OPM3®
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)
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
COMP3001 Technology Management & Professional Issues: Project Management CMMI and Improving Process Quality Lecture 10 Graham Collins, UCL
Chapter 2 Process: A Generic View
Lecture 1 Introduction to Software Engineering
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
Software Process Assessment and Improvement
University of Sunderland CIFM03Lecture 2 1 Quality Management of IT CIFM03 Lecture 2.
Z26 Project Management CMMI and Improving Process Quality Lecture 5 a Graham Collins, UCL.
Lecture Topics covered CMMI- - Continuous model -Staged model PROCESS PATTERNS- -Generic Process pattern elements.
Capability Maturity Model CS3300 Fall The Problem Contractors over budget and late. Need a way to rank how likely a software company is to deliver.
1 ISO 9001:2000 ISO 9001 is the creation of the International Organisation for Standardisation (ISO), a Swiss-based federation of national standards bodies.ISO.
SEI CMM Robert Johnson Bobby Kolski Rafi Seddiqi Kumeel Alsmail.
SWEN 5130 Requirements Engineering 1 Dr Jim Helm SWEN 5130 Requirements Engineering Requirements Management Under the CMM.
Software Engineering - I
The Essence of Capability Maturity Model Prerna Sethi Oct 26, 2004.
CSE4002CMMI Capability Maturity Model Integration (CMMI) CMMI is replacing the well established CMM rating for software developers and systems engineers.
System Implementation System Implementation - Mr. Ahmad Al-Ghoul System Analysis and Design.
Process Improvement. It is not necessary to change. Survival is not mandatory. »W. Edwards Deming Both change and stability are fundamental to process.
Process: A Generic View
Requirements Development in CMMI
CMMI FRAMEWORK SRIKANTH DEVINENI. Process failure is recognised when Project is delivered late Too much redundancy Customer complaints after delivery.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Applying Project Management Practices to Continuously Improve the Chance of IT Project Success Charlie C. Chen, Ph.D., PMP Dept. of Computer Information.
SPM (5e) Software process quality© The McGraw-Hill Companies, Software Project Management Fifth Edition Chapter 13.2 Software process quality.
SOFTWARE PROCESS IMPROVEMENT
CMMI. Reference CMMI: Guidelines For Process Integration And Product Improvement by Mary Beth Chrissis, Mike Konrad, Sandy Schrum ISBN Copyright.
COMPGZ07 Project Management CMMI Project Planning Lecture 5b Graham Collins, UCL.
CMMI Overview Quality Frameworks. Slide 2 of 146 Outline Introduction High level overview of CMMI Questions and comments.
© 2004 Tangram Hi-Tech Solutions Project Management According to the CMMI1 Project Management according to the Capability Maturity Model (CMMI)
1 Week 3 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
Certification: CMMI Emerson Murphy-Hill. Capability Maturity Model Integration (CMMI) Creation of the Software Engineering Institute (SEI) at Carnegie.
F29IF2: Databases & Information Systems Lachlan M. MacKinnon The Information Systems Life Cycle Databases & Information Systems Lachlan M. MacKinnon.
CS4311 Spring 2011 Process Improvement Dr
Chapter 10 Software Quality Assurance& Test Plan Software Testing
CMMI Overview Quality Frameworks.
Process Maturity Profile
Information Technology Project Management – Fifth Edition
CMMI – Staged Representation
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Acknowledgment of achievement
Using the CMM. Using the CMM Maturity Levels CMM History.
Requirements Development in CMMI
Capability Maturity Model
Presentation transcript:

Lero© 2010 Software Process & Quality Improvement Dr. Ita Richardson Lero – the Irish Software Engineering Research Centre and Department of Computer Science & Information Systems University of Limerick 1 Lero© 2010

LECTURE 2: SOFTWARE PROCESSES

Lero© 2010 Software Process “Set of activities, methods, practices and transformations that people use to develop and maintain software and the associated products” Paulk et al., 1993

Lero© 2010 Software Process Organisation Customer interaction Supplier interaction Development Project Management Risk Management Support activities

Lero© 2010 Total Quality Management Improved Manufacturing Process Improved Manufactured Product

Lero© 2010 Software Process Improved software process Improved software product ?

Lero© 2010 SOFTWARE PROCESS MODELS

Lero© 2010 Software Process Models Capability Maturity Model SPICE - ISO15504 ISO9001 / ISO9000-3

Lero© 2010 Capability Maturity Model Integrated Based on Crosby’s Maturity Grid Level 1 - Initial Level 2 - Repeatable Level 3 - Defined Level 4 - Managed Level 5 – Optimizing – Chrissis et al. 2003

Lero© 2010 SPICE – ISO15504 Framework – Architecture for processes associated with software process – Set of criteria for performing assessments – Tool support for assessment

Lero© 2010 Process Categories Customer-supplier process Engineering process Project process Support process Organisation process

Lero© 2010 SPICE Capability levels 0 Not-Performed – General failure to perform base practices 1 Performed-Informally 2 Planned-and-Tracked 3 Well-Defined 4 Quantitatively-Controlled 5 Continuously-Improving

Lero© 2010 IMPROVING SOFTWARE PROCESS

Lero© 2010 Roots of Software Process Improvement U.S. Department of Defence Software Engineering Institute at Carnegie- Mellon University Watts S. Humphrey, 1989 Capability Maturity Model

Lero© 2010 Software Process Improvement Increase in Productivity Reduction in Defects Reduction in Error Rates Decrease in Costs Increase in On-Time Deliverables Reduction in Rework Savings in Test Time

Lero© 2010 Process in an organisation Investigate what is wrong with the process? Suggest improvements to be made

Lero© 2010 Continuous Improvement Plan - Do - Check - Act

Lero© 2010 What is a Process? “Sequence of steps performed for a given purpose” IEEE-STD-610 “Set of activities, methods, practices and transformations that people use to develop and maintain software and the associated products” Paulk et al., 1993

Lero© 2010 Some processes Develop software design Perform configuration management Manage the project Provide skilled human resources

Lero© 2010 Software Process Improvement Proponents of Software Process Improvement state that the product is improved when the process is improved

Lero© 2010 Argument for ….. …“the link between the quality of the development process and the final product is well established” Gillies, 1992 “It is now generally recognized that an effective way to improve software quality is by improving the development and maintenance process” Humphrey, 1996

Lero© 2010 Argument against "there is, as yet, no convincing evidence that higher rated companies produce better quality software" Fenton et al., 1995

Lero© 2010 Research Conclusions “Improving the process improves the quality of the product; it also improves implementation and maintenance of the product” “…many of the changes which happened as a result of this project were moving the researched companies out of chaos”

Lero© 2010 Software Problems Business importance of software is increasing – Increasing number of services are available to organisations Poor software quality – Is expensive – Reduces customer satisfaction – Delayed shipments – Expensive service / enhancement

Lero© 2010 Acknowledgements The information presented in these slides has been collected from a variety of sources including: – Software Quality Assurance: From Theory to Implementation by Daniel Galin, 2003 – Software Process Improvement: Practical Guidelines for Business Success by Sami Zahran, 1998 – Research carried out by post-doctoral researchers and PhD students at Lero – the Irish Software Engineering Research Centre, Ireland under the supervision of Dr. Ita Richardson – Software Process: Improvement and Practice (journal) – The SPIRE Handbook: Better, Faster, Cheaper Software Development in Small Organisations, edited by Marty Sanders (Version 1, 1998) and Jill Pritchet (Version 2, 2000) The research presented in this lecture has been partially supported by Science Foundation Ireland funded through Global Software Development in SMEs Cluster Grant (no 03/IN3/1408C) and Lero – the Irish Software Engineering Research Centre (CSET grant no 03CE2/I303.1).

Lero© 2010 References Paulk Mark C., Bill Curtis, Mary Beth Chrissis, Charles V Weber, "The Capability Maturity Model for Software, Version 1.1", Technical Report SEI- 93-TR-24, Software Engineering Institute, Carnegie Mellon University, U.S.A., 1993 Chrissis, Mary Beth, Mike Konrad, Sandy Shrum, CMMI – Guidelines for Process Integration & Product Improvement, SEI Series in Software Engineering, Addison-Wesley 2003 –,, © S-Cube – 26/