| 000 | 07659nam a2201237 i 4500 | ||
|---|---|---|---|
| 001 | 5361030 | ||
| 003 | IEEE | ||
| 005 | 20220712205728.0 | ||
| 006 | m o d | ||
| 007 | cr |n||||||||| | ||
| 008 | 090618t20152009njua ob 001 0 eng d | ||
| 020 |
_a9780470455401 _qelectronic |
||
| 020 |
_z9780470408605 _qprint |
||
| 020 |
_z9780470455388 _qelectronic |
||
| 020 |
_z0470455381 _qelectronic |
||
| 020 |
_z0470455403 _qelectronic |
||
| 020 |
_z047040860X _qpaper |
||
| 024 | 7 |
_a10.1002/9780470455401 _2doi |
|
| 035 | _a(CaBNVSL)mat05361030 | ||
| 035 | _a(IDAMS)0b0000648117884a | ||
| 040 |
_aCaBNVSL _beng _erda _cCaBNVSL _dCaBNVSL |
||
| 050 | 4 |
_aTA169 _b.B38 2009eb |
|
| 050 | 4 |
_aTK5102.5 _b.B38 2009eb |
|
| 082 | 0 | 4 |
_a620.00452 _222 |
| 100 | 1 |
_aBauer, Eric, _eauthor. _927333 |
|
| 245 | 1 | 0 |
_aPractical system reliability / _cEric Bauer, Xuemei Zhang, Douglas A. Kimber. |
| 264 | 1 |
_aPiscataway, New Jersey : _bIEEE Press, _cc2009. |
|
| 264 | 2 |
_a[Piscataqay, New Jersey] : _bIEEE Xplore, _c[2009] |
|
| 300 |
_a1 PDF (xiii, 287 pages) : _billustrations. |
||
| 336 |
_atext _2rdacontent |
||
| 337 |
_aelectronic _2isbdmedia |
||
| 338 |
_aonline resource _2rdacarrier |
||
| 504 | _aIncludes bibliographical references (p. 265-277) and index. | ||
| 505 | 0 | _aPreface -- Acknowledgments -- 1 Introduction -- 2 System Availability -- 2.1 Availability, Service and Elements -- 2.2 Classical View -- 2.3 Customers' View -- 2.4 Standards View -- 3 Conceptual Model of Reliability and Availability -- 3.1 Concept of Highly Available Systems -- 3.2 Conceptual Model of System Availability -- 3.3 Failures -- 3.4 Outage Resolution -- 3.5 Downtime Budgets -- 4 Why Availability Varies Between Customers -- 4.1 Causes of Variation in Outage Event Reporting -- 4.2 Causes of Variation in Outage Duration -- 5 Modeling Availability -- 5.1 Overview of Modeling Techniques -- 5.2 Modeling Definitions -- 5.3 Practical Modeling -- 5.4 Widget Example -- 5.5 Alignment with Industry Standards -- 6 Estimating Parameters and Availability from Field Data -- 6.1 Self-Maintaining Customers -- 6.2 Analyzing Field Outage Data -- 6.3 Analyzing Performance and Alarm Data -- 6.4 Coverage Factor and Failure Rate -- 6.5 Uncovered Failure Recovery Time -- 6.6 Covered Failure Detection and Recovery Time -- 7 Estimating Input Parameters from Lab Data -- 7.1 Hardware Failure Rate -- 7.2 Software Failure Rate -- 7.3 Coverage Factors -- 7.4 Timing Parameters -- 7.5 System-Level Parameters -- 8 Estimating Input Parameters in the Architecture/Design Stage -- 8.1 Hardware Parameters -- 8.2 System-Level Parameters -- 8.3 Sensitivity Analysis -- 9 Prediction Accuracy -- 9.1 How Much Field Data Is Enough? -- 9.2 How Does One Measure Sampling and Prediction Errors? -- 9.3 What Causes Prediction Errors? -- 10 Connecting the Dots -- 10.1 Set Availability Requirements -- 10.2 Incorporate Architectural and Design Techniques -- 10.3 Modeling to Verify Feasibility -- 10.4 Testing -- 10.5 Update Availability Prediction -- 10.6 Periodic Field Validation and Model Update -- 10.7 Building an Availability Roadmap -- 10.8 Reliability Report -- 11 Summary -- Appendix A System Reliability Report outline -- 1 Executive Summary -- 2 Reliability Requirements -- 3 Unplanned Downtime Model and Results. | |
| 505 | 8 | _aAnnex A Reliability Definitions -- Annex B References -- Annex C Markov Model State-Transition Diagrams -- Appendix B Reliability and Availability Theory -- 1 Reliability and Availability Definitions -- 2 Probability Distributions in Reliability Evaluation -- 3 Estimation of Confidence Intervals -- Appendix C Software Reliability Growth Models -- 1 Software Characteristic Models -- 2 Nonhomogeneous Poisson Process Models -- Appendix D Acronyms and Abbreviations -- Appendix E Bibliography -- Index -- About the Authors. | |
| 506 | 1 | _aRestricted to subscribers or individual electronic text purchasers. | |
| 520 | _aLearn how to model, predict, and manage system reliability/availability throughout the development life cycle Written by a panel of authors with a wealth of industry experience, the methods and concepts presented here give readers a solid understanding of modeling and managing system and software availability and reliability through the development of real applications and products. The modeling and prediction techniques and tools are customer-focused and data-driven, and are also aligned with industry standards (Telcordia, TL 9000, ISO, etc.). Readers will get a clear understanding about what real-world reliability and availability mean through step-by-step discussions of: . System availability. Conceptual model of reliability and availability. Why availability varies between customers. Modeling availability. Estimating parameters and availability from field data. Estimating input parameters from laboratory data. Estimating input parameters in the architecture/design stage. Prediction accuracy. Connecting the dots This book can be used by system architects, engineers, and developers to better understand and manage the reliability/availability of their products; quality engineers to grasp how software and hardware quality relate to system availability; and engineering students as part of a short course on system availability and software reliability. | ||
| 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 | _aHazards | ||
| 695 | _aISO standards | ||
| 695 | _aIncentive schemes | ||
| 695 | _aIndexes | ||
| 695 | _aMaintenance engineering | ||
| 695 | _aMarkov processes | ||
| 695 | _aMathematical model | ||
| 695 | _aMeasurement | ||
| 695 | _aMicroprogramming | ||
| 695 | _aModeling | ||
| 695 | _aOutages | ||
| 695 | _aParameter estimation | ||
| 695 | _aPower supplies | ||
| 695 | _aPredictive models | ||
| 695 | _aRandom variables | ||
| 695 | _aReliability | ||
| 695 | _aReliability engineering | ||
| 695 | _aReliability theory | ||
| 695 | _aSampling | ||
| 695 | _aSensitivity analysis | ||
| 695 | _aService management | ||
| 695 | _aSoftware | ||
| 695 | _aSoftware reliability | ||
| 695 | _aStability analysis | ||
| 695 | _aStandards | ||
| 695 | _aSystem-level design | ||
| 695 | _aTelecommunication network management | ||
| 695 | _aTelecommunication services | ||
| 695 | _aTerminology | ||
| 695 | _aTesting | ||
| 695 | _aTime factors | ||
| 695 | _aTransient analysis | ||
| 695 | _aAvailability | ||
| 695 | _aBibliographies | ||
| 695 | _aBiographies | ||
| 695 | _aBudgets | ||
| 695 | _aComplexity theory | ||
| 695 | _aComputational modeling | ||
| 695 | _aComputer architecture | ||
| 695 | _aDSL | ||
| 695 | _aData models | ||
| 695 | _aData processing | ||
| 695 | _aDebugging | ||
| 695 | _aDelay | ||
| 695 | _aDensity functional theory | ||
| 695 | _aDesign methodology | ||
| 695 | _aDetectors | ||
| 695 | _aEquations | ||
| 695 | _aError analysis | ||
| 695 | _aEvent reporting | ||
| 695 | _aFCC | ||
| 695 | _aFailure analysis | ||
| 695 | _aFault detection | ||
| 695 | _aFeeds | ||
| 695 | _aField results | ||
| 695 | _aHardware | ||
| 700 | 1 |
_aZhang, Xuemei. _4aut _927334 |
|
| 700 | 1 |
_aKimber, Douglas A. _4aut _927335 |
|
| 710 | 2 |
_aJohn Wiley & Sons, _epublisher. _96902 |
|
| 710 | 2 |
_aIEEE Xplore (Online service), _edistributor. _927336 |
|
| 776 | 0 | 8 |
_iPrint version: _z9780470408605 |
| 856 | 4 | 2 |
_3Abstract with links to resource _uhttps://ieeexplore.ieee.org/xpl/bkabstractplus.jsp?bkn=5361030 |
| 942 | _cEBK | ||
| 999 |
_c74033 _d74033 |
||