Modelling Recursive Calls with UML State Diagrams

Abstract. One of the principal uses of UML is the modelling of synchronous object-oriented software systems, in which the behaviour of each of several classes is modelled using a state diagram. UML permits a transition of the state diagram to show both the event which causes the transition (typically, the fact that the object receives a message) and the object’s reaction (typically, the fact that the object sends a message). UML’s semantics for state diagrams is “run to completion”. We show that this can lead to anomalous behaviour, and in particular that it is not possible to model recursive calls, in which an object receives a second message whilst still in the process of reacting to the first. Drawing on both ongoing work by the UML2.0 submitters and recent theoretical work [1,6], we propose a solution to this problem using state diagrams in two complementary ways.

• Type: Conference
• Year: 2003
• Where: FASE
• Authors: Jennifer Tenzer, Perdita Stevens
• Keywords: FASE 2003, Object’s Reaction, Software Engineering, State Diagrams, Synchronous Object-oriented Software