Published: Newnes, 2013
Description:
1 online resource (xlix, 1150 pages).
Contents:
“…-- Certification killers -- Project
planning strategies -- Strategy 1: determine the project certification scope early -- Strategy 2: determine feasibility of certification -- Strategy 3: select an independent assessor (if used) -- Strategy 4: understand your assessor's role (if used) -- Strategy 5: assessment communication is key -- Strategy 6: establish a basis of certification -- Strategy 7: establish a "fit and purpose" for your product -- Strategy 8: establish a certification block diagram -- Strategy 9: establish communication integrity objectives -- Strategy 10: identify all interfaces along the certification boundary -- Strategy 11: identify the key safety defensive strategies -- Strategy 12:
define built in test (BIT) capability -- Strategy 13:
define fault annunciation coverage -- Strategy 14:
define reliance and expectation of the
operator/user -- Strategy 15:
define plan for developing software to appropriate integrity level -- Strategy 16:
define artifacts to be used as evidence of compliance -- Strategy 17:
plan for labor-intensive analyses -- Strategy 18: create user-level documentation -- Strategy 19:
plan on residual activity -- Strategy 20: publish a well-
defined certification
plan -- Faults, failures, hazards, and risk analysis -- Faults, errors, and failures -- Availability and reliability -- Fault handling -- Hazard analysis -- Risk analysis -- Safety-critical architectures -- "Do-er"/"Check-er" -- Two processors -- "Voter" -- Software implementation strategies -- Strategy 1: have a well-
defined, repeatable peer-review process -- Strategy 2: consider using existing safety coding standards -- Strategy 3: handle all combinations of input data -- Strategy 4: specific variable value checking -- Strategy 5: mark safety-critical code sections -- Strategy 6: timing execution checking -- Strategy 7: stale data -- Strategy 8: comparison of outputs -- Strategy 9: initialize data to least permissive state -- Strategy 10: order of execution -- Strategy 11: volatile data checking -- Strategy 12: non-volatile data checking -- Strategy 13: make sure the entire system can run -- Strategy 14: remove "dead" code -- Strategy 15: fill unused memory -- Strategy 16: static code analysis -- Background -- Is that software yours? …”
Call Number:
Loading…
Located:
Loading…
Elsevier - Click here for access
eBook