Object-Oriented Metrics: A Review of Theory and Practice

El-Emam, Khaled

doi:10.1007/978-0-387-21599-0_2

Cited by 28 publications

(13 citation statements)

References 69 publications

(100 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…High cognitive complexity leads to a component exhibiting undesirable external qualities, such as increased fault-proneness and reduced maintainability. Further detailed elaboration of this model has been recently made [32]. Hatton has extended this general theory to include a mechanism for thresholds.…”

Section: Theoretical Justificationmentioning

confidence: 99%

See 1 more Smart Citation

Methodology for Validating Software Product Metrics

Emam

Schneidewind²

2002

Encyclopedia of Software Engineering

View full text Add to dashboard Cite

A large number of software product metrics have been proposed in software engineering. We use the term metric here to be consistent with prevailing international standards. Product metrics quantitatively characterize some aspect of the structure of a software product, such as a requirements specification, a design, or source code. They are also commonly collectively known as complexity metrics . While many of these metrics are based on good ideas about what is important to measure in software to capture its complexity, it is still necessary to systematically validate them. Two types of validation are recognized internal and external. Internal validation is a theoretical exercise that ensures that the metric is a proper numerical characterization of the property it claims to measure. Demonstrating that a metric measures what it purports to measure is a form of theoretical validation. Typically, one defines the properties of the attribute that is to be measured, for example, the properties of module coupling. Then one demonstrates analytically that the product metric satisfies these properties. External validation involves empirically demonstrating that the product nature is associated which is important external metter or an improvement is shown above. Internal and external validation are also commonly referred to as theoretical and empirical validation respectively This article presents a comprehensive methodology for validating software product metrics. Our focus will be limited to empirical validation.

show abstract

Section: Theoretical Justificationmentioning

confidence: 99%

“…Based on this argument, one can hypothesize threshold effects for many contemporary product metrics. El Emam has elaborated on this mechanism for object-oriented metrics [32].…”

Section: Theoretical Justificationmentioning

confidence: 99%

Methodology for Validating Software Product Metrics

Emam

Schneidewind²

2002

Encyclopedia of Software Engineering

View full text Add to dashboard Cite

show abstract

“…By ensuring appropriate computation of measures of internal properties, the framework can allow practitioners to focus on the issue of appropriate linkages between internal properties and external characteristics such testability, reliability and maintainability, which makes then very important to practitioners at all levels [12,28]. Such external characteristics are visible to the users, and therefore, remain the goal for measurement practices, and visualization mechanisms [22].…”

Section: Discussionmentioning

confidence: 99%

Object-oriented product metrics: A generic framework

Vaishnavi

Purao

Liegle

2007

Information Sciences

View full text Add to dashboard Cite

“…It is from a set of measures proposed by Chidamber and Kemerer (1994). RFC is the set of methods in a class and the set of methods that can be invoked by a method within that class (Chidamber and Kemerer, 1994;El-Emam, 2002). The complexity measure, churned LOC were computed for XRS files by summing total changed LOC and inserted total LOC for each release.…”

Section: Quantitative Datamentioning

confidence: 99%

Distributed software development in an offshore outsourcing project: A case study of source code evolution and quality

Jabangwe

Šmite

Hessbo

2016

Information and Software Technology

View full text Add to dashboard Cite

Context: Offshore outsourcing collaborations can result in distributed development, which has been linked to quality-related concerns. However, there are few studies that focus on the implication of distributed development on quality, and they report inconsistent findings using different proxies for quality. Thus, there is a need for more studies, as well as to identify useful proxies for certain distributed contexts. The presented empirical study was performed in a context that involved offshore outsourcing vendors in a multisite distributed development setting.Objective: The aim of the study is to investigate how quality changes during evolution in a distributed development environment that incurs organizational changes in terms of number of companies involved.Method: A case study approach is followed in the investigation. Only post-release defects are used as a proxy for external quality due to unreliable defect data found pre-release such as those reported during integration. Focus group meetings were also held with practitioners.Results: The results suggest that practices that can be grouped into product, people, and process categories can help ensure post-release quality. However, postrelease defects are insufficient for showing a conclusive impact on quality of the development setting. This is because the development teams worked independently as isolated distributed teams, and integration defects would help to better reflect on the impact on quality of the development setting.Conclusions: The mitigation practices identified can be useful information to practitioners that are planning to engage in similar globally distributed development projects. Finally, it is important to take into consideration the arrangement of distributed development teams in global projects, and to use the context to iden- tify appropriate proxies for quality in order to draw correct conclusions about the implications of the context. This would help with providing practitioners with wellfounded findings about the impact on quality of globally distributed development settings.

show abstract

Object-Oriented Metrics: A Review of Theory and Practice

Cited by 28 publications

References 69 publications

Methodology for Validating Software Product Metrics

Methodology for Validating Software Product Metrics

Object-oriented product metrics: A generic framework

Distributed software development in an offshore outsourcing project: A case study of source code evolution and quality

Contact Info

Product

Resources

About