| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:TaskDescription 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="-SLY9_MQQ_ykBIaLojfgzBQ" name="02_install_validate_infrastructure,_FVOHgDHMEeC7j_IRiP-WPQ" guid="-SLY9_MQQ_ykBIaLojfgzBQ" changeDate="2011-09-13T22:12:43.813-0700" version="7.5.1"> |
| <mainDescription><p>
 |
| A release package cannot be deployed to production if the environmental infrastructure within which the release will be
 |
| run is not sufficiently built or tested. Whether the release is deployed as a "push" (where the application is deployed
 |
| from a central point and proactively delivered to target locations) or a "pull" (where the application is made
 |
| available at central point and pulled by a user at a time of their choosing), the infrastructure needed to support the
 |
| application must be considered and implemented.
 |
| </p>
 |
| <p>
 |
| Some key aspects of installing and/or validating the desired infrastructure:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Identify the requirements and components of the environment configuration
 |
| </li>
 |
| <li>
 |
| Determine the lead times required to establish the infrastructure environments
 |
| </li>
 |
| <li>
 |
| Procure and install the infrastructure components that are not yet available
 |
| </li>
 |
| <li>
 |
| Test the newly installed infrastructure components
 |
| </li>
 |
| <li>
 |
| Test the integration of newly installed components with the rest of the environmental configuration
 |
| </li>
 |
| <li>
 |
| Validate other aspects of the infrastructure including: 
 |
| <ul>
 |
| <li>
 |
| Security components and their integration
 |
| </li>
 |
| <li>
 |
| Database connectivity and security
 |
| </li>
 |
| <li>
 |
| License management, as appropriate
 |
| </li>
 |
| <li>
 |
| Configuration management, in terms of configuration items (CIs)
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| </ul></mainDescription> |
| <sections xmi:id="_IAIH4-B-EeC1y_NExchKwQ" name="Identify infrastructure needs" guid="_IAIH4-B-EeC1y_NExchKwQ"> |
| <sectionDescription>Identify and describe all the components of the infrastructure that are needed to support the upcoming release. These
 |
| requirements should be based completely on the feature set that is about to be deployed, not on intended future needs.</sectionDescription> |
| </sections> |
| <sections xmi:id="_IAIu8eB-EeC1y_NExchKwQ" name="Procure components" guid="_IAIu8eB-EeC1y_NExchKwQ"> |
| <sectionDescription>Determine how long it will reasonably take to procure the needed components and to engage the appropriate division in the
 |
| organization to place the order. Be sure to work with the procurement agency to track the order and to identify any issues
 |
| with that order. Ultimately, the development team, not the procurement agency, is responsible for ensuring that the correct
 |
| infrastructure components are in place.</sectionDescription> |
| </sections> |
| <sections xmi:id="_IAIH5OB-EeC1y_NExchKwQ" name="Schedule components for installation" guid="_IAIH5OB-EeC1y_NExchKwQ"> |
| <sectionDescription>After the procured components arrive, schedule to have them installed by the IT operations group(s) that control the
 |
| production environment. The development team should be developing tests to confirm the correct installation at this time.</sectionDescription> |
| </sections> |
| <sections xmi:id="_IAIH4uB-EeC1y_NExchKwQ" name="Install and test components" guid="_IAIH4uB-EeC1y_NExchKwQ"> |
| <sectionDescription>When the components have been installed, be prepared to run the validation tests developed in the previous step. These
 |
| tests should not only verify the individual components' readiness, but also should validate their integration with each
 |
| other and with legacy components.</sectionDescription> |
| </sections> |
| <sections xmi:id="_IAIu8OB-EeC1y_NExchKwQ" name="Validate other component aspects" guid="_IAIu8OB-EeC1y_NExchKwQ"> |
| <sectionDescription><p>
 |
| As the validation testing is underway, the development team also should consider how the newly installed components
 |
| impact overall system security, whether or not database connectivity and security have been compromised, and what
 |
| impact they have on the configuration management database that contains an inventory of CIs.
 |
| </p>
 |
| <p>
 |
| Also reconcile any licensing issues for the new components with the division that is responsible for documenting and
 |
| tracking enterprise licenses.
 |
| </p></sectionDescription> |
| </sections> |
| <purpose>The purpose of this task is to ensure that all the necessary infrastructure components needed to support a successful
 |
| release are in place.</purpose> |
| </org.eclipse.epf.uma:TaskDescription> |
