cnotes11

c hazard analysis and control

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: +     *  *  )     c � !  ' +     *  *  )     c � Hazard analysis and control is a continuous, iterative process throughout system development and use. Conceptual development Design Development Operations Hazard identification Hazard resolution Verification Change analysis Operational feedback Hazard resolution precedence: 1. 2. 3. 4. Eliminate the hazard Prevent or minimize the occurrence of the hazard Control the hazard if it occurs. Minimize damage. Management  '       c � Process Steps 1. Perform a Preliminary Hazard Analysis Produces hazard list 2. Perform a System Hazard Analysis (not just Failure Analysis) Identifies potential causes of hazards 3. Identify appropriate design constraints on system, software, and humans. 4. Design at system level to eliminate or control hazards. 5. Trace unresolved hazards and system hazard controls to software requirements.   + +     * * * * ) )     � System Safety (2)  '       c Specifying Safety Constraints Most software requirements only specify nominal behavior Need to specify off−nominal behavior Need to specify what software must NOT do What must not do is not inverse of what must do Derive from system hazard analysis...
View Full Document

This note was uploaded on 11/07/2011 for the course AERO 16.36 taught by Professor Alexandremegretski during the Spring '09 term at MIT.

Ask a homework question - tutors are online