Descripciones mejoradas de Syndetics:

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.

Tabla de contenidos provista por Syndetics

• Figures(p. xiii)
• Tables(p. xv)
• Preface(p. xvii)
• Acknowledgments(p. xxi)
• Part 1 Reliability Basics
• 1 Reliability and Availability Concepts(p. 3)
• 1.1 Reliability and Availability(p. 3)
• 1.2 Faults, Errors, and Failures(p. 5)
• 1.3 Error Severity(p. 6)
• 1.4 Failure Recovery(p. 7)
• 1.5 Highly Available Systems(p. 9)
• 1.6 Quantifying Availability(p. 12)
• 1.7 Outage Attributability(p. 14)
• 1.8 Hardware Reliability(p. 16)
• 1.9 Software Reliability(p. 22)
• 1.10 Problems(p. 28)
• 1.11 For Further Study(p. 29)
• 2 System Basics(p. 31)
• 2.1 Hardware and Software(p. 31)
• 2.2 External Entities(p. 35)
• 2.3 System Management(p. 37)
• 2.4 System Outages(p. 43)
• 2.5 Service Quality(p. 47)
• 2.6 Total Cost of Ownership(p. 49)
• 2.7 Problems(p. 56)
• 3 What Can Go Wrong(p. 57)
• 3.1 Failures in the Real World(p. 57)
• 3.2 Eight-Ingredient Framework(p. 59)
• 3.3 Mapping Ingredients to Error Categories(p. 63)
• 3.4 Applying Error Categories(p. 66)
• 3.5 Error Category: Field-Replaceable Unit (FRU) Hardware(p. 68)
• 3.6 Error Category: Programming Errors(p. 70)
• 3.7 Error Category: Data Error(p. 71)
• 3.8 Error Category: Redundancy(p. 73)
• 3.9 Error Category: System Power(p. 74)
• 3.10 Error Category: Network(p. 75)
• 3.11 Error Category: Application Protocol(p. 76)
• 3.12 Error Category: Procedures(p. 77)
• 3.13 Summary(p. 79)
• 3.14 Problems(p. 80)
• 3.15 For Further Study(p. 80)
• Part 2 Reliability Concepts
• 4 Failure Containment and Redundancy(p. 85)
• 4.1 Units of Design(p. 85)
• 4.2 Failure Recovery Groups(p. 91)
• 4.3 Redundancy(p. 92)
• 4.4 Summary(p. 96)
• 4.5 Problems(p. 97)
• 4.6 For Further Study(p. 97)
• 5 Robust Design Principles(p. 99)
• 5.1 Robust Design Principles(p. 99)
• 5.2 Robust Protocols(p. 101)
• 5.3 Robust Concurrency Controls(p. 103)
• 5.4 Overload Control(p. 103)
• 5.5 Process, Resource, and Throughput Monitoring(p. 108)
• 5.6 Data Auditing(p. 109)
• 5.7 Fault Correlation(p. 110)
• 5.8 Failed Error Detection, Isolation, or Recovery(p. 111)
• 5.9 Geographic Redundancy(p. 112)
• 5.10 Security, Availability, and System Robustness(p. 114)
• 5.11 Procedural Considerations(p. 119)
• 5.12 Problems(p. 130)
• 5.13 For Further Study(p. 130)
• 6 Error Detection(p. 131)
• 6.1 Detecting Field-Replaceable Unit (FRU) Hardware Faults(p. 131)
• 6.2 Detecting Programming and Data Faults(p. 132)
• 6.3 Detecting Redundancy Failures(p. 134)
• 6.4 Detecting Power Failures(p. 139)
• 6.5 Detecting Networking Failures(p. 141)
• 6.6 Detecting Application Protocol Failures(p. 142)
• 6.7 Detecting Procedural Failures(p. 144)
• 6.8 Problems(p. 144)
• 6.9 For Further Study(p. 144)
• 7 Analyzing and Modeling Reliability and Robustness(p. 145)
• 7.1 Reliability Block Diagrams(p. 145)
• 7.2 Qualitative Model of Redundancy(p. 147)
• 7.3 Failure Mode and Effects Analysis(p. 149)
• 7.4 Availability Modeling(p. 151)
• 7.5 Planned Downtime(p. 165)
• 7.6 Problems(p. 168)
• 7.7 For Further Study(p. 168)
• Part 3 Design for Reliability
• 8 Reliability Requirements(p. 171)
• 8.1 Background(p. 171)
• 8.2 Defining Service Outages(p. 172)
• 8.3 Service Availability Requirements(p. 175)
• 8.4 Detailed Service Availability Requirements(p. 177)
• 8.5 Service Reliability Requirements(p. 180)
• 8.6 Triangulating Reliability Requirements(p. 181)
• 8.7 Problems(p. 182)
• 9 Reliability Analysis(p. 185)
• 9.1 Step 1: Enumerate Recoverable Modules(p. 186)
• 9.2 Step 2: Construct Reliability Block Diagrams(p. 191)
• 9.3 Step 3: Characterize Impact of Recovery(p. 193)
• 9.4 Step 4: Characterize Impact of Procedures(p. 198)
• 9.5 Step 5: Audit Adequacy of Automatic Failure Detection and Recovery(p. 200)
• 9.6 Step 6: Consider Failures of Robustness Mechanisms(p. 201)
• 9.7 Step 7: Prioritizing Gaps(p. 202)
• 9.8 Reliability of Sourced Modules and Components(p. 202)
• 9.9 Problems(p. 206)
• 10 Reliability Budgeting and Modeling(p. 207)
• 10.1 Downtime Categories(p. 208)
• 10.2 Service Downtime Budget(p. 209)
• 10.3 Availability Modeling(p. 212)
• 10.4 Update Downtime Budget(p. 213)
• 10.5 Robustness Latency Budgets(p. 215)
• 10.6 Problems(p. 218)
• 11 Robustness and Stability Testing(p. 219)
• 11.1 Robustness Testing(p. 219)
• 11.2 Context of Robustness Testing(p. 220)
• 11.3 Factoring Robustness Testing(p. 221)
• 11.4 Robustness Testing in the Development Process(p. 222)
• 11.5 Robustness Testing Techniques(p. 223)
• 11.6 Selecting Robustness Test Cases(p. 232)
• 11.7 Analyzing Robustness Test Results(p. 233)
• 11.8 Stability Testing(p. 234)
• 11.9 Release Criteria(p. 240)
• 11.10 Problems(p. 243)
• 12 Closing the Loop(p. 245)
• 12.1 Analyzing Field Outage Events(p. 245)
• 12.2 Reliability Roadmapping(p. 255)
• 12.3 Problems(p. 260)
• 13 Design for Reliability Case Study(p. 263)
• 13.1 System Context(p. 263)
• 13.2 System Reliability Requirements(p. 268)
• 13.3 Reliability Analysis(p. 270)
• 13.4 Downtime Budgeting(p. 283)
• 13.5 Availability Modeling(p. 284)
• 13.6 Reliability Roadmap(p. 286)
• 13.7 Robustness Testing(p. 287)
• 13.8 Stability Testing(p. 289)
• 13.9 Reliability Review(p. 290)
• 13.10 Reliability Report(p. 291)
• 13.11 Release Criteria(p. 292)
• 13.12 Field Data Analysis(p. 293)
• 14 Conclusion(p. 295)
• 14.1 Overview of Design for Reliability(p. 295)
• 14.2 Concluding Remarks(p. 299)
• 14.3 Problems(p. 300)
• 15 Appendix: Assessing Design for Reliability Diligence(p. 301)
• 15.1 Assessment Methodology(p. 302)
• 15.2 Reliability Requirements(p. 304)
• 15.3 Reliability Analysis(p. 306)
• 15.4 Reliability Modeling and Budgeting(p. 307)
• 15.5 Robustness Testing(p. 308)
• 15.6 Stability Testing(p. 310)
• 15.7 Release Criteria(p. 311)
• 15.8 Field Availability(p. 312)
• 15.9 Reliability Roadmap(p. 313)
• 15.10 Hardware Reliability(p. 313)
• Abbreviations(p. 315)
• References(p. 317)
• Photo Credits(p. 319)
• About the Author(p. 321)
• Index(p. 323)

Notas de autor provistas por Syndetics

Eric Bauer is Reliability Engineering Manager in the Wireline Division of Alcatel-Lucent. After two decades of software development experience, he joined the Lucent reliability team to lead a reliability group, and has since worked reliability engineering on a variety of wireless and wireline products and solutions. Mr. Bauer currently focuses on increasing the reliability of Alcatel-Lucent's IP Multimedia Subsystem (IMS) solution and the network elements that comprise the IMS solution. He has been awarded twelve U.S. patents, coauthored Practical System Reliability (Wiley), and has published several papers in the Bell Labs Technical Journal.