Scenarios: Models, Transformations and Tools : International Workshop, Dagstuhl Castle, Germany, September 7-12, 2003, Revised Selected Papers / edited by Stefan Leue, Tarja J. Systä.

Format:

Book

Contributor:

Leue, Stefan, editor.

Systä, Tarja J., editor.

SpringerLink (Online service)

Series:

Computer Science (Springer-11645)

LNCS sublibrary. Programming and software engineering ; SL 2, 3466.

Programming and Software Engineering ; 3466

Language:

English

Subjects (All):

Software engineering.

Computer logic.

Computer networks.

Management information systems.

Computer science.

Software Engineering/Programming and Operating Systems.

Logics and Meanings of Programs.

Computer Communication Networks.

Software Engineering.

Management of Computing and Information Systems.

Local Subjects:

Software Engineering/Programming and Operating Systems.

Logics and Meanings of Programs.

Computer Communication Networks.

Software Engineering.

Management of Computing and Information Systems.

Physical Description:

1 online resource (XII, 279 pages).

Edition:

First edition 2005.

Contained In:

Springer eBooks

Place of Publication:

Berlin, Heidelberg : Springer Berlin Heidelberg : Imprint: Springer, 2005.

System Details:

text file PDF

Summary:

Visual notations and languages continue to play a pivotal role ̂ in the design of complex software systems. In many cases visual notations are used to - scribe usage or interaction scenarios of software systems or their components. While representing scenarios using a visual notation is not the only possibility, a vast majority of scenario description languages is visual. Scenarios are used in telecommunications as Message Sequence Charts, in object-oriented system design as Sequence Diagrams, in reverse engineering as execution traces, and in requirements engineering as, for example, Use Case Maps or Life Sequence Charts. These techniques are used to capture requirements, to capture use cases in system documentation, to specify test cases, or to visualize runs of existing systems. They are often employed to represent concurrent systems that int- act via message passing or method invocation. In telecommunications, for more than 15 years the International Telecommunication Union has standardized the Message Sequence Charts (MSCs) notation in its recommendation Z. 120. More recently, with the emergence of UML as a predominant software design meth- ology, there has been special interest in the development of the sequence d- gram notation. As a result, the most recent version, 2. 0, of UML encompasses the Message Sequence Chart notation, including its hierarchical modeling f- tures. Other scenario-?avored diagrams in UML 2. 0 include activity diagrams and timing diagrams.

Contents:

Scenarios: Models, Transformations and Tools

Why Timed Sequence Diagrams Require Three-Event Semantics

Some Methodological Observations Resulting from Experience Using LSCs and the Play-In/Play-Out Approach

Deciding Properties of Message Sequence Charts

Operational Semantics of Security Protocols

Autonomous Shuttle System Case Study

Genetic Design: Amplifying Our Ability to Deal With Requirements Complexity

Applying Story Driven Modeling to the Paderborn Shuttle System Case Study

Traceability and Evaluation in Scenario Analysis by Use Case Maps

Scenario-Based Statistical Testing of Quality of Service Requirements

Lightweight Formal Methods for Scenario-Based Software Engineering

Pattern Synthesis from Multiple Scenarios for Parameterized Real-Time UML Models

Partial Order Semantics of Sequence Diagrams for Mobility

From MSC to SDL: Overview and an Application to the Autonomous Shuttle Transport System

Component Synthesis from Service Specifications.

Other Format:

Printed edition:

ISBN:

978-3-540-32032-6

9783540320326

Access Restriction:

Restricted for use by site license.