Design for reliability: information and computer-based systems
"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...
Gespeichert in:
| 1. Verfasser: | |
|---|---|
| Format: | Buch |
| Sprache: | English |
| Veröffentlicht: |
Hoboken, NJ
Wiley
2010
Piscataway, NJ. IEEE Press |
| Schlagworte: | |
| Online-Zugang: | Inhaltsverzeichnis |
| Zusammenfassung: | "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"-- |
| Beschreibung: | Literaturverz. S. 317 - 318 |
| Beschreibung: | XXI, 325 S. Ill., graph. Darst. |
| ISBN: | 0470604654 9780470604656 |
Internformat
MARC
| LEADER | 00000nam a2200000 c 4500 | ||
|---|---|---|---|
| 001 | BV036966872 | ||
| 003 | DE-604 | ||
| 005 | 20140328 | ||
| 007 | t | ||
| 008 | 110119s2010 ad|| |||| 00||| eng d | ||
| 010 | |a 2010028409 | ||
| 020 | |a 0470604654 |c hardback |9 0-470-60465-4 | ||
| 020 | |a 9780470604656 |c hardback |9 978-0-470-60465-6 | ||
| 035 | |a (OCoLC)698573942 | ||
| 035 | |a (DE-599)GBV632702656 | ||
| 040 | |a DE-604 |b ger | ||
| 041 | 0 | |a eng | |
| 049 | |a DE-473 | ||
| 084 | |a ST 233 |0 (DE-625)143620: |2 rvk | ||
| 100 | 1 | |a Bauer, Eric |e Verfasser |0 (DE-588)1026373336 |4 aut | |
| 245 | 1 | 0 | |a Design for reliability |b information and computer-based systems |c Eric Bauer |
| 264 | 1 | |a Hoboken, NJ |b Wiley |c 2010 | |
| 264 | 1 | |a Piscataway, NJ. |b IEEE Press | |
| 300 | |a XXI, 325 S. |b Ill., graph. Darst. | ||
| 336 | |b txt |2 rdacontent | ||
| 337 | |b n |2 rdamedia | ||
| 338 | |b nc |2 rdacarrier | ||
| 500 | |a Literaturverz. S. 317 - 318 | ||
| 520 | 1 | |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"-- | |
| 650 | 0 | 7 | |a Hardwareentwurf |0 (DE-588)4159103-3 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Zuverlässigkeit |0 (DE-588)4059245-5 |2 gnd |9 rswk-swf |
| 650 | 0 | 7 | |a Softwareentwicklung |0 (DE-588)4116522-6 |2 gnd |9 rswk-swf |
| 689 | 0 | 0 | |a Softwareentwicklung |0 (DE-588)4116522-6 |D s |
| 689 | 0 | 1 | |a Zuverlässigkeit |0 (DE-588)4059245-5 |D s |
| 689 | 0 | |5 DE-604 | |
| 689 | 1 | 0 | |a Hardwareentwurf |0 (DE-588)4159103-3 |D s |
| 689 | 1 | 1 | |a Zuverlässigkeit |0 (DE-588)4059245-5 |D s |
| 689 | 1 | |5 DE-604 | |
| 856 | 4 | 2 | |m Digitalisierung UB Bamberg |q application/pdf |u http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=020881660&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |3 Inhaltsverzeichnis |
| 999 | |a oai:aleph.bib-bvb.de:BVB01-020881660 | ||
Datensatz im Suchindex
| _version_ | 1804143694213808128 |
|---|---|
| adam_text | Contents
Figures
xiii
Tables
xv
Preface
xvii
Acknowledgments
xxi
Part One Reliability Basics
1.
Reliability and Availability Concepts
1.1
Reliability and Availability
3
1.2
Faults, Errors, and Failures
5
1.3
Error Severity
6
1.4
Failure Recovery
7
1.5
Highly Available Systems
9
1.6
Quantifying Availability
12
1.7
Outage Attributability
14
1.8
Hardware Reliability
16
1.9
Software Reliability
22
1.10
Problems
28
1.11
For Further Study
29
2.
System Basics
31
2.1
Hardware and Software
31
2.2
External Entities
35
2.3
System Management
37
2.4
System Outages
43
2.5
Service Quality
47
2.6
Total Cost of Ownership
49
2.7
Problems
56
vii
viii Contents
3.
What Can Go Wrong
57
3.1
Failures in the Real World
57
3.2
Eight-Ingredient Framework
59
3.3
Mapping Ingredients to Error Categories
63
3.4
Applying Error Categories
66
3.5
Error Category: Field-Replaceable Unit
(FRU)
Hardware
68
3.6
Error Category: Programming Errors
70
3.7
Error Category: Data Error
71
3.8
Error Category: Redundancy
73
3.9
Error Category: System Power
74
3.10
Error Category: Network
75
3.11
Error Category: Application Protocol
76
3.12
Error Category: Procedures
77
3.13
Summary
79
3.14
Problems
80
3.15
For Further Study
80
Part Two Reliability Concepts
4.
Failure Containment and Redundancy
85
4.1
Units of Design
85
4.2
Failure Recovery Groups
91
4.3
Redundancy
92
4.4
Summary
96
4.5
Problems
97
4.6
For Further Study
97
5.
Robust Design Principles
99
5.1
Robust Design Principles
99
5.2
Robust Protocols
101
5.3
Robust Concurrency Controls
103
5.4
Overload Control
103
5.5
Process, Resource, and Throughput Monitoring
108
5.6
Data Auditing
109
5.7
Fault Correlation
110
5.8
Failed Error Detection, Isolation, or Recovery 111
5.9
Geographic Redundancy
112
5.10
Security, Availability, and System Robustness
114
5.11
Procedural Considerations
119
5.12
Problems
130
5.13
For Further Study
130
Contents ix
6.
Error Detection
131
6.1
Detecting Field-Replaceable Unit
(FRU)
Hardware Faults
131
6.2
Detecting Programming and Data Faults
132
6.3
Detecting Redundancy Failures
134
6.4
Detecting Power Failures
139
6.5
Detecting Networking Failures
141
6.6
Detecting Application Protocol Failures
142
6.7
Detecting Procedural Failures
144
6.8
Problems
144
6.9
For Further Study
144
7.
Analyzing and Modeling Reliability and Robustness
145
7.1
Reliability Block Diagrams
145
7.2
Qualitative Model of Redundancy
147
7.3
Failure Mode and Effects Analysis
149
7.4
Availability Modeling
151
7.5
Planned Downtime
165
7.6
Problems
168
7.7
For Further Study
168
Part Three Design for Reliability
8.
Reliability Requirements
171
8.1
Background
171
8.2
Defining Service Outages
172
8.3
Service Availability Requirements
175
8.4
Detailed Service Availability Requirements
177
8.5
Service Reliability Requirements
180
8.6
Triangulating Reliability Requirements
181
8.7
Problems
182
9.
Reliability Analysis
185
9.1
Step
1:
Enumerate Recoverable Modules
186
9.2
Step
2:
Construct Reliability Block Diagrams
191
9.3
Step
3:
Characterize Impact of Recovery
193
9.4
Step
4:
Characterize Impact of Procedures
198
9.5
Step
5:
Audit Adequacy of Automatic Failure
Detection and Recovery
200
9.6
Step
6:
Consider Failures of Robustness Mechanisms
201
9.7
Step
7:
Prioritizing Gaps
202
9.8
Reliability of Sourced Modules and Components
202
9.9
Problems
206
χ
Contents
10.
Reliability Budgeting and Modeling
207
10.1
Downtime Categories
208
10.2
Service Downtime Budget
209
10.3
Availability Modeling
212
10.4
Update Downtime Budget
213
10.5
Robustness Latency Budgets
215
10.6
Problems
218
11.
Robustness and Stability Testing
219
11.1
Robustness Testing
219
11.2
Context of Robustness Testing
220
11.3
Factoring Robustness Testing
221
11.4
Robustness Testing in the Development Process
222
11.5
Robustness Testing Techniques
223
11.6
Selecting Robustness Test Cases
232
11.7
Analyzing Robustness Test Results
233
11.8
Stability Testing
234
11.9
Release Criteria
240
11.10
Problems
243
12.
Closing the Loop
245
12.1
Analyzing Field Outage Events
245
12.2
Reliability Roadmapping
255
12.3
Problems
260
13.
Design for Reliability Case Study
263
13.1
System Context
263
13.2
System Reliability Requirements
268
13.3
Reliability Analysis
270
13.4
Downtime Budgeting
283
13.5
Availability Modeling
284
13.6
Reliability Roadmap
286
13.7
Robustness Testing
287
13.8
Stability Testing
289
13.9
Reliability Review
290
13.10
Reliability Report
291
13.11
Release Criteria
292
13.12
Field Data Analysis
293
14.
Conclusion
295
14.1
Overview of Design for Reliability
295
14.2
Concluding Remarks
299
14.3
Problems
300
Contents xi
15. Appendix:
Assessing
Design
for Reliability Diligence
301
15.1
Assessment Methodology
302
15.2
Reliability Requirements
304
15.3
Reliability Analysis
306
15.4
Reliability Modeling and Budgeting
307
15.5
Robustness Testing
308
15.6
Stability Testing
310
15.7
Release Criteria
311
15.8
Field Availability
312
15.9
Reliability Roadmap
313
15.10
Hardware Reliability
313
Abbreviations
315
References
317
Photo Credits
319
About the Author
321
Index
323
|
| any_adam_object | 1 |
| author | Bauer, Eric |
| author_GND | (DE-588)1026373336 |
| author_facet | Bauer, Eric |
| author_role | aut |
| author_sort | Bauer, Eric |
| author_variant | e b eb |
| building | Verbundindex |
| bvnumber | BV036966872 |
| classification_rvk | ST 233 |
| ctrlnum | (OCoLC)698573942 (DE-599)GBV632702656 |
| discipline | Informatik |
| format | Book |
| fullrecord | <?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>02400nam a2200445 c 4500</leader><controlfield tag="001">BV036966872</controlfield><controlfield tag="003">DE-604</controlfield><controlfield tag="005">20140328 </controlfield><controlfield tag="007">t</controlfield><controlfield tag="008">110119s2010 ad|| |||| 00||| eng d</controlfield><datafield tag="010" ind1=" " ind2=" "><subfield code="a">2010028409</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">0470604654</subfield><subfield code="c">hardback</subfield><subfield code="9">0-470-60465-4</subfield></datafield><datafield tag="020" ind1=" " ind2=" "><subfield code="a">9780470604656</subfield><subfield code="c">hardback</subfield><subfield code="9">978-0-470-60465-6</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(OCoLC)698573942</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-599)GBV632702656</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-604</subfield><subfield code="b">ger</subfield></datafield><datafield tag="041" ind1="0" ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="049" ind1=" " ind2=" "><subfield code="a">DE-473</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">ST 233</subfield><subfield code="0">(DE-625)143620:</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Bauer, Eric</subfield><subfield code="e">Verfasser</subfield><subfield code="0">(DE-588)1026373336</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Design for reliability</subfield><subfield code="b">information and computer-based systems</subfield><subfield code="c">Eric Bauer</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Hoboken, NJ</subfield><subfield code="b">Wiley</subfield><subfield code="c">2010</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="a">Piscataway, NJ.</subfield><subfield code="b">IEEE Press</subfield></datafield><datafield tag="300" ind1=" " ind2=" "><subfield code="a">XXI, 325 S.</subfield><subfield code="b">Ill., graph. Darst.</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">Literaturverz. S. 317 - 318</subfield></datafield><datafield tag="520" ind1="1" ind2=" "><subfield code="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"--</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Hardwareentwurf</subfield><subfield code="0">(DE-588)4159103-3</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Zuverlässigkeit</subfield><subfield code="0">(DE-588)4059245-5</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="650" ind1="0" ind2="7"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="2">gnd</subfield><subfield code="9">rswk-swf</subfield></datafield><datafield tag="689" ind1="0" ind2="0"><subfield code="a">Softwareentwicklung</subfield><subfield code="0">(DE-588)4116522-6</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2="1"><subfield code="a">Zuverlässigkeit</subfield><subfield code="0">(DE-588)4059245-5</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="0" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="689" ind1="1" ind2="0"><subfield code="a">Hardwareentwurf</subfield><subfield code="0">(DE-588)4159103-3</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2="1"><subfield code="a">Zuverlässigkeit</subfield><subfield code="0">(DE-588)4059245-5</subfield><subfield code="D">s</subfield></datafield><datafield tag="689" ind1="1" ind2=" "><subfield code="5">DE-604</subfield></datafield><datafield tag="856" ind1="4" ind2="2"><subfield code="m">Digitalisierung UB Bamberg</subfield><subfield code="q">application/pdf</subfield><subfield code="u">http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=020881660&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA</subfield><subfield code="3">Inhaltsverzeichnis</subfield></datafield><datafield tag="999" ind1=" " ind2=" "><subfield code="a">oai:aleph.bib-bvb.de:BVB01-020881660</subfield></datafield></record></collection> |
| id | DE-604.BV036966872 |
| illustrated | Illustrated |
| indexdate | 2024-07-09T22:51:44Z |
| institution | BVB |
| isbn | 0470604654 9780470604656 |
| language | English |
| lccn | 2010028409 |
| oai_aleph_id | oai:aleph.bib-bvb.de:BVB01-020881660 |
| oclc_num | 698573942 |
| open_access_boolean | |
| owner | DE-473 DE-BY-UBG |
| owner_facet | DE-473 DE-BY-UBG |
| physical | XXI, 325 S. Ill., graph. Darst. |
| publishDate | 2010 |
| publishDateSearch | 2010 |
| publishDateSort | 2010 |
| publisher | Wiley IEEE Press |
| record_format | marc |
| spelling | Bauer, Eric Verfasser (DE-588)1026373336 aut Design for reliability information and computer-based systems Eric Bauer Hoboken, NJ Wiley 2010 Piscataway, NJ. IEEE Press XXI, 325 S. Ill., graph. Darst. txt rdacontent n rdamedia nc rdacarrier Literaturverz. S. 317 - 318 "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"-- Hardwareentwurf (DE-588)4159103-3 gnd rswk-swf Zuverlässigkeit (DE-588)4059245-5 gnd rswk-swf Softwareentwicklung (DE-588)4116522-6 gnd rswk-swf Softwareentwicklung (DE-588)4116522-6 s Zuverlässigkeit (DE-588)4059245-5 s DE-604 Hardwareentwurf (DE-588)4159103-3 s Digitalisierung UB Bamberg application/pdf http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=020881660&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA Inhaltsverzeichnis |
| spellingShingle | Bauer, Eric Design for reliability information and computer-based systems Hardwareentwurf (DE-588)4159103-3 gnd Zuverlässigkeit (DE-588)4059245-5 gnd Softwareentwicklung (DE-588)4116522-6 gnd |
| subject_GND | (DE-588)4159103-3 (DE-588)4059245-5 (DE-588)4116522-6 |
| title | Design for reliability information and computer-based systems |
| title_auth | Design for reliability information and computer-based systems |
| title_exact_search | Design for reliability information and computer-based systems |
| title_full | Design for reliability information and computer-based systems Eric Bauer |
| title_fullStr | Design for reliability information and computer-based systems Eric Bauer |
| title_full_unstemmed | Design for reliability information and computer-based systems Eric Bauer |
| title_short | Design for reliability |
| title_sort | design for reliability information and computer based systems |
| title_sub | information and computer-based systems |
| topic | Hardwareentwurf (DE-588)4159103-3 gnd Zuverlässigkeit (DE-588)4059245-5 gnd Softwareentwicklung (DE-588)4116522-6 gnd |
| topic_facet | Hardwareentwurf Zuverlässigkeit Softwareentwicklung |
| url | http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&local_base=BVB01&doc_number=020881660&sequence=000002&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA |
| work_keys_str_mv | AT bauereric designforreliabilityinformationandcomputerbasedsystems |