Software Requirements : Practical Techniques for Gathering and Managing Requirements Throughout the Product Development Cycle (2 SUB)

Software Requirements : Practical Techniques for Gathering and Managing Requirements Throughout the Product Development Cycle (2 SUB)

  • ただいまウェブストアではご注文を受け付けておりません。 ⇒古書を探す
  • 製本 Paperback:紙装版/ペーパーバック版/ページ数 516 p.
  • 言語 ENG,ENG
  • 商品コード 9780735618794
  • DDC分類 005.1

Full Description


Without formal, verifiable software requirements-and an effective system for managing them-the programs that developers think they've agreed to build often will not be the same products their customers are expecting. In SOFTWARE REQUIREMENTS, Second Edition, requirements engineering authority Karl Wiegers amplifies the best practices presented in his original award-winning text?now a mainstay for anyone participating in the software development process. In this book, you'll discover effective techniques for managing the requirements engineering process all the way through the development cycle-including dozens of techniques to facilitate that all-important communication between users, developers, and management. This updated edition features new case examples, anecdotes culled from the author's extensive consulting career, and specific Next Steps for putting the book's process-improvement principles into practice. You'll also find several new chapters, sample documents, and an incisive troubleshooting guide. Discover how to: Set achievable expectations for functionality and quality NEW: Incorporate business rules into application development Employ use cases to discover user requirements Arrest creeping requirements and manage change requests NEW: Deal with requirements on maintenance, outsourced, and package solution projects Curb the impulse to "gold-plate" your programs NEW: Grow effective requirements analysts Cut revisions-and costs-dramatically Produce better software! No matter what kind of software you build, or what your role in the development process, SOFTWARE REQUIREMENTS, Second Edition, delivers expert guidance and field-tested techniques for engineering software

Table of Contents

