LEADER 05180nam 22007455 450 001 9910254254903321 005 20200706015159.0 010 $a3-319-29465-2 024 7 $a10.1007/978-3-319-29465-0 035 $a(CKB)3710000000596714 035 $a(EBL)4406566 035 $a(SSID)ssj0001653874 035 $a(PQKBManifestationID)16432903 035 $a(PQKBTitleCode)TC0001653874 035 $a(PQKBWorkID)14983115 035 $a(PQKB)10254777 035 $a(DE-He213)978-3-319-29465-0 035 $a(MiAaPQ)EBC4406566 035 $a(PPN)192219693 035 $a(EXLCZ)993710000000596714 100 $a20160213d2016 u| 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aSoftware Design for Resilient Computer Systems /$fby Igor Schagaev, Kaegi Thomas 205 $a1st ed. 2016. 210 1$aCham :$cSpringer International Publishing :$cImprint: Springer,$d2016. 215 $a1 online resource (218 p.) 300 $aIncludes index. 311 $a3-319-29463-6 327 $aIntroduction -- Hardware Faults -- Fault Tolerance: Theory and Concepts -- Generalized Algorithm of Fault Tolerance (GAFT) -- GAFT Generalization: A Principle and Model of Active System Safety -- System Software Support for Hardware Deficiency: Function and Features -- Testing and Checking -- Recovery Preparation -- Recovery: Searching and Monitoring of Correct Software States -- Recovery Algorithms: An Analysis -- Programming Language for Safety Critical Systems -- Proposed Runtime System Structure -- Proposed Runtime System vs. Existing Approaches -- Hardware: The ERRIC Architecture -- Architecture Comparison and Evaluation -- ERRIC Reliability. 330 $aThis book addresses the question of how system software should be designed to account for faults, and which fault tolerance features it should provide for highest reliability. The authors first show how the system software interacts with the hardware to tolerate faults. They analyze and further develop the theory of fault tolerance to understand the different ways to increase the reliability of a system, with special attention on the role of system software in this process. They further develop the general algorithm of fault tolerance (GAFT) with its three main processes: hardware checking, preparation for recovery, and the recovery procedure. For each of the three processes, they analyze the requirements and properties theoretically and give possible implementation scenarios and system software support required. Based on the theoretical results, the authors derive an Oberon-based programming language with direct support of the three processes of GAFT. In the last part of this book, they introduce a simulator, using it as a proof of concept implementation of a novel fault tolerant processor architecture (ERRIC) and its newly developed runtime system feature-wise and performance-wise. The content applies to industries such as military, aviation, intensive health care, industrial control, space exploration, etc. · Outlines potential critical faults in the modern computer systems and what is required to change them · Explains how to design and re-design system software for the next generation of computers for wider application domains and greater efficiency and reliability · Presents how implemented system software support makes maintenance of computer systems much easier, while reliability and performance increases. 606 $aElectrical engineering 606 $aElectronic circuits 606 $aSoftware engineering 606 $aComputer software?Reusability 606 $aQuality control 606 $aReliability 606 $aIndustrial safety 606 $aCommunications Engineering, Networks$3https://scigraph.springernature.com/ontologies/product-market-codes/T24035 606 $aCircuits and Systems$3https://scigraph.springernature.com/ontologies/product-market-codes/T24068 606 $aSoftware Engineering$3https://scigraph.springernature.com/ontologies/product-market-codes/I14029 606 $aPerformance and Reliability$3https://scigraph.springernature.com/ontologies/product-market-codes/I12077 606 $aQuality Control, Reliability, Safety and Risk$3https://scigraph.springernature.com/ontologies/product-market-codes/T22032 615 0$aElectrical engineering. 615 0$aElectronic circuits. 615 0$aSoftware engineering. 615 0$aComputer software?Reusability. 615 0$aQuality control. 615 0$aReliability. 615 0$aIndustrial safety. 615 14$aCommunications Engineering, Networks. 615 24$aCircuits and Systems. 615 24$aSoftware Engineering. 615 24$aPerformance and Reliability. 615 24$aQuality Control, Reliability, Safety and Risk. 676 $a620 700 $aSchagaev$b Igor$4aut$4http://id.loc.gov/vocabulary/relators/aut$0720771 702 $aThomas$b Kaegi$4aut$4http://id.loc.gov/vocabulary/relators/aut 906 $aBOOK 912 $a9910254254903321 996 $aSoftware Design for Resilient Computer Systems$92527431 997 $aUNINA LEADER 03258nam 2200637 a 450 001 9910964999103321 005 20230721010922.0 010 $a3-938793-81-3 010 $a3-11-032709-0 024 7 $a10.1515/9783110327090 035 $a(CKB)2550000001097117 035 $a(EBL)1195536 035 $a(OCoLC)851970848 035 $a(SSID)ssj0000801484 035 $a(PQKBManifestationID)11494183 035 $a(PQKBTitleCode)TC0000801484 035 $a(PQKBWorkID)10794098 035 $a(PQKB)10744625 035 $a(DE-B1597)211608 035 $a(OCoLC)1013945576 035 $a(OCoLC)881295584 035 $a(DE-B1597)9783110327090 035 $a(Au-PeEL)EBL1195536 035 $a(CaPaEBR)ebr10728647 035 $a(CaONFJC)MIL503651 035 $a(Perlego)654479 035 $a(MiAaPQ)EBC1195536 035 $a(EXLCZ)992550000001097117 100 $a20130709d2008 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aOmniscience $efrom a logical point of view /$fPaul Weingartner 210 $aFrankfurt $cOntos Verlag$d2008 215 $a1 online resource (202 p.) 225 1 $aPhilosophische Analyse / Philosophical analysis ;$vBd. 23 300 $aDescription based upon print version of record. 311 08$a3-11-032669-8 311 08$a1-299-72400-0 320 $aIncludes bibliographical references and indexes. 327 $t Frontmatter -- $tPreface -- $tContents -- $t1. Whether Everything is True What God Knows -- $t2. Whether God Necessarily Knows Whatever He Knows -- $t3. Whether God Knows Something at Some Time -- $t4. Whether God Knows All Past and Present Events -- $t5. Whether God's Knowledge Exceeds His Power -- $t6. Whether God Causes Everything What He Knows -- $t7. Whether God Knows Singular Truths? -- $t8. Whether God's Knowledge of Singular, Contingent Truths Implies the Mutability of God -- $t9. Whether God Knows What Is Not. -- $t10. Whether Knowledge or Truth Can Change the Status of a State of Affairs -- $t11. Whether God Knows Future States of Affairs -- $t12. Whether God Knows Everything That is True -- $t13. A Theory of Omniscience -- $tLITERATURE -- $tSubject Index -- $tName Index -- $t Backmatter 330 $aThe aim of the book is to clarify the concept of omniscience. This is done first by discussing basic questions on omniscience (chs.1-12) and secondly by offering a theory of omniscience as an axiomatic system in which also a definition of omniscience is given (ch.13). The twelve chapters deal with questions like whether everything is true what God knows, whether God ?s knowledge is bound to time, whether it concerns singular truths or only laws, whether it extends also to contingent futureevents.etc. The book is neither a book about the existence of God nor about proofs for his existence. It is 410 0$aPhilosophische Analyse ;$vBd. 23. 606 $aGod (Christianity)$xOmniscience 615 0$aGod (Christianity)$xOmniscience. 676 $a200 700 $aWeingartner$b Paul$051211 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910964999103321 996 $aOmniscience$94447555 997 $aUNINA