{"text_format":"2","workbook":"xls","n_sheets":1,"sheets":["report2"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":1,"defined_names":1,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900","formulas":"cached_only"}

{"sheet":"report2","index":0,"n_rows":18,"n_cols":5,"rows_kept":18,"cut":false,"hidden":false,"merged":[[0,2,0,3],[0,4,0,5],[1,2,1,3],[1,4,1,5],[2,2,2,3],[2,4,2,5],[3,2,3,3],[4,2,4,3],[8,2,8,3],[9,2,9,3],[10,2,10,3],[11,2,11,3],[12,2,12,3],[16,2,16,3]],"flags":["formulas_cached_only"]}
[null,"1.","Record Nr.",null,"UNINA9910133450803321"]
[null,null,"Autore",null,"Bauer Eric"]
[null,null,"Titolo",null,"Design for reliability : information and computer-based systems / / Eric Bauer"]
[null,null,"Pubbl/distr/stampa",null,"Hoboken, N.J., : Wiley, : IEEE Press, c2010"]
[null,null,"ISBN",null,"1-283-03544-8"]
[{"$nulls":4},"9786613035448"]
[{"$nulls":4},"1-118-07508-0"]
[{"$nulls":4},"1-118-07510-2"]
[null,null,"Descrizione fisica",null,"1 online resource (349 p.)"]
[null,null,"Disciplina",null,"620/.00452"]
[null,null,"Soggetti",null,"Reliability (Engineering)"]
[null,null,"Lingua di pubblicazione",null,"Inglese"]
[null,null,"Formato",null,"Materiale a stampa"]
[null,null,null,"Livello bibliografico","Monografia"]
[null,null,null,"Note generali","Description based upon print version of record."]
[null,null,null,"Nota di bibliografia","Includes bibliographical references (p. 317-318) and index."]
[null,null,"Nota di contenuto",null,"pt. 1. Reliability basics -- pt. 2. Reliability concepts -- pt. 3. Design for reliability."]
[null,null,null,"Sommario/riassunto","\"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."]