Elsmar Cove Quality DiscussionsThe Cove Business Standards Discussion Forums More Free Files Forum Discussion Thread Post Attachments Listing Cove Discussion Forums Main Page
UL - Underwriters Laboratories - Health Sciences

Elsmar XML RSS Feed
Elsmar Cove Forum RSS Feed

Monitor the Elsmar Forum
Sponsor Links

Courtesy Quick Links

Links Elsmar Cove visitors will find useful in the quest for knowledge and support:

Jennifer Kirley's
Conway Business Services

International Quality Services

Marcelo Antunes'
SQR Consulting, and
Medical Devices Expert Forum

Bob Doering
Bob Doering's Blogs and,
Correct SPC - Precision Machining

Ajit Basrur
Claritas Consulting, LLC

International Standards Bodies - World Wide Standards Bodies

AIAG - Automotive Industry Action Group

ASQ - American Society for Quality

International Organization for Standardization - ISO Standards and Information

NIST's Engineering Statistics Handbook

IRCA - International Register of Certified Auditors

SAE - Society of Automotive Engineers

Quality Digest

IEST - Institute of Environmental Sciences and Technology

Single Post View
Old 13th March 2018, 03:13 PM

Total Posts: 1
Please Help! Firmware Verification Testing & Sample Size

Hi All,

We are developing custom firmware for our medical device (class II), and it is only intended to run on two versions of hardware. We are ISO 13485 and there is some leeway with statistical sample sizes/justification. I am struggling trying to understand if statistical sample size justification is required or not. Or if we can provide a justification for much smaller testing regime.

The firmware developer is trying to claim that they perform exhaustive testing of all features on all hardwares (n=2) . Testing more than 1 sample per hardware version is silly, because you are testing that the "bits" are transferring properly and working. The firmware also verifies itself on startup.

I am used to looking at a statistical plan for testing (ex: identifying confidence level and probability of finding a bug). I was balked at when throwing out a 90% CI with 15% bug finding resulting in a n=15 sample size.

Now, I do Usability testing with larger sample size that validates a lot of these firmware functionality. But it isn't officially verifying the input/output at the firmware "language" level. Does anyone have some insight on proper sampling method for this situation?

Sponsored Links

The time now is 03:43 AM. All times are GMT -4.
Your time zone can be changed in your UserCP --> Options.

Misc. Internal Links

NOTE: This forum uses "Cookies"

The Elsmar Cove is currently owned by the Marc Smith Retirement Trust and operated by Law-Nutz WyomingŠ2018