| 000 | 01594nam a2200253 a 4500 | ||
|---|---|---|---|
| 001 | vtls000051905 | ||
| 003 | KUKTEM | ||
| 005 | 20251117150459.0 | ||
| 008 | 110314t2010 njua f b 001 0 eng d | ||
| 020 | _a9780470604656 (hardback) | ||
| 020 | _a0470604654 (hardback) | ||
| 039 | 9 |
_a201312261432 _bjamie _c201109280858 _dfauzi _c201107140038 _dVLOAD _y201103141203 _zirma |
|
| 040 | _aUMP | ||
| 090 | _aTA169 .B38 2010 | ||
| 100 | 1 | _aBauer, Eric | |
| 245 | 1 | 0 |
_aDesign for reliability : _binformation and computer-based systems / _cEric Bauer |
| 260 |
_aHoboken, N. J. : _bWiley-IEEE Press, _cc2010 |
||
| 300 |
_axxi, 325 p. : _bill. ; _c25 cm. |
||
| 504 | _aIncludes bibliographical references and index | ||
| 520 | _aSystem 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 | _aReliability (Engineering) | |
| 999 |
_aVIRTUA40 _c59189 _d59195 |
||
| 999 | _aVTLSSORT0080*0200*0201*0400*0900*1000*2450*2600*3000*5040*5200*6500*9992 | ||
| 942 | 0 | 0 | _0180 |