SDE: incremental specification and development of communications software

Ichikawa, Haruhisa; Itoh, Masaki; Kato, J.; Takura, A.; Shibasaki, M.

doi:10.1109/12.88473

Cited by 17 publications

(5 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Note that in their approach, the states of the resulting diagram are manually identified by the analyst when building the scenario tree. Finally, as an example from the telecommunications domain, the research by Ichikawa et al [35] may be mentioned. They introduce a language for message sequence description as a basis for protocol synthesis.…”

Section: Related Workmentioning

confidence: 98%

Algorithmic support for model transformation in object‐oriented software development

Schönberger

Keller

Khriss

2001

Concurrency and Computation

View full text Add to dashboard Cite

SUMMARYCurrent methods for object-oriented software development provide notation for the specification of models, yet do not sufficiently relate the different model types to each other, nor do they provide support for transformations from one model type to another. This makes transformations a manual activity, which increases the risk of inconsistencies among models and may lead to a loss of information. We have developed and implemented an algorithm supporting one of the transitions from analysis to design, the transformation of scenario models into behavior models. This algorithm supports the Unified Modelling Language (UML), mapping the UML's collaboration diagrams into state transition diagrams. We believe that CASE tools implementing such algorithms will be highly beneficial in object-oriented software development. In this paper, we provide an overview of our algorithm and discuss all its major steps. The algorithm is detailed in semi-formal English and illustrated with a number of examples. Furthermore, the algorithm is assessed from different perspectives, such as scope and role in the overall development process, issues in the design of the algorithm, complexity, implementation and experimentation, and related work.

show abstract

Section: Related Workmentioning

confidence: 98%

Algorithmic support for model transformation in object‐oriented software development

Schönberger

Keller

Khriss

2001

Concurrency and Computation

View full text Add to dashboard Cite

show abstract

“…We believe that this is crucial as many of the subtle design issues can lead to errors when concurrent interacting components are composed. Other work based on translation have focused on producing SDL specifications (e.g., [21]), hierarchical state machines (e.g., [6]), and other state machine based formalisms (e.g., [25]).…”

Section: Semantic Definitionsmentioning

confidence: 99%

“…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

“…This tool supports the editing of hMSCs, but analysis is focussed on only basic MSCs. -The SDE [13] and MuSiC++ [20] developed by NTT are closely related tools centered around SDL and providing for MSC editing, analysis and code synthesis. Analyses include an inconsistency check that is based on deadlock detection in bMSCs, and code synthesis that produces SDL code from bMSCs.…”

Section: Call This Requirement the "What-you-see-is-what-you-ge~'mentioning

confidence: 99%

“…They have already been adopted within several software engineering methodologies and tools, e.g., [13], [8], [17], [22], [7], [2], and [3]. MSCs are used to document system requirements that guide the system design [22], describe test scenarios (e.g., [17,7]), express system properties that are verified against SDL specifications [2], visualize sample behavior of a simulated system specification [22,2,12], capture early life-cycle requirements [3], and to express legacy specifications in an intermediate representation that helps in software maintenance and reengineering [13]. In this paper we propose the architecture for an MSC-based tool for the requirements and design phases of the life-cycle of reactive systems.…”

Section: Introductionmentioning

confidence: 99%

Mesa: Support for scenario-based design of concurrent systems

Ben-Abdallah

Leue

1998

Tools and Algorithms for the Construction and Analysis of Systems

View full text Add to dashboard Cite

Abstract. The latest ITU-T standard syntax of Message Sequence Charts (MSCs) [16] offers several operators to compose MSCs in a hierarchical, iterating, and nondeterministic way. However, current tools operate on MSCs that describe finite, deterministic behavior. In this paper, we describe the architecture and the partial implementation of MESA, an MSC-based tool that supports early phases of the software development cycle. The main functionalities of MESA are: an environment for the composition of system models through MSCs, syntactic and model-based analysis of an MSC model, and resolution of resource related underspecifications in an MSC model.

show abstract

SDE: incremental specification and development of communications software

Cited by 17 publications

References 11 publications

Algorithmic support for model transformation in object‐oriented software development

Algorithmic support for model transformation in object‐oriented software development

Synthesis of behavioral models from scenarios

Mesa: Support for scenario-based design of concurrent systems

Contact Info

Product

Resources

About