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. kubernetes pod termination pending

    在将k8s从1.7.9 升级到1.10.2 之后,发现删除pod一直处于terminating状态, 调查发现删不掉的pod都有一个特点就是pod yaml中command部分写错了,如下所示: ap ...

  2. window.name实现跨域

    在 http://www.cnblogs.com/zhuzhenwei918/p/6759459.html 这篇文章中,我提到了几种跨域的方式,这里主要讲解使用window.name实现跨域. 跨域就 ...

  3. Vue单文件模板实例

    AddItemComponent.vue <template> <div id="add-item-template"> <div class=&qu ...

  4. Linux下Tomcat8.0.44配置使用Apr

    听说Apr可以提高tomcat很多的性能,配置具体如下 1.安装apr 1.5.2 [root@ecs-3c46 ]# cd /usr/local/src [root@ecs-3c46 src]# w ...

  5. Linux 命令学习之cd

    功能说明: cd 命令是 linux 最基本的命令语句,其他的命令都会依赖与 cd 命令.因此学好 cd 命令是必须的. 语 法:cd [目的目录] 补充说明:cd指令可让用户在不同的目录间切换,需要 ...

  6. C++中文件流操作

    一.C++中流和流操作符 C++中把数据之间的传输操作称为流,流既可以表示数据从内存传送到某个载体或设备中,即输出流,也可以表示数据从某个载体或设备传送到内存缓冲区变量中,即输入流.C++输入输出除了 ...

  7. bug: 1.eclipse 中tomcat server 变灰色 2.build path 添加的jar不识别

    1.网上百度的方案试过,没有作用. 最后删掉tomcat重新解压配置解决. 确保工程属性栏中,server正确才可加载tomcat. 猜测可能原因,tomcat在eclipse有时崩溃,一般做法是将s ...

  8. angular2自学笔记（二）---路由、服务等八大主要构造块

    angular的思想:总是把数据访问工作委托给一个支持性服务类. Angular 应用的:用 Angular 扩展语法编写 HTML 模板, 用组件类管理这些模板,用服务添加应用逻辑, 用模块打包发布 ...

  9. linux和Android的Makefile和android.mk

    1. makefile 1.1 gcc的参数 -Wall: 是打开警告开关, -O:    代表默认优化,可选:-O0不优化,-O1低级优化,-O2中级优化,-O3高级优化,-Os代码空间优化. -g ...

  10. 使用 Redis 实现分布式锁（转载）

    背景 在一般的分布式应用中,要安全有效地同步多服务器多进程之间的共享资源访问,就要涉及到分布式锁.目前项目是基于 Tornado 实现的分布式部署,同时也使用了 Redis 作为缓存.参考了一些资料并 ...