What's the recommended approach to setting Suspicion Profiles Crossing RDNG PAs?
Accepted answer
Let's say your two projects are called "Business Requirements" and "System Requirements" respectively and you want to monitor the "Link To/Link From" relationship. Here is the check list.
1. The two projects are associated with one another with the "Provides Related Requirements" relationship.
2. In the details page of "Suspicion Profiles for Business Requirements", there are at least two sections of link types to follow - "Link Types for Business Requirements" and "Link Types for System Requirements". Make sure that the "Link" link type is at "Watching" state in the "Link Types for System Requirements" section (important).
3. Make sure that the suspicion profile is enabled in the "Business Requirements" project.
4. In the details page of "Suspicion Profiles for System Requirements", there are at least two sections of link types to follow - "Link Types for Business Requirements" and "Link Types for System Requirements". Make sure that the "Link" link type is at "Watching" state in the "Link Types for Business Requirements" section (important).
5. Make sure that the suspicion profile is enabled in the "System Requirements" project.
Based on your description, it appears that only the link types in the "Link Types for System Requirements" section of "Suspicion Profiles for System Requirements" are being monitored. In other words, only links within the same project "System Requirements" are being monitored. You need to enable the "cross project" bit as mentioned above.
Comments
Thanks for the clarification. Indeed, that's not exactly the setup we have. I'll be making the recommended changes to ensure it meets what you described.
@dnong - The suggested setup worked, with one consideration.
That's an expected behavior and not a defect.
The suspect state is for an artifact, under a suspicion profile. It is not another "link" relationship, so there is nothing to "carry over".
Let's put it this way, the suspicion profile only monitor "incoming" relationships, and does not care about "outgoing" relationships. Incoming changes flag the artifacts as suspects. When you clear the suspect status, you basically say "let's ignore these changes".
@dnong - I'm not sure I understand.
Is this really the expected and designed behavior? Is there any benefit in having the tool behave this way that I'm missing?
It appears that I'm wrong in saying the suspicion profile not caring about the "outgoing" relationship. When an artifact is causing another artifact to be a suspect, the outgoing suspicion is flagged in the link section and the "Clear All Suspicion" icon becomes enabled in the overview section.
If both the outgoing and incoming suspicion are in the same project area (or under the same suspicion profile), using the "Clear All Suspicion" (or "Clear for profile") function will clear both suspicion.
If however the outgoing and incoming suspicion are in different project areas (hence definitely in different suspicion profiles), there is currently no such function to clear the suspicion in both profiles. As mentioned earlier, RM only clear suspicion within the profile.
I'm leaning towards an RFE to improve this bit, and the functionality is limited to RM only. So it will not work for a CCM/RM or QM/RM.
One other answer
What about the case where the Only interaction allowed between the projects is the link?
We have over 150 projects and growing. Managing the association between project A and project B just to get suspect flags is a lot of overhead.
Comments
If the suspicious profile is not bound to a project area, it will mean that the tracking will check the entire repository for changes for each update period. Is it what you want? If so, you can open an RFE to change the current implementation.
https://www.ibm.com/developerworks/rfe/