REGISTER

FR
Search
×
FR

Placeholder headline

This is just a placeholder headline

API SPEC 14L: Lock Mandrels and Landing Nipples : Reaffirmed

$

273

BUY NOW

Placeholder headline

This is just a placeholder headline

API SPEC 20F: Corrosion Resistant Bolting for Use in the Petroleum and Natural Gas Industries : Reaffirmed

$

169

BUY NOW

Placeholder headline

This is just a placeholder headline

API TR 5NCL Nickel Content Limits for API 5CT Sour Service Products

$

149

BUY NOW

Placeholder headline

This is just a placeholder headline

API SPEC 19ICD: Inflow Control Devices : Reaffirmed

$

189

BUY NOW

Placeholder headline

This is just a placeholder headline

API MPMS CH 23.2: Reconciliation of Liquid Tank Car(s) Quantities : Reaffirmed

$

218

BUY NOW

Placeholder headline

This is just a placeholder headline

API SPEC 16A: Specification for Drill-through Equipment

$

322

BUY NOW

Placeholder headline

This is just a placeholder headline

API RP 13B-2: Field Testing Oil-based Drilling Fluids wA1

$

388

BUY NOW

ISO 80002:2014

ISO 80002:2014 Medical device software – Part 3: Process reference model of medical device software life cycle processes (IEC 62304)

CDN $353.00

SKU: 56f1ad7f7162 Categories: ,

Description

IEC TR 80002-3:2014 which is a technical report (TR), provides the description of software life cycle processes for medical devices. The medical device software life cycle processes are derived from IEC 62304:2006, with corresponding safety classes. They have been aligned with the software development life cycle processes of ISO/IEC 12207:2008 and are presented herein in full compliance with ISO/IEC 24774:2010. The content of these three standards provides the foundation of this TR. This TR does not:
– address areas already covered by existing related standards, e.g. the international standards that relate to the four standards used to build this TR (see Bibliography);

– FDA guidance documents; or

– software development tools. This TR describes the process reference model for medical device software development and is limited in scope to the life cycle processes described in IEC 62304:2006. The process names correspond to those of IEC 62304:2006. The mappings provided in Annex B are essential for the alignment between IEC 62304:2006 (which is based on ISO/IEC 12207:1995) and ISO/IEC 12207:2008, developed to address the detailed normative relationship between the two standards. This technical report is not intended to be used as the basis of regulatory inspection or certification assessment activities.

Edition

1

Published Date

2014-06-05

Status

PUBLISHED

Pages

23

Language Detail Icon

English

Format Secure Icon

Secure PDF

Abstract

IEC TR 80002-3:2014 which is a technical report (TR), provides the description of software life cycle processes for medical devices. The medical device software life cycle processes are derived from IEC 62304:2006, with corresponding safety classes. They have been aligned with the software development life cycle processes of ISO/IEC 12207:2008 and are presented herein in full compliance with ISO/IEC 24774:2010. The content of these three standards provides the foundation of this TR. This TR does not:
- address areas already covered by existing related standards, e.g. the international standards that relate to the four standards used to build this TR (see Bibliography);
- FDA guidance documents; or
- software development tools. This TR describes the process reference model for medical device software development and is limited in scope to the life cycle processes described in IEC 62304:2006. The process names correspond to those of IEC 62304:2006. The mappings provided in Annex B are essential for the alignment between IEC 62304:2006 (which is based on ISO/IEC 12207:1995) and ISO/IEC 12207:2008, developed to address the detailed normative relationship between the two standards. This technical report is not intended to be used as the basis of regulatory inspection or certification assessment activities.

Previous Editions

Can’t find what you are looking for?

Please contact us at: