Chapter 4

Requirements Analysis

As the business analyst on your project, you’ve worked with key stakeholders to understand their objectives. You’ve interviewed user representatives and others to learn about the business domain, define the solution’s boundaries, and identify stakeholder needs, expectations, and constraints. Now you must transform all that information into a description of the capabilities and characteristics of a solution that will satisfy those needs and expectations. That transformation process is the province of requirements analysis.

But what exactly does it mean to analyze requirements? A surprising number of books on software requirements don’t even have an index entry for requirements analysis. Analysis sounds like something ...

Get Software Requirements Essentials: Core Practices for Successful Business Analysis 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.