More about software requirements
Subtitle: thorny issues and practical advice
By: Karl E. Wiegers
Publisher: O'Reilly Media, Inc.
Published: 2009
Place of publication: Sebastopol, Calif
Language: eng
Format: [electronic resource] :
Number of pages: 201
ISBN-13: 9780735635319
Subjects: Development; Software Development & Engineering; Application software; COMPUTERS; Computer software; Project Management; Computer science
Description: No matter how much instruction you've had on managing software requirements, there's no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book. With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions raised by.
Notes: When to Baseline.

Includes bibliographical references and index.

Description based on print version record.
Table of contents: title: Cover; Copyright page; Contents at a Glance; Table of Contents; Preface; Acknowledgments; Part I: On Essential Requirements Concepts; Chapter 1: Requirements Engineering Overview; "Requirement" Defined; Different Types of Requirements; Business Requirements; User Requirements; Functional Requirements; System Requirements; Business Rules; Quality Attributes; External Interfaces; Constraints; Requirements Engineering Activities; Looking Ahead; Chapter 2: Cosmic Truths About Software Requirements; Requirements Realities; Requirements Stakeholders; Requirements Specifications.; title: Part II: On the Management View of RequirementsChapter 3: The Business Value of Better Requirements; Tell Me Where It Hurts; What Can Better Requirements Do for You?; The Investment; The Return; An Economic Argument; Chapter 4: How Long Do Requirements Take?; Industry Benchmarks; Your Own Experience; Incremental Approaches; Planning Elicitation; Chapter 5: Estimating Based on Requirements; Some Estimation Fundamentals; Estimation Approaches; Goals Aren't Estimates; Estimating from Requirements; Measuring Software Size; Story Points; Use Case Points; Testable Requirements.; title: The Reality of EstimationPart III: On Customer Interactions; Chapter 6: The Myth of the On-Site Customer; User Classes and Product Champions; Surrogate Users; Now Hear This; Chapter 7: An Inquiry, Not an Inquisition; But First, Some Questions to Avoid; Questions for Eliciting Business Requirements; User Requirements and Use Cases; Questions for Eliciting User Requirements; Open-Ended Questions; Why Ask Why?; Chapter 8: Two Eyes Aren't Enough; Improving Your Requirements Reviews; Part IV: On Use Cases; Chapter 9: Use Cases and Scenarios and Stories, Oh My!; Use Cases; Scenarios; User Stories.; title: Chapter 10: Actors and UsersChapter 11: When Use Cases Aren't Enough; The Power of Use Cases; Project Type Limitations; Event-Response Tables; Use Cases Don't Replace Functional Requirements; Use Cases Reveal Functional Requirements; Part V: On Writing Requirements; Chapter 12: Bridging Documents; Chapter 13: How Much Detail Do You Need?; Who Makes the Call?; When More Detail Is Needed; When Less Detail Is Appropriate; Implied Requirements; Sample Levels of Requirements Detail; Chapter 14: To Duplicate or Not to Duplicate; Cross-Referencing; Hyperlinks; Traceability Links; Recommendation.; title: Chapter 15: Elements of Requirements StyleI Shall Call This a Requirement; System Perspective or User Perspective?; Parent and Child Requirements; What Was That Again?; Complex Logic; Negative Requirements; Omissions; Boundaries; Avoiding Ambiguous Wording; Chapter 16: The Fuzzy Line Between Requirements and Design; Solution Ideas and Design Constraints; Solution Clues; Part VI: On the Requirements Process; Chapter 17: Defining Project Scope; Vision and Scope; Context Diagram; Use Case Diagram; Feature Levels; Managing Scope Creep; Chapter 18: The Line in the Sand; The Requirements Baseline.