Quality Function Deployment
QFD for Software Requirements Management
Guy Davis Carmen Zannier Adam Geras
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
2 of 46
1. Introduction to QFD
?
Requirements Engineer
QFD
3 of 46
1(a) QFD - Definition
VOICE OF THE CUSTOMER
+ =
QFD
CUSTOMER SATISFACTION
4 of 46
1(a) QFD Definition (Cont.)
[ASI, 2000]
5 of 46
1(b) QFD - Benefits
[ASI, 2000]
6 of 46
1(c) QFD - History
STATISTICAL PROCESS CONTROL DESIGN QUALITY VALUE ENGINEERING QFD
7 of 46
1(d) Software Engineering Context
TQM
SDLC
Requirements Engineer
SQFD
Customer
Software Engineer
8 of 46
1(e) Requirements Engineering Context
Requirements Engineer
SQFD
Voice of the Customer Requirements Prioritization
Customer
9 of 46
2. QFD Life Cycle Considerations
QFD Process SQFD Process
10 of 46
2(a) Traditional QFD Phases
11 of 46
2(b) Adapting QFD to Software
Measurable Objectives
High Leve l Design
Methods, tools
Procedures
Customer Voice
Product Planning
Design Planning
Process Planning
Methods, tools
Measurable Objectives
High Level Design
Production Planning
Phase 1: Conceive
Phase 2: Develop
Phase 3: Manufacture
Phase 4: Deliver
12 of 46
2(b) SQFD Process
13 of 46
3. The House of Quality
5. 5.Roof Roof 3. 3.Technical Technical Requirements Requirements
4. 4.InterInterrelationships relationships
6. 6.Targets Targets
2. Planning Matrix
1. Customer Requirements
14 of 46
3(a) Customer Requirements
Structured Requirements Document
Title Card Group 1 Group 2 Group 3
15 of 46
3(b) Affinity and Tree Diagrams
Does not restrict movement Fits over Different clothes Safe Attractive Lightweight Accessible Gear Loops Lightweight Comfortable Comfortable Fits over Different clothes Accessible Gear Loops Attractive Does not restrict movement Safe
Facilitates Climbing Usability Attractive Performance
16 of 46
Exercise 1 Affinity Workshop
17 of 46
3(c) The Planning Matrix
Quantifies Customer Requirements. Quantifies Perceptions of Existing Products. Allows adjustment based on design team.
COMFORTABLE EASY TO PUT ON FITS OVER DIFFERENT CLOTHES 5 5 4 4 3 3 2 2 1 1
18 of 46
3(c) The Planning Matrix
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
19 of 46
3(c) The Planning Matrix
hti me ng r S Pla ati nn sfa ed cti on Sa t isf Im act pr ion ov em en tR Sa ati les o Po int Ov era ll W eig hti ng
5 2 4 2.5 2 1.3 1.4 1.0 1.1 17.5 2 2.9
20 of 46
rta po Im
Comfortable Easy to Put On Fits over different clothes 2 5 1
nc
2 1 3
Cu
sto
eW
eig
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.
21 of 46
3(e) Interrelationships
Between customer requirements and technical requirements Translation and correlation step Critical to generate consensus between development team and customers. Critical Question:
How significant is technical requirement A in satisfying customer requirement B?
22 of 46
3(e) Interrelationships
Technical Requirements
Harness weight
High Medium Low Customer Requirements
(9) (3) (1)
Light weight Does not restrict movement Safe Technical Priority
3.0 11.2 6.0
Overall Weighting
Webbing strength
# of buckles
23 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?
24 of 46
3(f) The Roof
Webbing strength
Padding thickness
Legend
Meets standards
Harness weight
+ -
positive/ supporting negative/ tradeoff
25 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
26 of 46
3(h) Technical Priorities
Harness weight
High Medium Low Light weight Does not restrict movement Safe Technical Priority (9) (3) (1)
3.0 11.2 6.0
Overall Weighting
Webbing strength
# of buckles
27 of 46
3(i) Competitive Benchmarks
Webbing strength Padding thickness Meets standards Harness weight
Existing System Competitor #1 Competitor #2
28 of 46
# of buckles
3(j) Final Product Targets
Target System
29 of 46
3(k) House of Quality Summary
Inputs:
Customer requirements Technical requirements Customer priorities Market reality / competitive analysis Organizations strengths & weaknesses
Prioritized technical requirements Measurable, testable goals
30 of 46
Outputs
Exercise 2 Build a House of Quality
31 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
32 of 46
4. QFD Life Cycle Comparisons
XP CLEANROOM
RUP
? ?
JAD
?
QFD
SASD
? ?
PD
SSM
?
RAD
33 of 46
4(a) QFD and Cleanroom
[SAIC, 2001]
34 of 46
4(b) QFD and SASD
Environmental Models Behavioural Models Implementation Models
35 of 46
4(c) QFD vs. JAD
QFD is a Quality-focused approach
JAD is a communication-focused approach
36 of 46
4(d) QFD and PD
Workers and Designers work together
37 of 46
4(e) QFD vs. RAD
QUALITY
SPEED
38 of 46
4(f) QFD vs. SSM
[Wilson, 2001]
39 of 46
4(g) QFD and RUP
[Ronin, 2001]
40 of 46
4(h) QFD and XP
[Wells, 2001]
41 of 46
5. Conclusions
?
Requirements Engineer
QFD
42 of 46
5. Conclusions (Cont.)
?
Requirements Engineer
QFD
43 of 46
5. Conclusions (Cont.)
?
Requirements Engineer
QFD
44 of 46
QFD Designer
QFD Designer Business Improvement Software Templates to define various aspects of QFD Icons, graphs, simplify add/delete
45 of 46
References
46 of 46