Part I SOFTWARE REQUIREMENTS: WHAT, WHY, WHO
1 The Essential Software Requirement 3
Software Requirements Defined 7 (5)
Some Interpretations of Requirement 7 (1)
Levels of Requirements 8 (4)
What Requirements Are Not 12 (1)
Requirements Development and Management 12 (3)
Requirements Development 13 (1)
Requirements Management 14 (3)
Every Project Has Requirements 15 (2)
When Bad Requirements Happen to Nice People 17 (3)
Insufficient User Involvement 18 (1)
Creeping User Requirements 18 (1)
Ambiguous Requirements 18 (1)
Gold Plating 19 (1)
Minimal Specification 19 (1)
Overlooked User Classes 20 (1)
Inaccurate Planning 20 (2)
Benefits from a High-Quality Requirements 20 (2)
Process
Characteristics of Excellent Requirements 22 (5)
Requirement Statement Characteristics 22 (2)
Requirements Specification Characteristics 24 (7)
2 Requirements from the Customer's 27 (16)
Perspective
Who Is the Customer? 29 (2)
The Customer-Development Partnership 31 (8)
Requirements Bill of Rights for Software 33 (3)
Customers
Requirements Bill of Responsibilities for 36 (27)
Software Customers
What About Sign-Off? 39 (4)
3 Good Practices for Requirements Engineering 43 (20)
Knowledge 45 (2)
Requirements Elicitation 47 (3)
Requirements Analysis 50 (2)
Requirements Specification 52 (1)
Requirements Validation 53 (1)
Requirements Management 54 (2)
Project Management 56 (1)
Getting Started with New Practices 57 (2)
A Requirements Development Process 59 (4)
4 The Requirements Analyst 63 (14)
The Requirements Analyst Role 63 (8)
The Analyst's Tasks 65 (3)
Essential Analyst Skills 68 (2)
Essential Analyst Knowledge 70 (1)
The Making of an Analyst 71 (2)
The Former User 71 (1)
The Former Developer 72 (1)
The Subject Matter Expert 73 (5)
Creating a Collaborative Environment 73 (4)
Part II Software Requirements Development
5 Establishing the Product Vision and 77 (18)
Project Scope
Defining the Vision Through Business 78 (3)
Requirements
Conflicting Business Requirements 80 (1)
Business Requirements and Use Cases 81 (1)
Vision and Scope Document 81 (9)
1. Business Requirements 83 (2)
2. Vision of the Solution 85 (1)
3. Scope and Limitations 86 (2)
4. Business Context 88 (15)
The Context Diagram 90 (1)
Keeping the Scope in Focus 91 (4)
6 Finding the Voice of the Customer 95 (18)
Sources of Requirements 96 (1)
User Classes 97 (4)
Finding User Representatives 101(2)
The Product Champion 103(6)
External Product Champions 104(1)
Product Champion Expectations 105(1)
Multiple Product Champions 106(1)
Selling the Product Champion Idea 107(1)
Product Champion Traps to Avoid 108(25)
Who Makes the Decisions? 109(4)
7 Hearing the Voice of the Customer 113(18)
Requirements Elicitation 115(2)
Elicitation Workshops 117(2)
Classifying Customer Input 119(6)
Some Cautions About Elicitation 125(1)
Finding Missing Requirements 126(3)
How Do You Know When You're Done? 129(2)
8 Understanding User Requirements 131(22)
The Use-Case Approach 133(16)
Use Cases and Usage Scenarios 134(4)
Identifying Use Cases 138(1)
Documenting Use Cases 139(6)
Use Cases and Functional Requirements 145(2)
Benefits of Use Cases 147(1)
Use-Case Traps to Avoid 148(6)
Event-Response Tables 149(4)
9 Playing by the Rules 153(12)
The Rules of the Business 154(6)
Facts 155(1)
Constraints 156(1)
Action Enablers 157(1)
Inferences 158(1)
Computations 158(8)
Documenting Business Rules 160(1)
Business Rules and Requirements 161(4)
10 Documenting the Requirements 165(28)
The Software Requirements Specification 166(5)
Labeling Requirements 168(1)
Dealing with Incompleteness 169(1)
User Interfaces and the SRS 170(1)
A Software Requirements Specification 171(10)
Template
1. Introduction 172(1)
2. Overall Description 173(2)
3. System Features 175(1)
4. External Interface Requirements 176(2)
5. Other Nonfunctional Requirements 178(2)
6. Other Requirements 180(1)
Appendix A: Glossary 180(1)
Appendix B: Analysis Models 180(1)
Appendix C: Issues List 181(37)
Guidelines for Writing Requirements 181(4)
Sample Requirements, Before and After 185(5)
The Data Dictionary 190(3)
11 A Picture Is Worth 1024 Words 193(22)
Modeling the Requirements 194(1)
From Voice of the Customer to Analysis 195(2)
Models
Data Flow Diagram 197(3)
Entity-Relationship Diagram 200(3)
State-Transition Diagram 203(3)
Dialog Map 206(4)
Class Diagrams 210(2)
Decision Tables and Decision Trees 212(2)
A Final Reminder 214(1)
12 Beyond Functionality: Software Quality 215(18)
Attributes
Quality Attributes 216(2)
Defining Quality Attributes 218(9)
Attributes Important to Users 219(6)
Attributes Important to Developers 225(37)
Performance Requirements 227(1)
Defining Nonfunctional Requirements By 228(1)
Using Planguage
Attribute Trade-Offs 229(2)
Implementing Nonfunctional Requirements 231(2)
13 Risk Reduction Through Prototyping 233(14)
Prototyping: What and Why 234(1)
Horizontal Prototypes 235(1)
Vertical Prototypes 236(1)
Throwaway Prototypes 236(2)
Evolutionary Prototypes 238(2)
Paper and Electronic Prototypes 240(2)
Prototype Evaluation 242(1)
The Risks of Prototyping 243(2)
Prototyping Success Factors 245(2)
14 Setting Requirement Priorities 247(12)
Why Prioritize Requirements? 248(1)
Games People Play with Priorities 249(1)
A Prioritization Scale 250(2)
Prioritization Based on Value, Cost, and 252(7)
Risk
15 Validating the Requirements 259(24)
Reviewing Requirements 262(11)
The Inspection Process 264(8)
Requirements Review Challenges 272(11)
Testing the Requirements 273(7)
Defining Acceptance Criteria 280(3)
16 Special Requirements Development Challenges 283(14)
Requirements for Maintenance Projects 283(5)
Begin Capturing Information 284(3)
Practice New Requirements Techniques 287(1)
Follow the Traceability Chain 287(1)
Update the Documentation 288(1)
Requirements for Package Solutions 288(3)
Develop Use Cases 289(1)
Consider Business Rules 290(1)
Define Quality Requirements 290(3)
Requirements for Outsourced Projects 291(2)
Requirements for Emergent Projects 293(4)
Casual User Requirements Specification 294(1)
On-Site Customer 295(1)
Early and Frequent Prioritization 296(1)
Simple Change Management 296(2)
17 Beyond Requirements Development 297(16)
From Requirements to Project Plans 298(6)
Requirements and Estimation 300(3)
Requirements and Scheduling 303(28)
From Requirements to Designs and Code 304(3)
From Requirements to Tests 307(2)
From Requirements to Success 309(4)
Part III SOFTWARE REQUIREMENTS MANAGEMENT
18 Requirements Management Principles and 313(14)
Practices
The Requirements Baseline 315(1)
Requirements Management Procedures 315(2)
Requirements Version Control 317(2)
Requirement Attributes 319(2)
Tracking Requirements Status 321(3)
Measuring Requirements Management Effort 324(3)
19 Change Happens 327(26)
Managing Scope Creep 329(2)
The Change-Control Process 331(7)
Change-Control Policy 332(1)
Change-Control Process Description 333(5)
The Change Control Board 338(3)
CCB Composition 339(1)
CCB Charter 339(5)
Change-Control Tools 341(1)
Measuring Change Activity 342(2)
Change Isn't Free: Impact Analysis 344(9)
Impact Analysis Procedure 345(5)
Impact Analysis Report Template 350(24)
20 Links in the Requirements Chain 353(14)
Tracing Requirements 354(3)
Motivations for Tracing Requirements 357(1)
The Requirements Traceability Matrix 358(4)
Tools for Requirements Tracing 362(2)
Requirements Traceability Procedure 364(1)
Is Requirements Traceability Feasible? Is 365(2)
It Necessary?
21 Tools for Requirements Management 367(14)
Benefits of Using a Requirements Management 370(2)
Tool
Requirements Management Tool Capabilities 372(2)
Implementing Requirements Management 374(7)
Automation
Selecting a Tool 374(1)
Changing the Culture 375(3)
Making Requirements Management Tools Work 378(11)
for You
Part IV IMPLEMENTING REQUIREMENTS ENGINEERING
22 Improving Your Requirements Processes 381(20)
How Requirements Relate to Other Project 382(2)
Processes
Requirements and Various Stakeholder Groups 384(2)
Fundamentals of Software Process Improvement 386(3)
The Process Improvement Cycle 389(6)
Assess Current Practices 389(1)
Plan Improvement Actions 390(2)
Create, Pilot, and Implement New Processes 392(1)
Evaluate Results 393(2)
Requirements Engineering Process Assets 395(4)
Requirements Development Process Assets 396(2)
Requirements Management Process Assets 398(5)
Requirements Process Improvement Road Map 399(2)
23 Software Requirements and Risk Management 401(14)
Fundamentals of Software Risk Management 403(5)
Elements of Risk Management 403(1)
Documenting Project Risks 404(3)
Planning for Risk Management 407(1)
Requirements-Related Risks 408(4)
Requirements Elicitation 408(2)
Requirements Analysis 410(1)
Requirements Specification 410(1)
Requirements Validation 411(1)
Requirements Management 411(17)
Risk Management Is Your Friend 412(13)
Epilogue 415(2)
A Current Requirements Practice 417(8)
Self-Assessment
B Requirements and Process Improvement Models 425(8)
The Capability Maturity Model for Software 425(3)
CMMI-SE/SW 428(5)
Requirements Management Process Area 430(1)
Requirements Development Process Area 430(3)
C Requirements Troubleshooting Guide 433(24)
Root Cause Analysis 434(1)
Common Symptoms of Requirements Problems 435(1)
Common Barriers to Implementing Solutions 436(21)
D Sample Requirements Documents 457(26)
Vision and Scope Document 458(5)
Use Cases 463(6)
Software Requirements Specification 469(13)
Business Rules 482(1)
Glossary 483(8)
References 491(14)
Index 505