Scenarios: Models, Transformations and Tools (Record no. 91072)

000 -LEADER
fixed length control field 04738nam a22005775i 4500
001 - CONTROL NUMBER
control field 978-3-540-32032-6
003 - CONTROL NUMBER IDENTIFIER
control field DE-He213
005 - DATE AND TIME OF LATEST TRANSACTION
control field 20240730181756.0
007 - PHYSICAL DESCRIPTION FIXED FIELD--GENERAL INFORMATION
fixed length control field cr nn 008mamaa
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 100713s2005 gw | s |||| 0|eng d
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9783540320326
-- 978-3-540-32032-6
024 7# - OTHER STANDARD IDENTIFIER
Standard number or code 10.1007/b137052
Source of number or code doi
050 #4 - LIBRARY OF CONGRESS CALL NUMBER
Classification number QA76.758
072 #7 - SUBJECT CATEGORY CODE
Subject category code UMZ
Source bicssc
072 #7 - SUBJECT CATEGORY CODE
Subject category code COM051230
Source bisacsh
072 #7 - SUBJECT CATEGORY CODE
Subject category code UMZ
Source thema
082 04 - DEWEY DECIMAL CLASSIFICATION NUMBER
Classification number 005.1
Edition number 23
245 10 - TITLE STATEMENT
Title Scenarios: Models, Transformations and Tools
Medium [electronic resource] :
Remainder of title International Workshop, Dagstuhl Castle, Germany, September 7-12, 2003, Revised Selected Papers /
Statement of responsibility, etc. edited by Stefan Leue, Tarja J. Systä.
250 ## - EDITION STATEMENT
Edition statement 1st ed. 2005.
264 #1 - PRODUCTION, PUBLICATION, DISTRIBUTION, MANUFACTURE, AND COPYRIGHT NOTICE
Place of production, publication, distribution, manufacture Berlin, Heidelberg :
Name of producer, publisher, distributor, manufacturer Springer Berlin Heidelberg :
-- Imprint: Springer,
Date of production, publication, distribution, manufacture, or copyright notice 2005.
300 ## - PHYSICAL DESCRIPTION
Extent XII, 279 p.
Other physical details online resource.
336 ## - CONTENT TYPE
Content type term text
Content type code txt
Source rdacontent
337 ## - MEDIA TYPE
Media type term computer
Media type code c
Source rdamedia
338 ## - CARRIER TYPE
Carrier type term online resource
Carrier type code cr
Source rdacarrier
347 ## - DIGITAL FILE CHARACTERISTICS
File type text file
Encoding format PDF
Source rda
490 1# - SERIES STATEMENT
Series statement Programming and Software Engineering,
International Standard Serial Number 2945-9168 ;
Volume/sequential designation 3466
505 0# - FORMATTED CONTENTS NOTE
Formatted contents note Scenarios: 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 ## - SUMMARY, ETC.
Summary, etc. 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.
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Software engineering.
9 (RLIN) 4138
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Computer science.
9 (RLIN) 9832
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Computer networks .
9 (RLIN) 31572
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Electronic data processing
General subdivision Management.
9 (RLIN) 126130
650 14 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Software Engineering.
9 (RLIN) 4138
650 24 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Computer Science Logic and Foundations of Programming.
9 (RLIN) 42203
650 24 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element Computer Communication Networks.
9 (RLIN) 126131
650 24 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name entry element IT Operations.
9 (RLIN) 31703
700 1# - ADDED ENTRY--PERSONAL NAME
Personal name Leue, Stefan.
Relator term editor.
Relationship edt
-- http://id.loc.gov/vocabulary/relators/edt
9 (RLIN) 126132
700 1# - ADDED ENTRY--PERSONAL NAME
Personal name Systä, Tarja J.
Relator term editor.
Relationship edt
-- http://id.loc.gov/vocabulary/relators/edt
9 (RLIN) 126133
710 2# - ADDED ENTRY--CORPORATE NAME
Corporate name or jurisdiction name as entry element SpringerLink (Online service)
9 (RLIN) 126134
773 0# - HOST ITEM ENTRY
Title Springer Nature eBook
776 08 - ADDITIONAL PHYSICAL FORM ENTRY
Relationship information Printed edition:
International Standard Book Number 9783540261896
776 08 - ADDITIONAL PHYSICAL FORM ENTRY
Relationship information Printed edition:
International Standard Book Number 9783540811695
830 #0 - SERIES ADDED ENTRY--UNIFORM TITLE
Uniform title Programming and Software Engineering,
International Standard Serial Number 2945-9168 ;
Volume/sequential designation 3466
9 (RLIN) 126135
856 40 - ELECTRONIC LOCATION AND ACCESS
Uniform Resource Identifier <a href="https://doi.org/10.1007/b137052">https://doi.org/10.1007/b137052</a>
912 ## -
-- ZDB-2-SCS
912 ## -
-- ZDB-2-SXCS
912 ## -
-- ZDB-2-LNC
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Koha item type eBooks-Lecture Notes in CS

No items available.