LEADER 05829nam 2200769 a 450 001 9911004776103321 005 20200520144314.0 010 $a9786612618529 010 $a9781282618527 010 $a1282618520 010 $a9780080942551 010 $a0080942555 035 $a(CKB)2540000000000009 035 $a(EBL)583356 035 $a(OCoLC)700688937 035 $a(SSID)ssj0000332032 035 $a(PQKBManifestationID)12082718 035 $a(PQKBTitleCode)TC0000332032 035 $a(PQKBWorkID)10333220 035 $a(PQKB)11400962 035 $a(MiAaPQ)EBC583356 035 $a(PPN)170602605 035 $a(OCoLC)801817396 035 $a(OCoLC)ocn801817396 035 $a(FR-PaCSA)88812143 035 $a(CaSebORM)9780750685672 035 $a(FRCYB88812143)88812143 035 $a(EXLCZ)992540000000000009 100 $a20091006d2010 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 00$aMission-critical and safety-critical systems handbook $edesign and development for embedded applications /$fedited by Kim Fowler ; technical consultant, Sharfus Draid, Inc 205 $a1st edition 210 $aAmsterdam ;$aBoston $cNewnes, an imprint of Elsevier$dc2010 215 $a1 online resource (593 p.) 300 $aDescription based upon print version of record. 311 08$a9780750685672 311 08$a0750685670 320 $aIncludes bibliographical references and index. 327 $aFront Cover; Mission-Critical and Safety-Critical Systems Handbook: Design and Development for Embedded Applications; Copyright Page; Contents; About the Editor; About the Contributors; Chapter 1: Best Practices in Mission-Assured, Mission-Critical, and Safety-Critical Systems; 1. Roadmap to This Book; 1.1. Systems Engineering; 1.2. Important Issues; 1.3. Material Covered; 2. Best Practices; 2.1. What and Why?; 2.2. Rationale; 2.3. Standards and Guidelines for a QMS; 3. Project Management and Systems Engineering; 3.1. Project Management; 3.2. Systems Engineering; 3.3. Mission Assurance 327 $a4. Process Flows for Developing Products4.1. Plan, Execute, Review, Report, and Update (PERRU); 4.2. Development Processes; 4.3. Processes vs. Procedures; 4.4. General Process Models; 4.5. An Example of Phases, Processes, and Procedures; 5. Standards; 5.1. General Standards Organizations; 5.2. Industry-Based Standards Organizations; 5.3. Military Standards Organizations; 5.4. Aviation and Aerospace Standards Organizations; 6. Potential Procedures, Checklists, and Documents; 7. Review of Procedures and Processes; 7.1. Difference between Procedures and Processes 327 $a7.2. Why Review Procedures and Processes?7.3. Types of Review; 7.4. Frequency of Review; 7.5. Review Content; 7.6. Course of Action, Changes, and Updates Following Review; 7.7. Review Responsibilities; 8. Configuration Management; 8.1. Rationale for Configuration Management; 8.2. Configuration Management Coverage; 8.3. Records Responsibility; 8.4. System and Location; 8.5. Version Control; 8.6. Design Repository; 8.7. File Structure; 8.8. Obsolete Documents; 8.9. Training for Use of the System; 9. Documentation; 9.1. Rationale for Documentation 327 $a9.2. Coverage and Responsibility for Documentation9.3. Types of Documentation; 9.4. Best Practices for Documentation; References; Appendix A: Example Document Outlines; Work Order (WO); Minutes; Problem Report/Corrective Action (PRCA); Engineering Change Request (ECR); Engineering Change Notice (ECN); Project Management Plan (PMP); Interface Control Documents (ICDs); Development Plans; Requirements; Risk Management Plan; Configuration Management Plan; Documentation Plan; Analysis Reports; Design Description; Test Plan; Operation Plan; Metrology Concerns and Procedures 327 $aAppendix B: Program Management Documents for Project DevelopmentAppendix C: Technical Project Documents for Project Development; Chapter 2: Failsafe Software Design: Embedded Programming in a Fail-Certain World; 1. Software Matters; 2. The Essence of Process; 3. Three Principles for Design and Coding; 3.1. What Does It Mean to Be Failsafe?; 3.2. Safety (and Mission) First; 3.3. Verification and Redundancy in the Implementation Process; 4. The User Interface; 5. Rolling Your Own; 6. Hardware as Software: A Thought Exercise in Crossover Thinking; 7. Conclusions 327 $aChapter 3: Compliance Concerns for Medical Equipment 330 $a This handbook provides a consolidated, comprehensive information resource for engineers working with mission and safety critical systems. Principles, regulations, and processes common to all critical design projects are introduced in the opening chapters. Expert contributors then offer development models, process templates, and documentation guidelines from their own core critical applications fields: medical, aerospace, and military. Readers will gain in-depth knowledge of how to avoid common pitfalls and meet even the strictest certification standards. Particular emphasis is placed 606 $aReliability (Engineering) 606 $aFault tolerance (Engineering) 606 $aEmbedded computer systems$xDesign and construction 606 $aSafety factor in engineering 615 0$aReliability (Engineering) 615 0$aFault tolerance (Engineering) 615 0$aEmbedded computer systems$xDesign and construction. 615 0$aSafety factor in engineering. 676 $a620/.00452 701 $aFowler$b Kim$01824039 712 02$aSharfus Draid, Inc. 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9911004776103321 996 $aMission-critical and safety-critical systems handbook$94391071 997 $aUNINA