Traceability and Monitoring includes the processes used to establish relationships and dependencies between requirements and other product information, which helps ensure that requirements are approved and managed, and that the impact of changes to them is assessed.
The business analysis processes are presented as discrete processes below, although in practice, they overlap and interact :
| 5.1 Determine Traceability and Monitoring Approach | 5.2 Establish Relationships and Dependencies | 5.3 Select and Approve Requirements | 5.4 Manage Changes to Requirements |
|---|---|---|---|
| The process of considering how traceability will be performed on the portfolio, program, project, or product, and defining how requirement changes will be managed. | The process of tracing or setting linkages between and among requirements and other product information. | The process of facilitating discussions with stakeholders to negotiate and confirm which requirements should be incorporated within an iteration, release, or project. | The process of examining changes that arise during a project by understanding the value and impact of the changes. As changes are agreed upon, information about those changes is reflected wherever necessary to support prioritization and eventual product development. |
| Inputs | Inputs | Inputs | Inputs |
|
|
|
|
| Tools | Tools | Tools | Tools |
|
|
|
|
| Output(s) | Output(s) | Output(s) | Output(s) |
|
|
|
|
| Templates | |||