Professional Documents
Culture Documents
Flowchart
These definitions are accompanied by a flowchart, which explains at a glance the selection of safety
class.
The questions can be mapped to the above definitions:
Here is a snapshot of the flowchart found in section 4.3 of IEC 62304 Amd1 2015:
Consequence
The consequence of these definitions is the introduction of the acceptability of risks in the
assessment of software safety class:
Using the same legend as in the previous matrix, the software safety classes areas can be
represented like this:
The class A region can be extended to the upper side of the matrix. This is possible thanks to the
sentence in bold in the definition of class A written above. In our example, the cell (critical,
improbable) sees its corresponding software safety class set to class A, hence the risk is acceptable.
The software development process is divided into a set of activities, with most activities further divided
into a set of tasks. These activities are listed below:
Software Release.
The maintenance process activities are considered to be as important as the software development
process activities. These activities include: