Candidate metrics for object-oriented software within a taxonomy framework

Abstract

This paper offers an overview of the state-of-the-art in OO metrics as well as some new contributions. The usefulness of metrics is reviewed. The inappropriateness of "traditional" metrics to encompass development under the OO paradigm is discussed. A framework for classifying metrics is suggested. Metrics are classified along two vectors: category and granularity. The usefulness and rationale behind each category are presented. Candidate metrics are suggested within the proposed framework. Finally, some research directions that require further effort are identified. I -IntroductionObject-Oriented (OO) technology has been pointed out as being one of the keys for solving the software crisis problem. For the past few years we have witnessed a burst in the availability of OO analysis and design methodologies, languages, database management systems and tools. However, little work has been done in the area of management of OO software development.One of the key issues in the management of the development process is the capability to measure and record the relevant attributes of the software products and of the process itself in a structured, coherent framework. The availability of metrics helps managers in the staffing, costing, scheduling and controlling activities of the development life cycle and contributes to the overall objective of software quality. The need for software metrics is now fully recognized by the software engineering community and included in standards like the ISO 9000-3 (ISO, 1991a). This paper is organized as follows: section II reviews the reasons why metrics are needed within the software development process, when using the OO paradigm; section III introduces a classification framework for OO software metrics; section IV analyses the need for each category and introduces one possible selection of metrics; section V attempts to draw some conclusions and to suggest some research directions.

Penerapan Dominance-Based Rough Set Approach Dalam Pemeringkatan Kualitas Desain Software Berorientasi Objek

“…Contohnya, metrics yang diusulkan oleh Abreu [4], C.K metrics [5] masing-masing secara berurut menyatakan Pdominating set (kumpulan yang mendominasi P) dan P-dominated set (kumpulan yang didominasi oleh P). Gagasan utama dari filosofi rough set adalah memperkirakan sebuah pengetahuan berdasarkan pengetahuan yang sudah ada.…”

“…Ranking 2+: (1) 0,572 0,572 java.lang (2) 0,442 0,442 java.math (3) 0,531 0,531 java.net (4) 0,577 0,577 java.text (5) 0,581 0,581 java.util (6) 0,654 0,654 java.awt (7 (1,2), (3,2), (4,2), (5,2), (6,1), (6,2), (6,3), (6,4), (6,5) (2,5), (2,6), (3,6), (4,6), (5,6); jika xP 3 <-1 y dan xP 4 <-1 y, maka xS c y, (3,1), (3,4), (3,5), (3,6); …”

Critical Analysis of Traditional Size Estimation Metrics for Object Oriented Programming

“…Out of these, the metrics proposed by Abreau [3,4], J. Bansiya et al [5], Briand et al [6], Chidamber and Kemerer [7], Lorenz et al [8], W. Li et al [18,19] are mostly referred.…”

“…The MOOD metric, proposed by Abreu [3], is used to measure the various features of object-oriented design methods such as …”

Adaptive Software Fault Prediction Approach Using Object-Oriented Metrics

“…Furthermore, applying equal validation effort to all parts of a software system has become cost-prohibitive [12]. Hence, identifying faulty modules early would support the development of reliable systems through improved scheduling and quality control.…”