Mastering the Requirements Process, 2/e (Hardcover)
暫譯: 掌握需求流程，第二版 (精裝本)
Suzanne Robertson, James C. Robertson
- 出版商: Addison Wesley
- 出版日期: 2006-03-27
- 定價: $1,650
- 售價: 6.0 折 $990
- 語言: 英文
- 頁數: 592
- 裝訂: Hardcover
- ISBN: 0321419499
- ISBN-13: 9780321419491
-
相關分類:
專案管理 PM、軟體工程
-
其他版本:
Mastering the Requirements Process: Getting Requirements Right, 3/e (Hardcover)
買這商品的人也買了...
-
The Rational Unified Process: An Introduction, 2/e（Paperback）$1,530$1,454 -
Programming Pearls 中文版 (Programming Pearls, 2/e)$520$411 -
CCNA Self-Study: Interconnecting Cisco Network Devices (ICND) 640-811, 640-801, 2/e$2,380$2,261 -
Microelectronic Circuits, 5/e$1,250$1,225 -
Head First Servlets & JSP：SCWCD 專業認證指南 (Head First Servlets & JSP)$880$748 -
深入淺出設計模式 (Head First Design Patterns)$880$695 -
深入淺出 Java 程式設計, 2/e (Head First Java, 2/e)$880$695 -
Java 認證 SCJP 5.0 猛虎出閘$650$514 -
Linear Algebra with Applications, 7/e (IE) (美國版ISBN:0131857851)$920$902 -
SQL Server 2005 資料庫開發聖經$890$757 -
如何設計好網站 (Don't Make Me Think: A Common Sense Approach to Web Usability, 2/e)$450$383 -
鳥哥的 Linux 私房菜基礎學習篇, 2/e$780$663 -
駭客攻防技術擂臺$520$411 -
專案管理之美學 (The Art of Project Management)$620$490 -
Ajax 網頁程式設計─Google 成功背後的技術$580$458 -
Ajax 與 Google Map API 入門實作$450$351 -
ASP.NET 2.0 深度剖析範例集$650$507 -
SQL 語法範例辭典$550$435 -
Linux 驅動程式, 3/e (Linux Device Drivers, 3/e)$980$774 -
Visual C# 2005 精要剖析$650$514 -
寫給 SA 的 UML/MDA 實務手冊$350$298 -
Engineering Mechanics - Statics, 6/e$1,080$1,058 -
C++ Primer, 4/e (中文版)$990$891 -
3ds Max 9 動畫奧義 (3ds Max 9 Essentials: Autodesk Media and Entertainment Courseware)$680$578 -
現代嵌入式系統開發專案實務－菜鳥成長日誌與專案經理的私房菜$600$480
商品描述
Description
"If the purpose is to create one of the best books on requirements yet written, the authors have succeeded."
—Capers Jones
It is widely recognized that incorrect requirements account for up to 60 percent of errors in software products, and yet the majority of software development organizations do not have a formal requirements process. Many organizations appear willing to spend huge amounts on fixing and altering poorly specified software, but seem unwilling to invest a much smaller amount to get the requirements right in the first place.
Mastering the Requirements Process, Second Edition, sets out an industry-proven process for gathering and verifying requirements with an eye toward today's agile development environments. In this total update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs while doing the minimum requirements work according to the project's level of agility.
Features include
- The Volere requirements process—completely specified, and revised for compatibility with agile environments
- A specification template that can be used as the basis for your own requirements specifications
- New agility ratings that help you funnel your efforts into only the requirements work needed for your particular development environment and project
- How to make requirements testable using fit criteria
- Iterative requirements gathering leading to faster delivery to the client
- Checklists to help identify stakeholders, users, nonfunctional requirements, and more
- Details on gathering and implementing requirements for iterative releases
- An expanded project sociology section for help with identifying and communicating with stakeholders
- Strategies for exploiting use cases to determine the best product to build
- Methods for reusing requirements and requirements patterns
- Examples showing how the techniques and templates are applied in real-world situations
Table of Contents
Preface to the Second Edition xxiForeword to the First Edition xxiii Acknowledgments xxiv Chapter 1 What Are Requirements? 1
Requirements Gathering and Systems Modeling 3
Agile Software Development 4
Why Do I Need Requirements? 8
What Is a Requirement? 9
Evolution of Requirements 11
The Template 11
The Shell 14
The Volere Requirements Process 15
Chapter 2 The Requirements Process 17
Agility Guide 19
Requirements Process in Context 20
The Process 21
A Case Study 21
Trawling for Requirements 24
Prototyping the Requirements 25
Scenarios 25
Writing the Requirements 26
The Quality Gateway 28
Reusing Requirements 29
Reviewing the Specification 29
Iterative and Incremental Processes 30
Requirements Retrospective 31
Your Own Requirements Process 31
In Conclusion 33
Chapter 3 Project Blastoff 35
Agility Guide 38
IceBreaker 38
Scope, Stakeholders, Goals 40
Setting the Scope 40
Stakeholders 45
Other Stakeholders 51
Finding the Stakeholders 54
Goals: What Do You Want to Achieve? 55
Requirements Constraints 60
Naming Conventions and Definitions 61
How Much Is This Going to Cost? 62
Risks 63
To Go or Not to Go 64
Blastoff Alternatives 65
Summary 65
Chapter 4 Event-Driven Use Cases 67
Agility Guide 67
Understanding the Work 67
Use Cases and Their Scope 69
The Work 70
The Context of the Work 70
Business Events 73
Why Business Events and Business Use Cases Are a Good Idea 75
Finding the Business Events 76
Business Use Cases 78
The Role of Adjacent Systems 79
Business Use Cases and Product Use Cases 86
Summary 90
Chapter 5 Trawling for Requirements 93
Agility Guide 93
Responsibility 94
Trawling and Business Use Cases 96
The Role of the Current Situation 98
Apprenticing 101
Observing Structures and Patterns 103
Interviewing the Stakeholders 104
Getting to the Essence of the Work 107
Solving the Right Problem 109
Innovative Products 110
Business Use Case Workshops 113
Creativity Workshops 116
Brainstorming 117
Personas 119
Mind Maps 122
Wallpaper 124
Video and Photographs 124
Wikis, Blogs, and Discussion Forums 125
Document Archeology 126
Some Other Requirements-Gathering Techniques 128
Determining What the Product Should Be 129
Does Technology Matter? 131
Choosing the Best Trawling Technique 132
Summary 134
Chapter 6 Scenarios and Requirements 135
Agility Guide 135
Scenarios 136
Normal Case Scenarios 140
Diagramming the Scenario 142
Alternative Cases 144
Exception Cases 145
What If? Scenarios 146
Misuse Cases and Negative Scenarios 147
Scenario Template 148
Product Use Case Scenarios 150
Summary 152
Chapter 7 Functional Requirements 155
Agility Guide 155
Functional Requirements 157
Finding the Functional Requirements 157
Level of Detail or Granularity 160
Exceptions and Alternatives 161
Avoiding Ambiguity 162
Technological Requirements 164
Requirements, Not Solutions 165
Grouping Requirements 166
Alternatives to Functional Requirements 167
Summary 169
Chapter 8 Nonfunctional Requirements 171
Agility Guide 172
Nonfunctional Requirements 173
Use Cases and Nonfunctional Requirements 174
The Nonfunctional Requirements 174
Look and Feel Requirements: Type 10 176
Usability and Humanity Requirements: Type 11 178
Performance Requirements: Type 12 182
Operational and Environmental Requirements: Type 13 184
Maintainability and Support Requirements: Type 14 186
Security Requirements: Type 15 187
Cultural and Political Requirements: Type 16 190
Legal Requirements: Type 17 192
Finding the Nonfunctional Requirements 195
Don't Write a Solution 199
Summary 201
Chapter 9 Fit Criteria 203
Agility Guide 203
Why Does Fit Need a Criterion? 204
Scale of Measurement 206
Rationale 206
Fit Criteria for Nonfunctional Requirements 208
Fit Criteria for Functional Requirements 217
Use Cases and Fit Criteria 218
Fit Criterion for Project Purpose 219
Fit Criteria for Solution Constraints 219
Summary 220
Chapter 10 Writing the Requirements 223
Agility Guide 223
Turning Potential Requirements into Written Requirements 225
Knowledge Versus Specification 225
The Volere Requirements Specification Template 227
1 The Purpose of the Project 229
2 The Client, the Customer, and Other Stakeholders 232
3 Users of the Product 233
4 Mandated Constraints 234
5 Naming Conventions and Definitions 237
6 Relevant Facts and Assumptions 238
7 The Scope of the Work 240
8 The Scope of the Product 241
The Shell 241
The Atomic Requirement 243
Writing the Specification 248
9 Functional Requirements 249
Nonfunctional Requirements 251
Project Issues 252
18 Open Issues 252
19 Off-the-Shelf Solutions 253
20 New Problems 254
21 Tasks 254
22 Migration to the New Product 254
23 Risks 254
24 Costs 255
25 User Documentation and Training 256
26 Waiting Room 256
27 Ideas for Solutions 257
Summary 257
Chapter 11 The Quality Gateway 259
Agility Guide 260
Requirements Quality 261
Using the Quality Gateway 262
Testing Completeness 263
Testing Traceability 265
Consistent Terminology 267
Relevant to Purpose? 268
Testing the Fit Criterion 270
Viable within Constraints? 272
Requirement or Solution? 273
Customer Value 274
Gold Plating 275
Requirements Creep 276
Implementing the Quality Gateway 279
Summary 281
Chapter 12 Prototyping the Requirements 283
Agility Guide 285
Prototypes and Reality 286
Low-Fidelity Prototypes 288
High-Fidelity Prototypes 292
Storyboards 294
Object Life History 296
The Prototyping Loop 297
Summary 301
Chapter 13 Reusing Requirements 303
What Is Reusing Requirements? 303
Sources of Reusable Requirements 306
Requirements Patterns 307
A Business Event Pattern 309
Forming Patterns by Abstracting 313
Domain Analysis 317
Trends in Reuse 318
Reuse and Objects 318
Summary 319
Chapter 14 Reviewing the Specification 321
Agility Guide 322
Reviewing the Specification 323
Inspections 323
Find Missing Requirements 324
Have All Business Use Cases Been Discovered? 325
Define the Scope 326
Customer Value 332
Prioritizing the Requirements 333
Conflicting Requirements 337
Ambiguous Specifications 339
Risk Analysis 340
Measure the Required Effort 342
Summary 342
Chapter 15 Whither Requirements? 345
Adapting the Process 345
What About Requirements Tools? 347
Mapping Tools to Purpose 348
Publishing the Requirements 350
Requirements Traceability 353
Dealing with Change 357
Requirements Retrospective 360
Your Notebook 363
The End 363
Appendix A Volere Requirements Process Model 365Appendix B Volere Requirements Specification Template 451Appendix C Function Point Counting: A Simplified Introduction 507Appendix D Project Sociology Analysis Templates 523Glossary 531Bibliography 535Index 539
商品描述(中文翻譯)
**描述**
「如果目的是創造一本有關需求的最佳書籍之一，作者們已經成功了。」
—Capers Jones
廣泛認為，不正確的需求佔據了軟體產品錯誤的60％，然而大多數軟體開發組織並沒有正式的需求流程。許多組織似乎願意花費大量資金來修正和修改規範不清的軟體，但卻不願意投入更少的資金來確保需求在一開始就正確。
《掌握需求流程，第二版》提出了一個行業驗證的需求收集和驗證流程，並考慮到當今的敏捷開發環境。在這本暢銷指南的全面更新中，作者展示了如何準確發現客戶的需求和期望，同時根據項目的敏捷程度進行最小的需求工作。
特色包括：
- Volere需求流程——完全規範，並修訂以兼容敏捷環境
- 可作為您自己需求規範基礎的規範模板
- 新的敏捷評級，幫助您將精力集中在特定開發環境和項目所需的需求工作上
- 如何使用適合標準使需求可測試
- 迭代需求收集，促進更快的客戶交付
- 幫助識別利益相關者、用戶、非功能需求等的檢查清單
- 有關收集和實施迭代版本需求的詳細資訊
- 擴展的項目社會學部分，幫助識別和與利益相關者溝通
- 利用用例確定最佳產品的策略
- 重用需求和需求模式的方法
- 實際情況中應用技術和模板的示例
**目錄**
**第二版前言 xxi**
**第一版序言 xxiii**
**致謝 xxiv**
**第一章 什麼是需求？ 1**
需求收集與系統建模 3
敏捷軟體開發 4
為什麼我需要需求？ 8
什麼是需求？ 9
需求的演變 11
模板 11
外殼 14
Volere需求流程 15
**第二章 需求流程 17**
敏捷指南 19
需求流程的背景 20
流程 21
案例研究 21
需求收集 24
需求原型 25
場景 25
撰寫需求 26
質量門檻 28
重用需求 29
審查規範 29
迭代和增量流程 30
需求回顧 31
您自己的需求流程 31
結論 33
**第三章 專案啟動 35**
敏捷指南 38
破冰活動 38
範圍、利益相關者、目標 40
設定範圍 40
利益相關者 45
其他利益相關者 51
尋找利益相關者 54
目標：您想達成什麼？ 55
需求限制 60
命名慣例和定義 61
這將花費多少？ 62
風險 63
是否進行 64
啟動替代方案 65
摘要 65
**第四章 事件驅動的用例 67**
敏捷指南 67
理解工作 67
用例及其範圍 69
工作 70
工作的背景 70
商業事件 73
為什麼商業事件和商業用例是一個好主意 75
尋找商業事件 76
商業用例 78
相鄰系統的角色 79
商業用例和產品用例 86
摘要 90
**第五章 需求收集 93**
敏捷指南 93
責任 94
需求收集與商業用例 96
當前情況的角色 98
學徒制 101
觀察結構和模式 103
訪談利益相關者 104
抓住工作的本質 107
解決正確的問題 109
創新產品 110
商業用例工作坊 113
創意工作坊 116
腦力激盪 117
角色 119
心智圖 122
牆紙 124
視頻和照片 124
維基、部落格和討論論壇 125
文件考古學 126
其他一些需求收集技術 128
確定產品應該是什麼 129
技術是否重要？ 131
選擇最佳的需求收集技術 132
摘要 134
**第六章 場景與需求 135**
敏捷指南 135
場景 136
正常案例場景 140
場景圖示 142
替代案例 144
例外案例 145
如果？場景 146
誤用案例和負面場景 147
場景模板 148
產品用例場景 150
摘要 152
**第七章 功能需求 155**
敏捷指南 155
功能需求 157
尋找功能需求 157
細節或粒度的程度 160
例外和替代方案 161
避免模糊性 162
技術需求 164
需求，而非解決方案 165
需求分組 166
功能需求的替代方案 167
摘要 169
**第八章 非功能需求 171**
敏捷指南 172
非功能需求 173
用例與非功能需求 174
非功能需求 174
外觀和感覺需求：類型10 176
可用性和人性需求：類型11 178
性能需求：類型12 182
操作和環境需求：類型13 184
可維護性和支持需求：類型14 186
安全需求：類型15 187
文化和政治需求：類型16 190
法律需求：類型17 192
尋找非功能需求 195
不要寫解決方案 199
摘要 201
**第九章 適合標準 203**
敏捷指南 203
為什麼適合需要標準？ 204
測量尺度 206
理由 206
非功能需求的適合標準 208
功能需求的適合標準 217
用例與適合標準 218
專案目的的適合標準 219
解決方案限制的適合標準 219
摘要 220
