000 04738nam a22005775i 4500
001 978-3-540-32032-6
003 DE-He213
005 20240730181756.0
007 cr nn 008mamaa
008 100713s2005 gw | s |||| 0|eng d
020 _a9783540320326
_9978-3-540-32032-6
024 7 _a10.1007/b137052
_2doi
050 4 _aQA76.758
072 7 _aUMZ
_2bicssc
072 7 _aCOM051230
_2bisacsh
072 7 _aUMZ
_2thema
082 0 4 _a005.1
_223
245 1 0 _aScenarios: Models, Transformations and Tools
_h[electronic resource] :
_bInternational Workshop, Dagstuhl Castle, Germany, September 7-12, 2003, Revised Selected Papers /
_cedited by Stefan Leue, Tarja J. Systä.
250 _a1st ed. 2005.
264 1 _aBerlin, Heidelberg :
_bSpringer Berlin Heidelberg :
_bImprint: Springer,
_c2005.
300 _aXII, 279 p.
_bonline resource.
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
347 _atext file
_bPDF
_2rda
490 1 _aProgramming and Software Engineering,
_x2945-9168 ;
_v3466
505 0 _aScenarios: 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.
520 _aVisual 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.
650 0 _aSoftware engineering.
_94138
650 0 _aComputer science.
_99832
650 0 _aComputer networks .
_931572
650 0 _aElectronic data processing
_xManagement.
_9126130
650 1 4 _aSoftware Engineering.
_94138
650 2 4 _aComputer Science Logic and Foundations of Programming.
_942203
650 2 4 _aComputer Communication Networks.
_9126131
650 2 4 _aIT Operations.
_931703
700 1 _aLeue, Stefan.
_eeditor.
_4edt
_4http://id.loc.gov/vocabulary/relators/edt
_9126132
700 1 _aSystä, Tarja J.
_eeditor.
_4edt
_4http://id.loc.gov/vocabulary/relators/edt
_9126133
710 2 _aSpringerLink (Online service)
_9126134
773 0 _tSpringer Nature eBook
776 0 8 _iPrinted edition:
_z9783540261896
776 0 8 _iPrinted edition:
_z9783540811695
830 0 _aProgramming and Software Engineering,
_x2945-9168 ;
_v3466
_9126135
856 4 0 _uhttps://doi.org/10.1007/b137052
912 _aZDB-2-SCS
912 _aZDB-2-SXCS
912 _aZDB-2-LNC
942 _cELN
999 _c91072
_d91072