Dear Hitoshi > The paper cited does not use UML state chart diagram, but I think the > concept is the same.
Actually, the concept is very different. The key differences are: 1. UML state charts do not support the idea of event refusal. 2. UML state charts cannot be composed in the way we describe (using CSP parallel composition). 3. UML state charts do not support derived (calculated) states. 4. UML state charts do not support different behavioural types (Essential, Allowed, Desired). The detailed semantics of UML state charts derives mainly from the work of Harel and Shlaer/Mellor, and has its origins in real-time/embedded systems design. They are not suitable, in my view, for work in the business process domain. Rgds Ashley
