Software ¡Process ¡ Improvement ¡Plan ¡– ¡ INF ¡5181 ¡Presentation ¡ Study of a Software Bug-Fixing Project at a large software outsourcing company Yannick LYF 20 Sep 2012
Project ¡Context ¡ O Infosys Ltd – Indian multinational provider of business consulting, technology, engineering and outsourcing services company* O Client Project – Big European Insurance company O Bug-Fixing of a (VB6 to VB.NET) Software Migration Project – Involving testing, debugging, and fixing of defects raised by users at client location * Source: http://en.wikipedia.org/wiki/Infosys
Project ¡Issues ¡ O Poor understanding of bug descriptions O Syntax, Semantics, and Pragmatics Europe O High bug-fixing turnaround time O Poor code quality (Adherence, style) O Partial / Incomplete bug fixes Pune Bangalore O Frequent “bug reopens” O Code-rewrite effort O Lack of highly trained staff O Productivity nuisances Mauritius O Low bug fix count (1-2) per day O Poor, inefficient, unequal utilization rate Image courtesy: http://en.wikipedia.org/wiki/File:World_Map_flat_Mercator.png
Improvement ¡Goals ¡ O Easy analysis and reproduction of bugs O Through re-structuring of bug descriptions O Improved Bug-Fixing turnaround time: <= 2 days O Code quality Improvements: 100 % random checks O Code-Rewrite Effort: < 20 % of total time / week O Less bugs re-opened due to poor code fixing and new bugs caused by previous code fixes O Better training support for new and existing staff O Higher Productivity: min. of 4-5 bug fixes / day O Better utilization rate: > 90% utilization / day
Recommend
More recommend