Software Design Verification

Trying to understand Software Design Verification … A QA’s takeaway on reading the General Principles of Software Validation for the first time.
FDA gives guidance in the General Principles of Software Validation guidance document, but in general:
  • Testing at different levels: units, integrated units, software complete
  • Testing types: negative, combinatorial, fault injection, risk controls challenge, boundary, corner cases, stress, power fail/low/intermittent,
  • Software testing coordinated with system testing: What should software do when subjected to EMI? What are acceptable failure states? Mix coverage
  • Platform (and hardware) variants and OS versions:  Use risk analysis to determine impact of variants and/or versions, then scale.
  • Planning and understanding of software testing prior to shipment versus built-in self tests (i.e., if software configuration can change in the field)
  • Coverage of requirements, coverage of risk controls
  • Planned exploratory testing

Software Design Verification is not just to satisfy the requirements of design, though it starts there. Testing must also include actual use environment, or simulated environment, prior to design validation activities.

Software Design Verification is not a substitute for design validation

Software that has a direct effect on safety should be tested and verified with more scrutiny.


About the author

Joel is a quality systems associate and researcher for SoftwareCPR. After working for 7 years in the medical field with the United States Army, he now spends his time exploring tech development and programming. He is the father to two wonderful children and avid fisherman.

SoftwareCPR Training Courses:

IEC 62304 and other emerging standards for Medical Device and HealthIT Software

Our flagship course for preparing regulatory, quality, engineering, operations, and others for the activities and documentation expected for IEC 62304 conformance and for FDA expectations. The goal is to educate on the intent and purpose so that the participants are able to make informed decisions in the future.  Focus is not simply what the standard says, but what is meant and discuss examples and approaches one might implement to comply.  Special deep discount pricing available to FDA attendees and other regulators.

3-days onsite with group exercises, quizzes, examples, Q&A.

Instructor: Brian Pate

Next public offering:  TBD

Email to request a special pre-registration discount.  Limited number of pre-registration coupons.

Registration Link:




Being Agile & Yet Compliant (Public or Private)

Our SoftwareCPR unique approach to incorporating agile and lean engineering to your medical device software process training course is now open for scheduling!

  • Agile principles that align well with medical
  • Backlog management
  • Agile risk management
  • Incremental and iterative software development lifecycle management
  •  Frequent release management
  • And more!

2-days onsite (4 days virtual) with group exercises, quizzes, examples, Q&A.

Instructors: Mike Russell, Ron Baerg

Next public offering: March 7 & 28, 2024

Virtual via Zoom

Registration Link:

Register Now



Medical Device Cybersecurity (Public or Private)

This course takes a deep dive into the US FDA expectations for cybersecurity activities in the product development process with central focus on the cybersecurity risk analysis process. Overall approach will be tied to relevant standards and FDA guidance documentation. The course will follow the ISO 14971:2019 framework for overall structure but utilize IEC 62304, IEC 81001-5-1, and AAMI TIR57 for specific details regarding cybersecurity planning, risk characterization, threat modeling, and control strategies.

2-days onsite with group exercises, quizzes, examples, Q&A.

Instructor: Dr Peter Rech, 2nd instructor (optional)

Next public offering:  TBD

Corporate Office

15148 Springview St.
Tampa, FL 33624
Partners located in the US (CA, FL, MA, MN, TX) and Canada.