blob: 3e261395a48c2a2cbc3bff280850942126c9561f [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" rmc:version="7.1.0" epf:version="1.0.0" xmi:id="_H9TXMLv-EdmmUvZAZjqE3g" name="change_management,_0TwXgMlgEdmt3adZL5Dmdw" guid="_H9TXMLv-EdmmUvZAZjqE3g" changeDate="2006-09-28T10:05:40.519-0700" version="1.0.0">
<mainDescription>&lt;p&gt;
The purpose of this discipline is to:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
Maintain a consistent set of work products as they evolve.
&lt;/li&gt;
&lt;li&gt;
Maintain consistent builds of the software.
&lt;/li&gt;
&lt;li&gt;
Provide an efficient means to adapt to changes and issues and re-plan work accordingly.
&lt;/li&gt;
&lt;li&gt;
Provide data for measuring progress.
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
In many organizations, the term &quot;configuration management&quot; implies all of these things.
&lt;/p&gt;
&lt;p&gt;
Within the context of this process, configuration management refers to the ability to maintain&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/guidances/termdefinitions/version,_eX8K8ElyEducWJcS4yanqg.html&quot; guid=&quot;_eX8K8ElyEducWJcS4yanqg&quot;&gt;version&lt;/a&gt;s of artifacts and consistent&amp;nbsp;&lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/guidances/termdefinitions/configuration,__Cw30ElxEducWJcS4yanqg.html&quot; guid=&quot;__Cw30ElxEducWJcS4yanqg&quot;&gt;configuration&lt;/a&gt;s of artifacts, addressing the first two objectives listed above.
Change Management refers to the process of managing changes to configuration controlled artifacts, addressing the
latter two objectives listed above.
&lt;/p&gt;
&lt;p&gt;
Although it is important to keep up to date versions and configurations of all work product, the primary work products
of concern&amp;nbsp;are the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/implementation,_0YoQcMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0YoQcMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Implementation&lt;/a&gt;&amp;nbsp;and&amp;nbsp;the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/build,_0YuXEMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0YuXEMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Build&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Changes are managed via the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/tasks/request_change,_0mwzEclgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0mwzEclgEdmt3adZL5Dmdw&quot;&gt;Task: Request Change&lt;/a&gt;&amp;nbsp;and subsequent prioritization and disposition of change requests via the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../openup_basic/workproducts/work_items_list,_rGNWsCbSEdqh1LYUOGRh2A.html&quot; guid=&quot;_rGNWsCbSEdqh1LYUOGRh2A&quot;&gt;Artifact: Work Items List&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
This discipline spans the entire lifecycle. Every other discipline relies upon the configuration and change management
discipline to maintain a consistent, up to date, set of work products and to prioritize and track changes to those work
products throughout the lifecycle.
&lt;/p&gt;
&lt;p&gt;
Configuration and change management is done by everyone on the development team. Because of the importance and
pervasiveness of this discipline, configuration and change management guidance is associated with tasks and work
products in all other disciplines.
&lt;/p&gt;</mainDescription>
<keyConsiderations>&lt;p&gt;
It is assumed that the project has some form of configuration management system, such as CVS, to maintain version and
configuration information and enable collaborative development of the system. Without this, all but the most trivial of
development will be virtually impossible.
&lt;/p&gt;</keyConsiderations>
</org.eclipse.epf.uma:ContentDescription>