OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan

Slides:



Advertisements
Similar presentations
Introduction to Software Capability Maturity Model Chuck Connell Copyright 2002, Charles H. Connell Jr.
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 –
More CMM Part Two : Details.
1 State of Michigan Achieving Software Process Improvement with Capability Maturity Model (CMM)
Chapter 2 The Software Process
CMMI Overview Dr. Korson Software Engineering. 2 Immature organizations can be successful on occasion, but ultimately run into difficulties because –Success.
CPIS 357 Software Quality & Testing I.Rehab Bahaaddin Ashary Faculty of Computing and Information Technology Information Systems Department Fall 2010.
Agile Software Development. Traditional Software Development 1.Initiation (RFP) 2.Feasibility study Technical – can we build it? Economic – should we.
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.
R&D SDM 1 Software Process Improvement Capability Maturity Models
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.
Capability Maturity Model
OHT 22.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Chapter : Software Process
OHT 3.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan
Capability Maturity Model Integration
Capability Maturity Model. Reflection Have you ever been a part of, or observed, a “difficult” software development effort? How did the difficulty surface?
Software Engineering II Lecture 1 Fakhar Lodhi. Software Engineering - IEEE 1.The application of a systematic, disciplined, quantifiable approach to the.
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
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.
OHT 23.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The benefits of use of standards The organizations involved in standards.
Introduction to Software Engineering LECTURE 2 By Umm-e-Laila 1Compiled by: Umm-e-Laila.
Lecture 1 Introduction to Software Engineering
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
Capability Maturity Model. History Effort started by SEI and MITRE Corporation  assess capability of DoD contractors First version published in.
By Ritesh Reddy Nagaram.  Organizations which are developing software processes are facing many problems regarding the need for change of already existing.
Quality Concepts within CMM and PMI G.C.Reddy
1 Project Quality Management Lec#12 Project Quality Processes Ghazala Amin.
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.
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,
CMMI. 1.Initial - The software process is characterized as ad hoc, and occasionally even chaotic. Few processes are defined, and success depends on individual.
CMMI FRAMEWORK SRIKANTH DEVINENI. Process failure is recognised when Project is delivered late Too much redundancy Customer complaints after delivery.
Introduction to Software Capability Maturity Model.
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.
Purpose: The purpose of CMM Integration is to provide guidance for improving your organization’s processes and your ability to manage the development,
COMP 6710 Course NotesSlide 3-0 Auburn University Computer Science and Software Engineering Course Notes Set 3: Software Process Maturity Computer Science.
Software Engineering (CSI 321) Software Process: A Generic View 1.
The Capability Maturity Model for Software: An Overview
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
Capability Maturity Model. CS460 - Senior Design Project I (AY2004)2 Immature Organisations Software processes are often rigorously followed. Organisation.
1 These slides are designed to accompany Software Engineering: A Practitioner’s Approach, 7/e (McGraw-Hill 2009). Slides copyright 2009 by Roger Pressman.
Cmpe 589 Spring Fundamental Process and Process Management Concepts Process –the people, methods, and tools used to produce software products. –Improving.
CMMI for Services, Version 1.3
By Manish Shrotriya CSE MS Software Engineering vs Software Project Engineering Goals: Develop quality software What is quality of a software.
Capability Maturity Model. What is CMM? n CMM: Capability Maturity Model n Developed by the Software Engineering Institute of the Carnegie Mellon University.
State of Michigan Achieving Software Process Improvement with
CS4311 Spring 2011 Process Improvement Dr
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)
Quality management standards
Software Engineering Lecture 16.
Software Engineering I
Capability Maturity Model
Capability Maturity Model
Presentation transcript:

OHT 2.1 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Software Quality assurance (SQA) SWE 333 Dr Khalid Alnafjan

OHT 2.2 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is a CMMi? A Capability Maturity Model (CMMi) is a reference model of mature practices in a specified discipline, used to improve PROCESS at work The results of adopting CMMi is a much better product or process quality. Before we focus on CMMi we need to understand the meaning of a PROCESS so What is a PROCESS ?

OHT 2.3 Galin, SQA from theory to implementation © Pearson Education Limited 2004 What is a process A process is a series of actions or steps taken in order to achieve a particular end in the form of a product or service We may not realize it, but processes are everywhere and in every aspect of our leisure and work. A few examples of processes might include: Preparing breakfast Placing an order Developing a budget Writing a computer program Obtaining application requirements And so on

OHT 2.4 Galin, SQA from theory to implementation © Pearson Education Limited 2004 The quality of a system is highly influenced by the quality of the process used to acquire, develop, and maintain it. even our finest people can’t perform at their best when the process is not understood or operating at its best.” Everyone realizes the importance of having a motivated, quality work force and the latest technology, but even the finest people can’t perform at their best when the process is not understood or operating at its best This premise implies a focus on processes as well as on products. Process Improvement

OHT 2.5 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Commitments consistently missed Late delivery Last minute crunches Increasing costs No management visibility into progress You’re always being surprised. Quality problems Too much rework Functions do not work correctly. Customer complaints after delivery Poor morale People frustrated Is anyone in charge? Symptoms of Process Failure

OHT 2.6 Galin, SQA from theory to implementation © Pearson Education Limited 2004 CMMI for Process Improvement The aim of CMMi is to improve processes so they can be performed in the best manner with least cost Use CMMI in process improvement activities as a collection of best practices framework for organizing and prioritizing activities support for the coordination of multi-disciplined activities that might be required to successfully build a product means to emphasize the alignment of the process improvement objectives with organizational business objectives

