module 6 turning fuzzy expectations into engineering reality: quality function deployment...

14
Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 1 05/18/22 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

Upload: madison-hutchinson

Post on 27-Mar-2015

214 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 6

Turning Fuzzy Expectations Into Engineering Reality:

Quality Function Deployment

104/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

Page 2: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 6

Requirements development: Stakeholder expectations

synthesis• Two categories of Stakeholder

Expectations

– Capabilities: These are expectations that reflect functions or system behavior desired by the stakeholders

• For an Automatic Teller Machine: Ability to withdraw and deposit money 24 hours a day; Check account balances; Transfer funds between accounts, etc.

– Characteristics: These are requirements that reflect system attributes or properties

• For an Automatic Teller Machine: Quality, reliability, safety, security, cost, aesthetics, performance, accuracy, compliance with standards and protocols, etc.

2Module 3

Page 3: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 6304/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

Requirements development follows Requirements development follows a two-pronged approach for a two-pronged approach for completenesscompleteness

Operational Operational Concept/Concept/

Functional NeedFunctional Need

StakeholderStakeholderRequirementsRequirements

SystemSystemObjectives/Objectives/

Non-FunctionalNon-FunctionalRequirementsRequirements

SelectedSelectedConceptConcept

SystemSystemRequirementsRequirements

Input/OutputInput/OutputRequirementsRequirements

Checklists,I/O Matrices,

QFD

ContextDiagram,

Use Cases

Capabilities

Characteristics

Page 4: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 6

Requirements development: Stakeholder expectations

synthesis

Examples of “Capability” Expectations

• The F-35 Joint Strike Fighter must be highly survivable against current air-to-air threats

• The Airborne Laser must be highly lethal against current tactical ballistic missiles in the boost phase

• The FalconSat 5 spacecraft must have a useful life of X years

4Module 3

How do we turn these fuzzy expectations into “Concrete”

Design Requirements?

Page 5: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 6

Another Example: Another Example: “Cell Phone Must Feel “Cell Phone Must Feel Good Good in the Hand” in the Hand”

• Nokia engineers were challenged by a requirement for a new mobile phone. Customers had told them the phone had to “feel good in the hand.”

• They brainstormed a number of design parameters that might lead to a phone that satisfied the requirement:– “Length, width, depth, weight, center of gravity, curvature,

surface roughness, thermal conductivity, …”

• They recognized that considerable effort would be required to determine the correlations and establish the objectives.– Prototyping, benchmarking, etc.

504/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

Page 6: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 6604/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

Methods and Tools for developing design requirements from Characteristic expectations:

– Checklists and Hierarchies (For Legacy Systems. I.e. cars)– Input-Output Matrices– Quality Function Deployment– A Host of Other Elemental Activities Pertaining to Customer

Surveys, Benchmarking, Competition Analysis, etc.

Number of tools are useful in defining Number of tools are useful in defining system objectives and non-functional system objectives and non-functional requirementsrequirements

Page 7: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 6704/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

Quality Function Deployment is a Design Practice

Used to Facilitate Translation of Stakeholder Characteristics into System Objectives and Specifications at Each Stage of the System Design and Development Process

Objective of the QFD Method: Make the “Voice of the Customer” an Integral Part of the Research, Design, and Development Activities. This is Accomplished Through the Development of Multiple and Linked QFD Matrices

Quality Function Deployment (QFD) is useful Quality Function Deployment (QFD) is useful in developing non-functional in developing non-functional requirementsrequirements

Page 8: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 6804/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

• Developed in 1966 by Dr. Yoji Akao, to combine the concepts of Quality Assurance with Function DeploymentHe called it a “method to transform user demands into design quality, to deploy the functions forming quality, and to deploy methods for achieving the design quality into subsystems and component parts, and ultimately to specific elements of the manufacturing process.”

• “House of Quality” first used on a Mitsubishi heavy oil tanker in 1972

• QFD used in projects such as the F-35 Joint Strike Fighter

Quality Function Deployment (QFD) HistoryQuality Function Deployment (QFD) History

Ref: Wikipedia

Page 9: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 6

•From Industry Week (Nov. 1, 1993; v242, n21)– According to a survey included in this publication, organizations applying

Quality Function Deployment (QFD) for the identification and analysis of product requirements realized

• 30% to 50% reduction in engineering charges;

• 30% to 50% reduction in design cycle time;

• 20% to 60% reduction in start-up costs; and

• 30% to 50% reduction in time to market.

– Du Pont’s Beech Street Engineering Center Group, Wilmington, DE. Reports a 75% reduction in product design cycle time after making QFD an integral part of a newly revamped design structure.

– Ford Motor company adopted it in 1984, and by 1988 it was being implemented on 50 different applications

904/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

QFD has been shown to significantly enhance QFD has been shown to significantly enhance the system design processthe system design process

Design Changes Before and After Implementing QFD (Reported by Toyota)

Before QFD

After QFD

Leverage QFD, in conjunction with own Heuristics...Leverage QFD, in conjunction with own Heuristics...

Page 10: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 61004/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

Sample Quality Function Deployment Sample Quality Function Deployment (QFD) Matrix(QFD) Matrix

StakeholderCharacteristics

CustomerPriorities

Design Parameters

CorrelationMatrix

Correlation

High

Med/Hi

Medium

Lo/Med

Low

Page 11: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 61104/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

Sample Quality Function Sample Quality Function Deployment (QFD) MatrixDeployment (QFD) Matrix

CustomerNeeds

CustomerPriorities

Design Parameters

CorrelationMatrix

Correlation

High

Med/Hi

Medium

Lo/Med

Low

CapabilityBenchmarking

DDPBenchmarking

Page 12: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 61204/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

• Multiple, Linked “Houses of Quality” Are Often Developed in Order to:

– Ensure the “Voice of the Customer” Plays a Consistent Role throughout the Design and Development Process

– Maintain Traceability With Customer Needs and Requirements

• The “HOWS” in One QFD Matrix Become the “WHATS” in the Subsequent Matrix

Quality Function Deployment (QFD):Quality Function Deployment (QFD):Multiple “Houses of Quality”Multiple “Houses of Quality”

Page 13: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 61304/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

HOWS(Design Dependent Parameters)

HOW MUCH

WH

AT

S(C

usto

mer

Req

uire

men

ts)

Relationships

HOW MUCHW

HA

TS

(Des

ign

Dep

ende

nt P

aram

eter

s)

Relationships

HOWS(Design Specifications)

Quality Function Deployment (QFD):Quality Function Deployment (QFD):Example of multiple “Houses of Quality”Example of multiple “Houses of Quality”

Page 14: Module 6 Turning Fuzzy Expectations Into Engineering Reality: Quality Function Deployment 12/7/2014Copyright 2005 - Stevens Institute of Technology, Dinesh

Module 61404/10/23 Copyright 2005 - Stevens Institute of Technology, Dinesh Verma, and Mike Pennotti

Reliability Maintainability

Min

imal

M

aint

enan

ce

Reliability

Maintainability

Infrequent Visits to Service Station

Minimal Time Spent at Service Station

Competitor A

Competitor B

R(A)

R(B)

M(A)

M(B)

Targets

Competition Evaluation

A B

6

6 m(A) m(B)

m(A) m(B)

Targets

Competitor A

Competitor B

Competition Evaluation

A B

Objective

Measures

Objective

Measures

6

4

Mat

eri

al

Co

mp

os

itio

nN

um

be

r o

f M

ov

ing

Pa

rts

Sta

nd

ard

P

arts

The “HOWS” From One House Become the

“WHATS” of the Succeeding House

Quality Function Deployment (QFD):Quality Function Deployment (QFD):Multiple “Houses of Quality”Multiple “Houses of Quality”