This document presents software product metrics we usually use to build software defect prediction models. 1 Software product metrics This document presents software product metrics we usually use to build software defect prediction models, especially those built by Madeyski and Jureczko [6, 5, 4]. • The metrics suite suggested by Chidamber and Kemerer [2]: Weighted Methods per Class (WMC). The...

The concepts of implementation and extension complexities were developed in connection with an object oriented reengineering of a legacy CAD system [KA97]. These concepts consider a software system as an implementation of a number of different algorithms. Ideally, an algorithm in an object oriented (O-O) system is implemented by a single method that only processes data in its own object. Such a...

Previous studies reported that reviewers ask questions and engage in discussions during software reviews the concerns identified by help detect defects. Although such about potential defects lead to finding defects, review metrics as number of detected do not always reflect because which are applicable material excluded from This paper proposes a metric, discussions, identifies reviews. First, ...

Jon Avotins Department of Software Development Monash University, Caul eld Campus PO Box 197, Caul eld East Australia 3145 Email: [email protected] Abstract Two of the principal lessons to emerge from software measurement over the last twenty years have been the need for an e ective approach to metric modelling (Shepperd and Ince 1993), and the need for automated support of such a mo...

Software metrics should be used in order to improve the productivity and quality of software, because they provide critical information about reliability and maintainability of the system. In this paper, we propose a cognitive complexity metric for evaluating design of object-oriented (OO) code. The proposed metric is based on an important feature of the OO systems: Inheritance. It calculates t...

This paper proposes System Test Point (STP), a new metric for estimating system test effort. The proposed Metric encompasses various attributes, which affect testing effort and can be tailored to a specific project environment. A survey was conducted for expert ratings on the 12 identified attributes, which affect system testing. A Software package "RISK 4.0" was used to find the correlation be...

The purpose of this paper is to describe a practical view of software measurement that formed the basis for a company-wide software metrics initiative within Motorola. A multi-dimensional view of measurement is provided by identifying different dimensions (e.g., metric usefulness/utility, metric types or categories, metric audiences, etc.) that were considered in this company-wide metrics imple...

This paper is based upon the type of software metrics available and their behavior on a piece of code in static environment and in run-time/ dynamic environment. Observing the current trend in the research in software metrics, it is noted that the work is majorly being carried in either using the metrics to evaluate the performance of any software or a source code, or in the path of creating so...

We propose a novel, practical coverage metric called “location pairs” (LP) for concurrently-accessed software components. The LP metric captures well common concurrency errors that lead to atomicity or refinement violations. We describe a software tool for measuring LP coverage and outline an inexpensive application of predicate abstraction and model checking for ruling out infeasible coverage ...