Chapter 6: Organizing Requirements
In the previous chapters, we learned how to elicit and discover requirements, analyze them to identify requirement domain entities, model those entities and their relationships with an impact map, and capture system behavior in Feature Scenarios. At this point, we know how to create the following artifacts:
- Our requirements model as one or more impact maps
- Our specification as feature files
- A stakeholder or actor model
- A glossary
In this chapter, we will learn how to organize our existing artifacts and create some new ones. The aim is to increase the transparency and traceability of our methodology's outputs. This will give us the solid basis we need in order to start writing code that delivers the correct ...
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.
