Design for reliability : (Record no. 74114)
[ view plain ]
| 000 -LEADER | |
|---|---|
| fixed length control field | 04964nam a2201213 i 4500 |
| 001 - CONTROL NUMBER | |
| control field | 5732779 |
| 005 - DATE AND TIME OF LATEST TRANSACTION | |
| control field | 20220712205753.0 |
| 008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION | |
| fixed length control field | 151221s2011 njua ob 001 eng d |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| ISBN | 9781118075104 |
| -- | ebook |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| -- | hardback |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| -- | hardback |
| 020 ## - INTERNATIONAL STANDARD BOOK NUMBER | |
| -- | electronic |
| 100 1# - AUTHOR NAME | |
| Author | Bauer, Eric, |
| 245 10 - TITLE STATEMENT | |
| Title | Design for reliability : |
| Sub Title | information and computer-based systems / |
| 300 ## - PHYSICAL DESCRIPTION | |
| Number of Pages | 1 PDF (xxi, 325 pages) : |
| 505 0# - FORMATTED CONTENTS NOTE | |
| Remark 2 | Frontmatter -- Reliability Basics. Reliability and Availability Concepts -- System Basics -- What can go Wrong -- Reliability Concepts. Failure Containment and Redundancy -- Robust Design Principles -- Error Detection -- Analyzing and Modeling Reliability and Robustness -- Design for Reliability. Reliability Requirements -- Reliability Analysis -- Reliability Budgeting and Modeling -- Robustness and Stability Testing -- Closing the Loop -- Design for Reliability Case Study -- Conclusion -- Appendix: Assessing Design for Reliability Diligence -- Abbreviations -- References -- Photo Credits -- About the Author -- Index. |
| 520 ## - SUMMARY, ETC. | |
| Summary, etc | "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"--Provided by publisher. |
| 650 #0 - SUBJECT ADDED ENTRY--SUBJECT 1 | |
| Subject | Reliability (Engineering) |
| 856 42 - ELECTRONIC LOCATION AND ACCESS | |
| Uniform Resource Identifier | https://ieeexplore.ieee.org/xpl/bkabstractplus.jsp?bkn=5732779 |
| 942 ## - ADDED ENTRY ELEMENTS (KOHA) | |
| Koha item type | eBooks |
| 264 #1 - | |
| -- | Hoboken, New Jersey : |
| -- | Wiley-IEEE Press, |
| -- | c2010. |
| 264 #2 - | |
| -- | [Piscataqay, New Jersey] : |
| -- | IEEE Xplore, |
| -- | [2011] |
| 336 ## - | |
| -- | text |
| -- | rdacontent |
| 337 ## - | |
| -- | electronic |
| -- | isbdmedia |
| 338 ## - | |
| -- | online resource |
| -- | rdacarrier |
| 588 ## - | |
| -- | Description based on PDF viewed 12/21/2015. |
| 695 ## - | |
| -- | Aerospace electronics |
| 695 ## - | |
| -- | Analytical models |
| 695 ## - | |
| -- | Application software |
| 695 ## - | |
| -- | Availability |
| 695 ## - | |
| -- | Backplanes |
| 695 ## - | |
| -- | Best practices |
| 695 ## - | |
| -- | Bibliographies |
| 695 ## - | |
| -- | Biographies |
| 695 ## - | |
| -- | Block diagrams |
| 695 ## - | |
| -- | Budgets |
| 695 ## - | |
| -- | Business |
| 695 ## - | |
| -- | Circuit faults |
| 695 ## - | |
| -- | Computational modeling |
| 695 ## - | |
| -- | Computer architecture |
| 695 ## - | |
| -- | Concurrency control |
| 695 ## - | |
| -- | Context awareness |
| 695 ## - | |
| -- | Data processing |
| 695 ## - | |
| -- | Data structures |
| 695 ## - | |
| -- | Design methodology |
| 695 ## - | |
| -- | Downtime |
| 695 ## - | |
| -- | Electron microscopy |
| 695 ## - | |
| -- | Error analysis |
| 695 ## - | |
| -- | Failure analysis |
| 695 ## - | |
| -- | Fault diagnosis |
| 695 ## - | |
| -- | Field outages |
| 695 ## - | |
| -- | Hard disks |
| 695 ## - | |
| -- | Hardware |
| 695 ## - | |
| -- | Human factors |
| 695 ## - | |
| -- | Indexes |
| 695 ## - | |
| -- | Instant messaging |
| 695 ## - | |
| -- | Load management |
| 695 ## - | |
| -- | Maintenance engineering |
| 695 ## - | |
| -- | Markov processes |
| 695 ## - | |
| -- | Modeling |
| 695 ## - | |
| -- | Monitoring |
| 695 ## - | |
| -- | Network management |
| 695 ## - | |
| -- | Outages |
| 695 ## - | |
| -- | Performance evaluation |
| 695 ## - | |
| -- | Photography |
| 695 ## - | |
| -- | Power distribution |
| 695 ## - | |
| -- | Process control |
| 695 ## - | |
| -- | Programming |
| 695 ## - | |
| -- | Protocols |
| 695 ## - | |
| -- | Real time systems |
| 695 ## - | |
| -- | Redundancy |
| 695 ## - | |
| -- | Reliability |
| 695 ## - | |
| -- | Reliability engineering |
| 695 ## - | |
| -- | Robustness |
| 695 ## - | |
| -- | Security |
| 695 ## - | |
| -- | Servers |
| 695 ## - | |
| -- | Service management |
| 695 ## - | |
| -- | Software |
| 695 ## - | |
| -- | Software modeling |
| 695 ## - | |
| -- | Software reliability |
| 695 ## - | |
| -- | Software testing |
| 695 ## - | |
| -- | Stability analysis |
| 695 ## - | |
| -- | Switches |
| 695 ## - | |
| -- | Telecommunication network management |
| 695 ## - | |
| -- | Terminology |
| 695 ## - | |
| -- | Testing |
| 695 ## - | |
| -- | Throughput |
No items available.