IEC
62304

Reference

Software Lifecycle
Process

Applicable
for

Class

A

Class

B

Class

C

　

PRIMARY
LIFECYCLE PROCESESS

　

　

　

5

SOFTWARE
DEVELOPMENT Process

　

　

　

5.1

Development Planning
Activity

　

　

　

5.1.1

Software
development plan task

X

X

X

5.1.2

Software
development plan reference to SYSTEM requirements task

X

X

X

5.1.3

SOUP management
planning task

　

X

X

5.1.4

Software
development measures planning task

　

X

X

5.1.5

Software
integration and integration testing planning task

　

X

X

5.1.6

Software
VERIFICATION planning task

X

X

X

5.1.7

Software
VERIFICATION requirements coverage planning task

　

X

X

5.1.8

Software RISK
MANAGEMENT planning task

X

X

X

5.1.9

Documentation
planning task

X

X

X

5.1.10

Software
configuration management planning task

X

X

X

5.1.11

Software
configuration control planning task

　

X

X

5.1.12

Software problem
resolution planning task

　

　

X

5.2

Requirements Analysis
Activity

　

　

　

5.2.1

Define software
requirements from SYSTEM requirements task

X

X

X

5.2.2

Establish
software requirements task

X

X

X

5.2.3

Software
requirements content task

X

X

X

5.2.4

Include RISK
CONTROL measures in software requirements task

　

X

X

5.2.5

Update RISK
ANALYSIS task

X

X

X

5.2.6

Ensure
compliance with SYSTEM requirements task

X

X

X

5.2.7

Uniquely
identify software requirements task

X

X

X

5.2.8

Update SYSTEM
requirements task

X

X

X

5.2.9

Verify software
requirements task

X

X

X

5.2.10

Document
software requirements VERIFICATION task

X

X

X

5.3

Architectural Design
Activity

　

　

　

5.3.1

Transform
software requirements into an ARCHITECTURE task

X

X

X

5.3.2

Document
software ARCHITECTURE task

X

X

X

5.3.3

Document
software safety classification of each SOFTWARE ITEM
task

X

X

X

5.3.4

Develop an
ARCHITECTURE for the interfaces of SOFTWARE ITEMS task

　

X

X

5.3.5

Specify SYSTEM
hardware and software required by SOUP item task

　

X

X

5.3.6

Specify
functional and performance requirements of SOUP item
task

　

X

X

5.3.7

Identify
segregation necessary for SAFETY task

　

X

X

5.3.8

Verify software
ARCHITECTURE task

　

X

X

5.3.9

Verify
appropriateness of software development plan task

　

X

X

5.3.10

Document results
of software ARCHITECTURE VERIFICATION task

　

X

X

5.4

Detailed
Design Activity

　

　

　

5.4.1

Refine SOFTWARE
ITEMS into SOFTWARE UNITS task

　

X

X

5.4.2

Inheritance of
software safety classification task

　

X

X

5.4.3

Develop detailed
design for each SOFTWARE UNIT task

　

　

X

5.4.4

Develop detailed
design for interfaces task

　

　

X

5.4.5

Verify detailed
design task

　

X

X

5.4.6

Additional
detailed design VERIFICATION task

　

　

X

5.4.7

Document results
of design VERIFICATION task

　

X

X

5.5

Software
Coding Activity

　

　

　

5.5.1

Implement each
SOFTWARE UNIT task

　

X

X

5.5.2

Establish
SOFTWARE UNIT VERIFICATION PROCESS task

　

X

X

5.5.3

Verify software
code task

　

X

X

5.5.4

Additional
software code VERIFICATION task

　

X

X

5.5.5

Document the
results of software code VERIFICATION task

　

X

X

5.6

Integration and Testing
Activity

　

　

　

5.6.1

Integrate
SOFTWARE UNITS task

　

X

X

5.6.2

Verify software
integration task

　

X

X

5.6.3

Document the
results of software integration task

　

X

X

5.5.4

Additional
software code VERIFICATION task

　

X

X

5.6.5

Integration
testing content task

　

X

X

5.6.6

Include
integration testing for non-normal cases task

　

　

X

5.6.7

Conduct
regression tests task

　

X

X

5.6.8

Document results
of software integration tests task

　

X

X

5.6.9

Integration test
documentation contents task

　

X

X

5.6.10

Use formal
software problem resolution PROCESS task

　

X

X

5.7

System
Testing Activity

　

　

　

5.7.1

Establish tests
for each software requirement task

　

X

X

5.7.2

Use formal
software problem resolution PROCESS task

　

X

X

5.7.3

Repeat tests and
conduct regression tests task

　

X

X

5.7.4

Verify SOFTWARE
SYSTEM testing task

　

X

X

5.7.5

Record data for
each test task

　

X

X

5.8

Release
Activity

　

　

　

5.8.1

Ensure software
VERIFICATION is complete

　

X

X

5.8.2

Ensure
documentation is complete

　

X

X

5.8.3

Document known
residual anomalies

　

X

X

5.8.4

Evaluate known
residual anomalies

　

X

X

5.8.5

Document
released VERSIONS

　

X

X

5.8.6

Document how
released software was created

　

X

X

5.8.7

Archive master
copies

　

X

X

5.8.8

Use established
procedures for software release

　

X

X

6

SOFTWARE
MAINTENANCE Process

　

　

　

6.1

Establish software
maintenance plan Activity

　

　

　

6.1.1

Establish
software maintenance plan task

X

X

X

6.2

Problem
and Modification Analysis Activity

　

　

　

6.2.1

Record and
evaluate feedback task

X

X

X

6.2.2

Use software
problem resolution PROCESS task

X

X

X

6.2.3

Analyse
modification requests task

X

X

X

6.2.4

Conduct analysis
of changes implied by modification request task

X

X

X

6.2.5

Document new,
modified and deleted item task

X

X

X

6.2.6

Review and
approve modification task

X

X

X

6.2.7

Document
modification task

　

X

X

6.3

Modification
Implementation Activity

　

　

　

6.3.1

Use established
PROCESS to implement modification task

X

X

X

6.3.2

Define criteria
for testing modifications task

　

X

X

6.3.3

Verify
modifications task

　

X

X

6.3.4

Conduct
regression testing task

　

X

X

6.3.5

Demonstrate
software RISK CONTROL measures remain effective task

　

X

X

6.3.6

Document the
test results task

　

X

X

see
5.3

Architectural Design
Activity

　

　

　

see
5.4

Detailed
Design Activity

　

　

　

see
5.5

Software
Coding Activity

　

　

　

see
5.6

Integration and Testing
Activity

　

　

　

see
5.7

System
Testing Activity

　

　

　

see
5.8

Release
Activity

　

　

　

　

SUPPORTING
PROCESSES

　

　

　

7

SOFTWARE
RISK MANAGEMENT Process (referenced ISO 14971)

　

　

　

7.1

Analysis
of software contributing to HAZARDS Activity

　

　

　

7.1.1

Identify
SOFTWARE ITEMS that could contribute to a HAZARD task

　

X

X

7.1.2

Identify
potential causes of contribution to a HAZARD task

　

X

X

7.1.3

Consider
specific potential causes task

　

X

X

7.1.4

Review published
SOUP anomaly lists task

　

X

X

7.1.5

Document
potential causes task

　

X

X

7.1.6

Document
sequences of events task

　

X

X

7.2

RISK
CONTROL measures Activity

　

　

　

7.2.1

Define RISK
CONTROL measures task

　

X

X

7.2.2

RISK CONTROL
measures implemented in software task

　

X

X

7.3

VERIFICATION of RISK
CONTROL measures Activity

　

　

　

7.3.1

Verify RISK
CONTROL measures task

　

X

X

7.3.2

Document any new
sequences of events task

　

X

X

7.3.3

Document
TRACEABILITY task

　

X

X

7.4

RISK
MANAGEMENT of software changes Activity

　

　

　

7.4.1

Analyse changes
TO MEDICAL DEVICE SOFTWARE with respect to safety task

X

X

X

7.4.2

Analyse impact
software changes on existing RISK CONTROL measures task

　

X

X

7.4.3

Perform RISK
MANAGEMENT ACTIVITIES based on analyses task

　

X

X

8

