Software Unit Acceptance Criteria (5.5.4)

cwilburn

Starting to get Involved
#1
Hi Everyone!

Does anyone have examples of acceptance criteria for the items listed in 5.5.4?

My initial thought is to create a checklist to be used during code review, and include items like, "have all variables been initialized?" and "have boundary conditions been handled correctly?"

I know that I could also use static analysis tools too...saying something like "when using tool X, no warning or errors related to memory management are found"

What other ways are there to meet this requirement?

Thanks,
Cathy
 
Elsmar Forum Sponsor

QAengineer13

Quite Involved in Discussions
#2
Hi Everyone!

Does anyone have examples of acceptance criteria for the items listed in 5.5.4?

My initial thought is to create a checklist to be used during code review, and include items like, "have all variables been initialized?" and "have boundary conditions been handled correctly?"

I know that I could also use static analysis tools too...saying something like "when using tool X, no warning or errors related to memory management are found"

What other ways are there to meet this requirement?

Thanks,
Cathy
Hi Cathy,

My 2c's, just ensure that whatever method you choose to demonstrate Acceptance criteria it needs to be objective and supported by a technical evidence.
 

yodon

Leader
Super Moderator
#3
First off, that (additional software unit acceptance criteria) is only required for class C so I presume you are developing class C software. Thus, the intent is to take a "deeper dive" at the unit level to help ensure safety.

The standard itself lists some options:
a) proper event sequence;
b) data and control flow;
c) planned resource allocation;
d) fault handling (error definition, isolation, and recovery);
e) initialization of variables;
f) self-diagnostics;
g) memory management and memory overflows; and
h) boundary conditions.

What are your "baseline" acceptance criteria (i.e., for both class B and C)? Ours, for example, are code reviews and static analysis similar to what you described. When we are working on class C software, then we apply any of the above, as applicable for the units, as additional.
 
Thread starter Similar threads Forum Replies Date
A 5.5.3 - Software Unit Acceptance Criteria (Risk Control Measures) IEC 62304 - Medical Device Software Life Cycle Processes 3
T Software Unit definition - IEC 62304 - Medical Device Software Life Cycle Processes 3
F Configurator for a power unit - Software or other solution? Manufacturing and Related Processes 0
I IEC 62304:2006 Definitions - Software System, a Software Element and Software Unit IEC 62304 - Medical Device Software Life Cycle Processes 13
C 7.6 for a Software Company - Calibrating Unit Testing ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 7
T Software item classification and Detailed Design IEC 62304 - Medical Device Software Life Cycle Processes 4
T Software user interface - definition of hazards ISO 14971 - Medical Device Risk Management 15
T Classification Accessory Software medical device EU Medical Device Regulations 4
G Software Medical Device Classification EU Medical Device Regulations 7
D Software Validation Question ISO 13485:2016 - Medical Device Quality Management Systems 10
C. Tejeda Computer system validation approach for Minitab Statistical software Software Quality Assurance 7
B Can a software that receive data from a MD be classified as Class I?or is not a MD? EU Medical Device Regulations 5
A What JIRA Software workflows you use for your software lifecycle? IEC 62304 - Medical Device Software Life Cycle Processes 4
G Software change management Design and Development of Products and Processes 2
G IATF 7.1.5.2.1 Calibration/verification records :Program/software verification IATF 16949 - Automotive Quality Systems Standard 7
John C. Abnet ...validation of computer software ISO 13485:2016 - Medical Device Quality Management Systems 14
N Free statistical software Reliability Analysis - Predictions, Testing and Standards 7
T ISO quality system software such as MQ1 (which is what we currently use) Document Control Systems, Procedures, Forms and Templates 7
X Looking for 17025 auditor to perform internal audit on IT software testing laboratory ISO 17025 related Discussions 3
B ERP software validation - risk assessment vs validation scope ISO 13485:2016 - Medical Device Quality Management Systems 11
D Guidance for Medical records software/template ISO 13485:2016 - Medical Device Quality Management Systems 1
M MDSW Software importer distributor CE Marking (Conformité Européene) / CB Scheme 2
B Software as a Medical Device - Language Requirements EU Medical Device Regulations 6
B Software as a NON-medical device Medical Information Technology, Medical Software and Health Informatics 22
qualprod 8.3 for software development. ISO 9000, ISO 9001, and ISO 9004 Quality Management Systems Standards 1
S Software design document NMPA guidance and consultant China Medical Device Regulations 3
C How to place software version for SaMD product in HIBC secondary data structure (UDI-PI)? Other US Medical Device Regulations 3
L Acquiring software from 3rd party company IEC 62304 - Medical Device Software Life Cycle Processes 8
R Validation of Software used in Verification Testing ISO 13485:2016 - Medical Device Quality Management Systems 2
A FMEA Software IATF 16949 - Automotive Quality Systems Standard 6
A Medical Device Software POC Medical Device and FDA Regulations and Standards News 6
C Discus Software for First Article Inspection Inspection, Prints (Drawings), Testing, Sampling and Related Topics 1
D One Software as Medical Device product or two? EU Medical Device Regulations 4
V Internal Audit Software IATF 16949 - Automotive Quality Systems Standard 5
Watchcat New Draft Guidance on Content of Premarket Submissions for Software Device "Functions" Other US Medical Device Regulations 2
Watchcat Software validation vs design V&V? Other US Medical Device Regulations 27
M Initial Importer/Distributor and Software Validation IEC 62304 - Medical Device Software Life Cycle Processes 1
D Test Management Software Software Quality Assurance 1
E ISO 13485 software validation ISO 13485:2016 - Medical Device Quality Management Systems 7
D Tracking software versions used with instruments ISO 13485:2016 - Medical Device Quality Management Systems 0
dgrainger Informational MHRA's Software and AI as a Medical Device Change Programme UK Medical Device Regulations 0
S Do you follow your QMS for non-device software features? Medical Information Technology, Medical Software and Health Informatics 4
J Can we register non-device clinical decision support software under draft guidance? Other US Medical Device Regulations 5
I Software (SaMD) mobile application verification testing: objective evidence Medical Information Technology, Medical Software and Health Informatics 2
J EU equivalent to Clinical Decision Support Software EU Medical Device Regulations 3
Y ISO 13485:2015 Software Validation IQ/OQ/PQ ISO 13485:2016 - Medical Device Quality Management Systems 13
S Recommended software to send Quality scorecards to suppliers (external providers) Supplier Quality Assurance and other Supplier Issues 3
J Software as a Medical Device - SaMD IEC 62304 - Medical Device Software Life Cycle Processes 7
BeaBea QMS/ Training Management Software Service Industry Specific Topics 4
shimonv Working with a software developer who is not setup for IEC 62304 IEC 62304 - Medical Device Software Life Cycle Processes 9

Similar threads

Top Bottom