Design for Reliability Information and Computer-Based Systems

by Bauer, Eric

• ISBN13: 9780470604656
• ISBN10: 0470604654
• Edition: 1st
• Format: Hardcover
• Copyright: 2010-10-04
• Publisher: Wiley-IEEE Press

Summary

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.

Author Biography

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.

Table of Contents

Figures	p. xiii
Tables	p. xv
Preface	p. xvii
Acknowledgments	p. xxi
Reliability Basics
Reliability and Availability Concepts	p. 3
Reliability and Availability	p. 3
Faults, Errors, and Failures	p. 5
Error Severity	p. 6
Failure Recovery	p. 7
Highly Available Systems	p. 9
Quantifying Availability	p. 12
Outage Attributability	p. 14
Hardware Reliability	p. 16
Software Reliability	p. 22
Problems	p. 28
For Further Study	p. 29
System Basics	p. 31
Hardware and Software	p. 31
External Entities	p. 35
System Management	p. 37
System Outages	p. 43
Service Quality	p. 47
Total Cost of Ownership	p. 49
Problems	p. 56
What Can Go Wrong	p. 57
Failures in the Real World	p. 57
Eight-Ingredient Framework	p. 59
Mapping Ingredients to Error Categories	p. 63
Applying Error Categories	p. 66
Error Category: Field-Replaceable Unit (FRU) Hardware	p. 68
Error Category: Programming Errors	p. 70
Error Category: Data Error	p. 71
Error Category: Redundancy	p. 73
Error Category: System Power	p. 74
Error Category: Network	p. 75
Error Category: Application Protocol	p. 76
Error Category: Procedures	p. 77
Summary	p. 79
Problems	p. 80
For Further Study	p. 80
Reliability Concepts
Failure Containment and Redundancy	p. 85
Units of Design	p. 85
Failure Recovery Groups	p. 91
Redundancy	p. 92
Summary	p. 96
Problems	p. 97
For Further Study	p. 97
Robust Design Principles	p. 99
Robust Design Principles	p. 99
Robust Protocols	p. 101
Robust Concurrency Controls	p. 103
Overload Control	p. 103
Process, Resource, and Throughput Monitoring	p. 108
Data Auditing	p. 109
Fault Correlation	p. 110
Failed Error Detection, Isolation, or Recovery	p. 111
Geographic Redundancy	p. 112
Security, Availability, and System Robustness	p. 114
Procedural Considerations	p. 119
Problems	p. 130
For Further Study	p. 130
Error Detection	p. 131
Detecting Field-Replaceable Unit (FRU) Hardware Faults	p. 131
Detecting Programming and Data Faults	p. 132
Detecting Redundancy Failures	p. 134
Detecting Power Failures	p. 139
Detecting Networking Failures	p. 141
Detecting Application Protocol Failures	p. 142
Detecting Procedural Failures	p. 144
Problems	p. 144
For Further Study	p. 144
Analyzing and Modeling Reliability and Robustness	p. 145
Reliability Block Diagrams	p. 145
Qualitative Model of Redundancy	p. 147
Failure Mode and Effects Analysis	p. 149
Availability Modeling	p. 151
Planned Downtime	p. 165
Problems	p. 168
For Further Study	p. 168
Design for Reliability
Reliability Requirements	p. 171
Background	p. 171
Defining Service Outages	p. 172
Service Availability Requirements	p. 175
Detailed Service Availability Requirements	p. 177
Service Reliability Requirements	p. 180
Triangulating Reliability Requirements	p. 181
Problems	p. 182
Reliability Analysis	p. 185
Step 1: Enumerate Recoverable Modules	p. 186
Step 2: Construct Reliability Block Diagrams	p. 191
Step 3: Characterize Impact of Recovery	p. 193
Step 4: Characterize Impact of Procedures	p. 198
Step 5: Audit Adequacy of Automatic Failure Detection and Recovery	p. 200
Step 6: Consider Failures of Robustness Mechanisms	p. 201
Step 7: Prioritizing Gaps	p. 202
Reliability of Sourced Modules and Components	p. 202
Problems	p. 206
Reliability Budgeting and Modeling	p. 207
Downtime Categories	p. 208
Service Downtime Budget	p. 209
Availability Modeling	p. 212
Update Downtime Budget	p. 213
Robustness Latency Budgets	p. 215
Problems	p. 218
Robustness and Stability Testing	p. 219
Robustness Testing	p. 219
Context of Robustness Testing	p. 220
Factoring Robustness Testing	p. 221
Robustness Testing in the Development Process	p. 222
Robustness Testing Techniques	p. 223
Selecting Robustness Test Cases	p. 232
Analyzing Robustness Test Results	p. 233
Stability Testing	p. 234
Release Criteria	p. 240
Problems	p. 243
Closing the Loop	p. 245
Analyzing Field Outage Events	p. 245
Reliability Roadmapping	p. 255
Problems	p. 260
Design for Reliability Case Study	p. 263
System Context	p. 263
System Reliability Requirements	p. 268
Reliability Analysis	p. 270
Downtime Budgeting	p. 283
Availability Modeling	p. 284
Reliability Roadmap	p. 286
Robustness Testing	p. 287
Stability Testing	p. 289
Reliability Review	p. 290
Reliability Report	p. 291
Release Criteria	p. 292
Field Data Analysis	p. 293
Conclusion	p. 295
Overview of Design for Reliability	p. 295
Concluding Remarks	p. 299
Problems	p. 300
Appendix: Assessing Design for Reliability Diligence	p. 301
Assessment Methodology	p. 302
Reliability Requirements	p. 304
Reliability Analysis	p. 306
Reliability Modeling and Budgeting	p. 307
Robustness Testing	p. 308
Stability Testing	p. 310
Release Criteria	p. 311
Field Availability	p. 312
Reliability Roadmap	p. 313
Hardware Reliability	p. 313
Abbreviations	p. 315
References	p. 317
Photo Credits	p. 319
About the Author	p. 321
Index	p. 323
Table of Contents provided by Ingram. All Rights Reserved.