Computing software metrics from design documents

Software metrics can provide an automated way for software practitioners to assess the quality of their software. The earlier in the software development lifecycle this information is available, the more valuable it is, since changes are much more expensive to make later in the lifecycle.Semantic metrics, introduced by Etzkorn and Delugach, assess software according to the meaning of the software's functionality in its domain. This is in contrast to traditional metrics, which use syntax measures to assess code. Because semantic metrics do not rely on the syntax or structure of code, they can be computed from requirements or design specifications before the system has been implemented. This paper focuses on using semantic metrics to assess systems that have not yet been implemented.

[1]  Letha H. Etzkorn,et al.  Towards a semantic metrics suite for object-oriented design , 2000, Proceedings. 34th International Conference on Technology of Object-Oriented Languages and Systems - TOOLS 34.

[2]  Wei Li,et al.  Another metric suite for object-oriented programming , 1998, J. Syst. Softw..

[3]  Chuck Rieger,et al.  Parsing and comprehending with word experts (a theory and its realization) , 1982 .

[4]  Letha H. Etzkorn,et al.  The language of comments in computer software: A sublanguage of English , 2001 .

[5]  Joseph Robert Horgan,et al.  A tool suite for diagnosis and testing of software design specifications , 2000, Proceeding International Conference on Dependable Systems and Networks. DSN 2000.

[6]  Letha H. Etzkorn,et al.  An approach to program understanding by natural language understanding , 1999, Natural Language Engineering.

[7]  Lionel C. Briand,et al.  Predicting fault-prone classes with design measures in object-oriented systems , 1998, Proceedings Ninth International Symposium on Software Reliability Engineering (Cat. No.98TB100257).

[8]  John E. Gaffney,et al.  Software Function, Source Lines of Code, and Development Effort Prediction: A Software Science Validation , 1983, IEEE Transactions on Software Engineering.

[9]  Sallie M. Henry,et al.  Object-oriented metrics that predict maintainability , 1993, J. Syst. Softw..

[10]  James M. Bieman,et al.  Measuring Design-Level Cohesion , 1998, IEEE Trans. Software Eng..

[11]  Letha H. Etzkorn,et al.  A semantic entropy metric , 2002, J. Softw. Maintenance Res. Pract..

[12]  Anuradha Lakshminarayana,et al.  Automatic extraction and visualization of object-oriented software design metrics , 2000, Electronic Imaging.

[13]  Chris F. Kemerer,et al.  Towards a metrics suite for object oriented design , 2017, OOPSLA '91.

[14]  Michel Dagenais,et al.  An analysis framework for understanding layered software architectures , 1998, Proceedings. 6th International Workshop on Program Comprehension. IWPC'98 (Cat. No.98TB100242).

[15]  Recommended Practice for Software Design Descriptions , 1998 .

[16]  Chris F. Kemerer,et al.  A Metrics Suite for Object Oriented Design , 2015, IEEE Trans. Software Eng..

[17]  Victor R. Basili,et al.  A Validation of Object-Oriented Design Metrics as Quality Indicators , 1996, IEEE Trans. Software Eng..

[18]  Letha Hughes Etzkorn,et al.  A metrics-based approach to the automated identification of object-oriented reusable software components , 1998 .

[19]  Giuliano Antoniol,et al.  Recovering Traceability Links between Code and Documentation , 2002, IEEE Trans. Software Eng..

[20]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[21]  R. Wilensky.  Points: a theory of the structure of stories in memory , 1986 .

[22]  J. M. Singer,et al.  IEEE Recommended Practice for Software Requirements SpeciÞcations , 1993 .

[23]  Niclas Ohlsson,et al.  Predicting Fault-Prone Software Modules in Telephone Switches , 1996, IEEE Trans. Software Eng..

[24]  Carl G. Davis,et al.  A Hierarchical Model for Object-Oriented Design Quality Assessment , 2002, IEEE Trans. Software Eng..