Scenarios: Models, Transformations and Tools

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

  • Stefan Leue
  • Tarja Johanna Systä
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3466)

Table of contents

  1. Front Matter
  2. Scenarios: Models, Transformations and Tools

    1. Øystein Haugen, Knut Eilif Husa, Ragnhild Kobro Runde, Ketil Stølen
      Pages 1-25
    2. Anca Muscholl, Doron Peled
      Pages 43-65
    3. Cas Cremers, Sjouke Mauw
      Pages 66-89
    4. Holger Giese, Florian Klein
      Pages 90-94
    5. Ira Diethelm, Leif Geiger, Albert Zündorf
      Pages 109-133
    6. Dorin B. Petriu, Daniel Amyot, Murray Woodside, Bo Jiang
      Pages 134-151
    7. Matthias Beyer, Winfried Dulz
      Pages 152-173
    8. Yves Bontemps, Patrick Heymans, Pierre-Yves Schobbens
      Pages 174-192
    9. Holger Giese, Florian Klein, Sven Burmester
      Pages 193-211
    10. Ingolf H. Krüger, Reena Mathew
      Pages 255-277
  3. Back Matter

About these proceedings

Introduction

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.

Keywords

modeling object-oriented programming programming semantics software engineering tools validation verification

Editors and affiliations

  • Stefan Leue
    • 1
  • Tarja Johanna Systä
    • 2
  1. 1.Department of Computer and Information ScienceUniversity of KonstanzKonstanzGermany
  2. 2.Department of Software SystemsTampere University of Technology 

Bibliographic information

  • DOI https://doi.org/10.1007/b137052
  • Copyright Information Springer-Verlag Berlin Heidelberg 2005
  • Publisher Name Springer, Berlin, Heidelberg
  • eBook Packages Computer Science
  • Print ISBN 978-3-540-26189-6
  • Online ISBN 978-3-540-32032-6
  • Series Print ISSN 0302-9743
  • Series Online ISSN 1611-3349