Abstract
UML 2.0, which is the standard modeling language for object-oriented systems, has only an informally given semantics. This is in particular the case for UML 2.0 state machines, which are widely used for modeling the reactive behavior of objects. In this paper, a list of 29 newly detected trouble spots consisting of ambiguities, inconsistencies, and unnecessarily strong restrictions of UML 2.0 state machines is given and illustrated using 6 state machines having a problematic meaning; suggestions for improvement are presented. In particular, we show that the concepts of history, priority, and entry/exit points have to be reconsidered. © Springer-Verlag Berlin Heidelberg 2005.
Cite
CITATION STYLE
Fecher, H., Schönborn, J., Kyas, M., & De Roever, W. P. (2005). 29 new unclarities in the semantics of UML 2.0 state machines. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 3785 LNCS, pp. 52–65). https://doi.org/10.1007/11576280_5
Register to see more suggestions
Mendeley helps you to discover research relevant for your work.
