The Unified Modeling Language user guide
The Unified Modeling Language user guide
Using Uml: Software Engineering with Objects and Components
Using Uml: Software Engineering with Objects and Components
Towards a Formal Operational Semantics of UML Statechart Diagrams
Proceedings of the IFIP TC6/WG6.1 Third International Conference on Formal Methods for Open Object-Based Distributed Systems (FMOODS)
A Formal Semantics of UML State Machines Based on Structured Graph Transformation
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
Formalization of UML-Statecharts
«UML» '01 Proceedings of the 4th International Conference on The Unified Modeling Language, Modeling Languages, Concepts, and Tools
Automated Software Engineering Using Concurrent Class Machines
Proceedings of the 16th IEEE international conference on Automated software engineering
Improving UML Design Tools by Formal Games
Proceedings of the 26th International Conference on Software Engineering
Visual security protocol modeling
NSPW '05 Proceedings of the 2005 workshop on New security paradigms
A formalism for visual security protocol modeling
Journal of Visual Languages and Computing
Automatic Protocol Conformance Checking of Recursive and Parallel Component-Based Systems
CBSE '08 Proceedings of the 11th International Symposium on Component-Based Software Engineering
Specifying Component Behavior with Port State Machines
Electronic Notes in Theoretical Computer Science (ENTCS)
Activity-driven synthesis of state machines
FASE'07 Proceedings of the 10th international conference on Fundamental approaches to software engineering
Model Checking of Component Protocol Conformance -- Optimizations by Reducing False Negatives
Electronic Notes in Theoretical Computer Science (ENTCS)
Automatic checking of component protocols in component-based systems
SC'06 Proceedings of the 5th international conference on Software Composition
Protocol conformance checking of services with exceptions
ESOCC'12 Proceedings of the First European conference on Service-Oriented and Cloud Computing
| Hi-index | 0.00 |
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.