The Cove Business Standards Discussion Forums
Monitor the Elsmar Forum
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, 06:48 PM

Total Posts: 1,169
Re: Firmware Verification Testing & Sample Size

The reason for a sample size is to account for variability. Usability testing has quite a bit of variability through the users.

Software, though, given the same inputs and conditions, is (supposed to be) deterministic and so doing more that one test given the same setup will give the same result. So, yes, a 'sample size' of 1 is appropriate for software tests. Given that you have, in your example, 2 hardware platforms, it is appropriate to test on both platforms.

The point about software verifying itself at startup is outside the scope of formal firmware verification (although, of course, the verification process itself would be verified).

Sponsored Links

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

Misc. Internal Links

NOTE: This forum uses "Cookies"