MSC and data: dynamic variables

Engels, André; Feijs, Loe; Mauw, Sjouke

doi:10.1016/b978-044450228-5/50009-6

Cited by 5 publications

(3 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Messages can be considered to represent synchronous (handshaking) or asynchronous communication. Notation for and assumptions on queues that impose restrictions on event orderings can be included, (e.g., [2], [36]), as can explicit use of time to describe delays, timeouts, and deadlines (e.g., [22], [26], [31]); dynamic creation and termination of instances (e.g., [22]); reference to component and system states (e.g., [28]); and parametric message and use of data (e.g., [10]).…”

Section: Scenarios and Message Sequence Chartsmentioning

confidence: 99%

Synthesis of behavioral models from scenarios

Uchitel

Kramer

Magee

2003

IIEEE Trans. Software Eng.

212

147

View full text Add to dashboard Cite

Scenario-based specifications such as Message Sequence Charts (MSCs) are useful as part of a requirements specification. A scenario is a partial story, describing how system components, the environment, and users work concurrently and interact in order to provide system level functionality. Scenarios need to be combined to provide a more complete description of system behavior. Consequently, scenario synthesis is central to the effective use of scenario descriptions. How should a set of scenarios be interpreted? How do they relate to one another? What is the underlying semantics? What assumptions are made when synthesizing behavior models from multiple scenarios? In this paper, we present an approach to scenario synthesis based on a clear sound semantics, which can support and integrate many of the existing approaches to scenario synthesis. The contributions of the paper are threefold. We first define an MSC language with sound abstract semantics in terms of labeled transition systems and parallel composition. The language integrates existing approaches based on scenario composition by using high-level MSCs (hMSCs) and those based on state identification by introducing explicit component state labeling. This combination allows stakeholders to break up scenario specifications into manageable parts and reuse scenarios using hMCSs; it also allows them to introduce additional domainspecific information and general assumptions explicitly into the scenario specification using state labels. Second, we provide a sound synthesis algorithm which translates scenarios into a behavioral specification in the form of Finite Sequential Processes. This specification can be analyzed with the Labeled Transition System Analyzer using model checking and animation. Finally, we demonstrate how many of the assumptions embedded in existing synthesis approaches can be made explicit and modeled in our approach. Thus, we provide the basis for a common approach to scenario-based specification, synthesis, and analysis.

show abstract

Section: Scenarios and Message Sequence Chartsmentioning

confidence: 99%

Synthesis of behavioral models from scenarios

Uchitel

Kramer

Magee

2003

IIEEE Trans. Software Eng.

212

147

View full text Add to dashboard Cite

show abstract

“…This means that an instance, say Pi, can only refer to a variable x if and only if either x is local to Pi, or x is passed from some Pj via a message. This requirement fits the MSC spirit and has been adopted in [5]. For example, a naive way to interpret MSC4 in Figure 2 is that the messages a(0), b (1) …”

Section: Assumptions On Datamentioning

confidence: 99%

“…Literature such as [5,6] proposed some problems and design decisions for this incorporation. A summary can be found in the work of Engels [4].…”

Section: Assumptions On Datamentioning

confidence: 99%