Browse > Article
http://dx.doi.org/10.3745/KIPSTD.2006.13D.1.061

Applying rework indicator to control software development project  

Han Hyuk-Soo (상명대학교 소프트웨어학부)
Kim Han-Saem (상명대학교 대학원 컴퓨터과학과)
Publication Information
The KIPS Transactions:PartD / v.13D, no.1, 2006 , pp. 61-66 More about this Journal
Abstract
It is reported that the success ratio of software development projects has been only 30%. Many causes lower project's chance of success, particularly lack of systematic project management. Especially, moving on the next phase of project with unsatisfactory outputs can be very problematic because it can cause much waste of resource, time and even lead to the failure of the whole project. Peer review and inspection are some of the practices designed to prevent such waste and possible failure. When defects are identified through such progress, each developer has to work on the product component again and fix the problem. This process is called rework. In this paper, we propose a method for improving quality of reworked product component to prevent excessive cost and time consumed caused by moving on the next phase of a project with a problematic product component. More specifically, this paper suggests a rework indicator that measures the level of rework based on its complexity and severity and is used to choose appropriate checking method on reworked product component. The research also confirmed the method's usefulness and effectiveness by applying the suggested method on four projects.
Keywords
Software Project Management; Rework; Inspection; Peer Review; Software Measurement; GQM;
Citations & Related Records
연도 인용수 순위
  • Reference
1 John H. Baumert, Mark S. McWhinney, 'Software Measures and the Capability Maturity Model', Technical Report CMU/SEI-92-TR-025, Software Engineering Institute, 1992
2 James A. Rezum, 'Defining and Understanding Software Measurement Data', Software Engineering Institute
3 William A. Florac, Robert E. Park and Anita D. Carleton, 'Practical Software Measurement: Measuring for Process Management and Information'. CMU/SEI-97HB-003, Software Engineering Institute, 1997
4 Wolfhart Goethert and Will Hayes, 'Experiences in Implementing Measurement Programs', Technical Note CMU/SEI-2001-TN-026, Software Engineering Measurement and Analysis Initiative, 2001
5 M.B.Chrissis, M.Konrad and S Shrum, 'CMMI Guidelines for process integration and product improvement', Addison-Wesley, 2003
6 Donald R. McAndrews, 'Establishing a Software Measurement Process', Technical Report CMU/SEI-93-TR-016, Software Engineering Institute, 1993
7 Rini van Solingen, Egon Berghout, 'The Goal/Question/Metric Method: A Practical Guide for Quality Improvement of Software Development', McGraw-Hill, 1999
8 John McGarry, et al, 'Practical Software Measurement-Objective Information for Decision Makers', Addison-Wesley, 2001
9 CMMI Product Team, 'Capability Maturity Model® Integration (CMMISM), Version 1.1, CMMISM for Software Engineering (CMMI-SW, V1.1)', CMU/SEI-2002-TR-029, 2002
10 R.Pressman 'Software Engineering: A practitioner's approach', Addison Wesley, 2004
11 Wolfhart Goethert, Matthew Fisher, 'Measuring Acquisition Process', SEPG 2002, 2002
12 The Standish Group International Inc., 'Latest Standish Group CHAOS Report Shows Project Success Rates Have Improved by 50%', http://www.standishgroup.com/press/, 2003
13 Watts S. Humphrey, 'A Personal Commitment to Software Quality', The Software Engineering Institute Carnegie Mellon University, 1994   DOI   ScienceOn