Software measure specification

Gustafson, David A.; Tan, Joo; Weaver, Perla

doi:10.1145/256428.167075

Cited by 6 publications

(3 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Other ways of formalizing attributes may be used such as Measurement Theory [26], [27]. As shown in [18], the use of properties is not in contradiction with Measurement Theory.…”

Section: Discussionmentioning

confidence: 99%

An operational process for goal-driven definition of measures

Briand

Morasca

Basili

2002

IIEEE Trans. Software Eng.

102

View full text Add to dashboard Cite

Abstract-We propose an approach (GQM/MEDEA) for defining measures of product attributes in software engineering. The approach is driven by the experimental goals of measurement, expressed via the GQM paradigm, and a set of empirical hypotheses. To make the empirical hypotheses quantitatively verifiable, GQM/MEDEA supports the definition of theoretically valid measures for the attributes of interest based on their expected mathematical properties. The empirical hypotheses are subject to experimental verification. This approach integrates several research contributions from the literature into a consistent, practical, and rigorous approach.

show abstract

“…Other ways of formalizing attributes may be used such as Measurement Theory [26], [27]. As shown in [18], the use of properties is not in contradiction with Measurement Theory.…”

Section: Discussionmentioning

confidence: 99%

An operational process for goal-driven definition of measures

Briand

Morasca

Basili

2002

IIEEE Trans. Software Eng.

102

View full text Add to dashboard Cite

show abstract

“…In this section we describe how we developed some metrics for 'measuring' the extent of these requirements and design activities. We follow the model-order-mapping (MOM) approach [6] for developing new metrics, in which a model is created to represent a real-world document (such as a code module) and its characteristics of interest. Mappings are defined between the model and the real-world document, and between the model and an 'answer set' of 'real numbers' [6].…”

Section: Using Requirements and Design Datamentioning

confidence: 99%

“…We follow the model-order-mapping (MOM) approach [6] for developing new metrics, in which a model is created to represent a real-world document (such as a code module) and its characteristics of interest. Mappings are defined between the model and the real-world document, and between the model and an 'answer set' of 'real numbers' [6]. To create our models, we identified some key concepts from the requirements and design stages that may help predict future changes.…”

Section: Using Requirements and Design Datamentioning

confidence: 99%

Using early stage project data to predict change-proneness

Ingram

Riddle

2012

2012 3rd International Workshop on Emerging Trends in Software Metrics (WETSoM)

View full text Add to dashboard Cite

Several previous studies have suggested methods for predicting change-proneness based on software complexity metrics. We hypothesise that data from the early stages of a development project such as requirements and design could also be used to make such predictions. We define here a set of new metrics to capture data from the requirements and/or design stages, and derive values for these metrics using a case study project. We do find that significant differences in change-proneness can be detected between components with high or with low values for our metrics, suggesting that this is an area which would benefit from further study.

show abstract

A quantitative framework for software restructuring

Kang

Bieman

1999

J. Softw. Maint: Res. Pract.

View full text Add to dashboard Cite

Many existing software systems can benefit from restructuring to reduce maintenance cost and improve reusability. Yet, intuition‐based, ad hoc restructuring can be difficult and expensive, and can even make software structure worse. We introduce a quantitative framework for software restructuring. In the framework, restructuring decisions are guided by visualized design information and objective criteria. The design information can be extracted directly from code to restructure existing or legacy software. Criteria for comparing alternative design structures include measures of design‐level cohesion and coupling. Restructuring is accomplished through a series of decomposition and composition operations which increase the cohesion and/or decrease the coupling of individual system components. An example and a case study demonstrate the framework. The framework ensures that restructuring results in measurable improvements in design quality. Copyright © 1999 John Wiley & Sons, Ltd.

show abstract

Software measure specification

Cited by 6 publications

References 10 publications

An operational process for goal-driven definition of measures

An operational process for goal-driven definition of measures

Using early stage project data to predict change-proneness

A quantitative framework for software restructuring

Contact Info

Product

Resources

About