Applying Software Defect Prediction Model for Reliable Product Quality

.. Problem definition & its importance .. Potential Solution .. Empirical Defect Prediction Model framework .. Creating the baseline model .. Creating the defect profile for a project .. Case Study Applying the model .. Case Study -Process improvements .. Model Strengths & Results .. Critique of the model .. Limitation , Expectations & Usage .. Barriers .. References & Acronyms Problem definition & its importance .. Problem definition & its importance .. Telecom software / systems need to have reliable product quality .The Quality goal is very aggressive .. zero or only very few high severity defects in the customer site .. need to meet the Reliability / Availability requirements -99.999% .. Need to be well within the Down time - Outage frequency / duration limits .. Need to be the industry best-in-class TL 9000 Metrics on availabilty .. The additional challenges are .. The product code size is huge .. The time to market & schedule adherence are very important in addition to the Quality. .. The teams are often distributed globally increasing the handoffs between various teams during the product development .. To ensure reliable product quality the organization needs a accurate Software Defect Prediction Model that can predict the residual defects which will be found by the customer .. Need a simple model ( easy to understand ,create ,use & maintain ) .. Need acceptance of the model within the organization across various departments .. Industry need- a model that will help to plan , budget & track Quality of the product