Preface
Despite some fifty years of industry experience, many software development organizations struggle to gather, document, and manage their product requirements. Lack of user input, incomplete requirements, and changing requirements are the major reasons why so many information technology projects fail to deliver all of their planned functionality on schedule and within budget.[1] Many software developers aren’t comfortable or proficient at gathering requirements from customers. Customers often don’t have the patience to participate in requirements development, or they have the wrong people supply the requirements. Project participants often don’t even agree on what a "requirement" is. As one writer observed, "Engineers would rather decipher ...
Get Software Requirements, Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
