Furthering the understanding of practical complexity: identifying a kernel of UML

The Unified Modeling Language (UML) was adopted by the Object Management Group as the standard visual modeling language for OO systems development. However, UML has been criticized in the literature for its complexity, inconsistent semantics, and ambiguous constructs. A set of complexity indices for...

Full description

Saved in:
Bibliographic Details
Main Authors: ERICKSON, J., SIAU, Keng
Format: text
Language:English
Published: Institutional Knowledge at Singapore Management University 2004
Subjects:
Online Access:https://ink.library.smu.edu.sg/sis_research/9648
https://ink.library.smu.edu.sg/context/sis_research/article/10648/viewcontent/furthering.pdf
Tags: Add Tag
No Tags, Be the first to tag this record!
Institution: Singapore Management University
Language: English
Description
Summary:The Unified Modeling Language (UML) was adopted by the Object Management Group as the standard visual modeling language for OO systems development. However, UML has been criticized in the literature for its complexity, inconsistent semantics, and ambiguous constructs. A set of complexity indices for UML in aggregate, and the nine diagramming techniques individually, was compiled recently. Since this set of metrics is based on inclusion of all possible constructs in UML, it thus provides an indication of the theoretical (maximum) complexity of the modeling methods. This paper contends that in practice, developers do not use all of the possible diagrams or diagram constructs all of the time in their systems building efforts. The idea here is that a more practical complexity exists and can be identified as a subset of theoretical (maximum) complexity. This research aims to identify a kernel of UML, based on a Delphi study panel of UML experts, as a precursor to developing an alternate set of use-based complexity metrics. Preliminary results indicate that several diagrams (class, use case, sequence and statechart) rate as relatively more important to developers than the other UML diagrams.