Details

<b>Preface.</b> <p><b>Acknowledgments.</b></p> <p><b>1 Introduction.</b></p> <p><b>2 System Availability.</b></p> <p>2.1 Availability, Service and Elements.</p> <p>2.2 Classical View.</p> <p>2.3 Customers’ View.</p> <p>2.4 Standards View.</p> <p><b>3 Conceptual Model of Reliability and Availability.</b></p> <p>3.1 Concept of Highly Available Systems.</p> <p>3.2 Conceptual Model of System Availability.</p> <p>3.3 Failures.</p> <p>3.4 Outage Resolution.</p> <p>3.5 Downtime Budgets.</p> <p><b>4 Why Availability Varies Between Customers.</b></p> <p>4.1 Causes of Variation in Outage Event Reporting.</p> <p>4.2 Causes of Variation in Outage Duration.</p> <p><b>5 Modeling Availability.</b></p> <p>5.1 Overview of Modeling Techniques.</p> <p>5.2 Modeling Definitions.</p> <p>5.3 Practical Modeling.</p> <p>5.4 Widget Example.</p> <p>5.5 Alignment with Industry Standards.</p> <p><b>6 Estimating Parameters and Availability from Field Data.</b></p> <p>6.1 Self-Maintaining Customers.</p> <p>6.2 Analyzing Field Outage Data.</p> <p>6.3 Analyzing Performance and Alarm Data.</p> <p>6.4 Coverage Factor and Failure Rate.</p> <p>6.5 Uncovered Failure Recovery Time.</p> <p>6.6 Covered Failure Detection and Recovery Time.</p> <p><b>7 Estimating Input Parameters from Lab Data.</b></p> <p>7.1 Hardware Failure Rate.</p> <p>7.2 Software Failure Rate.</p> <p>7.3 Coverage Factors.</p> <p>7.4 Timing Parameters.</p> <p>7.5 System-Level Parameters.</p> <p><b>8 Estimating Input Parameters in the Architecture/Design Stage.</b></p> <p>8.1 Hardware Parameters.</p> <p>8.2 System-Level Parameters.</p> <p>8.3 Sensitivity Analysis.</p> <p><b>9 Prediction Accuracy.</b></p> <p>9.1 How Much Field Data Is Enough?</p> <p>9.2 How Does One Measure Sampling and Prediction Errors?</p> <p>9.3 What Causes Prediction Errors?</p> <p><b>10 Connecting the Dots.</b></p> <p>10.1 Set Availability Requirements.</p> <p>10.2 Incorporate Architectural and Design Techniques.</p> <p>10.3 Modeling to Verify Feasibility.</p> <p>10.4 Testing.</p> <p>10.5 Update Availability Prediction.</p> <p>10.6 Periodic Field Validation and Model Update.</p> <p>10.7 Building an Availability Roadmap.</p> <p>10.8 Reliability Report.</p> <p><b>11 Summary.</b></p> <p><b>Appendix A System Reliability Report outline.</b></p> <p>1 Executive Summary.</p> <p>2 Reliability Requirements.</p> <p>3 Unplanned Downtime Model and Results.</p> <p>Annex A Reliability Definitions.</p> <p>Annex B References.</p> <p>Annex C Markov Model State-Transition Diagrams.</p> <p><b>Appendix B Reliability and Availability Theory.</b></p> <p>1 Reliability and Availability Definitions.</p> <p>2 Probability Distributions in Reliability Evaluation.</p> <p>3 Estimation of Confidence Intervals.</p> <p><b>Appendix C Software Reliability Growth Models.</b></p> <p>1 Software Characteristic Models.</p> <p>2 Nonhomogeneous Poisson Process Models.</p> <p><b>Appendix D Acronyms and Abbreviations.</b></p> <p><b>Appendix E Bibliography.</b></p> <p><b>Index.</b></p> <p><b>About the Authors.</b></p>

<b>Eric Bauer</b> is a manager of reliability engineering in Alcatel-Lucent's wireline business in Murray Hill, New Jersey. He has designed, modeled, and analyzed reliability for many different products and solutions, and architected and developed software for a variety of communications devices, platforms, and products. <p><b>Xuemei Zhang, PhD</b>, is a principal member of the technical staff in the Network Design and Performance Analysis Department at AT&T Labs. She has been working on reliability and performance analysis of wireline and wireless communications systems and networks. Her major work and research areas are in system and architectural reliability and performance, product and solution reliability and performance modeling, and software reliability.</p> <p><b>Douglas A. Kimber</b> retired from Alcatel-Lucent as a staff reliability engineer. Throughout his career at Bell Labs, Lucent Technologies, and Alcatel-Lucent, he developed high reliability hardware and software platforms, applications, and systems, and then transitioned to reliability engineering where he did reliability modeling and analysis.</p>

<b>Learn how to model, predict, and manage system reliability/availability throughout the development life cycle</b> <p>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:</p> <ul> <li>System availability</li> <li>Conceptual model of reliability and availability</li> <li>Why availability varies between customers</li> <li>Modeling availability</li> <li>Estimating parameters and availability from field data</li> <li>Estimating input parameters from laboratory data</li> <li>Estimating input parameters in the architecture/design stage</li> <li>Prediction accuracy</li> <li>Connecting the dots</li> </ul> <p>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.</p>

US