Change Management: DOORS only or DOORS + EWM
Change management can be done inside an RM project by creating an RM artifact type ChangeRequest
|
3 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Apr 01 '21, 7:58 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER 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. |
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.
|
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
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.