- Agility Guide
- Requirements Process in Context
- The Process
- A Case Study
- Trawling for Requirements
- Prototyping the Requirements
- Scenarios
- Writing the Requirements
- The Quality Gateway
- Reusing Requirements
- Reviewing the Specification
- Iterative and Incremental Processes
- Requirements Retrospective
- Your Own Requirements Process
- In Conclusion
This chapter is from the book
This chapter is from the book
This chapter is from the book
Requirements Process in Context
There is no end to the requirements process. When a product, or partial product, is delivered and your users start using it, evolution kicks in. As people use the product, they discover new needs and uses for it, and they then want it to be extended. This raises new requirements that, in turn, go through the same requirements process. Just as the product evolves on its own, so you may choose to make it evolve by building the early versions with a minimal amount of functionality and later augmenting it by a planned series of releases. The Volere Requirements Process is designed with evolution in mind.
The people around the periphery of the process play an important part in it. These people supply information to the process or receive information from it. They are some of the stakeholders— the people who have an interest in the product, but not necessarily a financial one. They participate in the requirements process by providing requirements and receiving deliverables from the process. Additionally, some stakeholders do not show up on Figure 2.1—the consultants and other interested parties who have knowledge needed to gather the requirements for the product. As we discuss the requirements process throughout this book, we also discuss the different stakeholder roles and responsibilities.
){kind=link}