There
is a reference field in a CQ record that references 1 or more ReqPro records. A
ReqPro record has one or more columns for CQ record types. The interface maps
record types at either end
Test
Manager test cases have a 'proxy' Test record in ReqPro that can traced to a
'testable requirement' (requirement attribute. The Synchronizer application
handles the coordination.
MS
Project can be synched with ReqPro requirements, CQ records, or CC UCM
activities. However I'd pick one of the latter two or things might get
overloaded if you use the CQ/CC integration.
----------------------------------------------------------------------------
Paul George, Configuration Manager
The Dialog Corporation, Cary NC
----------------------------------------------------------------------------
Sounds Great!
Can
we have more on Traceability of the artifacts at various tools in various
constituents of the project. How do the artifacts in one tools keep the
pointers with the other tools viz. how do the tools communicate with each
other.
For
example,
ClearCase <------> ClearQest <-----------> ReqPro
<----------> TestManager
[George,
Paul] Requirement
ID
ChangeSet <----> Activity
<------> CR.No <-----> ??????<-------------->
???????
( ---------- In
ClearCase ------------- )( ClearQuest
...) ( ReqPro...) (
Manager )
Thanks,
Om Naidu Rational - Administrator ClearCase,
ClearQuest, SCM and CRM consultant, 734-622-4411 Pfizer Inc., 2800,
Plymouth Rd., Ann Arbor,MI. "Reasonable people adapt themselves to the world.
Unreasonable people attempt to adapt the world to themselves. All progress,
therefore, depends on unreasonable people - George Bernard
Shaw"
|