qfd.ppt
DESCRIPTION
asTRANSCRIPT
Quality Function Deployment
QFD for Software Requirements Management
Guy DavisCarmen Zannier
Adam Geras
2 of 46
Objectives
Upon completion of this chapter, students will: Understand what Quality Function Deployment (QFD) is Understand how QFD compares to other software
development life cycles Be able to identify the primary QFD tools and concepts Be able to identify the QFD practices that might be
useful in non-QFD working environments
8 of 46
1(d) Software Engineering Context
Customer
TQM
Software Engineer
SDLC
SQFDRequirements Engineer
9 of 46
1(e) Requirements Engineering Context
Voice of theCustomerSQFD
Requirements Engineer
Customer
RequirementsPrioritization
12 of 46
2(b) Adapting QFD to Software
ProductPlanning
MeasurableObjectives
Cu
sto
mer
Vo
ice
Phase 1:Conceive
DesignPlanning
High Leve lDesign
Mea
sura
ble
Ob
ject
ives
Phase 2:Develop
ProcessPlanning
Methods,tools
Hig
h L
evel
Des
ign
Phase 3:Manufacture
ProductionPlanning
Procedures
Met
ho
ds,
to
ols
Phase 4:Deliver
14 of 46
3. The House of Quality
6. Targets6. Targets
4. Inter-relationships
4. Inter-relationships
2. P
lann
ing
Mat
rix
1. C
usto
mer
Req
uire
men
ts3. Technical
Requirements
3. TechnicalRequirements
5. Roof5. Roof
15 of 46
3(a) Customer Requirements
StructuredRequirements
Document
Group 1 Group 2 Group 3
Title Card
Group 1 Group 2 Group 3
Title Card
16 of 46
3(b) Affinity and Tree Diagrams
AttractiveAttractiveUsabilityUsability PerformancePerformance
Facilitates Climbing
Does notrestrict movement
Safe
AccessibleGear Loops
Lightweight
Attractive
Comfortable
Fits overDifferent clothes
Does notrestrict movement
Safe
AccessibleGear Loops
Lightweight
Attractive
Comfortable
Fits overDifferent clothes
Does notrestrict movement
Safe
AccessibleGear Loops
Lightweight
AttractiveComfortable
Fits overDifferent clothes Does not
restrict movement
Safe
AccessibleGear Loops
Lightweight
AttractiveComfortable
Fits overDifferent clothes
18 of 46
3(c) The Planning Matrix
Quantifies Customer Requirements. Quantifies Perceptions of Existing Products. Allows adjustment based on design team.
COMFORTABLE 5 4 3 2 1
EASY TO PUT ON 5 4 3 2 1
FITS OVER DIFFERENT CLOTHES 5 4 3 2 1
19 of 46
Customer Satisfaction – existing products fulfilling specified requirements.
Improvement Ratio = Planned Performance / Existing Performance
Sales Point – weight for marketability
Overall Weighting = Importance Weighting x Improvement Ratio X Sales Point
3(c) The Planning Matrix
20 of 46
3(c) The Planning Matrix
Comfortable
Easy to Put On
Fits over different clothes
Impo
rtan
ce W
eigh
ting
Cus
tom
er S
atis
fact
ion
Plan
ned
Satis
fact
ion
Impr
ovem
ent R
atio
Sale
s Po
int
Ove
rall
Wei
ghtin
g
Impo
rtan
ce W
eigh
ting
Cus
tom
er S
atis
fact
ion
Plan
ned
Satis
fact
ion
Impr
ovem
ent R
atio
Sale
s Po
int
Ove
rall
Wei
ghtin
g
5
1
2
2
1
3
5
2
4
2.5
2
1.3
1.4
1.0
1.1
17.5
2
2.9
21 of 46
3(d) Technical Requirements
Engineering Characteristics, Voice of the Company.
Identify Measurable Characteristics related to Customer Requirements.
Direction of change included to lead to improvement of product performance.
22 of 46
Critical Question:
How significant is technical requirement A in satisfying customer requirement B?
3(e) Interrelationships
Between customer requirements and technical requirements
Translation and correlation step Critical to generate consensus between
development team and customers.
23 of 46
3(e) Interrelationships
6.0Safe
11.2
3.0
Technical Priority
Light weight
Does not restrict movement
6.0Safe
11.2
3.0
Technical Priority
Light weight
Does not restrict movement
Har
ness
wei
ght
Web
bing
str
engt
h
# of
buc
kles
High -
Medium -
Low -
Ove
rall
Wei
ghti
ng
(9)
(3)
(1)
24 of 46
3(f) “The Roof”
Considers impact of technical requirements on each other
Feature to feature comparison Augment or impede?
Critical Question: Does improving one requirement cause a
deterioration or improvement in another requirement?
25 of 46
+ positive/supporting
Mee
ts s
tand
ards
Har
ness
wei
ght
Web
bing
str
engt
h
Pad
ding
thic
knes
s Legend
- negative/tradeoff
3(f) “The Roof”
26 of 46
3(g) Targets
Summarize previous steps
Draw conclusions Consists of:
Technical Priorities Competitive
Benchmarks Final Product Targets
Results from previous steps: Customer requirements Prioritized customer
requirements Technical requirements Correlated requirements Feature
interdependencies
27 of 46
3(h) Technical Priorities
6.0Safe
11.2
3.0
Technical Priority
Light weight
Does not restrict movement
6.0Safe
11.2
3.0
Technical Priority
Light weight
Does not restrict movement
Har
ness
wei
ght
Web
bing
str
engt
h
# of
buc
kles
High -
Medium -
Low -
Ove
rall
Wei
ghti
ng
(9)
(3)
(1)
28 of 46
3(i) Competitive Benchmarks
Competitor #2
Existing System
Competitor #1
Competitor #2
Existing System
Competitor #1W
ebbi
ng s
tren
gth
Mee
ts s
tand
ards
Pad
ding
thic
knes
s
# of
buc
kles
Har
ness
wei
ght
29 of 46
Target System
Web
bing
str
engt
h
Mee
ts s
tand
ards
Pad
ding
thic
k nes
s
# o f
bu c
kles
Har
ness
wei
ght
3(j) Final Product Targets
30 of 46
3(k) House of Quality Summary
Inputs: Customer requirements Technical requirements Customer priorities Market reality / competitive analysis Organization’s strengths & weaknesses
Outputs Prioritized technical requirements Measurable, testable goals
32 of 46
3(l) House of Quality Pros and Cons
Pros: Generates specific technical requirements Requirements are traceable Follows a repeatable, quantitative process Effectively translates Voice of the Customer Records rationale for each technical requirement
Cons: Time-consuming process for >10 requirements Data storage, manipulation and maintenance costs Very dependent on customer requirement gathering Inflexible to changing requirements; must recalculate
45 of 46
QFD Designer
QFD Designer Business Improvement Software
Templates to define various aspects of QFD Icons, graphs, simplify add/delete