Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.

Overview

Learn proven, real-world techniques for specifying software requirements with this practical reference. It details 30 requirement “patterns” offering realistic examples for situation-specific guidance for building effective software requirements. Each pattern explains what a requirement needs to convey, offers potential questions to ask, points out potential pitfalls, suggests extra requirements, and other advice. This book also provides guidance on how to write other kinds of information that belong in a requirements specification, such as assumptions, a glossary, and document history and references, and how to structure a requirements specification.

A disturbing proportion of computer systems are judged to be inadequate; many are not even delivered; more are late or over budget. Studies consistently show one of the single biggest causes is poorly defined requirements: not properly defining what a system is for and what it’s supposed to do. Even a modest contribution to improving requirements offers the prospect of saving businesses part of a large sum of wasted investment. This guide emphasizes this important requirement need—determining what a software system needs to do before spending time on development. Expertly written, this book details solutions that have worked in the past, with guidance for modifying patterns to fit individual needs—giving developers the valuable advice they need for building effective software requirements

Subscriber Reviews

Average Rating: 3 out of 5 rating Based on 2 Ratings

"part II of the book is highly valuable " - by Anonymous on 21-FEB-2013
Reviewer Rating: 1 star rating2 star rating3 star rating4 star rating5 star rating
part II of the book explains all requirement patterns in detail.
If your objective is to develop new software pieces either as a plug-in or extension to an existing standard or proprietary software system then it serves well. It serves best however if you design a software application from scratch.
Highly valuable to software  consultants (functionally oriented) and project managers. It helps them catagorise and evaluate requirements.
I use it in my product manager role to have some objective criteria defined than enable us to decide on whether a requirement is worth including in the scope of our core product or not. If it doesn't the requirement catalog gives answers as to what is missing in the requirement statement  to qualify as core-worthy.

Report as Inappropriate

Table of Contents