Analyzing the impact of change

To analyze changes in the project, you can create baselines after reviews, iterations, and other project milestones are completed. You can filter artifact views to track the status of artifacts. Use suspect traceability to watch for the impact of changes in links between requirements and other artifacts.

About this task

Changes can come in various forms and from various sources. Some teams use change-management systems to record and submit stakeholder needs, enhancement requests, and defects on approved requirements. The Rational solution for Collaborative Lifecycle Management (CLM) helps teams record these types of requests as work items and link them to related requirements. When accepted, these requests can drive not only changes to the requirements, but also changes to linked plan items and test cases. Teams must implement processes to be aware of changes to requirements and linked artifacts and respond to those changes as they affect related artifacts.

Typically, your team defines processes for establishing baselines and artifact approvals. Your project lead can create a project baseline when requirement reviews, formal approvals, iterations, and other milestones have been completed. Baselines can provide a basis for analyzing change in the project. You can filter project artifacts lists for artifacts that have changed since a baseline date. You can also filter artifact views to show artifact status and other attributes.

You can use suspect traceability to monitor the potential impact of changes to linked artifacts.
Important: Suspect traceability is not supported in projects in which configuration management is enabled. However, you can now monitor the impact of changes to linked artifacts using link validity in configuration management enabled projects.
Administrators can create suspicion profiles, which specify which projects, link types, artifact types, and attributes to watch to determine if a change puts linked artifacts in a suspect state. Team members can view suspect indicators in various contexts in the project and access the affected artifacts. You can use your project dashboard to display traceability and the results of shared views, including suspect traceability indicators.

Procedure

  1. Complete reviews of significant requirements and their related artifacts.
  2. Create project baselines to record milestones in the project development.
  3. Filter your Artifacts page to display artifacts that have changed since a particular milestone date. Create views for tracking artifact linking, tags, status, and other attributes. Add requirements views to the project dashboard.
  4. Configure and use suspect traceability to watch for the impact of changes in linked requirements and other artifacts. For information on cross-application linking in CLM, see Linking to development, design, test, and requirement artifacts.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki