Challenges in Developing Sequence Diagrams (UML)


  • Tri Astoto Kurniawan Software Engineering Lab., Universitas Brawijaya
  • Lam-Son Lê Enterprise Software & Processes Group, HCMC University of Technology
  • Bayu Priyambadha Laboratory of Software Systems and Software Engineering, University of Miyazaki



During the object-oriented software design phase, the designers have to describe the dynamic aspect of the system under development through the most common interaction diagram variant in UML 2.0, i.e. sequence diagrams. Some novice designers, including undergraduate and postgraduate students, suffer from making inappropriate models due to insufficiently detailed guidance required to develop such sequence diagrams. This paper classifies some potential mistakes which are likely performed by such novice designers, and discusses the corresponding corrections. We summarized such mistakes based on our long experiences in teaching software modeling classes as well as software analysis and design classes. There were classified twenty-one potential mistakes with respect to the syntactical and semantical correctness of the developed models. It is concluded that novice designers have to be aware and take into account the identified mistakes in such a way they can produce correct sequence diagrams.


G. Engels, R. Heckel and S. Sauer, “UML --- A Universal Modeling Language?,†in Application and Theory of Petri Nets 2000: 21st International Conference, ICATPN 2000 Aarhus, Denmark, June 26--30, 2000 Proceedings, M. Nielsen and D. Simpson, Editors, Springer Berlin Heidelberg, pp. 24-38. (2000)

C. Larman, Applying UML and Patterns, 3rd Edition, NJ: Prentice-Hall. (2005).

C. F. J. Lange, M. R. V. Chaudron, and J. Muskens, “In Practice: UML Software Architecture and Design Description,†IEEE Software, vol. 23, no. 2, pp. 40-46. (2006)

T. A. Kurniawan, D. S. Rusdianto, A. H. Brata, F. Amalia, A. Santoso, and D. I. N. R. P. Raharjo, “An Exploratory Study of Requirements Engineering Practices in Indonesia – Part 2: Efforts, Processes and Techniques,†Journal of Information Technology and Computer Science, vol. 5, no. 1, pp. 65-74. (2020)

S. Cass, “Top Programming Languages 2020,†IEEE Spectrum. (2020)

OMG, OMG Unified Modeling Language (OMG UML) Version 2.5.1, Object Management Group.(2017)

G. Booch, J. Rumbaugh, and I. Jacobson, The Unified Modeling Language: User Guide, Addison Wesley. (1999)

I.-Y. Song, “Developing Sequence Diagrams in UML,†in International Conference on Conceptual Modeling. (2001)

B. Unhelkar, Verification and validation for quality of UML 2.0 models, Wiley Online Library. (2005)

O. I. Lindland, G. Sindre, and A. Solvberg, “Understanding Quality in Conceptual Modeling,†IEEE Software, vol. 11, no. 2, pp. 42-49. (1994)

T. Tamai, “How to Teach Software Modeling,†in The 27th International Conference on Software Engineering. (2005)

L. Kuzniarz and M. Staron, “Best practices for teaching UML based software development,†in International Conference on Model Driven Engineering Languages and Systems. (2005)

B. Westphal, “Teaching Software Modelling in an Undergraduate Introduction to Software Engineering,†in 2019 ACM/IEEE 22nd International Conference on Model Driven Engineering Languages and Systems Companion (MODELS-C). (2019)

A. Dennis, B. H. Wixom, and D. Tegarde, Systems Analysis and Design with UML Version 2.0: An Object-Oriented Approach, John Wiley & Sons, Inc. (2005)

D. Rosenberg and K. Scott, Use Case Driven Object Modeling with UML: A Practical Approach, Addison-Wesley. (1999)

I. Jacobson, Object-oriented software engineering: a use case driven approach, New York: ACM Press. (1992)

M. Grossman, J. E. Aronson, and R. V. McCarthy, “Does UML make the grade? Insights from the software development community,†Information and Software Technology, vol. 47, no. 6, pp. 383-397. (2005).




How to Cite

Kurniawan, T. A., Lê, L.-S., & Priyambadha, B. (2020). Challenges in Developing Sequence Diagrams (UML). Journal of Information Technology and Computer Science, 5(2), 221–234.