000 04964nam a2201213 i 4500
001 5732779
003 IEEE
005 20220712205753.0
006 m o d
007 cr |n|||||||||
008 151221s2011 njua ob 001 eng d
020 _a9781118075104
_qebook
020 _z9780470604656
_qhardback
020 _z0470604654
_qhardback
020 _z1118075102
_qelectronic
024 8 _a9786613035448
035 _a(CaBNVSL)mat05732779
035 _a(IDAMS)0b000064814ebef5
040 _aCaBNVSL
_beng
_erda
_cCaBNVSL
_dCaBNVSL
050 4 _aTA169
_b.B385 2010eb
100 1 _aBauer, Eric,
_eauthor.
_927599
245 1 0 _aDesign for reliability :
_binformation and computer-based systems /
_cEric Bauer.
264 1 _aHoboken, New Jersey :
_bWiley-IEEE Press,
_cc2010.
264 2 _a[Piscataqay, New Jersey] :
_bIEEE Xplore,
_c[2011]
300 _a1 PDF (xxi, 325 pages) :
_billustrations
336 _atext
_2rdacontent
337 _aelectronic
_2isbdmedia
338 _aonline resource
_2rdacarrier
504 _aIncludes bibliographical references and index.
505 0 _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.
506 1 _aRestricted to subscribers or individual electronic text purchasers.
520 _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.
530 _aAlso available in print.
538 _aMode of access: World Wide Web
588 _aDescription based on PDF viewed 12/21/2015.
650 0 _aReliability (Engineering)
_93395
655 0 _aElectronic books.
_93294
695 _aAerospace electronics
695 _aAnalytical models
695 _aApplication software
695 _aAvailability
695 _aBackplanes
695 _aBest practices
695 _aBibliographies
695 _aBiographies
695 _aBlock diagrams
695 _aBudgets
695 _aBusiness
695 _aCircuit faults
695 _aComputational modeling
695 _aComputer architecture
695 _aConcurrency control
695 _aContext awareness
695 _aData processing
695 _aData structures
695 _aDesign methodology
695 _aDowntime
695 _aElectron microscopy
695 _aError analysis
695 _aFailure analysis
695 _aFault diagnosis
695 _aField outages
695 _aHard disks
695 _aHardware
695 _aHuman factors
695 _aIndexes
695 _aInstant messaging
695 _aLoad management
695 _aMaintenance engineering
695 _aMarkov processes
695 _aModeling
695 _aMonitoring
695 _aNetwork management
695 _aOutages
695 _aPerformance evaluation
695 _aPhotography
695 _aPower distribution
695 _aProcess control
695 _aProgramming
695 _aProtocols
695 _aReal time systems
695 _aRedundancy
695 _aReliability
695 _aReliability engineering
695 _aRobustness
695 _aSecurity
695 _aServers
695 _aService management
695 _aSoftware
695 _aSoftware modeling
695 _aSoftware reliability
695 _aSoftware testing
695 _aStability analysis
695 _aSwitches
695 _aTelecommunication network management
695 _aTerminology
695 _aTesting
695 _aThroughput
710 2 _aJohn Wiley & Sons,
_epublisher.
_96902
710 2 _aIEEE Xplore,
_edistributor.
_927600
776 0 8 _iPrint version:
_z9780470604656
856 4 2 _3Abstract with links to resource
_uhttps://ieeexplore.ieee.org/xpl/bkabstractplus.jsp?bkn=5732779
942 _cEBK
999 _c74114
_d74114