Synthesizing state-based object systems from LSC specifications
2001
Sign up for access to the world's latest research
Abstract
Live sequence charts (LSCs) have been defined recently as an extension of message sequence charts (MSCs; or their UML variant, sequence diagrams) for rich inter-object specification. One of the main additions is the notion of universal charts and hot, mandatory behavior, which, among other things, enables one to specify forbidden scenarios. LSCs are thus essentially as expressive as statecharts.
Related papers
Lecture Notes in Computer Science, 2004
The language of Message Sequence Charts (MSC) is a wellestablished visual formalism which is typically used to capture scenarios in the early stages of system development. But when it comes to rigorous requirements capturing, in particular in the context of formal verification, serious deficiencies emerge: MSCs do not provide means to distinguish mandatory and possible behavior, for example to demand that a communication is required to finally occur. The Live Sequence Chart (LSC) language introduces the distinction between mandatory and possible on the level of the whole chart and for the elements messages, locations, and conditions. Furthermore they provide means to specify the desired activation time by an activation condition or by a whole communication sequence, called pre-chart. We present the current stage of LSC language and a sketch of its formal semantics in terms of Timed Büchi Automata.
Lecture notes in computer …, 2004
The language of Message Sequence Charts (MSC) is a well-established visual formalism which is typically used to capture scenarios in the early stages of system development. But when it comes to rigorous requirements capturing, in particular in the context of formal ...
arXiv (Cornell University), 2010
Sequence diagrams are a widely used design notation for describing software behaviors. Many reusable software artifacts such as design patterns and design aspects make use of sequence diagrams to describe interaction behaviors. When a pattern or an aspect is reused in an application, it is important to ensure that the sequence diagrams for the application conform to the corresponding sequence diagrams for the pattern or aspect. Reasoning about conformance relationship between sequence diagrams has not been addressed adequately in literature. In this paper, we focus on required behavior specified by a UML sequence diagram. A novel trace semantics is given that captures precisely required behavior specified by a sequence diagram and a conformance relation between sequence diagrams is formalized based on the semantics. Properties of the trace semantics and the conformance relation are studied.
Proceedings of the 2nd International Conference on Model-Driven Engineering and Software Development, 2014
We propose a semantics for Sequence Diagrams based on the COMPASS Modelling Language (CML): a formal specification language to model systems of systems. A distinguishing feature of our semantics is that it is defined as part of a larger effort to define the semantics of several diagrams of SysML, a UML profile for systems engineering. We have defined a fairly comprehensive semantics for Sequence Diagrams, which comprises sequential and parallel constructors, loops, breaks, alternatives, synchronous and asynchronous messages. We illustrate our semantics with a scenario of a case study of a system of systems. We also discuss an analysis strategy which involves an integrated view of several diagrams.
Communications in Computer and Information Science, 2018
UML2.X sequence diagrams (SD) are equipped with high structures: the combined fragments (CF) that permit to model complex behaviours of systems. CF can be nested to allow more sophisticated behaviours, however they complicate the interpretation of the SD and the computation of precedence relations between the events. In a previous work, we proposed a causal semantics for UML2.X SD. It is based partial order theory, its well-defined relations allow the computation of all precedence relations for the events of UML2.X SD with nested CF. We considered the most popular CF of control-flow alt, opt, loop, seq allowing to model respectively alternative, optional, iterative and sequential behaviours. In this work, we improve that previous work to consider a par CF allowing to model parallel behaviours, and we propose an operational semantics that is based on the causal semantics. The proposed operational semantics is a substantial step towards the refinement checking and the analysis of some properties of SD.
Message Sequence Charts (MSC) is a graphical language that has been widely used in the design of distributed systems and communication protocols. MSCs are particularly useful in the early stages of system development and have been very useful in revealing errors in early stages of development. As MSCs have found widespread usage, several new features are being introduced to overcome its shortcomings for a spectrum of applications keeping the rationale of MSCs in tact. In this paper, we shall discuss the design and implementation of MSC {a generalization of hierarchical MSC (hMSC) designed keeping in view the need of specifying complex reactive systems, and veriable prototype systems. MSC has new features like watching construct, generalized coregions, and incorporates features needed for specifying scenarios such as mandatory (hot) and provisional (cold) conditions. The generalization permits the specication of complex systems still preserving the simplicity and advantages of the hM...
Formal methods for open object-based distributed …
We propose a formal real-time semantics for UML statecharts aimed at the requirements level. A requirements-Ievel model assumes perfect technology and has a considerably simpler semantics than an implementation level model. Our semantics is an adaptation of the STATEMATE statechart semantics, with local variables, real time, identifier addressing, point-to-point communication, synchronous communication and dynamic object creation and deletion. We start with an informal comparison of STATEMATE and UML statechart semantics and then give a formalisation of our semantics in terms of labelIed transition systems.
2011
Sequence diagrams are a widely used design notation for describing software behaviors. Many reusable software artifacts such as design patterns and design aspects make use of sequence diagrams to describe interaction behaviors. When a pattern or an aspect is reused in an application, it is important to ensure that the sequence diagrams for the application conform to the corresponding sequence diagrams for the pattern or aspect. Reasoning about conformance relationship between sequence diagrams has not been addressed adequately in literature. In this paper, we focus on required behavior specified by a UML sequence diagram. A novel trace semantics is given that captures precisely required behavior specified by a sequence diagram and a conformance relation between sequence diagrams is formalized based on the semantics. Properties of the trace semantics and the conformance relation are studied.
2007
We report on S2A, a compiler that translates Modal UML Sequence Diagrams (MSDs), a UML-compliant version of Live Sequence Charts (LSCs), into AspectJ code. It thus provides full code generation of reactive behavior from visual inter-object scenario-based specifications. The S2A compiler is based on a compilation scheme presented by Maoz and Harel in [13].
WSEAS Transactions on Information …, 2009
We propose composed strings called "statechart DNA" as essential building blocks for a new statechart (sc) abstraction method. We define the simplified statechart (ssc) and show that our definition covers the UML 2.0 sc model, by matching it to all model elements of the StateMachine package of the UML 2.0 metamodel and to the OCL constraints on these model elements. A Model Driven Architecture (MDA) is defined, inspired by a PIM-to-PIM model transformation procedure between UML sc models and ssc models. We discuss the rationale behind action abstraction in ssc models. This framework is used to isolate sc DNA, first in ssc models, then in UML sc models. We show how sc DNA, a compaction of sc construction primitives, can be used to define behavior model metrics and more generally, to manage and maintain evolving object behavior. State machine versioning is an important application of statechart DNA to manage industrial model repositories.

Loading Preview
Sorry, preview is currently unavailable. You can download the paper by clicking the button above.