| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ArtifactDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-4Fv0TSuJBCRxarK5ssyLGw" name="deployment_plan,_j0qgcGPoEeCXEsUUiTbOuQ" guid="-4Fv0TSuJBCRxarK5ssyLGw" changeDate="2012-05-30T14:25:00.538-0700" version="7.5.1"> |
| <mainDescription><p>
 |
| The deployment plan should contain the unique instructions for deploying a particular version of a product. By "unique
 |
| instructions" we mean those things that are not part of a deployment engineer's normal procedures. Rather, they often
 |
| are specific procedures and timing constraints that a deployment engineer should be aware of as they are rolling out a
 |
| particular release.
 |
| </p>
 |
| <p>
 |
| While&nbsp;a draft version of the&nbsp;deployment plan is typically developed by a development team, the deployment
 |
| engineer is responsible for its contents and existence.&nbsp;A deployment plan&nbsp;normally consists of the following
 |
| sections:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The scope of the release and a general overview of the capabilities to be deployed
 |
| </li>
 |
| <li>
 |
| The timing and dependencies for deploying components to various nodes
 |
| </li>
 |
| <li>
 |
| The risks or issues associated with the release based on a risk assessment
 |
| </li>
 |
| <li>
 |
| The customer organization, stakeholders, and end user community that will be impacted by the release
 |
| </li>
 |
| <li>
 |
| The person or persons who have the authority to approve the release as "ready for production"
 |
| </li>
 |
| <li>
 |
| The development team members responsible for delivering the release package to the Deployment Manager, along with
 |
| contact information
 |
| </li>
 |
| <li>
 |
| The approach for transitioning the release package to the Deployment Engineer, including appropriate communications
 |
| protocols and escalation procedures
 |
| </li>
 |
| <li>
 |
| The success criteria for this deployment; in other words, how will the Deployment Engineer know that the release is
 |
| successful so it can report success
 |
| </li>
 |
| </ul></mainDescription> |
| <purpose>The purpose of this work product is to capture, in one document, the unique information that will be consumed by deployment
 |
| engineers before and during the deployment to production of a particular release package.</purpose> |
| </org.eclipse.epf.uma:ArtifactDescription> |
