Suspect traceability
Links between artifacts in a project or between projects across the lifecycle represent important traceability relationships and dependencies. Stakeholders must be aware of any change that can impact related artifacts. With suspect traceability, linked artifacts are marked with indicators to show that the artifacts might be affected by changes. Team members might need to modify one or more artifacts to maintain logical consistency between the linked artifacts.
Administrators can create suspicion profiles, which specify which link types, artifact types, and attributes to watch in a project to determine if a change puts linked artifacts in a suspect state. For example, an analyst might want to know if there is a change to a "priority" attribute in a user story requirement that is linked to a feature requirement. However, the analyst might not be concerned if the "owner" attribute for the user story is changed.
You can view suspect indicators in various contexts and access the affected artifacts. You can remove the indicators if you determine that the changes are not significant, or when necessary adjustments are made in the linked artifacts to accommodate the change and restore consistency.
Watch videos CLM playlistJazz.net channel User Education channel |
Learn more CLM learning circleAgile learning circle Learning circles |
Ask questions Jazz.net forumdeveloperWorks forums |
Get support Support PortalDeployment wiki Support blog |