| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.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><p>
 |
| The purpose of this discipline is to:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Maintain a consistent set of work products as they evolve
 |
| </li>
 |
| <li>
 |
| Maintain consistent builds of the software
 |
| </li>
 |
| <li>
 |
| Provide an efficient means to adapt to changes and issues, and re-plan work accordingly
 |
| </li>
 |
| <li>
 |
| Provide data for measuring progress
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| In many organizations, the term "configuration management" implies all of these things.
 |
| </p>
 |
| <p>
 |
| Within the context of this process, configuration management refers to the ability to maintain <a class="elementLink" href="./../../openup/guidances/termdefinitions/version_F3A31B17.html" guid="_eX8K8ElyEducWJcS4yanqg">version</a>s of artifacts and consistent <a class="elementLink" href="./../../openup/guidances/termdefinitions/configuration_FE64B3D8.html" guid="__Cw30ElxEducWJcS4yanqg">configuration</a>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.
 |
| </p>
 |
| <p>
 |
| Although it is important to keep up-to-date versions and configurations of all work products, the primary work products
 |
| of concern are the <a class="elementLinkWithType" href="./../../openup/workproducts/implementation_917CA61E.html" guid="_0YoQcMlgEdmt3adZL5Dmdw">Artifact: Implementation</a> and the <a class="elementLinkWithType" href="./../../openup/workproducts/build_95D7D8FD.html" guid="_0YuXEMlgEdmt3adZL5Dmdw">Artifact: Build</a>.
 |
| </p>
 |
| <p>
 |
| Changes are managed via the <a class="elementLinkWithType" href="./../../openup/tasks/request_change_A048C387.html" guid="_0mwzEclgEdmt3adZL5Dmdw">Task: Request Change</a> and subsequent prioritization and disposition of change requests via the <a class="elementLinkWithType" href="./../../openup/workproducts/work_items_list_39D03CC8.html" guid="_rGNWsCbSEdqh1LYUOGRh2A">Artifact: Work Items List</a>.
 |
| </p>
 |
| <p>
 |
| 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.
 |
| </p>
 |
| <p>
 |
| Configuration and change management is performed 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.
 |
| </p></mainDescription> |
| <keyConsiderations><p>
 |
| It is assumed that the project has some form of configuration management system, such as CVS, to maintain version and
 |
| configuration information, and to enable collaborative system development. Without this, all but the most trivial of
 |
| development will be virtually impossible.
 |
| </p></keyConsiderations> |
| </org.eclipse.epf.uma:ContentDescription> |