Object-Oriented Software Measures.

Author(s):  
Clark Archer ◽  
Michael Stinson
2001 ◽  
Vol 59 (1) ◽  
pp. 65-82 ◽  
Author(s):  
Witold Pedrycz ◽  
Giancarlo Succi ◽  
Petr Musı́lek ◽  
Xiao Bai

Author(s):  
ROBERT M. SZABO ◽  
TAGHI M. KHOSHGOFTAAR

Building on our earlier work in detecting high risk software modules in object-oriented systems, we extend the two group discriminant classification model to three risk groups. First, we give an overview of the discriminant modeling methodology. Using traditional and object-oriented software product measures collected from a commercial system, we develop two discriminant fault models. One model incorporates only traditional measures while the other model includes both traditional and object-oriented measures. The independent variables of both models are principal components derived from the observed software measures. The models are used to classify the modules comprising the system into three groups: high, medium, and low risk. Quality of fit and classification performance of both models are reported. We show that for this case study, the addition of the object-oriented measures enhances the model by reducing the overall misclassification rate and significantly reducing the misclassifications in the medium group. Last of all, we tender a cost based method to determine under what condition a three group model is superior to the simpler two group model. Our results suggest that additional case studies are needed to help develop a clearer picture of three group discriminant models and the utility of object-oriented software measures in general.


Author(s):  
Jana Dospisil

This chapter describes the foundation and properties of object-oriented software measures. Many software measures for object-oriented applications have been developed and tested in the development environment. However, the process of defining new measures is still alive. The reason for such development lies in difficulties associated with understanding and maintaining object-oriented applications. It is still difficult to relate the measures to the phenomena we want to improve. Do our measurements indicate problems in reliability, maintenance, or too much complexity of some portions of the application? In order to reduce the complexity of software, new development methodologies and tools are being introduced. An example of the new approach to development is separation of concern. The tools, such as Aspect/J (Kiezales et al., 1997) or Hyper/J (Ossher & Tarr, 1998), facilitate the development process. There does not seem to be a sound metrics suite to measure complexity and efficiency of applications developed and coded with Aspect/J or Hyper/J. In this chapter, we attempt to review the current research into object-oriented software metrics and suggest theoretical framework for complexity estimation and ranking of compositional units in object-oriented applications developed with Hyper/J.


2000 ◽  
Vol 147 (3) ◽  
pp. 61 ◽  
Author(s):  
V. Cortellessa ◽  
G. Iazeolla ◽  
R. Mirandola

Sign in / Sign up

Export Citation Format

Share Document