TL;DR: Live sequence charts (LSCs) as discussed by the authors allow the distinction between possible and necessary behavior both globally, on the level of an entire chart and locally, when specifying events, conditions and progress over time within a chart.
Abstract: While message sequence charts (MSCs) are widely used in industry to document the interworking of processes or objects, they are expressively weak, being based on the modest semantic notion of a partial ordering of events as defined, eg, in the ITU standard A highly expressive and rigorously defined MSC language is a must for serious, semantically meaningful tool support for use-cases and scenarios It is also a prerequisite to addressing what we regard as one of the central problems in behavioral specification of systems: relating scenario-based inter-object specification to state-machine intra-object specification This paper proposes an extension of MSCs, which we call live sequence charts (or LSCs), since our main extension deals with specifying “liveness”, ie, things that must occur In fact, LSCs allow the distinction between possible and necessary behavior both globally, on the level of an entire chart and locally, when specifying events, conditions and progress over time within a chart This makes it possible to specify forbidden scenarios, for example, and enables naturally specified structuring constructs such as subcharts, branching and iteration
TL;DR: This paper uses message sequence charts to specify the interaction between organizations and Petri nets are used to model the workflows inside each organization.
Abstract: To date, workflow management focuses on improving the effectivity and efficiency of business processes within one organization. However, today’s corporations are challenged to cross organizational boundaries. Phenomena such as electronic commerce, extended enterprises and the Internet stimulate the cooperation between organizations. Therefore, it is interesting to consider workflows distributed over a number of organizations. Interorganizational workflow offers companies the opportunity to re-shape business processes beyond the boundaries of individual organizations. In this paper, we use message sequence charts to specify the interaction between organizations. Petri nets are used to model the workflows inside each organization. Two challenging problems related to interorganizational workflow are tackled in this paper: (1) What are the minimal requirements any interorganizational workflow should satisfy?, and (2) How to decide whether an interorganizational workflow (modeled in terms of Petri nets) is consistent with the interaction structure specified in terms of a message sequence chart?
TL;DR: This work shows that message sequence charts are open to a variety of semantic interpretations, and can depend on, for instance, whether one allows or denies the possibility of message loss or message overtaking, and on the particulars of the message queuing policy to be adopted.
Abstract: Message sequence charts (MSCs) are used in the design phase of a distributed system to record intended system behaviors. They serve as informal documentation of design requirements that are referred to throughout the design process and even in the final system integration and acceptance testing. We show that message sequence charts are open to a variety of semantic interpretations. The meaning of an MSC can depend on, for instance, whether one allows or denies the possibility of message loss or message overtaking, and on the particulars of the message queuing policy to be adopted.
TL;DR: This work defines MSD as a UML 2.0 profile, paving the way to apply formal verification, synthesis, and scenario-based execution techniques from LSC to the mainstream UML standard, based on the universal/existential modal semantics of LSC.
Abstract: Live Sequence Charts (LSC) extend Message Sequence Charts (MSC), mainly by distinguishing possible from necessary behavior. They thus enable the specification of rich multi-modal scenario-based properties, such as mandatory, possible and forbidden scenarios. The sequence diagrams of UML 2.0 enrich those of previous versions of UML by two new operators, assert and negate, for specifying required and forbidden behaviors, which appear to have been inspired by LSC. The UML 2.0 semantics of sequence diagrams, however, being based on pairs of valid and invalid sets of traces, is inadequate, and prevents the new operators from being used effectively. We propose an extension of, and a different semantics for this UML language—Modal Sequence Diagrams (MSD)—based on the universal/existential modal semantics of LSC. In particular, in MSD assert and negate are really modalities, not operators. We define MSD as a UML 2.0 profile, thus paving the way to apply formal verification, synthesis, and scenario-based execution techniques from LSC to the mainstream UML standard.