When it comes to requirements management, it’s important to optimize the use of your data. To do
that, you must understand the effect of change and be able to strategically reuse information.
Change is inevitable;
don’t ignore or reject it. Instead, understanding and managing change is the only
way to truly keep control of project costs and quality. Perhaps a supplier is unable to meet an
target for cost or performance, or a test reveals that what was planned is not possible. Or, more
a requirement that has been acted upon needs to be either altered or corrected.
Effective change management is crucial. For every change, you must:
- Understand the impact of the change before
it is made
- Ensure that all impacted areas are changed
Using traditional requirements management methods, you cannot easily understand the relationships
between pieces of information.
If a test fails, or if a client issues an updated specification, documents and spreadsheets cannot
analyze the impact. It can take weeks for the individual responsible for requirements management
understand the impact of the change.
IBM’s requirements management tools help your whole team assess the impact of change before it
happens, allowing teams to
create a strategy for change and respond appropriately.
Teams can create a perspective or view of their data that shows where their requirements have
relationships to other data
spanning the entire development process. Users can graphically explore the complex mesh of
to understand the impact of change across multiple levels and domains. This information updates
when any team member makes changes. If a downstream requirement changes, users can immediately see
the potential impact of the change.
As changes occur, teams using traditional tools spend a lot of effort communicating the changes
and ensuring that all impacted
areas are addressed. By using an on-premises or cloud based requirements management solution,
and design teams get a comprehensive history of every requirement change. Collaborative teams can
see what changed, who changed it, and when it changed. IBM’s tools also take advantage of the
between information. The system can alert users of a change so they can review and act on it
After they asses the change, the alert can be cleared. With a minimum level of effort, changes
down all levels of linked data in the project.