Chapter 19 Process Quality. 山东大学计算机学院 2 outline  Then meaning of process quality  Process measurement  COQ  Failure costs, Appraisal costs, Prevetion.

Slides:



Advertisements
Similar presentations
Becoming a High Impact Board Susan Salter Director of Board Development Alabama Association of School Boards.
Advertisements

ICS 417: The ethics of ICT 4.2 The Ethics of Information and Communication Technologies (ICT) in Business by Simon Rogerson IMIS Journal May 1998.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #7 Software Engineering.
W5HH Principle As applied to Software Projects
山东大学齐鲁软件学院 1 Chapter 9 Managing Schedules. 山东大学齐鲁软件学院 2 In the chapter  How to develop schedules to track the progress of your work.  How to use checkpoints.
Personal Software Process
Software Quality Engineering Roadmap
The Software Process Strategy The Software Process Strategy Part III.
© 2010 John Dalbey Ch 9: Reviews Humphrey proposes that personal reviews will result in improved quality. Now that we have a defined process and some real.
Software Development Process. Process Improvement Using the Shewhart Cycle 1.PLAN - Plan a change aimed at improvement, collect data, and establish a.
CS 350: Introduction to Software Engineering Slide Set 5 Software Quality C. M. Overstreet Old Dominion University Spring 2006.
Lecture 2b: Software Project Management CSCI102 - Introduction to Information Technology B ITCS905 - Fundamentals of Information Technology.
Fundamentals of Information Systems, Second Edition
Notion of a Project Notes from OOSE Slides - modified.
Performance Measurement and Strategic Information Management
1 Software Testing and Quality Assurance Lecture 1 Software Verification & Validation.
Fundamental of Software Project Management Team Assignment 1 – K15T2 – Team 07.
Using A Defined and Measured Personal Software Process Watts S. Humphrey CS 5391 Article 8.
Personal Software Process Overview CIS 376 Bruce R. Maxim UM-Dearborn.
Introduction to Computer Technology
Personal Software Process Software Quality CIS 376 Bruce R. Maxim UM-Dearborn.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Hazard Identification
PowerPoint Presentation for Dennis, Wixom & Tegardem Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Software Quality Chapter Software Quality  How can you tell if software has high quality?  How can we measure the quality of software?  How.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
Chapter 15 Projecting Defects( 缺陷预测 ). 山东大学齐鲁软件学院 2 outline  Analyze and use your defect data to help improve both planning accuracy and product quality.
Be more effective at “planning the work and working the plan” Project Management Tips.
Prologue: The Software Process. Main Phases of Software Process 1. Requirements Analysis (answers “WHAT?”) Specifying what the application must do 2.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 10: Testing and Inspecting to Ensure High Quality Part 4:
THE MANAGEMENT AND CONTROL OF QUALITY, 5e, © 2002 South-Western/Thomson Learning TM 1 Chapter 8 Performance Measurement and Strategic Information Management.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Disciplined Software Engineering Lecture #8 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
INFO 637Lecture #41 Software Engineering Process II Development Plan INFO 637 Glenn Booker.
Chapter 12 Defects. 山东大学计算机学院 2 In the chapter  Concept of Defects  Defects and software quality  What is Defect?  Defects versus Bugs  Defect types.
Chapter 3: Software Maintenance Process Omar Meqdadi SE 3860 Lecture 3 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
CS 350, slide set 6 M. Overstreet Old Dominion University Spring 2005.
Software Development Process and Management (or how to be officious and unpopular)
Disciplined Software Engineering Lecture #7 Software Engineering Institute Carnegie Mellon University Pittsburgh, PA Sponsored by the U.S. Department.
© 1998 Carnegie Mellon UniversityTutorial The Personal Software Process (PSP) The overview of the PSP that follows has been built from material made.
1 复习. 2 Main Three Elements  Plan  Period plan  product plan  Project Plan  Measure  Size measurement  defect measurement  quality measurement.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 1 1 Disciplined Software Engineering Lecture #8 Software Engineering.
Software Engineering Prof. Dr. Bertrand Meyer March–June 2007 Chair of Software Engineering Lecture 2: The Personal Software Process.
CS 350, slide set 5 M. Overstreet Old Dominion University Spring 2005.
INFO 636 Software Engineering Process I Prof. Glenn Booker Week 9 – Quality Management 1INFO636 Week 9.
This chapter is extracted from Sommerville’s slides. Textbook chapter
PSP Quality Strategy [SE-280 Dr. Mark L. Hornick 1.
1 The Personal Software Process Estimation Based on Real Data* * Would Martin Fowler approve? “I want you to take this personally…”
Copyright © 1994 Carnegie Mellon University Disciplined Software Engineering - Lecture 7 1 Design and Code Reviews - Overview What are design and code.
9. Applying scientific tools & techniques for improving customer satisfaction.
SE-280 Dr. Mark L. Hornick 1 Design and Code Reviews Review Checklists.
Chapter 3: Software Project Management Metrics
Implementation Phase CS4311 – Spring 2008 References: Shach, Object Oriented and Classical Software Engineering E. Braude, Software Engineering, an Object-Oriented.
This material is approved for public release. Distribution is limited by the Software Engineering Institute to attendees. Sponsored by the U.S. Department.
Chapter 8. The Process Phases 1. Launching teams 2. The development strategy 3. Team planning 4. The requirements process 5. Designing with teams 6. Implementation.
COSTING AND THE VALUE CHAIN CHAPTER 18 PAGE# 794 Faisal
PRODUCT IMPLEMENTATION Chapter 8 Tawatchai Iempairote September 23, 2041.
Approaches to ---Testing Software Some of us “hope” that our software works as opposed to “ensuring” that our software works? Why? Just foolish Lazy Believe.
Focus on design principles and on a process for doing design = To produce a precise, complete, high- quality foundation for product implementation.
Using Total Quality Management Tools to Improve the Quality of Crash Data John Woosley Louisiana State University.
Monitoring, review and audit.
Reviews Chapter 5 Applied Software Project Management, Stellman & Greene See also:
This chapter is extracted from Sommerville’s slides. Textbook chapter 22 1 Chapter 8 Validation and Verification 1.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
Personal Software Process Team Software Process
SQA for Individuals based on
Team Software Process (TSP)
Presentation transcript:

Chapter 19 Process Quality

山东大学计算机学院 2 outline  Then meaning of process quality  Process measurement  COQ  Failure costs, Appraisal costs, Prevetion Costs  Simplifications of COQ- Failure costs, Appraisal costs  A/FR: The Appraisal/Failure Ratio  The calculation of A/FR

山东大学计算机学院 3 Process measure Quality of programQuality of processThe way you work Better programChange the way you work 取决于 Know your process Measure the quality of process need

山东大学计算机学院 4 Quality Measurement  It concerns:  The volume of products produced;  The quality of the products;  The time and resources required.  In this class, only the perspective of defect injection and defect removal are being addressed.

山东大学计算机学院 5 What not introduced?  Requirement  Usability  Compatibility  Interface  ……

山东大学计算机学院 6 Defect-Removal Paradox  One interesting phenomenon: Defect-removal rates decline as product quality improves.  It seems like a paradox, but it’s natural.  Clearly true for reviewing and testing;  Less true for compiling.

山东大学计算机学院 7 Defect-Removal Strategy  Defects can divided into two classes:  Involve only one module  Involve interactions among the modules  Defect –removal strategy:  Strive to develop modules of the highest possible quality;  Do thorough inspections of all the modules interfaces and interactions.  Inspect the requirements to ensure that all of the important capablities are properly understood, designed, and implemented;

山东大学计算机学院 8 Defect-Removal Strategy  Inspect the system and program design against the requirements to ensure that it properly address all the key requirements.  Do exhaustive unit testing after the code has been inspected;  Do comprehensive intergration testing;  Do thorough system testing.  The first step is up to you,but most important!

山东大学计算机学院 9 Cost of Quality--- COQ  Balance the time spent and quality of products produced.  COQ (cost measured in time)  Failure costs of quality (纠错成本) All the costs of fixing defects.  Fixing defects time; Debugging time; redesigning, retesting or recomiling;  Appraisal costs of quality (评价成本) all the work to assess the product to see if it has defects.  Code reviewing time; compiling and testing time;  Exclude the time spent on defects fixing in above phase.  Prevention costs of quality (预防成本) modify the process to avoid injecting defects  Do analysing time; process of development work to improve the requirements, design, or implementation;  Building prototypes.

山东大学计算机学院 10 Simplifying the calculation of COQ  PSP counts all compile time as failure costs.  Even include some defect-free compile time.  PSP counts all test time as failure costs.  PSP counts all review time as appraisal costs.  Appraisal COQ: sum of all review time as a percentage of total development time;  Failure COQ: sum of all compile and test time as a percentage of total development time;  See the example of table 19.1

山东大学计算机学院 11 A/FR-Appraisal/Failure Ratio  Simpler calculate: code review time/(compile time+test time);  It measures the relative amount of time spent finding defects before the first compile.  You should attempt to achieve A/FR of 2 or more.  Why? See figure  Improving the product quality;  Saving test time.

山东大学计算机学院 12

山东大学计算机学院 13 How to achieve A/FRs above 2.0 ?  Putting more time on code reviewing;  This will not improve program quality!!!  It is important to productively use review time in finding defects.  Code review with high quality.  For frequently missed defects.  Insert appropriate steps in checklist.  Take more time,find more defects,increase A/FR

山东大学计算机学院 14 Improving review rates  Continue check the defect data  Continue update your personal checklist.  How?

山东大学计算机学院 15 Calculating the true COQ  Break the review, compile, and test times to their respective appraisal and failure time.  C=C F +C A ; R=R F +R A ; T=T F +T A.  Appraisal COQ=100*(R A +C A +T A )/totaltime  Failure COQ=100*(R F +C F +T F )/totaltime.  See example in table 19.1 and table  To use this method,you need a stopwatch!

山东大学计算机学院 16 Summary  Process measurement;  COQ and its calculation;  Meaning of A/FR.  The value of A/FR should be equal to or more than 2.0.  Why?  How?

山东大学计算机学院 17 assignment  Determine the value of A/FR for all the programs you have written.  Show the relations of A/FR and test defects/KLOC like figure 19.1

Chapter 20 A Personal Commitment to Quality

山东大学计算机学院 19 outline  Why you should establish quality as your highest priority?  Personal life purposes.  Just for discussion, no content for examination.

山东大学计算机学院 20 The important of quality  Quality of software will be critically important to your employers and to your customers  Software defects can cause economic damage and even physical harm.  Airplane,auto,air traffic, factories, power plant, nuclear power plants.

山东大学计算机学院 21 The increasing risk of poor quality  Any defect in a small part of a large program could potentially cause serious problem.  Safety system also made of software.  Most common cause of problem is simple oversights and goofs.  Feel simple mistakes will be simple find.  The quality of large system depend on small programs.

山东大学计算机学院 22 Making a commitment to quality  To decided that quality is important  To establish the goal of producing defect-free program  To manage our fallibility( 失误 ).  Care enough to continue doing.

山东大学计算机学院 23 Your personal objectives  What do you want from your life?  This is a big problem!  One way is to have status or power.  Is it good?  No answer!

山东大学计算机学院 24 The rewards of accomplishment  Whatever you build,quality will be key!  Sloppy job will destroy your pride in the work and it will limit your satisfaction with life.  When do quality work, you will be proud.  So ask yourself the question:  “Do I want to feel proud of what I do?”

山东大学计算机学院 25  Challenge yourself to do superior work and you will be surprised at what you can accomplish.

The end Thanks very much!