ISO 62304 - Software requirements content

tazer

Involved In Discussions
#1
Hi all,
This is my first message in the board.
I am relying on your indulgence.

In my team, we had a discussion on paragraph 5.2.2.
In this paragraph it is written: "...` shall include in the software requirements: a) ... i) ... ".
2 positions emerged:
1 / in the SRS we must determine for each requirement its category (a, b, ..., i). Then the requirement must be writen as four columns:
"ID" "Title" "Description" "Requirement Content"

2 / This is only a description of the requirements that must be integrated into the SRS. Then the requirement must be writen as only 3 columns:
"ID" "Title" "Description"

In both cases, a paper Requirement_Traceability_Matrix ensures traceability between SRSID, riskID, VV ....

What is your opinion on the question?
 
Elsmar Forum Sponsor

mihzago

Trusted Information Resource
#2
The standard does not specify how a requirement should be described; however the requirement must be complete, unambiguous, unique (not conflicting), and testable.

ID helps with traceability. Title isn't really needed, but is probably useful when searching or browsing requirements. Not sure what's the different between the "description" and "requirement content"; I assume it's some additional narrative describing the purpose or a rationale for a requirement. Certainly helpful, but I wouldn't say a must.
 

yodon

Staff member
Super Moderator
#3
In my team, we had a discussion on paragraph 5.2.2.
In this paragraph it is written: "...` shall include in the software requirements: a) ... i) ... ".
Good response from mihzago. I'd like to add that the paragraph you're citing starts with "As appropriate..." so the intent, I believe, is to ensure that you have considered all those requirements types, not so much that you necessarily have all those categories (if not applicable).

And the standard doesn't require that you have a *separate* software requirements document. I've seen cases where the software requirements are included in system requirements and identified through special tags / attributes.
 

tazer

Involved In Discussions
#4
Thank you both for your answers.
I also agree with mihzago.
And the standard doesn't require that you have a *separate* software requirements document. I've seen cases where the software requirements are included in system requirements and identified through special tags / attributes.
Exact, but in our case, the system is broken down into several sub systems that have their own documentation.
 
