| Name | Quality Function Deployment |
| Abbreviation | QFD |
| Learning Cost | 160 |
| Playing Cost | 400 |
| Suggested Phases | 1,2 |
Engineers
| Mechanical Engineer | Industrial Design | System Engineer | Electrical Engineer | Production Engineer | Software Engineer |
| ✔ | ✔ | ✔ | ✔ | ✔ | ✗ |
Technique and Issue Views
| BusinessNeeds | Stakeholder | Stakeholder Needs | System Requirements | System Structure Architecture |
| ✔ | ✔ | ✔ | ✔ | ✔ |
| System Functional Architecture | Detail Hardware Design | Detail Service Design | Detail Software Design | Manufacturing Operations |
| ✗ | ✗ | ✗ | ✗ | ✔ |
Technique Traits
| Identify Stakeholders | Elicit Needs | Remove Ambiguity | Layman's Terms | Technical Terms | Teamworkings |
| 1 | 1 | 2 | 1 | 2 | 2 |
| Traceability | Prioritizing | Exploring Breadth | Inside the Box | Outside the box | V&V |
| 3 | 4 | 3 | 3 | 0 | 2 |
Verification and Validation
| Analysis | Calculus | Inspection | Demonstration | Test |
| ✔ | ✗ | ✗ | ✗ | ✗ |
Quality function deployment (QFD) is a tool to help transform customer needs into engineering characteristics and appropriate test methods for a product or service. Originally designed in 1966 by Yoji Akao, it helps create operational definitions of the requirements, which may be vague when first expressed. QFD prioritizes each product or service characteristic while simultaneously setting development targets for the product or service [1]. First applied at the Kobe Shipyard in Japan [2], QFD was used to solve the problems of communicating customer’s needs to the engineering value that the product will deliver, so the product will satisfy the customer[3]. The technique is applied in a variety of services, consumer products, military needs, and emerging technology products [1].
