Customer needs are expressed in the language of the customer. For product development these needs are to be developed into a metric and value. For example the customer language may be lasts for a long time. The specification may be life of the part is 2 years. (life of the part is the metric and 2 years is the value).
For simple products product specification can be specified once. But for technology intensive products the specification are once set based on customers and after the development team does external search and internal search, they are reset based the capabilities of available technologies.
Product Specifications
1. Prepare List of Metrics
2. Collect Competitive Benchmarking Information
3. Set Ideal and Marginally Acceptable Target Values
Setting the Final Specifications
1. Develop technical models of the product
2. Develop a cost model of the product
3. Refine the specifications, making trade-offs where necessary
4. Flow down the specifications as appropriate
The product specification plays various roles in the product development process:
Guidance to designers
Identify trade-off between requirements
A checklist e.g. during milestone meeting
Evaluation of solutions to select the one that is most suited to the specification
An agreement within the design team, and as an agreement with the client e.g. companysupplier
agreement on fulfilling the design task.
To trace the likelihood of change propagation.
Product overview
Ref: INTERNATIONAL DESIGN CONFERENCE - DESIGN 2010
Dubrovnik - Croatia, May 17 - 20, 2010.
THE ROLE OF A SPECIFICATION IN THE DESIGN PROCESS: A CASE STUDY
M. N. Sudin, S. Ahmed-Kristensen and M. M. Andreasen
Elicitation and Development of Requirements Through Integrated Methods
http://www.me.umn.edu/courses/me4054/assignments/pds.html
Updated 2 August 2016, 12 December 2015
No comments:
Post a Comment