Thread starter Similar threads Forum Replies Date
H ISO 14971 vs. IEC 62304 vs. 98/79/EC vs. ISO 13485 (Software Medical Device) ISO 14971 - Medical Device Risk Management 1
K ISO 14971 and IEC 62304 - Medical Device Software House ISO 14971 - Medical Device Risk Management 9
F How to Align a Software Consulting/Contract Firm to ISO 13485+14971 & 62304 ISO 13485:2016 - Medical Device Quality Management Systems 1
Q ISO 62304 (Medical Device Software Development) Verification Requirements IEC 62304 - Medical Device Software Life Cycle Processes 1
K ISO 62304 Software Risk Management and Medical Device Class IEC 62304 - Medical Device Software Life Cycle Processes 5
E ISO 62304 and Validation of Medical Device Software Tools IEC 62304 - Medical Device Software Life Cycle Processes 17
I Software Design SOP to ISO 62304 (Software life cycle for Medical Device) IEC 62304 - Medical Device Software Life Cycle Processes 3
K Medical Device Software - Design Outputs? ISO 90003 and ISO 62304 IEC 62304 - Medical Device Software Life Cycle Processes 3
M Risk Analysis Flow - Confusion between ISO 14971 and IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 8
P Risk acceptability alignment between ISO 14971 and IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 6
S Relationship between IEC 62304 problem resolution and ISO 13485 IEC 62304 - Medical Device Software Life Cycle Processes 8
T Is there any requirement to be compliant with IEC 62304 while implementing ISO 13485 ISO 13485:2016 - Medical Device Quality Management Systems 5
B Our NB says that IEC 62304 is an ISO 14971 Requirement ISO 14971 - Medical Device Risk Management 1
B Clarification on interpretation of some EN ISO 14971:2012 & IEC 62304:2006 req's ISO 14971 - Medical Device Risk Management 46
M IEC 62304, ISO 14971 and FDA Medical Device SW Guidance 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 5
K Regarding ISO 62304 Clause 7.3.3 - Hazard and Risk Controls IEC 62304 - Medical Device Software Life Cycle Processes 9
D Applications that assist completing IEC 62304, ISO 14971 or ISO 13485 Documentation IEC 62304 - Medical Device Software Life Cycle Processes 7
I Is ISO 14971 certification required for IEC 62304? IEC 62304 - Medical Device Software Life Cycle Processes 11
chris1price MDSAP and ISO 13485 ISO 13485:2016 - Medical Device Quality Management Systems 5
D ISO 13485 Contained NC ISO 13485:2016 - Medical Device Quality Management Systems 3
K Compliance Obligations 6.1.3 of ISO 14001 ISO 14001:2015 Specific Discussions 3
V EN ISO 10993-1, Category of surface device by nature of body contact Other Medical Device Related Standards 2
I Does BSI require suppliers to be ISO 9001 Certified? EU Medical Device Regulations 12
Ron Rompen ISO 9001 Sanctioned Interpretations and FAQs ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 8
Ashland78 Need IATF 16949 ISO Gap Analysis Excel File Internal Auditing 3
Brizilla ISO 13485 for a Distributor ISO 13485:2016 - Medical Device Quality Management Systems 7
E Organisational Chart-ISO 17025 Laboratory ISO 17025 related Discussions 3
S Do ISO certs require an Apostille? ISO 13485:2016 - Medical Device Quality Management Systems 13
Q Harmonised Standards (EN ISO 13485 / EN ISO 14971) in MDR (2017/745/EU) ISO 13485:2016 - Medical Device Quality Management Systems 3
Sidney Vianna Informational ISO/CD 7101 Health Care Quality Management System Standard Hospitals, Clinics & other Health Care Providers 0
Fjalar ISO 20417:2021: Technical Data (6.6.4 c) Other Medical Device Related Standards 0
D Automotive Customer asking for ISO 14001 Certification from suppliers ISO 14001:2015 Specific Discussions 3
K Need Help With Auditing Suppliers Against ISO 9001 ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 50
L PFMEA for test procedures (ISO 14971) ISO 14971 - Medical Device Risk Management 5
J ISO 13485- 8.3.1 Non-conforming material high volume ISO 13485:2016 - Medical Device Quality Management Systems 4
Q ISO 20417:2021- Regulatory Identification Other ISO and International Standards and European Regulations 2
L ISO/IEC 20000-6 Technical Areas IT (Information Technology) Service Management 0
R What are the new changes in EN ISO 11137-1:2015+A2:2019? Other Medical Device Related Standards 2
Y ISO 10993-14:2001 - Gel implants stored in glass syringes Other Medical Device Related Standards 1
eldercare Multi-Site ISO/AS Certification Requirement for some sites ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 22
Sidney Vianna ISO 14001 News ISO 14001 Continual Improvement Survey ISO 14001:2015 Specific Discussions 0
Casana ISO 17025 - Contractor certification? IATF 16949 - Automotive Quality Systems Standard 5
B Sanctioned interpretation #10 - ISO 17025 IATF 16949 - Automotive Quality Systems Standard 2
H Contract Manufacturer as Design Owner ISO 13485 ISO 13485:2016 - Medical Device Quality Management Systems 6
G Compliance with ISO 9001-2015 for ISO 17025 Accredited Labs? ISO 17025 related Discussions 5
blackholequasar ISO 13485 certification prior to Medical Device Manufacturing... worth it? ISO 13485:2016 - Medical Device Quality Management Systems 4
C ISO 14001 Internal Audit - Opportunity for Improvement ISO 14001:2015 Specific Discussions 2
P ISO 11607-2 Process Specification Other Medical Device Related Standards 1
S Which ISO Standards to Purchase - EN ISO and/or ISO Other Medical Device Related Standards 1
A ISO Clause 4.1/4.2 & 6.1 ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 13

Similar threads

Top Bottom