- Requirements Defined
- Good Practices for Requirements Engineering
- Who Does All This Stuff?
- Some Recurrent Themes
- The Life and Times of Requirements
- Getting Started
This chapter is from the book
This chapter is from the book
This chapter is from the book
The Life and Times of Requirements
Neither requirements development nor requirements management activities end when the initial project team delivers the solution. They continue throughout the product’s operational or market life, as it evolves through an ongoing series of enhancement and maintenance cycles. As change requests arrive, someone must elicit the corresponding requirements details and evaluate their impact on the current solution. They must then document the new or changed requirements, validate them, track their implementation status, trace them to other system elements, and so forth.
The BA should look for existing requirements-related items from other projects they could reuse. At times, they might create deliverables that have reuse potential elsewhere in the organization. Glossaries, business rules, process descriptions, stakeholder catalogs, data models, security requirements, and the like can apply to multiple situations. Once an organization invests in creating these artifacts, it should organize them to enable reuse and look for opportunities to leverage that investment further (Wiegers and Beatty 2013).