Software metrics: using measurement theory to describe the properties and scales of static software complexity metrics

Zuse, Horst; Bollmann, P.

doi:10.1145/70470.70473

Cited by 31 publications

(6 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We see that Theorem 2 gives us conditions for the additive ratio scale. In Bollmann and Zuse (t 987), Zuse and Bollmann (1989) and Zuse (1991) these concepts are applied to static software complexity measures on ftowgraphs.…”

Section: A•>_/ B~*#(a) ~> #(B)mentioning

confidence: 99%

“…We proposed the concatenation operations BSEQ and BALT, which are related to programs/ flowgraphs, in Bollmann and Zuse (1987); Zuse (1985;1991); Zuse and Bollmann (1989;1992). Additionally, the concatenation operations DSEQ and DALT for the Constantine software design method are proposed.…”

Section: Measurement Theory and Complexity Measuresmentioning

confidence: 99%

“…We consider the empirical relational system (P, • >~, o), where P is the set of flowgraphs, o is the sequential combination BSEQ of flowgraphs as defined in Fig. 1 and Zuse and Bollmann (1989), and #:P ~ 8{ is the measure /~ = MCC-V = ]El -INI + 2 of McCabe. We ask the following questions:…”

Section: Application Of Measurement Theory To the Measure Of Mccabementioning

confidence: 99%

“…The answer to the first question, already given in Bollmann and Zuse (1987); Zuse and Bollmann (1989); Zuse (1991), is as follows: Under the assumption of transitivity and reflexivity, the measures MCC-V and MCC-V2 of McCabe can be used as an ordinal scale, if and only if for all flowgraphs P, P' e P, the following three conditions hold:…”

Section: Answer To the First Question (Ordinal Scale)mentioning

confidence: 99%

See 3 more Smart Citations

Properties of software measures

Zuse

1992

Software Qual J

View full text Add to dashboard Cite

During recent years much attention has been directed towards the measurement of the properties and the complexity of software. The major goal of using software measures is to get reliable software and an objective representation of the properties of software and the software development process by numbers, Many software measures have been developed in order to determine the static complexity of single programs (intra-modular complexity) and of entire software systems (inter-modular complexity) during the phases of the software lifecycle. As a consequence of these developments many authors have discussed the properties of software measures. In this paper a measurement theory is introduced which gives conditions for the properties of measures. The properties of software measures and conditions of the use of software measures as an ordinal and ratio scale are given. As an example, these are applied to the measures of McCabe.Because composition and decomposition operations are major strategies in software development, theorems which describe the properties of software measures related to this type of operations are also presented. Properties of software measures, as required by masses in the literature, are discussed and explained with statements of measurement theory. The results show that it is possible to explain most of the required properties of software measures in the literature with conditions of measurement theory. This makes the properties of software measures during the software lifecycle and their application in practice more visible.

show abstract

Section: A•>_/ B~*#(a) ~> #(B)mentioning

confidence: 99%

Section: Measurement Theory and Complexity Measuresmentioning

confidence: 99%

Section: Application Of Measurement Theory To the Measure Of Mccabementioning

confidence: 99%

Section: Answer To the First Question (Ordinal Scale)mentioning

confidence: 99%

See 2 more Smart Citations

Properties of software measures

Zuse

1992

Software Qual J

View full text Add to dashboard Cite

show abstract

“…A viewpoint is a binary relation .> defined on the set P. For P, P', P" e set P , the following axioms must hold: P .> P (reflexivity) P .> P or P .> P (completeness) P.> P', P'.> P" => P.> P" (transitivity) i.e., a viewpoint must be of weak order [Zuse, 1987].…”

Section: Introductionmentioning

confidence: 99%

Towards a metrics suite for object oriented design

Chidamber

Kemerer

1991

Conference Proceedings on Object-Oriented Programming Systems, Languages, and Applications

484

275

View full text Add to dashboard Cite

This paper presents theoretical woric that builds a suite of metrics for object-oriented design.In particular, these metrics are based upon measurement theory and are also informed by the insights of experienced object-oriented software developers. In evaluating these metrics against a standard set of criteria, they are found to both (a) perform relatively well, and (b) suggest some ways in which Lhe object oriented approach may differ in terms of desirable or necessary design features from more traditional approaches.In order for object-oriented software production to fulfill its promise in moving software development and maintenance from the current 'craft' environment into something more closely resembling conventional engineering, it will require metrics of the process to aid the software management, project planning and project evaluation functions. While software metrics are a generally desirable feature in any software environment, they are of special imponance in the object-oriented approach, since it represents a non-trivial technological change for the organization.The metrics presented in this paper are the first steps in a project aimed at measuring and evaluating the use of object oriented design principles in organizations.

show abstract

Software Development Metrics

Reynolds

2002

Encyclopedia of Software Engineering

View full text Add to dashboard Cite

Software development metrics are the means by which software engineers assess and predict aspects of those processes, resources, and products that are relevant to the software engineering activity. Metrics serve as the compass that guides the discipline in the search for efficient and effective solutions to complex problems. Future progress in the discipline will be closely tied to the ability of these metrics to provide accurate and timely information to those software engineers navigating the problem‐solving seas. In this article, the notion of a software metric and its formulation for use in a problem‐solving situation are presented. A description of the basic categories of software metrics based on the entities of the software development process that they measure is given. Metrics that have been proposed for each phase of the software development process using this classification are surveyed.

show abstract

Software metrics: using measurement theory to describe the properties and scales of static software complexity metrics

Cited by 31 publications

References 5 publications

Properties of software measures

Properties of software measures

Towards a metrics suite for object oriented design

Software Development Metrics

Contact Info

Product

Resources

About