<?xml version="1.0" encoding="UTF-8"?>
<article article-type="research-article" xml:lang="en" xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="publisher">global-journal-of-computer-science-and-technology-h-information-technology</journal-id>
<journal-title-group>
<journal-title>Global Journal of Computer Science and Technology - H: Information &amp; Technology</journal-title>
</journal-title-group>
<issn publication-format="print">0975-4350</issn>
<issn publication-format="electronic">0975-4172</issn>
<publisher><publisher-name>Global Journals Publishing Group Incorporated</publisher-name></publisher>
<self-uri xlink:href="https://globaljournals.org/journal-seo-export/jats/54716.xml" />
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">54716</article-id>
<title-group>
<article-title>Software System Model Correctness using Graph Theory: A Review</article-title>
<subtitle>Formal Verification of UML Class Diagram Models</subtitle>
</title-group>
<contrib-group>
<contrib contrib-type="author"><name><surname>Shah</surname><given-names>Kruti P.</given-names></name><xref ref-type="aff" rid="aff1" />
</contrib>
<contrib contrib-type="author"><name><surname>Grant</surname><given-names>Emanuel S.</given-names></name></contrib>
</contrib-group>
<aff id="aff1">UNITED STATES</aff>
<pub-date publication-format="electronic" date-type="pub" iso-8601-date="2023-04-25">
<day>25</day>
<month>04</month>
<year>2023</year>
</pub-date>
<volume>23</volume>
<issue>H1</issue>
<fpage>25</fpage>
<lpage>31</lpage>
<abstract><p>The Unified Modeling Language (UML) is the de facto standard for object-oriented software model development. The UML class diagram plays an essential role in design and specification of software systems. The purpose of a class diagram is to display classes with their attributes and methods, hierarchy (generalization) class relationships, and associations (general, aggregation, and composition) between classes in one model. A model designing process can include a large number of designers. An issue with this is that the models created may be incorrectly designed. Moreover, there are many concepts in the UML that give rise to potential conflicts, uncertainty, and ambiguity. This paper evaluates the concept of software system model correctness. In this paper,a systematic literature review is conducted to examine how researchers identify problems related to software system model correctness. There are seven papers included in the literature review which cover different approaches for handling model correctness in software systems. The results of this review indicate that UML model correctness is a highly active area of research. There are already some valuable contributions in this direction. However, there are many concepts in the UML with imprecise semantics, which limit the use of the UML and reduce the quality of the UML models. This paper is concluded by providing some directions to identify and prove the mathematical equivalence of the UML class diagram models using standard graph theorems.</p></abstract>
<kwd-group kwd-group-type="author-generated">
<kwd>UML models</kwd>
<kwd>UML class diagrams</kwd>
<kwd>software engineering</kwd>
<kwd>model correctness</kwd>
<kwd>graph theory</kwd>
</kwd-group>
<self-uri content-type="pdf" xlink:href="https://globaljournals.org/GJCST_Volume23/3-Software-System-Model-Correctness.pdf" />
<self-uri content-type="html" xlink:href="https://globaljournals.org/scholarly-articles/software-system-model-correctness-using-graph-theory-a-review/" />
</article-meta>
</front>
<body>
<sec>
<title>Full Text</title>
<p>The Unified Modeling Language (UML) is the de facto standard for object-oriented software model development. The UML class diagram plays an essential role in design and specification of software systems. The purpose of a class diagram is to display classes with their attributes and methods, hierarchy (generalization) class relationships, and associations (general, aggregation, and composition) between classes in one model.</p>
</sec>
</body>
</article>