OHT 2.7 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Processes are ad hoc and improvised by practitioners and their management Process describes are not rigorously followed or enforced Performance is highly dependent on current practitioners Understanding of the current status of a project is limited Immature processes result in fighting fires: There is no time to improve – instead, practitioners are constantly reacting Firefighters get burned Embers might rekindle later Ad Hoc Processes (Not using CMMi)

OHT 2.8 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Process descriptions are consistent with the way work actually is done They are defined, documented and continuously improved Processes are supported visibly by management and others They are well controlled – process fidelity is evaluated and enforced There is constructive use of product and process enforced There is constructive use of product and process measurement Technology is introduced in a disciplined manner Improved Processes (Using CMMi)

OHT 2.9 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Process Improvement and Football - an example Let us take football as an example to show how process improvement can increase the quality of football game. We will compare how play is performed between a little league team and a professional football team

OHT 2.10 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Process Improvement and Football - an example What happens when a ball is hit to a Little League team? Everyone runs around at random. They might do the right thing, or they might not. The next time the ball is hit in the same place, they may do something different. What happens when a ball is hit to a professional team? Everyone moves in a coordinated fashion, based on practicing that play many times. Sometimes they fail to make the right play, but they almost always try to do the right thing. 10

OHT 2.11 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Process Improvement and Football - an example A professional football team is more "mature" than a Little League team (not referring to age). A professional team has self-perpetuating quality. They –Make good plays –Develop new players like themselves –Find ways to make better plays 11

OHT 2.12 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Process Improvement and Football - an example What happens when the team loses a star player? –Little League team gets much worse. –Professional team often has someone waiting to fill in. Self-improvement after a bad play… –Little League players don’t know what went wrong, or they blame each other. –Professional teams discuss their play and look for ways to improve. 12

OHT 2.13 Galin, SQA from theory to implementation © Pearson Education Limited 2004 … So what is CMMI? In the same way, high-quality software organizations are different from low-quality organizations. CMMI tries to capture and describe these differences. CMMI strives to create software development organizations that are “mature”, or more mature than before applying CMMI. 13

OHT 2.14 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Capability Maturity Model® Integration (CMMI®) Capability Maturity Modeling, CMM, and CMMI are registered in the U.S. Patent and Trademark Office by Carnegie Mellon University.

OHT 2.15 Galin, SQA from theory to implementation © Pearson Education Limited 2004 How CMMI Helps? CMMI provides guidance for improving an organization’s processes and ability to manage the development, acquisition and maintenance of products or services. CMMI places proven approaches into a structure that helps an organization: - appraise its organizational maturity or process area capability - establish priorities for improvement - implement these improvements

OHT 2.16 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Five levels of maturity … 16

OHT 2.17 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Summary of levels Level 1 – Initial. Anything at all. Ad-hoc and chaotic. Will have some successes, but will also have failures and badly missed deadlines. Level 2 – Repeatable. SW processes are defined, documented, practiced, and people are trained in them. Groups across an organization may use different processes. 17

OHT 2.18 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Summary of levels Level 3 – Defined. SW processes are consistent and known across the whole organization. Level 4 – Managed. SW processes and results are measured quantitatively, and processes are evaluated with this data. Level 5 – Optimizing. Continuous process improvement. Experimenting with new methods and technologies. Change processes when find something that works better. 18

OHT 2.19 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Level 1 – Initial Team tackles projects in different ways each time Can have strong successes, but may not repeat Some time/cost estimates are accurate, many far off Success comes from smart people doing the right things Hard to recover from good people leaving Frequent crises and "firefighting.” (Many believe this is standard for SW development. CMM says NO.) Most SW development organizations are Level 1. 19

OHT 2.20 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Level 2 – Repeatable Key areas –Requirements management –Software project planning –Project tracking and oversight –Subcontracts management –Quality assurance –Configuration management 20

OHT 2.21 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Level 3 – Defined Key areas. Level 2, plus… –Organization-wide process focus –Organization-wide process definition –Training program in above –Integrated software management (above applied per project) –Software product engineering (coding, etc.) –Inter-group coordination –Peer reviews 21

OHT 2.22 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Level 4 – Managed Key areas. Level 3, plus… –Quantitative process management (data gathering) –Quality management (data-driven quality improvement) 22

OHT 2.23 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Level 5 – Optimizing Key areas. Level 4, plus… –Defect prevention –Technology change management (bring in new methods) –Process change management (improve processes) 23

OHT 2.24 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Level 5 – Optimizing The optimizing level (Level 5) is not the destination of process management. The destination is better products for a better price: economic survival The optimizing level is a foundation for building an ever-improving capability. 24

OHT 2.25 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Example-Requirements Management SG 1: Manage Requirements SP1.1 : Obtain an understanding of the requirements SP1.2 : Obtain commitment to requirements SP1.3 :Manage Requirement Changes SP1.4 : Maintain bi- directional trace ability of Requirements SP1.5 : Identify inconsistencies between project work and requirements

OHT 2.26 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Time required to progress to next level 26 Capability level transition Mean time (months) No. of organizations Level 1 to level Level 2 to level Level 3 to level Level 4 to level Source: Based on Gartner Inc. (2001)

OHT 2.27 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Project Resources distribution 27 Percentage of project resources CMM capability level Original workReworking Testing and quality assurance

OHT 2.28 Galin, SQA from theory to implementation © Pearson Education Limited 2004 Versions of CMMI (capability maturity model integration) CMMI-SE/SW System Engineering CMM (SE-CMM) Software engineering CMM (SW-CMM) CMMI-SE/SW/IPPD/SS System Engineering CMM (SE-CMM) Software engineering CMM (SW-CMM) Integrated Product/Process Development (IPPD-CMM) Supplier Sourcing CMMI-SE/SW/IPPD System Engineering CMM (SE-CMM) Software engineering CMM (SW-CMM) Integrated Product/Process Development (IPPD-CMM) 28