001482498 000__ 07555cam\\22006137i\4500
001482498 001__ 1482498
001482498 003__ OCoLC
001482498 005__ 20231128003338.0
001482498 006__ m\\\\\o\\d\\\\\\\\
001482498 007__ cr\un\nnnunnun
001482498 008__ 231019s2023\\\\sz\a\\\\o\\\\\000\0\eng\d
001482498 019__ $$a1402201270$$a1402817635
001482498 020__ $$a9783031279010$$q(electronic bk.)
001482498 020__ $$a3031279018$$q(electronic bk.)
001482498 020__ $$z9783031279003
001482498 020__ $$z303127900X
001482498 0247_ $$a10.1007/978-3-031-27901-0$$2doi
001482498 035__ $$aSP(OCoLC)1404837820
001482498 040__ $$aGW5XE$$beng$$erda$$epn$$cGW5XE$$dEBLCP$$dYDX$$dOCLCO$$dOCLCF
001482498 049__ $$aISEA
001482498 050_4 $$aQA76.76.R44$$bK37 2023
001482498 08204 $$a004.2$$223/eng/20231019
001482498 1001_ $$aKarmakar, Gopinath,$$eauthor.
001482498 24510 $$aDevelopment of safety-critical systems :$$barchitecture and software /$$cGopinath Karmakar, Amol Wakankar, Ashutosh Kabra, Paritosh Pandya.
001482498 264_1 $$aCham :$$bSpringer,$$c2023.
001482498 300__ $$a1 online resource (xxii, 360 pages) :$$billustrations (some color)
001482498 336__ $$atext$$btxt$$2rdacontent
001482498 337__ $$acomputer$$bc$$2rdamedia
001482498 338__ $$aonline resource$$bcr$$2rdacarrier
001482498 5050_ $$aIntro -- Foreword -- Preface -- Acknowledgements -- Contents -- About the Authors -- 1 Introduction -- 1.1 Computer-Based Systems for Safety Applications -- 1.1.1 What Is a Safety-Critical System? -- 1.1.2 What Are the Advantages and Challenges? -- 1.2 Steps Towards the Development -- 1.3 Safety System and Its Architecture -- 1.4 Software in Safety Systems -- 1.4.1 The Software Development Process -- 1.5 Functional Safety and the Guiding Standards -- 1.5.1 Functional Safety: What and Why? -- 1.5.2 The Safety Standards -- 1.5.2.1 General: IEC 61508 -- 1.5.2.2 Nuclear: IEC 60880 and IEC 62138
001482498 5058_ $$a1.5.2.3 Avionics: DO-178-C and ARINC 653 -- 1.5.2.4 Automotive: ISO 26262 -- 1.5.2.5 The Common Ground -- 1.6 Qualification of Safety System Software -- 1.7 Automated Development and Formal Verification -- 1.8 Qualified Platform -- 2 System Architecture and Dependability -- 2.1 Redundancy, Reliability and Availability -- 2.1.1 Redundancy and Reliability -- 2.1.1.1 Components in Series -- 2.1.1.2 Components in Parallel -- 2.1.2 Redundancy and Availability -- 2.1.2.1 1oo2 System -- 2.1.2.2 2oo3 System -- 2.1.3 Availability -- 2.1.4 Plant Safety and Safety System
001482498 5058_ $$a2.2 Redundancy: How Far We Should Go and Why -- 2.2.1 Failure Modes and Dependability Parameters -- 2.2.1.1 Failure Modes -- 2.2.2 Comparison Between 2oo3 and 2oo4 Architectures -- 2.2.2.1 Two-out-of-Three (2oo3) Architecture -- 2.2.2.2 Two-out-of-Four (2oo4) Architecture -- 2.2.2.3 Markov Model for Comparative Analysis -- 2.2.3 Markov Analysis: Implementation Technique -- 2.2.4 Analysis for Safety and Availability -- 2.2.4.1 Results in a Nutshell -- 2.3 Architecture Model-Driven Dependability Analysis -- 2.3.1 The Background -- 2.3.2 Architecture-Driven Dependability: A Formal Approach
001482498 5058_ $$a2.3.2.1 Compositional Analysis -- 2.3.3 System Architecture Modeling in AADL -- 2.3.4 AADL Fault Model -- 2.3.5 AADL Fault Model for Dependability Analysis -- 2.3.6 Model-Based Dependability Analysis: Safety and Availability -- 2.3.7 Compositional Analysis Methodology -- 2.3.7.1 Analysis of the Algorithm -- 2.3.8 Automatic Translation of AADL Fault Model to a PRISM DTMC Model -- 2.3.8.1 Translation of Atomic Component -- 2.3.8.2 Translation of Composite Component -- 2.4 Case Studies -- 2.4.1 Case Study 1: Reactor Trip System (RTS) of a PWR -- 2.4.1.1 The Architecture
001482498 5058_ $$a2.4.1.2 Architectural Model -- 2.4.1.3 Compositional Dependability Analysis of the Reactor Trip System -- 2.4.1.4 Results -- 2.4.2 Case Study 2: Engineered Safety Feature Actuation System (ESFAS) of a PWR -- 2.4.2.1 Experimental Results -- 2.4.2.2 Comparative Study of Different Architectural Options -- 2.5 Summary and Takeaways -- 3 Software Development Process -- 3.1 Development Plan -- 3.1.1 Software Project Management Plan (SPMP) -- 3.1.2 Software Quality Assurance Plan (SQAP) -- 3.1.3 Software Verification and Validation Plan (SVVP) -- 3.1.4 Software Configuration Management Plan
001482498 506__ $$aAccess limited to authorized users.
001482498 520__ $$aThis book provides professionals and students with practical guidance for the development of safety-critical computer-based systems. It covers important aspects ranging from complying with standards and guidelines to the necessary software development process and tools, and also techniques pertaining to model-based application development platforms as well as qualified programmable controllers. After a general introduction to the book's topic in chapter 1, chapter 2 discusses dependability aspects of safety systems and how architectural design at the system level helps deal with failures and yet achieves the targeted dependability attributes. Chapter 3 presents the software development process which includes verification and validation at every stage, essential to the development of software for systems performing safety functions. It also explains how the process helps in developing a safety case that can be independently verified and validated. The subsequent chapter 4 presents some important standards and guidelines, which apply to different industries and in different countries. Chapter 5 then discusses the steps towards complying with the standards at every phase of development. It offers a guided tour traversing the path of software qualification by exploring the necessary steps towards achieving the goal with the help of case studies. Chapter 6 highlights the application of formal methods for the development of safety systems software and introduces some available notations and tools which assist the process. Finally, chapter 7 presents a detailed discussion on the importance and the advantages of qualified platforms for safety systems application development, including programmable controller (PLC) and formal model-based development platforms. Each chapter includes case studies illustrating the subject matter. The book is aimed at both practitioners and students interested in the art and science of developing computer-based systems for safety-critical applications. Both audiences will get insights into the tools and techniques along with the latest developments in the design, analysis and qualification, which are constrained by the regulatory and compliance requirements mandated by the applicable guides and standards. It also addresses the needs of professionals and young graduates who specialize in the development of necessary tools and qualified platforms.
001482498 588__ $$aOnline resource; title from PDF title page (SpringerLink, viewed October 19, 2023).
001482498 650_6 $$aOrdinateurs$$xFiabilité.
001482498 650_6 $$aSécurité des systèmes.
001482498 650_0 $$aComputers$$xReliability.$$0(DLC)sh 85000011
001482498 650_0 $$aSystem safety.
001482498 655_0 $$aElectronic books.
001482498 7001_ $$aWakankar, Amol,$$eauthor.
001482498 7001_ $$aKabra, Ashutosh,$$eauthor.
001482498 7001_ $$aPandya, Paritosh,$$eauthor.
001482498 77608 $$iPrint version:$$aKarmakar, Gopinath$$tDevelopment of Safety-Critical Systems$$dCham : Springer,c2023$$z9783031279003
001482498 852__ $$bebk
001482498 85640 $$3Springer Nature$$uhttps://univsouthin.idm.oclc.org/login?url=https://link.springer.com/10.1007/978-3-031-27901-0$$zOnline Access$$91397441.1
001482498 909CO $$ooai:library.usi.edu:1482498$$pGLOBAL_SET
001482498 980__ $$aBIB
001482498 980__ $$aEBOOK
001482498 982__ $$aEbook
001482498 983__ $$aOnline
001482498 994__ $$a92$$bISE