书籍详情
有效需求分析（英文本）
作者：（美）Ralph R.Young编著
出版社：科学出版社
出版时间：2004-01-01
ISBN：9787030124685
定价：¥40.00
购买这本书可以去
内容简介
本书从管理和技术两个角度，以案例方式阐述了软件项目中与需求分析相关的各种问题，力图让读者能够对需求分析的框架体系和过程形成较为清晰的认识，在实践中准确了解客户的业务需求，正确调配各种资源，更加准确地把握项目的方向，保证整个项目的成功。本书内容丰富翔实，实用性强，适合作为高等学校本科生和研究生的软件工程类教材，同时也可供软件企业对开发和项目管理人员进行培训使用。本书原版配有光盘，包括书中出现的部分插图和模板文件，读者如有需要，请与我社联系（电话：010-62622941）。
作者简介
暂缺《有效需求分析（英文本）》作者简介
目录
List of Figures xi
Foreword xv
Preface xvii
Acknowledgments xxiii
PART I BACKGROUND 1
CHAPTER 1 INTRODUCTION 3
The State of the Industry Today 3
The Need to Use Effective Requirements Practices 6
The Requirements Process 7
What Is a Process? 7
What Is the Requirements Process? 9
Benefits of a Process Approach 11
Pitfalls of Using a Process Approach 12
About This Book 14
Roles 14
Key Terms 14
A Requirements Taxonomy 16
Systems and Software Engineers 17
Intended Audience 17
Recommended Mind-set for Readers of This Book 18
The "Team," the "Project," and the "Project Manager" 18
Footnotes in This Book 19
Key References and Suggested Readings 19
Upcoming Topics 19
Summary 20
Key References and Suggested Readings 20
PART II RECOMMENDED REQUIREMENTS
PRACTICES 25
CHAPTER 2 COMMIT TO THE APPROACH 27
What Do We Mean by Commitment? 28
How Can Commitment Be Attained and Maintained? 30
Recommendations to Assist in Evolving the Partnering Approach 37
Involve Managers with Authority in the Partnering Workshop 38
Develop a Requirements Plan 38
Utilize a Set of Mechanisms, Methods, Techniques, and Tools 40
Work Toward a Quality Culture 40
Summary 42
Key References and Suggested Readings 42
CHAPTER 3 ESTABLISH AND UTILIZE A JOINT
TEAM RESPONSIBLE FOR THE
REQUIREMENTS 45
What Is a"Joint Team"? 46
What Does the Joint Team Do? 47
How Is the Joint Team Created? 48
Who Should Be on the Joint Team? 48
How Often Should the Joint Team Meet? 49
What Metrics Need to Be Created and Tracked? 49
Calculating Return on Investment (ROI) from Using Effective
Requirements Practices 50
Customer and Supplier Roles 50
Summary 53
Key References and Suggested Readings 54
CHAPTER 4 DEFINE THE REAL CUSTOMER NEEDS 57
Recommendations to Facilitate Getting to the Real Requirements 59
Invest More in the Requirements Process 60
Train PMs to Pay More Attention to the Requirements Process 62
Identify a Project Champion 63
Define the Project Vision and Scope 64
Identify a Requirements Engineer and Utilize Domain Experts to Perform
Requirements Engineering Tasks 65
Train Developers Not to Make Requirements Decisions
and Not to Gold Plate 74
Utilize a Variety of Techniques to Elicit Customer and User Requirements and
Expectations 74
Use Cases 75
Train Requirements Engineers to Write Good Requirements 79
The Impact of Requirements Errors 79
The Importance of Requirements to Program Costs 80
What Is a Good Requirement? 82
Document the Rationale for Each Requirement 84
Utilize Methods and Automated Tools to Analyze, Prioritize, and
Track Requirements 85
Approaches, Tools, and Methods for Prioritizing Requirements 87
Collect Requirements from Multiple Viewpoints 89
Consider the Use of Formal Methods When Appropriate 90
Pitfalls 90
Summary 91
Key References and Suggested Readings 92
CHAPTER 5 USE AND CONTINUALLY IMPROVE
A REQUIREMENTS PROCESS 97
What Is a Process? 98
How Is a Process Designed? 99
Why Is a Requirements Process Needed? 103
Goals of Requirements Engineers 107
A Sample Requirements Process 110
How Can Organizations Create or Tailor a Requirements Process? 122
Tailoring of Processes 123
Web Support: An Organizational Process Asset Library 124
Summary 125
Key References and Suggested Readings 125
CHAPTER 6 ITERATE THE SYSTEM REQUIREMENTS
AND ARCHITECTURE REPEATEDLY 131
The System Engineering Process 132
Recommendations 134
Consider the "Designability" of the System When Addressing the Requirements 134
Allocate Requirements to Functional Partitions, Objects, People, or Support
Elements to Support Synthesis of Solutions 136
Utilize a System Architecture Process 136
Consider Open Systems Standards 146
Guidelines for"Architecting" 151
Another View 153
Summary 154
Key References and Suggested Readings 154
CHAPTER 7 USE A MECHANISM TO MAINTAIN
PROJECT COMMUNICATION 159
Setting the Stage 160
Natural Human Tendency 160
A Proactive Approach to Achieve Effective Communication 161
An Example Mechanism 162
When Negativism Shows Up 164
Another Valuable Mechanism--Brown Bags 165
Guidelines for Effective Meetings 165
Guidelines for Effective E-mail Communication 167
The Value of a Common Vocabulary 172
The Use of Vertical Experts 173
Avoid Multiple Locations 174
A Final Recommendation 174
Summary 174
Key References and Suggested Readings 175
CHAPTER 8 SELECT FAMILIAR METHODS AND
MAINTAIN A SET OF WORK PRODUCTS 179
The Foundation for System Development 180
What Are the Candidate Methods and Techniques? 180
Which Methods and Techniques Are Best? 182
Use of Function Points for Software Estimation 189
Quality Function Deployment 190
What Comprises the Requirements Specification? 192
The Rationale for Prioritizing Requirements 193
Summary 195
Key References and Suggested Readings 196
CHAPTER 9 PERFORM REQUIREMENTS VERIFICATION
AND VALIDATION 201
V&V Terminology 202
The Importance of V&V 203
V&V Planning 203
Verification Methods 207
V&V Techniques 208
Using Traceability to Support Verification 208
A Structured Approach to Testing 210
Recommendations 211
Pitfalls 211
Summary 213
Key References and Suggested Readings 214
CHAPTER 10 PROVIDE AN EFFECTIVE MECHANISM
TO ACCOMMODATE REQUIREMENTS
CHANGES 217
Why Such Emphasis? 218
Planning for Changes in Requirements 219
The Recommended Mechanism 221
Requirements Leakage 221
Focus on What Counts! 224
How Much Can Requirements Change? 224
A Way to Deal with Requirements Creep Contractually 225
Other Recommendations 227
Summary 229
Key References and Suggested Readings 229
CHAPTER 11 PERFORM THE DEVELOPMENT EFFORT
USING KNOWN, FAMILIAR PROVEN
INDUSTRY, ORGANIZATIONAL, AND
PROJECT BEST PRACTICES 231
What's All the Fuss? 233
What Can We Do About It? 234
Recommendations 235
Provide to the Development Team an Understanding of the Relevant Policies,
Processes, and Procedures to Be Used 235
Utilize a Practical, Effective Project Management Approach 235
Ensure That Selected Members of the Development Team Have Domain
Knowledge 244
Perform the Development Effort Using Known (Trained), Proven Processes,
Mechanisms, Methods, Techniques, and Tools 244
Provide and Utilize Mechanisms to Foster Effective Communications Throughout the
Development Team 247
Utilize Peer Reviews and Inspections to Remove Defects from Processes and Work
Products 248
Ensure That Configuration Management Is Effective 250
Foster an Independent QA Role That Proactively Assists and Supports the
Development Team and Provides Value to the Project 251
Ensure That Subcontractors Are Managed So That Their Contributions Are
Effective 252
Use Appropriate, Useful Metrics to Manage the Project 255
Ensure That a Systematic Approach to Involving the Customer in This Entire
Effort ls Working 258
Manage Processes Quantitatively. Also, Use a Defect Prevention (DP) Process, a
Technology Change Management (TCM) Process, and a Process Change
Management (PCM) Process. Perform Extensive Reinsertion and Reuse
Throughout the Organization 261
Musings on Project Management 262
Summary 265
Key References and Suggested Readings 266
PART III WHAT TO DO NEXT 271
CHAPTER 12 HOW TO PROCEED 273
Common Issues 273
Key Factors in Addressing These Issues 275
The Customer 275
Requirements as a Key Driver to Any Systems or Software Effort 275
Financing Improvements in the Requirements Process 275
Survival of the Fittest 276
Management Awareness and Expectations 276
Metrics 276
The Development Team 277
Where to Start 277
How to Prioritize Needed Efforts 284
Relationship of the Recommended Effective Requirements
Practices to the CMM 289
But I Have So Many Things to Do... 291
What If We Are "Further Along" on Our Project? 293
Summary 293
Key References and Suggested Readings 294
Epilogue 299
List of Acronyms 301
Glossary 309
Credits 321
Bibliography 325
Author Index 345
Subject Index 349
Foreword xv
Preface xvii
Acknowledgments xxiii
PART I BACKGROUND 1
CHAPTER 1 INTRODUCTION 3
The State of the Industry Today 3
The Need to Use Effective Requirements Practices 6
The Requirements Process 7
What Is a Process? 7
What Is the Requirements Process? 9
Benefits of a Process Approach 11
Pitfalls of Using a Process Approach 12
About This Book 14
Roles 14
Key Terms 14
A Requirements Taxonomy 16
Systems and Software Engineers 17
Intended Audience 17
Recommended Mind-set for Readers of This Book 18
The "Team," the "Project," and the "Project Manager" 18
Footnotes in This Book 19
Key References and Suggested Readings 19
Upcoming Topics 19
Summary 20
Key References and Suggested Readings 20
PART II RECOMMENDED REQUIREMENTS
PRACTICES 25
CHAPTER 2 COMMIT TO THE APPROACH 27
What Do We Mean by Commitment? 28
How Can Commitment Be Attained and Maintained? 30
Recommendations to Assist in Evolving the Partnering Approach 37
Involve Managers with Authority in the Partnering Workshop 38
Develop a Requirements Plan 38
Utilize a Set of Mechanisms, Methods, Techniques, and Tools 40
Work Toward a Quality Culture 40
Summary 42
Key References and Suggested Readings 42
CHAPTER 3 ESTABLISH AND UTILIZE A JOINT
TEAM RESPONSIBLE FOR THE
REQUIREMENTS 45
What Is a"Joint Team"? 46
What Does the Joint Team Do? 47
How Is the Joint Team Created? 48
Who Should Be on the Joint Team? 48
How Often Should the Joint Team Meet? 49
What Metrics Need to Be Created and Tracked? 49
Calculating Return on Investment (ROI) from Using Effective
Requirements Practices 50
Customer and Supplier Roles 50
Summary 53
Key References and Suggested Readings 54
CHAPTER 4 DEFINE THE REAL CUSTOMER NEEDS 57
Recommendations to Facilitate Getting to the Real Requirements 59
Invest More in the Requirements Process 60
Train PMs to Pay More Attention to the Requirements Process 62
Identify a Project Champion 63
Define the Project Vision and Scope 64
Identify a Requirements Engineer and Utilize Domain Experts to Perform
Requirements Engineering Tasks 65
Train Developers Not to Make Requirements Decisions
and Not to Gold Plate 74
Utilize a Variety of Techniques to Elicit Customer and User Requirements and
Expectations 74
Use Cases 75
Train Requirements Engineers to Write Good Requirements 79
The Impact of Requirements Errors 79
The Importance of Requirements to Program Costs 80
What Is a Good Requirement? 82
Document the Rationale for Each Requirement 84
Utilize Methods and Automated Tools to Analyze, Prioritize, and
Track Requirements 85
Approaches, Tools, and Methods for Prioritizing Requirements 87
Collect Requirements from Multiple Viewpoints 89
Consider the Use of Formal Methods When Appropriate 90
Pitfalls 90
Summary 91
Key References and Suggested Readings 92
CHAPTER 5 USE AND CONTINUALLY IMPROVE
A REQUIREMENTS PROCESS 97
What Is a Process? 98
How Is a Process Designed? 99
Why Is a Requirements Process Needed? 103
Goals of Requirements Engineers 107
A Sample Requirements Process 110
How Can Organizations Create or Tailor a Requirements Process? 122
Tailoring of Processes 123
Web Support: An Organizational Process Asset Library 124
Summary 125
Key References and Suggested Readings 125
CHAPTER 6 ITERATE THE SYSTEM REQUIREMENTS
AND ARCHITECTURE REPEATEDLY 131
The System Engineering Process 132
Recommendations 134
Consider the "Designability" of the System When Addressing the Requirements 134
Allocate Requirements to Functional Partitions, Objects, People, or Support
Elements to Support Synthesis of Solutions 136
Utilize a System Architecture Process 136
Consider Open Systems Standards 146
Guidelines for"Architecting" 151
Another View 153
Summary 154
Key References and Suggested Readings 154
CHAPTER 7 USE A MECHANISM TO MAINTAIN
PROJECT COMMUNICATION 159
Setting the Stage 160
Natural Human Tendency 160
A Proactive Approach to Achieve Effective Communication 161
An Example Mechanism 162
When Negativism Shows Up 164
Another Valuable Mechanism--Brown Bags 165
Guidelines for Effective Meetings 165
Guidelines for Effective E-mail Communication 167
The Value of a Common Vocabulary 172
The Use of Vertical Experts 173
Avoid Multiple Locations 174
A Final Recommendation 174
Summary 174
Key References and Suggested Readings 175
CHAPTER 8 SELECT FAMILIAR METHODS AND
MAINTAIN A SET OF WORK PRODUCTS 179
The Foundation for System Development 180
What Are the Candidate Methods and Techniques? 180
Which Methods and Techniques Are Best? 182
Use of Function Points for Software Estimation 189
Quality Function Deployment 190
What Comprises the Requirements Specification? 192
The Rationale for Prioritizing Requirements 193
Summary 195
Key References and Suggested Readings 196
CHAPTER 9 PERFORM REQUIREMENTS VERIFICATION
AND VALIDATION 201
V&V Terminology 202
The Importance of V&V 203
V&V Planning 203
Verification Methods 207
V&V Techniques 208
Using Traceability to Support Verification 208
A Structured Approach to Testing 210
Recommendations 211
Pitfalls 211
Summary 213
Key References and Suggested Readings 214
CHAPTER 10 PROVIDE AN EFFECTIVE MECHANISM
TO ACCOMMODATE REQUIREMENTS
CHANGES 217
Why Such Emphasis? 218
Planning for Changes in Requirements 219
The Recommended Mechanism 221
Requirements Leakage 221
Focus on What Counts! 224
How Much Can Requirements Change? 224
A Way to Deal with Requirements Creep Contractually 225
Other Recommendations 227
Summary 229
Key References and Suggested Readings 229
CHAPTER 11 PERFORM THE DEVELOPMENT EFFORT
USING KNOWN, FAMILIAR PROVEN
INDUSTRY, ORGANIZATIONAL, AND
PROJECT BEST PRACTICES 231
What's All the Fuss? 233
What Can We Do About It? 234
Recommendations 235
Provide to the Development Team an Understanding of the Relevant Policies,
Processes, and Procedures to Be Used 235
Utilize a Practical, Effective Project Management Approach 235
Ensure That Selected Members of the Development Team Have Domain
Knowledge 244
Perform the Development Effort Using Known (Trained), Proven Processes,
Mechanisms, Methods, Techniques, and Tools 244
Provide and Utilize Mechanisms to Foster Effective Communications Throughout the
Development Team 247
Utilize Peer Reviews and Inspections to Remove Defects from Processes and Work
Products 248
Ensure That Configuration Management Is Effective 250
Foster an Independent QA Role That Proactively Assists and Supports the
Development Team and Provides Value to the Project 251
Ensure That Subcontractors Are Managed So That Their Contributions Are
Effective 252
Use Appropriate, Useful Metrics to Manage the Project 255
Ensure That a Systematic Approach to Involving the Customer in This Entire
Effort ls Working 258
Manage Processes Quantitatively. Also, Use a Defect Prevention (DP) Process, a
Technology Change Management (TCM) Process, and a Process Change
Management (PCM) Process. Perform Extensive Reinsertion and Reuse
Throughout the Organization 261
Musings on Project Management 262
Summary 265
Key References and Suggested Readings 266
PART III WHAT TO DO NEXT 271
CHAPTER 12 HOW TO PROCEED 273
Common Issues 273
Key Factors in Addressing These Issues 275
The Customer 275
Requirements as a Key Driver to Any Systems or Software Effort 275
Financing Improvements in the Requirements Process 275
Survival of the Fittest 276
Management Awareness and Expectations 276
Metrics 276
The Development Team 277
Where to Start 277
How to Prioritize Needed Efforts 284
Relationship of the Recommended Effective Requirements
Practices to the CMM 289
But I Have So Many Things to Do... 291
What If We Are "Further Along" on Our Project? 293
Summary 293
Key References and Suggested Readings 294
Epilogue 299
List of Acronyms 301
Glossary 309
Credits 321
Bibliography 325
Author Index 345
Subject Index 349
猜您喜欢
