Product Design Analysis Mechanical Engineering Notes | EduRev

 Page 1


© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
1 
Product Design Analysis 
Page 2


© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
1 
Product Design Analysis 
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
2 
Objectives 
? To explain the product design process as 
top-down and user centered 
? To list and explain several needs 
elicitation heuristics and techniques 
? To describe how to analyze and 
document needs elicitation results 
? To explain how to check analysis results 
Page 3


© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
1 
Product Design Analysis 
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
2 
Objectives 
? To explain the product design process as 
top-down and user centered 
? To list and explain several needs 
elicitation heuristics and techniques 
? To describe how to analyze and 
document needs elicitation results 
? To explain how to check analysis results 
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
3 
Topics 
? Product design process overview 
? Needs versus requirements 
? Needs elicitation challenges, heuristics, 
and techniques 
? Documenting domain, goals, and needs 
? Modeling 
? Checking needs documentation 
Page 4


© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
1 
Product Design Analysis 
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
2 
Objectives 
? To explain the product design process as 
top-down and user centered 
? To list and explain several needs 
elicitation heuristics and techniques 
? To describe how to analyze and 
document needs elicitation results 
? To explain how to check analysis results 
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
3 
Topics 
? Product design process overview 
? Needs versus requirements 
? Needs elicitation challenges, heuristics, 
and techniques 
? Documenting domain, goals, and needs 
? Modeling 
? Checking needs documentation 
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
4 
Software Product Design Process 
Generic Software Product Design
Project Mission Statement : Problem
SRS : Solution
Project Mission 
Statement
SRS
[adequate]
[else]
[complete]
[else]
Analyze Product 
Design Problem
Elicit/Analyze 
Detailed Needs
Generate/Improve 
Candidate Requirements
Evaluate Candidate 
Requirements
Select Requirements
Finalize Requirements
Page 5


© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
1 
Product Design Analysis 
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
2 
Objectives 
? To explain the product design process as 
top-down and user centered 
? To list and explain several needs 
elicitation heuristics and techniques 
? To describe how to analyze and 
document needs elicitation results 
? To explain how to check analysis results 
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
3 
Topics 
? Product design process overview 
? Needs versus requirements 
? Needs elicitation challenges, heuristics, 
and techniques 
? Documenting domain, goals, and needs 
? Modeling 
? Checking needs documentation 
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
4 
Software Product Design Process 
Generic Software Product Design
Project Mission Statement : Problem
SRS : Solution
Project Mission 
Statement
SRS
[adequate]
[else]
[complete]
[else]
Analyze Product 
Design Problem
Elicit/Analyze 
Detailed Needs
Generate/Improve 
Candidate Requirements
Evaluate Candidate 
Requirements
Select Requirements
Finalize Requirements
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley  
5 
Top-Down Process 
? Design resolution begins with abstract 
requirements and refines them 
? Designers move from user-level to 
operational-level to physical level 
requirements 
? Main activity in the resolution loop