Scenarios: Models, Transformations and Tools

Tarja J. Systä

ISBN 10: 3540261893 / ISBN 13: 9783540261896

Published by Springer Berlin Heidelberg, Springer Berlin Heidelberg Jun 2005, 2005

About this Item

This item is printed on demand - Print on Demand Titel. Neuware -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.Springer Verlag GmbH, Tiergartenstr. 17, 69121 Heidelberg 296 pp. Englisch.

Seller Inventory # 9783540261896

Bibliographic Details

• Title: Scenarios: Models, Transformations and Tools
• Publisher: Springer Berlin Heidelberg, Springer Berlin Heidelberg Jun 2005
• Publication Date: 2005
• Language: English
• ISBN 10: 3540261893
• ISBN 13: 9783540261896
• Binding: Taschenbuch
• Condition: Neu
• Dimensions: 235W x 155H x 17D millimeters 235 millimeters width by 155 millimeters height by 17 millimeters depth
• Weight: 452 grams

About this title

Synopsis

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.

Synopsis

This volume is a post-event proceedings volume and contains selected papers based on presentations given during a seminar, held in Dagstuhl Castle, Germany in September 2003. It was organized as a continuation of a series of workshops that have been co-located with larger conferences such as the International Conference on Software Engineering (ICSE) and the Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA) since 2000. The 14 included papers were thoroughly peer-reviewed in two rounds of reviewing and are organized in topical sections on semantics for scenario-based notations, scenario-based notations in software validation and verification, analysis of scenario-based specifications, abstraction, refinement, and synthesis for scenario-based notations, non-functional properties and data in scenario notations, synthesis of executable models from scenario descriptions, tool support for scenario-based notations, domain and application specific dialects of scenario notations, scenario-based modelling patterns, integration of scenarios and implied behaviour.