It's all about the answers!

Ask a question

Change Management: DOORS only or DOORS + EWM

Sean F (1.3k247158) | asked Apr 01 '21, 11:34 a.m.

Change management can be done inside an RM project by creating an RM artifact type ChangeRequest

The ChangeRequest artifact type can be given a workflow like any artifact type in RM.

A ChangeRequest artifact can be created and linked to Requirement artifacts to show impact and track the effects of change.

Alternatively Requirements change management can be done by linking EWM/RTC with DOORS in a lifecycle project. Change Request Items can be created in EWM and linked to requirements in DOORS.

The lifcycle definition feature in EWM seems identical to that in RM.

The former single product approach seems simpler.

What are the advantages of the more complex approach using 2 products?

3 answers

permanent link
Geoffrey Clemm (30.1k33035) | answered Apr 01 '21, 7:58 p.m.

In addition to the list from Bartosz, if you turn on versioning, in your DNG project area, your DNG change request artifact gets put under version control, which isn't at all what you want for a change management artifact.   The bottom line is that using EWM for change tracking (and not DOORS Next) is the only recommended approach.

permanent link
Bartosz Chrabski (3.4k22949) | answered Apr 01 '21, 6:43 p.m.

 1. Planning in EWM

 2. Notifications in EWM (emails)
 3. EWM scales up much better than RM
 4. EWM is already included in the DNG license. 

permanent link
Davyd Norris (2.4k217) | answered Apr 03 '21, 10:07 p.m.
I agree with all the above - why would you go to all the trouble of shoehorning DNG when you have a built in solution and are licensed to use it????

This is often something I see when people come form a DOORS Classic background where test management and change management were additional products and so people would follow the old saying of "When all you have is a hammer, everything looks like a nail"

To the above list I would add:
 - workflow preconditions that give you huge control over the process
 - attribute customisation and calculated values
 - child work items with workflow enforcement
 - approvals with electronic signatures, and workflow enforcement
 - out of the box widgets and reports that show how the process is going
 - timelines, teams, subteams and roles with different levels of process control via preconditions on the workflows

Your answer

Register or to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.