Defects yet to be fixed Defects Time Total reported defects Defects fixed to date Defects Defects yet to be fixed As long as the gap between is increasing between the Time

Software Engineering II Lecture 16 Fakhar Lodhi

Defects Test cases Upper limit Actual defects Lower limit Defect line crosses the upper limit – bad product quality – maybe time to take a step back and try to fix the product design etc. Defect line crossing the lower limit – too good to be true – check the quality and coverage of your testing Test cases

Recap

Summary of Today’s Lecture

4 - 3 - 2 - 1 - 0 - Defect Ripple 1 2 3 4 5 6 7 8 9 Defect Fixed Three new defects appeared as a consequence of fixing defect 5 4 - 3 - 2 - 1 - 0 - Defect Ripple Too many ripples – highly coupled design 1 2 3 4 5 6 7 8 9 Defect Fixed

4 - 3 - 2 - 1 - 0 - Not - A - Defect Time 4 - 3 - 2 - 1 - 0 - Too many defects resolved as not a defect – quality of your requirements document or skill set of your testing team. Time

Feasibility 4 dimensions Technology Finance Time Resources Technology Is the project technically feasible? Is it within the state of the art? Can defects be reduced to a level matching the application needs? Finance Is it financially feasible? Can development be completed at a cost that software organization, its client, or the market can afford? Time Will the project time to market beat the competition? Resources Does the organization have resources needed to succeed?

Technology Is the project technically feasible? Is it within the state of the art? Can defects be reduced to a level matching the application needs?

Finance Is it financially feasible? Can development be completed at a cost that software organization, its client, or the market can afford?

Time Will the project time to market beat the competition?

Resources Does the organization have resources needed to succeed? HW/SW tools Reusable software components People