This paper uses the case study and its results to qualitatively compare our approach against current ad hoc practices used to improve existing measurement frameworks

Counts of defects found during the various defect detection activities in software projects and their classification provide a basis for product quality evaluation and process improvement. However, since defect classifications are subjective, it is necessary to ensure that they are repeatable (i.e., that the classification is not dependent on the individual). In this paper we evaluate a slight adaptation of a commonly used defect classification scheme that has been applied in IBM's Orthogonal Defect Classification work, and in the SEI's Personal Software Process. The evaluation utilizes the Kappa statistic. We use defect data from code inspections conducted during a development project. Our results indicate that the classification scheme is in general repeatable. We further evaluate classes of defects to find out if confusion between some categories is more common, and suggest a potential improvement to the scheme. Keywords: defect classification, software inspections, measurement rel...

A major characteristic of software engineering compared with other engineering disciplines, is our inability to get the product right first time around. Change is an intrinsic and essential part of software development, and for good reasons. It is difficult to specify what is required without having some form of model to help formalise the problem. The real-world problem, which the software exists to solve, is itself subject to change. And even if we know what to produce, the design, and development of these invisible, intangible, and complex software products is still inherently difficult. At the same time, software has become a critical competitive factor for many organisations. For instance, the development of software for aeroengine controllers can be critical to whole aeroengine developments. The ability to produce software of higher quality, for less cost, in shorter timescales is a matter of survival. Organisations must continually seek to improve the processes by which software...

This paper examines only just a few, but extremely impressive examples of "successful Software Process Improvement (SPI)," a highly controversial and much disputed field. SPI is the discipline of characterizing, defining, measuring, and improving software management and engineering processes, leading to successful software engineering management, higher product quality, greater product innovation, faster cycle times, and lower development costs, simultaneously. The case studies, examples, information, and data examined in this paper were the result of a notion called "using powerful solutions." Powerful SPI solutions are examined here and others introduced, in order to lead the way and encourage others that have not been successful with SPI, or have yet to try SPI, to use high leverage strategies as methods of making quantum leaps forward in bottom line organizational performance. This paper represents a significant departure from traditional SPI methods, in that it simply advises o...

This paper will present a framework developed by IBM for classifying and analyzing defect data collected during software development. The paper will describe Orthogonal Defect Classification (ODC) and illustrate how ODC can be used to measure development progress with respect to product quality and identify process problems. Next, the paper will present the results of a feasibility study conducted by the Motorola Corporate Software Center, Software Solutions Lab (CSC/SSL) and the Cellular Infrastructure Group, GSM Products Division's Base Station Systems (GSMBSS) software development group using ODC. Finally, GSMBSS's future plans for deploying ODC are discussed. KEY WORDS - Defect Prevention, Orthogonal Defect Classification, Inspections, Process Improvement, Quantitative Process Management, Root-Cause Analysis. 1. Introduction Formal Inspections are currently used throughout Motorola to identify software errors near the point of insertion. In 1996 nearly 85% of all product softwar...

This 288-page study is one of the most comprehensive comparisons of the costs and benefits of software process improvement (SPI) methods to-date. It begins by exhibiting a comprehensive survey of software process improvement (SPI) literature, methods, approaches, metrics, costs and benefits, and existing comparisons. And, it concludes with the design of an in-depth return-on-investment (ROI) model, stunning breakeven analyses, and an extensible methodology for comparing software process improvement (SPI) cost and benefit data. It contains some very surprising results concerning the Personal Software Process (PSP), the Michael Fagan software inspection process, software reuse, defect prevention, software testing, cleanroom, Software Capability Maturity Model (SW-CMM or CMM), and ISO 9001.

Abstract not found