LEADER 06396nam 22008055 450 001 996466040503316 005 20220423010526.0 010 $a3-540-48267-9 024 7 $a10.1007/11916246 035 $a(CKB)1000000000283990 035 $a(SSID)ssj0000319850 035 $a(PQKBManifestationID)11255745 035 $a(PQKBTitleCode)TC0000319850 035 $a(PQKBWorkID)10342250 035 $a(PQKB)10406320 035 $a(DE-He213)978-3-540-48267-3 035 $a(MiAaPQ)EBC3068579 035 $a(PPN)123139392 035 $a(EXLCZ)991000000000283990 100 $a20100301d2006 u| 0 101 0 $aeng 135 $aurnn#008mamaa 181 $ctxt 182 $cc 183 $acr 200 10$aRigorous Development of Complex Fault-Tolerant Systems$b[electronic resource] /$fedited by Michael Butler, Cliff Jones, Alexander Romanovsky, Elena Troubitsyna 205 $a1st ed. 2006. 210 1$aBerlin, Heidelberg :$cSpringer Berlin Heidelberg :$cImprint: Springer,$d2006. 215 $a1 online resource (X, 406 p.) 225 1 $aProgramming and Software Engineering ;$v4157 300 $a"Workshop on Rigorous Engineering of Fault-tolerant Systems, REFT 2005, was held in conjunction with the Formal Methods 2005 conference at Newcastle University"--Pref. 311 $a3-540-48265-2 320 $aIncludes bibliographical references and index. 327 $aTrain Systems -- Train Systems -- Formalising Reconciliation in Partitionable Networks with Distributed Services -- The Fault-Tolerant Insulin Pump Therapy -- Reasoning About Exception Flow at the Architectural Level -- Are Practitioners Writing Contracts? -- Determining the Specification of a Control System: An Illustrative Example -- Achieving Fault Tolerance by a Formally Validated Interaction Policy -- F(I)MEA-Technique of Web Services Analysis and Dependability Ensuring -- On Specification and Verification of Location-Based Fault Tolerant Mobile Systems -- Formal Development of Mechanisms for Tolerating Transient Faults -- Separating Concerns in Requirements Analysis: An Example -- Rigorous Fault Tolerance Using Aspects and Formal Methods -- Rigorous Development of Fault-Tolerant Agent Systems -- Formal Service-Oriented Development of Fault Tolerant Communicating Systems -- Programming-Logic Analysis of Fault Tolerance: Expected Performance of Self-stabilisation -- Formal Analysis of the Operational Concept for the Small Aircraft Transportation System -- Towards a Method for Rigorous Development of Generic Requirements Patterns -- Rigorous Design of Fault-Tolerant Transactions for Replicated Database Systems Using Event B -- Engineering Reconfigurable Distributed Software Systems: Issues Arising for Pervasive Computing -- Position Papers -- Tools for Developing Large Systems (A Proposal) -- Why Programming Languages Still Matter. 330 $aMany software systems have reached a level of complication, mainly because of their size, heterogeneity and distribution, which results in faults appearing that cannot be traced back easily to the code. Some of these "faults" could also be unexpected program behavior that appears as a result of interactions between different parts of the program; this is commonly known as complexity. New methods, approaches, tools and techniques are needed to cope with the increasing complexity in software systems; amongst them, fault-tolerance techniques and formal methods, supported by the corresponding tools, are promising solutions. This book brings together papers focusing on the application of rigorous design techniques to the development of fault-tolerant, software-based systems. This volume is an outcome of the REFT 2005 Workshop on Rigorous Engineering of Fault-Tolerant Systems held in conjunction with the Formal Methods 2005 conference at Newcastle upon Tyne, UK, in July 2005. The authors of the best workshop papers were asked to enhance and expand their work and a number of well-established researchers working in the area contributed invited chapters. From the 19 refereed and revised papers presented, 12 are versions reworked from the workshop; 9 of them are totally new. The book is rounded off by two provocatively different position on the role of programming languages. 410 0$aProgramming and Software Engineering ;$v4157 606 $aComputers 606 $aComputer communication systems 606 $aComputer programming 606 $aSoftware engineering 606 $aProgramming languages (Electronic computers) 606 $aOperating systems (Computers) 606 $aTheory of Computation$3https://scigraph.springernature.com/ontologies/product-market-codes/I16005 606 $aComputer Communication Networks$3https://scigraph.springernature.com/ontologies/product-market-codes/I13022 606 $aProgramming Techniques$3https://scigraph.springernature.com/ontologies/product-market-codes/I14010 606 $aSoftware Engineering$3https://scigraph.springernature.com/ontologies/product-market-codes/I14029 606 $aProgramming Languages, Compilers, Interpreters$3https://scigraph.springernature.com/ontologies/product-market-codes/I14037 606 $aOperating Systems$3https://scigraph.springernature.com/ontologies/product-market-codes/I14045 615 0$aComputers. 615 0$aComputer communication systems. 615 0$aComputer programming. 615 0$aSoftware engineering. 615 0$aProgramming languages (Electronic computers). 615 0$aOperating systems (Computers). 615 14$aTheory of Computation. 615 24$aComputer Communication Networks. 615 24$aProgramming Techniques. 615 24$aSoftware Engineering. 615 24$aProgramming Languages, Compilers, Interpreters. 615 24$aOperating Systems. 676 $a004.2 702 $aButler$b Michael$f1967-$4edt$4http://id.loc.gov/vocabulary/relators/edt 702 $aJones$b Cliff$4edt$4http://id.loc.gov/vocabulary/relators/edt 702 $aRomanovsky$b Alexander$4edt$4http://id.loc.gov/vocabulary/relators/edt 702 $aTroubitsyna$b Elena$4edt$4http://id.loc.gov/vocabulary/relators/edt 712 12$aWorkshop on Rigorous Engineering of Fault-tolerant Systems 906 $aBOOK 912 $a996466040503316 996 $aRigorous Development of Complex Fault-Tolerant Systems$9772219 997 $aUNISA