LEADER 03081nam 2200601 450 001 9910133450803321 005 20230125221645.0 010 $a1-283-03544-8 010 $a9786613035448 010 $a1-118-07508-0 010 $a1-118-07510-2 024 8 $a9786613035448 035 $a(CKB)3400000000000353 035 $a(EBL)700529 035 $a(OCoLC)817918242 035 $a(SSID)ssj0000476895 035 $a(PQKBManifestationID)12169744 035 $a(PQKBTitleCode)TC0000476895 035 $a(PQKBWorkID)10495904 035 $a(PQKB)10007741 035 $a(MiAaPQ)EBC700529 035 $a(CaBNVSL)mat05732779 035 $a(IDAMS)0b000064814ebef5 035 $a(IEEE)5732779 035 $a(PPN)267027850 035 $a(EXLCZ)993400000000000353 100 $a20151221d2011 uy 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aDesign for reliability $einformation and computer-based systems /$fEric Bauer 210 1$aHoboken, New Jersey :$cWiley-IEEE Press,$dc2010. 210 2$a[Piscataqay, New Jersey] :$cIEEE Xplore,$d[2011] 215 $a1 online resource (349 p.) 300 $aDescription based upon print version of record. 311 $a0-470-60465-4 320 $aIncludes bibliographical references (p. 317-318) and index. 327 $aFrontmatter -- Reliability Basics. Reliability and Availability Concepts -- System Basics -- What can go Wrong -- Reliability Concepts. Failure Containment and Redundancy -- Robust Design Principles -- Error Detection -- Analyzing and Modeling Reliability and Robustness -- Design for Reliability. Reliability Requirements -- Reliability Analysis -- Reliability Budgeting and Modeling -- Robustness and Stability Testing -- Closing the Loop -- Design for Reliability Case Study -- Conclusion -- Appendix: Assessing Design for Reliability Diligence -- Abbreviations -- References -- Photo Credits -- About the Author -- Index. 330 $a"System reliability, availability and robustness are often not well understood by system architects, engineers and developers. They often don't understand what drives customer's availability expectations, how to frame verifiable availability/robustness requirements, how to manage and budget availability/robustness, how to methodically architect and design systems that meet robustness requirements, and so on. The book takes a very pragmatic approach of framing reliability and robustness as a functional aspect of a system so that architects, designers, developers and testers can address it as a concrete, functional attribute of a system, rather than an abstract, non-functional notion"--Provided by publisher. 606 $aReliability (Engineering) 615 0$aReliability (Engineering) 676 $a620.00452 676 $a620/.00452 700 $aBauer$b Eric$0479708 801 0$bCaBNVSL 801 1$bCaBNVSL 801 2$bCaBNVSL 906 $aBOOK 912 $a9910133450803321 996 $aDesign for reliability$9258613 997 $aUNINA