Skip to main content
SpringerLink
Log in

Scenarios: Models, Transformations and Tools

International Workshop, Dagstuhl Castle, Germany, September 7-12, 2003, Revised Selected Papers

  • Conference proceedings
  • © 2005

Overview

Editors:
  1. Stefan Leue

    1. Department of Computer and Information Science, University of Konstanz, Konstanz, Germany

    View editor publications

    You can also search for this editor in PubMed   Google Scholar

  2. Tarja Johanna Systä

    1. Department of Software Systems, Tampere University of Technology,  

    View editor publications

    You can also search for this editor in PubMed   Google Scholar

Part of the book series: Lecture Notes in Computer Science (LNCS, volume 3466)

Part of the book sub series: Programming and Software Engineering (LNPSE)

This is a preview of subscription content, log in via an institution to check access.

Access this book

Log in via an institution
eBook USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Other ways to access

Licence this eBook for your library

Institutional subscriptions

Table of contents (14 papers)

  1. Front Matter

    Download chapter PDF

  2. Scenarios: Models, Transformations and Tools

    1. Why Timed Sequence Diagrams Require Three-Event Semantics

      • Øystein Haugen, Knut Eilif Husa, Ragnhild Kobro Runde, Ketil Stølen
      Pages 1-25

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

      • David Harel, Hillel Kugler, Gera Weiss
      Pages 26-42

    3. Deciding Properties of Message Sequence Charts

      • Anca Muscholl, Doron Peled
      Pages 43-65

    4. Operational Semantics of Security Protocols

      • Cas Cremers, Sjouke Mauw
      Pages 66-89

    5. Autonomous Shuttle System Case Study

      • Holger Giese, Florian Klein
      Pages 90-94

    6. Genetic Design: Amplifying Our Ability to Deal With Requirements Complexity

      • R. Geoff Dromey
      Pages 95-108

    7. Applying Story Driven Modeling to the Paderborn Shuttle System Case Study

      • Ira Diethelm, Leif Geiger, Albert Zündorf
      Pages 109-133

    8. Traceability and Evaluation in Scenario Analysis by Use Case Maps

      • Dorin B. Petriu, Daniel Amyot, Murray Woodside, Bo Jiang
      Pages 134-151

    9. Scenario-Based Statistical Testing of Quality of Service Requirements

      • Matthias Beyer, Winfried Dulz
      Pages 152-173

    10. Lightweight Formal Methods for Scenario-Based Software Engineering

      • Yves Bontemps, Patrick Heymans, Pierre-Yves Schobbens
      Pages 174-192

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

      • Holger Giese, Florian Klein, Sven Burmester
      Pages 193-211

    12. Partial Order Semantics of Sequence Diagrams for Mobility

      • Piotr Kosiuczenko
      Pages 212-227

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

      • Ferhat Khendek, Xiao Jun Zhang
      Pages 228-254

    14. Component Synthesis from Service Specifications

      • Ingolf H. Krüger, Reena Mathew
      Pages 255-277

  3. Back Matter

    Download chapter PDF
Back to top

Keywords

About this book

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.

Editors and Affiliations

  • Department of Computer and Information Science, University of Konstanz, Konstanz, Germany

    Stefan Leue

  • Department of Software Systems, Tampere University of Technology,  

    Tarja Johanna Systä

Bibliographic Information

Publish with us

Policies and ethics

Back to top

Search

Navigation