More About Software Requirements [electronic resource] : Thorny Issues and Practical Advice

Wiegers, Karl E.
1st edition
Sebastopol : Microsoft Press, 2009.
Best practices More about software requirements
1 online resource (0 p.)
Computer software -- Management -- Development.
Local subjects:
Computer software -- Development -- Management. (search)
Computer software -- Development. (search)
Computer software. (search)
Electronic books.
System Details:
text file
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
More About Software Requirements: Thorny Issues and Practical Advice; Preface; Acknowledgments; I. On Essential Requirements Concepts; Different Types of Requirements; User Requirements; Functional Requirements; System Requirements; Business Rules; Quality Attributes; External Interfaces; Constraints; Requirements Engineering Activities; Looking Ahead; 2. Cosmic Truths About Software Requirements; Cosmic Truth #2: Requirements development is a discovery and invention process, not just a collection process; Cosmic Truth #3: Change happens; Requirements Stakeholders
Cosmic Truth #5: Customer involvement is the most critical contributor to software qualityCosmic Truth #6: The customer is not always right, but the customer always has a point; Requirements Specifications; Cosmic Truth #8: Even the best requirements document cannot-and should not-replace human dialogue; Cosmic Truth #9: The requirements might be vague, but the product will be specific; Cosmic Truth #10: You're never going to have perfect requirements; II. On the Management View of Requirements; What Can Better Requirements Do for You?; Facilitating estimation; Enabling prioritization
Developing designsTesting effectively; The Investment; The Return; An Economic Argument; 4. How Long Do Requirements Take?; Your Own Experience; Incremental Approaches; Planning Elicitation; 5. Estimating Based on Requirements; Estimation Approaches; Top-down; Cost models; Expert opinion; Analogy; Wideband Delphi; Goals Aren't Estimates; Estimating from Requirements; Measuring Software Size; Function points; 3D function points; Story points; Use case points; Counts of testable requirements; Story Points; Use Case Points; Use Case Weights; Technical and Environmental Factors
Determining Your ProductivityProblems with Use Case Points; Testable Requirements; The Reality of Estimation; III. On Customer Interactions; Surrogate Users; Now Hear This; 7. An Inquiry, Not an Inquisition; Questions for Eliciting Business Requirements; What's the motivation for solving this problem?; What would a highly successful solution do for you?; How can we judge the success of the solution?; What's a successful solution worth?; Who are the individuals or groups that could influence this project or be influenced by it?
Are there any related projects or systems that could influence this one or that this project could affect?Which business activities and events should be included in the solution? Which should not?; Can you think of any unexpected or adverse consequences that the new system could cause?; User Requirements and Use Cases; Questions for Eliciting User Requirements; What goals might you have in mind that this product could help you accomplish?; What problems do you expect this product to solve for you?; What external events are associated with the product?
What words would you use to describe the product?
Description based upon print version of record.
Includes bibliographical references and index.
Location Notes Your Loan Policy
Description Status Barcode Your Loan Policy