Reply to: "Property-Based Software Engineering Measurement"

Authors:
Horst Zuse
Affiliations:
Technisch Univ. Berlin, Berlin, Germany
Venue:
IEEE Transactions on Software Engineering
Year:
1997

Citing 3
Cited 5

Software complexity: measures and methods

Software complexity: measures and methods
Property-Based Software Engineering Measurement

IEEE Transactions on Software Engineering
Measurement Theory and Software Measures

Proceedings of the BCS-FACS Workshop on Formal Aspects of Measurement

An Evaluation of the MOOD Set of Object-Oriented Software Metrics

IEEE Transactions on Software Engineering
A method for assessing the reusability of object-oriented code using a validated set of automated measurements

Proceedings of the 2002 ACM symposium on Applied computing
A Metric Framework for the Assessment of Object-Oriented systems

ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Class Point: An Approach for the Size Estimation of Object-Oriented Systems

IEEE Transactions on Software Engineering
Measuring size, complexity, and coupling of hypergraph abstractions of software: An information-theory approach

Software Quality Control

Quantified Score

Hi-index	0.00

Visualization

Abstract

Briand, Morasca, and Basili [1] introduce a measurement theoretic approach to software measurement and criticize among others the work of the author, but they misinterpret the work of the author. Zuse does not require additive software (complexity) measures as Briand, Morasca, and Basili state. Zuse uses the concept of the extensive structure in order to show the empirical properties behind software measures. Briand, Morasca, and Basili use the concept of meaningfulness in order to describe scales and that certain scale levels are not excluded by the Weyuker Properties. However, the authors do not consider, that scales and scale types are different things.