Unified Modeling Language: The Teen Years and Growing Pains

Unified Modeling Language (UML) is adopted by the Object Management Group as a standardized general-purpose modeling language for object-oriented software engineering. Despite its status as a standard, UML is still in a development stage and many studies have highlighted its weaknesses and challenges - including those related to human factor issues. Further, UML has grown considerably more complex since its inception. This paper traces the history of Unified Modeling Language (UML) from its formation to its current state and discusses the current state of the UML language. The paper first introduces UML and its various diagrams, and discusses its characteristics and features. The paper then looks at UML's strengths, challenges, and possible future development. The human factor issues with using UML are discussed and elaborated. Potential research questions related to UML are also highlighted.

[1]  Sjaak Brinkkemper,et al.  Complexity Metrics for Systems Development Methods and Techniques , 1996, Inf. Syst..

[2]  Keng Siau,et al.  Component-Based Development Using UML , 2002, Commun. Assoc. Inf. Syst..

[3]  Keith Duddy.  UML2 must enable a family of languages , 2002, CACM.

[4]  Patricia Lago.  Rendering Distributed Systems in UML , 2001, Unified Modeling Language: Systems Analysis, Design and Development Issues.

[5]  Martin Fowler.  Why use the UML , 1998 .

[6]  Keng Siau,et al.  Unified Modeling Language: A Complexity Analysis , 2001, J. Database Manag..

[7]  Keng Siau,et al.  Theoretical vs. Practical Complexity: The Case of UML , 2005, J. Database Manag..

[8]  Perdita Stevens,et al.  Using UML - software engineering with objects and components, Second Edition , 2006, Addison Wesley object technology series.

[9]  Stephen J. Mellor.  Make models be assets , 2002, CACM.

[10]  Keng Siau,et al.  Unified modeling language : systems analysis, design and development issues , 2001 .

[11]  Keng Siau,et al.  Theoretical and practical complexity of modeling methods , 2007, CACM.

[12]  Dan Pilone,et al.  UML 2.0 in a Nutshell (In a Nutshell (O'Reilly)) , 2005 .

[13]  Keng Siau,et al.  Are use case and class diagrams complementary in requirements analysis? An experimental study on use case and class diagrams in UML , 2004, Requirements Engineering.

[14]  Scott W. Ambler,et al.  How the UML models fit together , 1998 .

[15]  Jeffrey Parsons,et al.  Understanding the Role of Use Cases in UML: A Review and Research Agenda , 2000, J. Database Manag..

[16]  Keng Siau,et al.  Identifying Difficulties in Learning Uml , 2006, Inf. Syst. Manag..

[17]  Keng Siau,et al.  A semiotic analysis of unified modeling language graphical notations , 2009, Requirements Engineering.

[18]  Bran Selic,et al.  Evolution, not revolution , 2002, CACM.

[19]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[20]  Joaquin Miller,et al.  WHAT UML SHOULD BE , 2002 .

[21]  Jeffrey Parsons,et al.  How UML is used , 2006, CACM.

[22]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

[23]  Keng Siau,et al.  Using service responsibility tables to supplement UML in analyzing e-service systems , 2011, Decis. Support Syst..

[24]  Keng Siau,et al.  Using Cognitive Mapping Techniques to Supplement UML and up in Information Requirements Determination , 2006, J. Comput. Inf. Syst..

[25]  Dan Pilone,et al.  UML 2.0 in a nutshell , 2005 .