Escort: an environment for specifying communication requirements

Wakahara, Yasushi; Kakuda, Yoshiaki; Utsunomiya, Eiji

doi:10.1109/52.23128

Cited by 12 publications

(2 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Many authors consider that scenario specifications describe high-level design of system components, i.e., that a set of scenarios directly determines a state machine for each system component. This is particularly true for most approaches that use synthesis algorithms as a means of providing scenario semantics, for those in which component or system state identification is considered or those approaches that use state machine semantics (for e.g., [15], [21], [22], [27], [28], [39], [40], [49], [50]). These approaches take on a design-oriented perspective, in which scenario descriptions are a design document in their own right.…”

Section: Design Vs Early Requirements Oriented Semanticsmentioning

confidence: 99%

Synthesis of behavioral models from scenarios

Uchitel

Kramer

Magee

2003

IIEEE Trans. Software Eng.

211

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: Design Vs Early Requirements Oriented Semanticsmentioning

confidence: 99%

Synthesis of behavioral models from scenarios

Uchitel

Kramer

Magee

2003

IIEEE Trans. Software Eng.

211

147

View full text Add to dashboard Cite

show abstract

“…There has been various research on supporting the telecommunications service specification description [ 1, 2,3,4]. However, there has not been much discussion on how user requirements can be met easily.…”

Section: Introductionmentioning

confidence: 99%

Telecommunication service design support using the visual service description language STR-GR

Nakamura¹,

Inoue²,

Takami³

et al.

[Conference Record] GLOBECOM '92 - Communications for Global Users: IEEE

View full text Add to dashboard Cite

As we move toward an information society, telecommunications services are becoming more sophisticated and personalized. Accordingly, there is demand for technology that simplifies complex services so that even laymen can create and customize them.This paper describes the telecommunication service design support which facilitates the retrieval of existing service specifications, modification of these specifications using state transition rule (STR) based graphic representation, and verification of service interactions. The service design support provides the facility of finding out the existing services without knowing how to activate or operate them, when performing simulations.

show abstract

Implementation of a communication sdl specification

Hasegawa

Tanaka

1993

Electron. Comm. Jpn. Pt. I

View full text Add to dashboard Cite

This paper describes a method of converting a specification and description language (SDL) specification into a program by introducing SDL/OS. The TRONspecification 0s is adopted as 0s and C++ as a programming language to make the program portable. SDL/ OS, which consists of libraries described in C++, is constructed on 0s so that the program converted from SDL can run as it is. SDL/OS realizes the SDL functions easily by using the functions of TRON-specification 0s.Finally, this paper reports that this method is very effective in enhancement of software productivity by applying it to software development of real communication systems. Moreover, performance degradation can be compensated to some extent by introducing function calls in the same task.

show abstract

Escort: an environment for specifying communication requirements

Cited by 12 publications

References 4 publications

Synthesis of behavioral models from scenarios

Synthesis of behavioral models from scenarios

Telecommunication service design support using the visual service description language STR-GR

Implementation of a communication sdl specification

Contact Info

Product

Resources

About