DNG Requirements Change Control
![]() Is it possible to do requirements change control (RCC) in DNG without using configuration management?
|
5 answers
![]() Sean,
Change management constraints
<label class="constraintLabel" for="dijit_form_CheckBox_0">
To edit this stream, changes must be made in a change set
</label>
To deliver to this stream, change sets must be linked to an approved change request or work item
Is there a way to make an approval lifecycle task in RTC mandatory before a DNG change set can be delivered? Answered above. |
![]()
To be clear, there are two options when configuring Configuration Management in DNG. One is to enforce that each group of changes must be associated with a named "Change Set". I always recommend using this option. The 2nd configuration setting requires a Change Set to be associated to an Approved Work Item before the Change Set can be delivered to a selected Stream. i.e. once a change is done then the Work Item can be used to manage the approval process prior to delivery.
I think in your post you have missed the 2nd configuration setting. Enforce that Work Items must be approved prior to delivery to your Stream.
Is it possible to do Requirements Change Control (RCC) without opting in to Configuration Management? Not easily, no. One could attempt a Change Control process using a combination of Workflow and access rights but this would get quite complicated and I would not recommend it. If you wish to have Change Management but not break this down into version or variant streams then the easiest way to start would be to opt-in to Configuration Management and define only a single Stream.
|
![]() ^
|
![]()
^It's OK I figured it out.
On the Task there is an Approvals tab which I had missed before. I added an approval and then added myself as an approver for the approval. Then the task is deliverable.
|
![]()
>>the easiest way to start would be to opt-in to Configuration Management and define only a single Stream.
So it seems that Configuration Management for RM can be used in 2 ways:-
A. Managing 2 parallel streams of requirements where one set is a variation of the other and using change sets to manage delivery of 'bundles' of changes between the streams (with or without RTC approvals) or CM can be use for B. Managing change control of requirements by using a single stream and requiring that change sets be used and also requiring that an approved work item be linked to any change set before it is delivered.
?
The only issue with this second scenario is that it seems that the whole project is either under change control or not. Whereas a real world scenario might involve the Stakeholder Reqs being under change control but the System Reqs being freely editable.
So I guess that you would need to use components to separate out different types of requirement in that case?
If that is the case then I would be interested to know if anyone is really doing this.
|
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.