SOFTWARE
CONFIGURATION MANAGEMENT Process

　

　

　

8.1

Configuration
identification Activity

　

　

　

8.1.1

Establish means
to identify CONFIGURATION ITEMS task

X

X

X

8.1.2

Identify SOUP
task

X

X

X

8.1.3

Document SOUP
designator task

X

X

X

8.1.4

Identify SYSTEM
configuration documentation task

X

X

X

8.2

Configuration control
Activity

　

　

　

8.2.1

Identify and
record change requests task

X

X

X

8.2.2

Approve requests
prior to implementation task

X

X

X

8.2.3

Implement
changes task

X

X

X

8.2.4

Provide means
for TRACEABILITY of change task

X

X

X

8.3

Configuration status
accounting Activity

　

　

　

8.3.1

Configuration
status accounting task

X

X

X

9

SOFTWARE
PROBLEM RESOLUTION Process

　

　

　

　

SOFTWARE
PROBLEM RESOLUTION Activity

　

　

　

9.1.1

Prepare problem
reports task

X

X

X

9.1.2

Advise relevant
parties task

X

X

X

9.1.3

Investigate the
problem task

X

X

X

9.1.4

Evaluate the
problem's relevance to safety task

X

X

X

9.1.5

Track and report
status task

X

X

X

9.1.6

Resolve the
problem task

X

X

X

9.1.7

Maintain a
record of the problem task

X

X

X

9.1.8

Analyse problems
for trends task

X

X

X

9.1.9

Verify
task

X

X

X

IEC_62304_CheckList的更多相关文章

随机推荐

  1. PHP之string

    string addcslashes() Quote string with slashes in a C style 以 C 语言风格使用反斜线转义字符串中的字符 addslashes() Quot ...

  2. Maven报错：maven-archetype-webapp:RELEASE from any of the configured repositories

    今天学习maven,在控制台下新建maven项目没有问题,但是在STS(eclipse)下创建maven项目老是报错,郁闷死了: ----------------------------------- ...

  3. cmd sc命令进行服务操作

    sc 命令可以注册.删除和查询系统服务 sc可供选择的参数有很多,这里不详细描述.只介绍简单的最基本的sc使用方式. 1. sc create 创建windows服务 eg: sc \\myserve ...

  4. 多功能电子通讯录（涉及到了双向链表的使用，Linux文件编程等等）

    readme.txt //作为一个程序员,我们咋么能不写用户手册呢!MSP的我觉得用户体验是王道,苹果手机的用户体验的确不错!不过WP加油!我去,扯远了!赶紧看我的程序吧!  歡迎使用多功能電子通訊錄 ...

  5. java并发编程（4）性能与可伸缩性

    性能与可伸缩性 一.Amdahl定律 1.问题和资源的关系 在某些问题中,资源越多解决速度越快:而有些问题则相反: 注意:每个程序中必然有串行的部分,而合理的分析出串行和并行的部分对程序的影响极大:串 ...

  6. C《二》

    开始阅读谭浩强的C语言程序设计. 编译一个程序,除了语法以外,还需要管理内存,就是数据结构,学习如何高效的利用内存:数据关系的处理.例如学生管理系统的开发,但是数据关系是有最优解的,也就是可以学会的, ...

  7. JavaScript插入节点小结

    JS原生API插入节点的方式大致有innerHTML.outerHTML.appendChild.insertBefore.insertAdjacentHTML.applyElement这6种. 这里 ...

  8. 使用StackPanel进行简单地布局

    尽管StackPanel非常简单,但是其实用性也非常强 ,Stackpanel将子元素以堆叠的形式 排列在一行或一列.通常建议使用该控件对于一些小范围内的控件进行布局. 如果要架设用户控件的框架结构, ...

  9. 数据适配：DataAdapter对象概述

    DataAdapter对象可用于执行数据库的命令操作,含有四个不同的操作命令,分别如下:   SelectCommand:用来选取数据源中的记录: InsertCommand:用来向数据源中新插入一条 ...

  10. [javaSE] IO流（对象序列化）

    写入 获取ObjectOutputStream对象,new出来,构造参数:FileOutputStream对象目标文件 调用ObjectOutputStream对象的writeObject()方法,参 ...