 |
Trace identified
system hazards and system safety design constraints to software
interface.
|
|
Translate identified
software-related hazards and system safety design constraints into
requirements and constraints on software behavior.
|
|
Develop a software
hazard tracking system.
|
|
Evaluate software
requirements with respect to safety constraints and other
safety-related criteria.
|
|
Trace safety
requirements and constraints to the code. Design software and HMI to
eliminate or control hazards.
|
|
Plan and perform
software safety testing.
|
|
Perform special
safety analyses
 |
human-computer
interaction and interface
|
|
formal or
informal walkthroughs or proofs (SFTA)
|
|
interface
between critical and non-critical software. |
|
|
Review test results
for safety issues. Trace identified hazards back to the system
level.
|
|
Include design
decisions, design rationale, and other safety information in
documentation, user manuals, etc.
|
|
Establish
appropriate management structure, communication channels, authority,
accountability, and responsibility.
|
|
Analyze the behavior
of all COTS software.
|
|
Establish feedback
sources. Analyze operational data and relate to hazard analysis and
documented design assumptions.
|
|
Analyze all changes
for their effect on safety. |
