1.

Identify the software items

1. Analyze the changes to the Software 2. Identify the potential
software w.r.t safety Analysis causes
2. Analyze the impact of the contributing 3. Evaluate the published
software changes on existing to hazardous SOUP anomaly lists
Risk control Measures situation 4. Document potential causes
3. Perform Risk Management 5. Document sequence of
Activities based on analysis Events

Risk S/w Risk

management Risk Control
of Software Management Measures
changes Process

1. Define Risk control

Measures
1. Verify Risk control 2. Risk control Measures
Measures Verification need to implement in the
2. Document any new of risk software
sequence of Events control
3. Document Traceability measures
Class B (By Default)

Can a
hazardous
No
situation arise
from a failure of
the software?

Yes

Evaluate the
effectiveness of the Risk
control measures
external to the Software

Does the failure

No of the software
result in
Unacceptable
RISK?

What severity Serious Injury/Death

of the injury is
possible?

Non Serious Injury

Class A Class B Class C

 Software
Verified Software
Requirement
System
Specifications

Va
lid
Ver

Software

atio
System Integration
Software Test Specification
ifica

Architectural & Software

np
Design Verification
ti

h
on p

ase
Software Architecture
h as

Specification
e

Software Detailed Software Unit

Implementation Software Unit
Design
Verification
(Unit Design)

Coding Phase

Inputs from the Problem Resolution process Outputs from the Problem Resolution process
  S/W Development Plan
 Keeping plan Updated
 S/w development plan w.r.t System D&D
 Integration & testing plan
 Ensure software unit verification is  Risk management plan
complete  Document plan
 Document known residual anomalies  Configuration Management plan
 Evaluate known residual anomalies Planning  Supporting items to be control
 Document released version  Configuration item control before testing
 Document how released software was
created Requirements
Software Release Software Requirement Content
Analysis
 Ensure Activities and tasks are
completed
 Archive software
 Assure repeatability of software release  Transform requirements into
architecture
 Establish tests for software items  Develop an architecture for the
 Use Software Problem Resolution interfaces of software item
Architecture
Software Testing  Specify functional and performance
process design
 Retest after changes requirements of SOUP item
 Verify Software system testing  Specify System hardware and software
 Software system test records contents required by SOUP
 Specify Software architecture

 Integrate Software Units Integration and

Detailed Design Refine Architecture into Software units
 Verify Software Integration Testing
 Test Integrated Software
 Integration Testing Content Unit
Implementation  Implement each Software units
 Verify Integration Test procedures  Establish Software Unit verification
and Verification
 Conduct Regression Tests process
 Integrate Test Record Contents  Software Acceptance criteria
 Use Software Problem Resolution process  Software Unit Verification