LEADER 04915nam 22007095 450 001 9910483181003321 005 20251226203530.0 024 7 $a10.1007/b137052 035 $a(CKB)1000000000213042 035 $a(SSID)ssj0000319914 035 $a(PQKBManifestationID)11255871 035 $a(PQKBTitleCode)TC0000319914 035 $a(PQKBWorkID)10339212 035 $a(PQKB)10321551 035 $a(DE-He213)978-3-540-32032-6 035 $a(MiAaPQ)EBC3067990 035 $a(PPN)123095255 035 $a(EXLCZ)991000000000213042 100 $a20100713d2005 u| 0 101 0 $aeng 135 $aurnn|008mamaa 181 $ctxt 182 $cc 183 $acr 200 10$aScenarios: Models, Transformations and Tools $eInternational Workshop, Dagstuhl Castle, Germany, September 7-12, 2003, Revised Selected Papers /$fedited by Stefan Leue, Tarja J. Systä 205 $a1st ed. 2005. 210 1$aBerlin, Heidelberg :$cSpringer Berlin Heidelberg :$cImprint: Springer,$d2005. 215 $a1 online resource (XII, 279 p.) 225 1 $aProgramming and Software Engineering,$x2945-9168 ;$v3466 300 $aBibliographic Level Mode of Issuance: Monograph 311 08$a3-540-32032-6 311 08$a3-540-26189-3 320 $aIncludes bibliographical references and index. 327 $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. 330 $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. 410 0$aProgramming and Software Engineering,$x2945-9168 ;$v3466 606 $aSoftware engineering 606 $aComputer science 606 $aComputer networks 606 $aElectronic data processing$xManagement 606 $aSoftware Engineering 606 $aComputer Science Logic and Foundations of Programming 606 $aComputer Communication Networks 606 $aIT Operations 615 0$aSoftware engineering. 615 0$aComputer science. 615 0$aComputer networks. 615 0$aElectronic data processing$xManagement. 615 14$aSoftware Engineering. 615 24$aComputer Science Logic and Foundations of Programming. 615 24$aComputer Communication Networks. 615 24$aIT Operations. 676 $a005.1 701 $aLeue$b Stefan$01759619 701 $aSysta$b Tarja Johanna$01759620 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910483181003321 996 $aScenarios: Models, Transformations and Tools$94198191 997 $aUNINA