Mastering the Requirements Process, 2/e (Hardcover)

Suzanne Robertson, James C. Robertson

買這商品的人也買了...

相關主題

商品描述

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需求流程-完全規範化,並經過修訂以適應敏捷環境
- 可用作自己需求規範基礎的規範模板
- 新的敏捷度評級,幫助您將努力集中在特定開發環境和項目所需的需求工作上
- 如何使用適應性標準使需求可測試
- 迭代需求收集,加快交付給客戶的速度
- 檢查清單,幫助識別利益相關者、使用者、非功能性需求等
- 針對迭代版本收集和實施需求的詳細資訊
- 擴展的項目社會學部分,以幫助識別和與利益相關者溝通
- 利用用例確定最佳產品建構策略
- 重複使用需求和需求模式的方法
- 在實際情況中展示技術和模板的示例

目錄:
- 第二版前言
- 第一版前言
- 致謝
- 第一章:什麼是需求?
- 需求收集和系統建模
- 敏捷軟體開發
- 為什麼我需要需求?
- 什麼是需求?
- 需求的演變
- 模板
- Shell
- Volere需求流程
- 第二章:需求流程