Chapter 2: Impact Mapping and Behavior-Driven Development
As well as the initial capturing of requirements, as system builders, we also need to deal with changes in requirements. A project's requirements constantly evolve, and we need to react to each stage of their evolution in two steps. The first is to correctly understand what is changing in the requirements. The second is to act on that new information in a way that helps reflect these changes and that influences the design and implementation of our system. To achieve this, we need to have a model that is a meaningful representation of our requirements.
In the previous chapter, we began to explore some of the entities within the requirements domain, namely goals and stakeholders. In this ...
Get Managing Software Requirements the Agile Way 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.
