Predicting maintenance performance using object-oriented design complexity metrics

A Negative Input Space Complexity Metric as Selection Criterion for Fuzz Testing

“…Since he considered only errors that occurred for systems in the field , this correlation is not only of statistical but also of practical significance. Cataldo employed the metrics interface size and operation argument complexity that were used by Bandi et al [3]. Operation argument complexity was dependent of the type of the operation's arguments.…”

“…0 is assigned to Boolean, 2 to Real, and 6 to Record, Struct, and Objects. The operation argument complexity is determined by the sum of the complexity of each argument's type [3]. The interface size is defined the product of the number of parameters and the sum of their sizes (operation argument complexity).…”

Software Quality Prediction Models Compared

“…Efforts are directed to both the development of (object-oriented) product metrics [3]- [5] and on their validation [6]- [10]. The latter is particularly important since metrics are of little value by themselves unless there is empirical evidence that they are correlated with important external (quality) attributes [11].…”

“…This effort is measured by means of the time spent on performing a maintenance task [6], [22], the changes performed [21], [23], [24], or the maintainability index (MI) [25]. The changes made in the code is in most cases approximated by number of lines of code changed.…”

“…The system architecture, called Overall ATM/CNS Target Architecture (OATA), is a UML specification. As external consultants, we supported the structural assessment of the architecture using a metrics-based approach using our software metrics tool VizzAnalyzer 6 . The pilot validation focused only on a subsystem, consisting of 8 modules and 70 classes, of the complete architecture.…”