Chapter 20. Handling Requirements for Multiple Releases

Software products are rarely delivered in final form with the first release. More commonly, they evolve through a series of releases that correct defects, add progressively more features, and enrich or update previously implemented features. This means that during requirements development you’ll be accumulating requirements that could be targeted for various releases. You need to determine the best way to store and manage these requirements so that no one is confused about the contents of each upcoming release.

A related issue pertains to requirements that were proposed but never ...

Get More About Software Requirements: Thorny Issues and Practical Advice 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.