Change Management: DOORS only or DOORS + EWM
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
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.