Unified Modeling Language

Abstract

Unified Modeling Language (UML) has emerged as the software industry’s dominant modeling language. It is the de facto modeling language standard for specifying, visualizing, constructing, and documenting the components of software systems. Despite its prominence and status as the standard modeling language, UML has its critics. Opponents argue that it is complex and difficult to learn. Some question the rationale of having nine diagramming techniques in UML and the raison d’être of those nine techniques in UML. Others point out that UML lacks a comprehensive methodology to guide its users, which makes the language even more convoluted. A few studies on UML can be found in the literature. However, no study exists to provide a quantitative measure of UML complexity or to compare UML with other object oriented techniques. In this research, we evaluate the complexity of UML using complexity metrics. The objective is to provide a reliable and accurate quantitative measure of UML complexity. A comparison of the complexity metrical values of UML with other object-oriented techniques was also carried out. Our findings suggest that each diagram in UML is not distinctly more complex than techniques in other OO methods. But as a whole, UML is very complex - 2-11 times more complex than other OO methods.

An Analytical Framework for Evaluating Service-Oriented Software Development Methodologies

“…This was expected given that a service dependencies diagram covers a limited number of objects, properties, and relationships compared to BPMN. This is also in line with the previous complexity calculations for simpler work product types evaluated by other researchers [54] (e.g. UML class (C' = 26.4) and UML component (C' = 15.65) diagrams).…”

Software requirements modeling from the selected set of requirements using fuzzy based approach

“…The class diagrams are the most complex diagrams of UML and have high complexity because they include relationship and property types. Because of the complexity of the class diagrams, they may not be completely interpreted as UCDs [7,29]. Both diagrams represent different information about the requirements of an IES and there is no overlap in the information captured through these two diagrams.…”

Sistem Penjualan Daring Berbasis Web Pada Perusahaan Mode Pakaian

“…UML diagram bertujuan tujuan yakni untuk membantu tim pengembangan proyek pengembangan software berkomunikasi, mengeksplorasi potensi rancangan, dan memvalidasi rancangan arsitektur perangkat lunak atau pembuat program komputer [7]. Álvaro Farias menjelaskan bahwa UML adalah sekumpulan diagram yang berfungsi untuk memahami dan mengembangkan proyek perangkat lunak, yang menggambarkan apa yang harus dilakukan perangkat lunak [8]. Saputra menyimpulkan bahwa UML berfungsi sebagai alat bantu sistem perangkat lunak dalam memvisualisasi, merancang, dan mendokumentasikan data kedalam bentuk sistem yang berorientasi objek [9].…”