M
mr.mike
Hi Everyone,
I've been browsing some of the posted templates for documenting design inputs and outputs, and it seems to me that they are all too simplistic and don't really give a clear picture of how various inputs feed into outputs.
The reason being that design & product realization (at least our process) occurs in stages, with the output of one feeding into the inputs of another.
So, I'm wondering if a "stage-by-stage" input/output document might make the product-realization process more clear. Below is an example, any feedback appreciated.
******
Stage 1: Planning
Inputs (examples): International Standards, Public-domain market research...
Outputs (example): Development Plan document, System Requirements Document...
Stage 2: Design
Inputs: Outputs of stage 1
Outputs (examples): Validation Plan, Risk Management File, Component specifications, Assembly instructions...
Stage 3: Prototype
Inputs: Outputs of stage 2
Outputs: Test reports & Device history records
*****
The above is obviously just an outline, and the actual document would be much more detailed. What I want to know, is if this is overkill? ...or maybe I'm totally missing the point of what a design input/ouput document is supposed to contain?
Feeback much appreciated,
MM.
I've been browsing some of the posted templates for documenting design inputs and outputs, and it seems to me that they are all too simplistic and don't really give a clear picture of how various inputs feed into outputs.
The reason being that design & product realization (at least our process) occurs in stages, with the output of one feeding into the inputs of another.
So, I'm wondering if a "stage-by-stage" input/output document might make the product-realization process more clear. Below is an example, any feedback appreciated.
******
Stage 1: Planning
Inputs (examples): International Standards, Public-domain market research...
Outputs (example): Development Plan document, System Requirements Document...
Stage 2: Design
Inputs: Outputs of stage 1
Outputs (examples): Validation Plan, Risk Management File, Component specifications, Assembly instructions...
Stage 3: Prototype
Inputs: Outputs of stage 2
Outputs: Test reports & Device history records
*****
The above is obviously just an outline, and the actual document would be much more detailed. What I want to know, is if this is overkill? ...or maybe I'm totally missing the point of what a design input/ouput document is supposed to contain?
Feeback much appreciated,
MM.