Requirements Workflow

The RM application (RRC V3.0.1) does not expose the work flow engine for customized workflows. And the RRC review and approval work flow is "hard coded". The RRC V3 license does include the RTC work item capability, so you can define workflows (for example for change request work items) and link them to the requirements artifacts (including RRC review and approval artifacts). But the work items do not control the state of the requirements artifacts.

By contrast, Rational DOORS 9.3 does support a change request process driven by RTC or ClearQuest or Change -- with whatever change process you have defined in your Change Management tool. And the CM tool DOES control the state of the requirements objects in DOORS through the lifecycle of a change request.

The RM application (RRC V3.0.1) does not expose the work flow engine for customized workflows. And the RRC review and approval work flow is "hard coded". The RRC V3 license does include the RTC work item capability, so you can define workflows (for example for change request work items) and link them to the requirements artifacts (including RRC review and approval artifacts). But the work items do not control the state of the requirements artifacts.

By contrast, Rational DOORS 9.3 does support a change request process driven by RTC or ClearQuest or Change -- with whatever change process you have defined in your Change Management tool. And the CM tool DOES control the state of the requirements objects in DOORS through the lifecycle of a change request.

So, if i want to use a customize workflow for CLM 3.0.1 the RM app does not fit into my needs?.
Because I want to use a CLM 3.0.1 with RQM also and need the workflows of the requierments.

No. The process engine is not available to drive custom work flows over artifacts in the RM repository / RRC V3.0.1.

No. The process engine is not available to drive custom work flows over artifacts in the RM repository / RRC V3.0.1.

And why is that? that the requirement has a work flow is not on the standards of the CLM? Because Now in CLM 3.0.1 we can only provide requirements from RM(RRC) and not from CCM (RTC).

And why is that? that the requirement has a work flow is not on the standards of the CLM? Because Now in CLM 3.0.1 we can only provide requirements from RM(RRC) and not from CCM (RTC).

It's a point-in-time limitation -- one we would like to address in a future release.

No. The process engine is not available to drive custom work flows over artifacts in the RM repository / RRC V3.0.1.

And why is that? that the requirement has a work flow is not on the standards of the CLM? Because Now in CLM 3.0.1 we can only provide requirements from RM(RRC) and not from CCM (RTC).

What is the requirement work flow usage that you are looking for?

I ask because CLM 3.0.1 does have workflow. The CCM application can be used to control the creation/use of assets. For example, suppose you have a set of requirements that are reused by several projects, at once, with different release schedules. By using ccm it is possible that each project has its own parent work item that references the reused requirements. The development and testing of the requirement, by various teams, can then be tracked/controlled by the child work items in the various project plans.

Also any discovered requirement change requests/defects can be tracked back to the originating requirements for updated in a later release by the analysts.

We use this way of working in the CLM 3.0.1 Money that Matters example scenario

https://jazz.net/wiki/bin/view/Main/MTM_Lifecycle_Scenario

To create the original requirements there can be tasks to control the development and review of requirements.