The Cove Business Standards Discussion Forums
Design Input/Output and Design V&V (Verification and Validation) Interpretations
Please read this thread...
Software update
Design Input/Output and Design V&V (Verification and Validation) Interpretations
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > > > >
Forum Username

Elsmar Cove Forum Visitor Notice(s)

Wooden Line

Design Input/Output and Design V&V (Verification and Validation) Interpretations

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


Howard's
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


Some Related Topic Tags
definitions, design and development, design inputs and outputs, design validation, design verification, fda (food and drug administration), fda requirements, requirements and specifications, medical devices
Reply
 
Thread Tools Search this Thread Rate Thread Content Display Modes
  Post Number #1  
Old 9th June 2011, 04:33 PM
dweebie

 
 
Total Posts: 6
Please Help! Design Input/Output and Design V&V (Verification and Validation) Interpretations

Hi,

I was wondering is someone could help me interpret the following statements I once heard from a Design control expert:

***********************************

Requirements = design input: broader than specifications and concern (are derived from) intended use(s) and user needs (testable natural language).

Specifications = design output: translates requirements into detailed measurable descriptions (engineering language).

Requirements must be verifiable i.e. quantified through specifications in a way that can be verified.

It might require several verification-results (against specifications) to demonstrate compliance to one single design input requirement.

*****************

To me this sounds as is requirements (design input) are verified by demonstrating that the derived specifications (design output) can be met, because the underlying assumption is that the specifications meet the requirements. Validation, on the other hand, is done by testing directly against the requirement (which represents the user needs and intended use). But how does this fit with: "verification must show that design output meets design input"?

I found an blog entry on mddi, which in my opinion supports the above, by stating that "design validation is really what happens near the end of the design or redesign of a medical device, it is done as a set of various activities to answer the question, does this design solution actually perform and function as I intend it to and does it meet my user needs. Design verification activities provide theoretical assurance that the design is appropriate in regards to your defined design input requirements, design validation provides evidence beyond theoretical that the device you designed is truly safe and effective within the context of those same design input requirements".

In additions to this, the FDA state in their "Medical device quality systems manual" that "design verification is always done versus specifications".

Do I understand the concept of verification and validation correctly? How do you interpret the above?

Best regards

Last edited by dweebie; 11th June 2011 at 04:29 PM.

Sponsored Links
  Post Number #2  
Old 9th June 2011, 04:44 PM
Marc's Avatar
Marc

 
 
Total Posts: 26,582
I Say... Re: Design Input/Output and Design V&V (Verification and Validation) Interpretations

Quote:
In Reply to Parent Post by dweebie View Post

<snip> "design validation is really what happens near the end of the design or redesign of a medical device, it is done as a set of various activities to answer the question, does this design solution actually perform and function as I intend it to and does it meet my user needs. Design verification activities provide theoretical assurance that the design is appropriate in regards to your defined design input requirements, design validation provides evidence beyond theoretical that the device you designed is truly safe and effective within the context of those same design input requirements". <snip>
Yup - That's it in a nutshell.

Verification = Theoretical (the old "According to my calculations...")
Validation = Actual as determined by testing (often done on a prototype, but in some cases validation is done through actual use - depends upon the product and the industry).
  Post Number #3  
Old 9th June 2011, 05:05 PM
dweebie

 
 
Total Posts: 6
Re: Design Input/Output and Design V&V (Verification and Validation) Interpretations

Thanks for your quick reply. I really appreciate it.

The blog entry's real message is that validation is more than user testing (which is a common misconception). As I see it right now, validation is basically about simulating use scenarios, to check that the device indeed does what is required of it in the real world post release, including by the users. This could concern e.g. driving a car into a wall (can our design really survive a real-life crash), taking a plane on its first flight (can our design really fly), confirming the shelf-life of a product through accelerated tests (can our design really last 2 years) etc.

Does this sound right?

Last edited by dweebie; 11th June 2011 at 04:29 PM.
  Post Number #4  
Old 9th June 2011, 05:22 PM
Marc's Avatar
Marc

 
 
Total Posts: 26,582
Re: Design Input/Output and Design V&V (Verification and Validation) Interpretations

That's my understanding.
  Post Number #5  
Old 15th June 2011, 03:25 PM
gholland

 
 
Total Posts: 101
Re: Design Input/Output and Design V&V (Verification and Validation) Interpretations

Validation is also ensuring your device meets the user needs. How you define your user needs is up to you but as you develop an idea you would have a set of user needs you are trying to meet. Something like 'the customer needs the device to be used in xxx environment' for example. Then you would go out and show that the device is usable in whatever environment you chose (laminar flow hood, clean room, whatever). You have to show that you understand what the user needs are and that your device meets them.
  Post Number #6  
Old 15th June 2011, 03:47 PM
dweebie

 
 
Total Posts: 6
Re: Design Input/Output and Design V&V (Verification and Validation) Interpretations

Thanks Gholland for your reply. I agree with what you say - validation is also about demonstrating that the device meets the user needs, in addition to intended use(s).

As I understand the literature on Design controls, user needs + intended use(s) are expressed as (organized into) testable design input requirements (the "what", written in a language that all stakeholders can understand), such as "the device must tolerate being used in xxx environment for the stated period of time" (similar to your example). Specifications are the "how" (translated from requirements), and are typically concept-dependent. The link between requirements and user needs is called requirements validation. The link between implementation and requirements is called design validation.

What do you think? Any comments anyone?
  Post Number #7  
Old 15th June 2011, 04:01 PM
Marc's Avatar
Marc

 
 
Total Posts: 26,582
Re: Design Input/Output and Design V&V (Verification and Validation) Interpretations

Typically ensuring your device meets the user needs starts in the design stage prior to design verification. User needs is part of the design process "front end" inputs.

Validation is more "Does it work as intended".
  Post Number #8  
Old 18th December 2013, 11:35 PM
Julie O

 
 
Total Posts: 221
Re: Design Input/Output and Design V&V (Verification and Validation) Interpretations

21CFR 820.3 Definitions:

Verification means confirmation by examination and provision of objective evidence that specified requirements have been fulfilled.

Design validation means establishing by objective evidence that device specifications conform with user needs and intended use(s).
Reply

Lower Navigation Bar
Go Back   The Elsmar Cove Business Systems and Standards Discussion Forums > > > >

Bookmarks



Visitors Currently Viewing this Thread: 1 (0 Registered Visitors (Members) and 1 Unregistered Guest Visitors)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Forum Search
Display Modes Rate Thread Content
Rate Thread Content:

Forum Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Emoticons are On
[IMG] code is On
HTML code is Off


Similar Discussion Threads
Discussion Thread Title Thread Starter Forum Replies Last Post or Poll Vote
Design Input vs. Design Output - What constitutes Design Input? tantan Design and Development of Products and Processes 11 2nd January 2014 08:11 PM
Design Input & Output in Stages - Overkill? mr.mike ISO 13485:2016 - Medical Device Quality Management Systems 16 13th May 2011 01:08 AM
Are some Design Input elements part of the Design Output? sagai 21 CFR Part 820 - US FDA Quality System Regulations (QSR) 2 12th October 2010 01:26 AM
Is Prototyping Design Output or Design Verification? dyeysi Design and Development of Products and Processes 12 1st April 2008 01:05 PM
Design/Development Output & Verification - ISO 9001 7.3.3 Design & Development Output Curt72 Design and Development of Products and Processes 1 24th March 2006 08:03 PM



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



Misc. Internal Links


NOTE: This forum uses "Cookies"