Definition User Needs - Concrete definition for "User Needs" as required by the FDA

[david316]

Hello,

I don't suppose someone would be able to give me a concrete definition for "User Needs" as required by the FDA. What I ideally want is to screen user needs requirements to see if they are really a user need and hence require validation. For example, I would argue there is a difference between user "wants" and "needs". For example a user may want something to be easy to use but this isn't necessary a user need.

Thanks.

 

[sagai]

That's actually a non-functional user needs for me with a potential to refine it further being easy to digest by engineering.
Cheers

 

[yodon]

We typically have a 'Product Requirements' or 'Marketing Requirements' type document that covers user needs. These are, though, framed as "shalls" and they form the basis for validation. So, indeed, there are typically no "wants" in there. As sagai notes, these requirements are then elaborated as system requirements which is "engineering's answer" to the user needs (with appropriate tracing between the sets).