home libri books Fumetti ebook dvd top ten sconti 0 Carrello


Torna Indietro

hobbs chris - embedded software development for safety-critical systems

Embedded Software Development for Safety-Critical Systems




Disponibilità: Normalmente disponibile in 20 giorni
A causa di problematiche nell'approvvigionamento legate alla Brexit sono possibili ritardi nelle consegne.


PREZZO
156,98 €
NICEPRICE
149,13 €
SCONTO
5%



Questo prodotto usufruisce delle SPEDIZIONI GRATIS
selezionando l'opzione Corriere Veloce in fase di ordine.


Pagabile anche con Carta della cultura giovani e del merito, 18App Bonus Cultura e Carta del Docente


Facebook Twitter Aggiungi commento


Spese Gratis

Dettagli

Genere:Libro
Lingua: Inglese
Pubblicazione: 09/2015
Edizione: 1° edizione





Note Editore

"I highly recommend Mr. Hobbs' book." - Stephen Thomas, PE, Founder and Editor of FunctionalSafetyEngineer.com Safety-critical devices, whether medical, automotive, or industrial, are increasingly dependent on the correct operation of sophisticated software. Many standards have appeared in the last decade on how such systems should be designed and built. Developers, who previously only had to know how to program devices for their industry, must now understand remarkably esoteric development practices and be prepared to justify their work to external auditors. Embedded Software Development for Safety-Critical Systems discusses the development of safety-critical systems under the following standards: IEC 61508; ISO 26262; EN 50128; and IEC 62304. It details the advantages and disadvantages of many architectural and design practices recommended in the standards, ranging from replication and diversification, through anomaly detection to the so-called "safety bag" systems.Reviewing the use of open-source components in safety-critical systems, this book has evolved from a course text used by QNX Software Systems for a training module on building embedded software for safety-critical devices, including medical devices, railway systems, industrial systems, and driver assistance devices in cars. Although the book describes open-source tools for the most part, it also provides enough information for you to seek out commercial vendors if that’s the route you decide to pursue. All of the techniques described in this book may be further explored through hundreds of learned articles. In order to provide you with a way in, the author supplies references he has found helpful as a working software developer. Most of these references are available to download for free.




Sommario

SECTION I: BACKGROUNDIntroductionDependable, embedded software The safety culture Our path Choosing the techniques to describe The development approach Today's challenges References The Terminology of Safety General Safety Terminology Software-Specific Terminology ReferencesSafety Standards and CertificationThe standards bodies Accreditation and certification Why do we need these standards? Goal- and prescription-based standards Functional safety standards IEC 62304 and ISO 14971 Process and the standards Summary References Representative CompaniesAlpha Device CorpBeta Component Inc Using a Certified Component SECTION II: THE PROJECTThe Foundational Analyses The Analyses The inter-relationshipsThe hazard and risk analysis The safety case The failure analysis Analyses by the representative companies SummaryReferences Certified and Uncertified ComponentsSOUP by any other name Certified or uncertified SOUP Using non-certified componentsUsing a certified component Aligning release cycles The example companies SECTION III: ARCHITECTURAL PATTERNSArchitectural BalancingThe availability/reliability balance The usefulness/safety balanceThe security/performance/safety balance The performance/reliability balance The implementation balance SummaryReferencesError Detection and HandlingWhy detect errors? Error detection and the standardsAnomaly detection Rejuvenation Recovery blocks A note on the diverse monitorSummaryReferences Expecting the UnexpectedThe design safe state Recovery The crash-only model Anticipation of the unexpected by the example companies SummaryReferences Replication and Diversification History of replication and diversification Replication in the standards Component or system replication? ReplicationDiversification Virtual synchrony Locked-step processors Diverse monitorSummary References SECTION IV: DESIGN VALIDATIONMarkov Models Markov models Markov models and the standards The Markovian assumptionsAn example calculationMarkovian advantages and disadvantages ReferencesThe Fault TreeFTA and FMECA Fault tree analysis in the standards Types of fault treeExample 1: The Boolean fault tree Example 2: The extended Boolean fault tree Example 3: The Bayesian fault treeCombining FTAs FTA ToolsThe use of FTA References Software Failure Rates The underlying heresy Assessing failure rates Modelling the failures References Semi-Formal Design Verification Verification of a reconstructed design Discrete event simulation Timed Petri nets Simulation and our sample companies References Formal Design VerificationWhat are formal methods?History of formal methods Formal methods and the standards Do formal methods work?Types of formal methodsAutomatic code generation The Spin modelling system The Rodin modelling tool Our companies' use of Rodin and Spin Formal methods References SECTION V: CODINGCoding Guidelines Programming language selection Programming languages and the standards Language features Use of language subsets So what is the best programming language? ReferencesCode Coverage Metrics Code coverage testingTypes of code coverage Coverage and the standardsThe effectiveness of coverage testingAchieving coverage Combinatorial Testing Summary References Static AnalysisWhat static analysis is asked to do Static code analysis and the standards Static code analysis Symbolic execution Summary References SECTION VI: VERIFICATIONIntegration Testing Fault injection testing Back-to-back comparison test between model and code Requirements-based testing References The Tool ChainValidation of the tool chain Tool classification BCI's tools classification Using third-party tools Verifying the compiler ADC's and BCI's compiler verification References Conclusion Appendix A:Goal Structuring NotationBackground Example GSN or BBN? References Appendix B: Bayesian Belief Networks Frequentists and Bayesians Prior probabilities Bayes' theorem A Bayesian example What do the arrows mean in a BBN?BBNs in safety case arguments BBNs in fault trees BBN or GSN for a safety case? ReferencesAppendix C:Notations General symbols Pi and IpThe structure functionComponents in parallel and series Temporal logic Vector bases ReferencesIndex




Autore

Chris is a programmer at QNX Software Systems with some 40 years of software development experience. His specialty is "Sufficiently Dependable Software," which is software that meets its dependability requirements with the minimum development effort and risk. In particular, he works with software for safety-critical systems that must meet the requirements of international safety standards such as IEC61508, ISO26262, EN50128 and IEC62304. Outside his professional work as a software developer, Chris is the author of several books including "Flying Beyond: The Canadian Commercial Pilot Textbook" and "Embedded Software Development for Safety-Critical Systems."










Altre Informazioni

ISBN:

9781498726702

Condizione: Nuovo
Dimensioni: 9.25 x 6.25 in Ø 1.40 lb
Formato: Copertina rigida
Illustration Notes:67 b/w images and 11 tables
Pagine Arabe: 344
Pagine Romane: xx


Dicono di noi