Reusable requirements are those that can be applied across multiple projects or contexts without being tightly coupled to a specific solution. This is achieved by ensuring that the requirement is:
Technology-agnostic
Independent of a specific implementation
Focused on business rules or policies
Such characteristics make them valuable long-term assets for future initiatives.
BABOK® Reference:
Found in the Requirements Life Cycle Management knowledge area, under the task “Maintain Requirements,” which emphasizes maintaining requirements that may be reused across initiatives.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit