Model size matters

Size is an important attribute of software artefacts; for most artefact types exists a body of measurement knowledge. As software engineering is becoming more and more model-centric, it is surprising that there exists only little work on model size metrics (MoSMe). In this position paper we identify the goals justifying the need for MoSMe, such as prediction, description and progress measurement. Additionally, we identify challenges that make it difficult to measure the size of UML models and that MoSMe have to deal with. Finally, we propose a classification of MoSMe and concrete examples of metrics for the size of UML models.

[1]  Michel R. V. Chaudron,et al.  Managing Model Quality in UML-Based Software Development , 2005, 13th IEEE International Workshop on Software Technology and Engineering Practice (STEP'05).

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

[3]  Ellis Horowitz,et al.  Software Cost Estimation with COCOMO II , 2000 .

[4]  Shari Lawrence Pfleeger,et al.  Software Metrics : A Rigorous and Practical Approach , 1998 .

[5]  Michel R. V. Chaudron,et al.  In practice: UML software architecture and design description , 2006, IEEE Software.

[6]  Shari Lawrence Pfleeger,et al.  Preliminary Guidelines for Empirical Research in Software Engineering , 2002, IEEE Trans. Software Eng..

[7]  Ivar Jacobson,et al.  Unified Modeling Language , 2020, Definitions.

[8]  Norman E. Fenton,et al.  Quantitative Analysis of Faults and Failures in a Complex Software System , 2000, IEEE Trans. Software Eng..

[9]  Michel R. V. Chaudron,et al.  An empirical assessment of completeness in UML designs , 2004, ICSE 2004.

[10]  Jan Verelst,et al.  The Influence of the Level of Abstraction on the Evolvability of Conceptual Models of Information Systems , 2004, Proceedings. 2004 International Symposium on Empirical Software Engineering, 2004. ISESE '04..