An Objectified Entropy-Based Software Metric for Assessing the Maturity of Use Case Diagrams

Various metrics exist for evaluating UML diagrams, including entropy-based ones like ours, which assess information content. They allow for judging certain features of the design that depend on the information content. This paper proposes the FBS24 use case diagram measure, which should ensure that the software architecture design consists of mature UML diagrams. Detecting an inappropriate (immature, unfinished) Use Case Diagram before the software development phase can stall the entire software development process until a mature UCD is developed. Currently, no indicators (metrics) show the maturity (or lack of applicability) of diagrams. Moreover, in most such software metrics, weights are selected arbitrarily, which leads to numerous anomalies. We show how to construct the measure most resistant to such anomalies. We also show how to check the correctness and usefulness of the constructed measure. As our measure is objective, it is suitable for remote work of distributed teams building IT systems.

Authors

Institutions

Publication Details

Journal
Proceedings of the International Conference on Information Systems Development
Published
2024-09-09
DOI
https://doi.org/10.62036/isd.2024.14
Primary Topic
Software Engineering Research
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

An Objectified Entropy-Based Software Metric for Assessing the Maturity of Use Case Diagrams

Stanisław Jerzy Niepostyn, Wiktor B. Daszczuk
Proceedings of the International Conference on Information Systems Development
Software Engineering Research
article

An Objectified Entropy-Based Software Metric for Assessing the Maturity of Use Case Diagrams

Stanisław Jerzy Niepostyn, Wiktor B. Daszczuk
article en

Abstract

Various metrics exist for evaluating UML diagrams, including entropy-based ones like ours, which assess information content. They allow for judging certain features of the design that depend on the information content. This paper proposes the FBS24 use case diagram measure, which should ensure that the software architecture design consists of mature UML diagrams. Detecting an inappropriate (immature, unfinished) Use Case Diagram before the software development phase can stall the entire software development process until a mature UCD is developed. Currently, no indicators (metrics) show the maturity (or lack of applicability) of diagrams. Moreover, in most such software metrics, weights are selected arbitrarily, which leads to numerous anomalies. We show how to construct the measure most resistant to such anomalies. We also show how to check the correctness and usefulness of the constructed measure. As our measure is objective, it is suitable for remote work of distributed teams building IT systems.

Proceedings of the International Conference on Information Systems Development
Warsaw University of Technology (PL), University of Humanities and Economics in Lodz (PL)
Openalex Percentile: Top 77%
Software Engineering Research
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.