Design and code metrics through a DIANA-based tool

  • Wayne M. Zage
  • Dolores M. Zage
  • Manjari Bhargava
  • Dale J. Gaumer
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 603)


This paper discusses a metrics approach for analyzing software designs which helps designers engineer quality into the design product. These metrics gauge project quality as well as design complexity at all times during the design phase. The metrics are developed from primitive design metrics which are predictive, objective and automatable. The architectural design metrics used are comprised of terms related to the amount of data flowing through the module and the number of paths through the module. A detailed design metrics component takes into account the structure and complexity of a module. To automate the calculation of the design metrics in the Rational environment, DIANA (Descriptive Intermediate Attributed Notation for Ada) was utilized. Provided in the environment are packages allowing for the traversal and retrieval of the DIANA structure. By combining the defined packages with customized packages, an Ada design metrics analysis tool was developed. This paper will discuss our design metrics and their automation at Magnavox. Empirical results will illustrate the metrics' success in identifying stress points in a software design and demonstrate their relationship to the quality of the resulting software.

Key words

Design metrics code metrics quality assessment DIANA 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [BASI81]
    Basili, V., “Evaluating Software Development Characteristics: Assessment of Software Measures in the Software Engineering Laboratory”, Proceedings of the Sixth Annual Software Engineering Workshop, SEL-81-013, December 1981.Google Scholar
  2. [BHAR91]
    Bhargava, M., Analysis of Multiple Software Releases of AFATDS Using Design Metrics, Master of Science Degree Thesis, Ball State University, December 1991.Google Scholar
  3. [BOEH88]
    Boehm, B. and P. Papaccio, “Understanding and Controlling Software Costs”, IEEE Transactions on Software Engineering, Vol. SE-14, No. 10, pp. 1462–1477, October 1988.Google Scholar
  4. [GIBS89]
    Gibson, V.R. and J.A. Senn, “System Structure and Software Maintenance Performance”, Communications of the ACM, Vol. 32, No. 3, pp.347–357, March 1989.Google Scholar
  5. [GRAD87]
    Grady, R., “Measuring and Managing Software Maintenance”, IEEE Software, Vol. 4, No. 5, pp.35–45, September 1987.Google Scholar
  6. [HENR90]
    Henry, S. and C. Selig, “Predicting Source Code Complexity at the Design Stage”, IEEE Software, Vol. 7, No. 2, pp.36–43, March 1990.Google Scholar
  7. [KITC89]
    Kitchenham, B.A. and J.G. Walker, “A Quantitative Approach to Monitoring Software Development”, Software Engineering Journal, pp.2–13, January 1989.Google Scholar
  8. [LEW88]
    Lew, K., T.S. Dillon and K.E. Forward, “Software Complexity and Its Impact on Software Reliability”, IEEE Transactions on Software Engineering, Vol. 14, No. 11, pp.1645–1655, November 1988.Google Scholar
  9. [LI87]
    Li, H.F. and W.K. Cheung, “An Empirical Study of Software Metrics”, IEEE Transactions on Software Engineering, Vol. SE-13, No. 6, pp.697–708, June 1987.Google Scholar
  10. [PORT90]
    Porter, A. and R. Selby, “Empirically Guided Software Development Using Metric-Based Classification Trees”, IEEE Software, Vol. 7, No. 2, pp.46–54, March 1990.Google Scholar
  11. [ROMB90]
    Rombach, H.D., “Design Measurement: Some Lessons Learned”, IEEE Software, Vol. 7, No. 2, pp. 17–25, March 1990.Google Scholar
  12. [ZAGE90]
    Zage, W.M. and D.M. Zage, “Relating Design Metrics to Software Quality: Some Empirical Results”, SERC-TR-74-P, May 1990.Google Scholar
  13. [ZAGE91a]
    Zage, W.M., D.M. Zage, S. Wagner, “The Design Metric Software Design Analyzer”, SERC-TR-97-P, March 1991.Google Scholar
  14. [ZAGE91b]
    Zage, W.M., D.M. Zage, P. McDaniel and I. Khan, “Evaluating Design Metrics on Large-Scale Software”, SERC-TR-106-P, September 1991.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1992

Authors and Affiliations

  • Wayne M. Zage
    • 1
  • Dolores M. Zage
    • 1
  • Manjari Bhargava
    • 2
  • Dale J. Gaumer
    • 2
  1. 1.Computer Science DepartmentBall State UniversityMuncieUSA
  2. 2.Magnavox Electronic Systems Co.Fort WayneUSA

Personalised recommendations