Scope

Scope 

To make the multiple version of the software easier to understand, the three PURE upgrades and their associated implications have been put in the following table: 

• The project was initiated when PURE upgrade 4.20.1 was released at the end of 2014. 
  • This release required that Java be upgraded to version 1.8.
  • Due to the added Java requirement, this upgrade was raised as an in-year project, rather than being completed through the usual support arrangements. 
  • Due to time constraints, the business requested that the software install be applied to Dev in parallel with the project planning process. 
  • Initial tests seemed to indicate that the software was acceptable, and could safely be released into Test.  This was therefore carried out.
  • During business UAT testing in Test, a "show-stopper" issue was identified.

• The vendor released fix 4.20.3.  This fix was applied to Dev. 
  • Initial tests seemed to indicate that the software was acceptable, and could safely be released into Test.  This was therefore carried out.
  • During business UAT testing in Test, a larger issue was uncovered.  This issue related to data compliance, and meant that the Interim upgrade could not be approved for deployment to Live.

• The software vendor released a major version release, 4.21.1.  This included a fix for the issue identled in version 4.20.3. 
  • This release required that Tomcat be upgraded to version 8. 
  • Following the Tomcat upgrade, release 4.21.1 was applied to Dev. 
  • During business testing in Dev, two "show-stopper" issues were identified in Dev.

• The software vendor released fix 4.21.3.   This fix was applied to Dev. 
  • This release fixed one of the two "show-stopper" issues, but the other still remained.

• The software vendor released fix 4.21.4.   This fix was applied to Dev. 
  • This release did not fix the previously-reported "show-stopper" issue.

• The software vendor released fix 4.21.4-1.   This fix was applied to Dev. 
  • This release is currently undergoing business testing in Dev.

This project will manage and deliver the upgrade of Java to version 1.8, the upgrade of Tomcat to version 8, and the upgrade of PURE to the version that passes business UAT testing.

Project Objectives and Deliverables

This project will:

1. Upgrade Java to version 1.8 on PURE's Dev, Test and Live environments (including DR).
2. Upgrade Tomcat to version 8 on PURE's Dev, Test and Live environments (including DR).
3. Upgrade PURE's Dev environment (until a version passes business testing).
4. Clear down the PURE Test environment, and refresh it from PURE Live.
5. Upgrade PURE (to the version that passes business testing in Dev) on PURE's Test and Live environments (including DR).
6. Support the business as they run regression testing.

Success Criteria

1. PURE continues to function as normal using the new version of Java and Tomcat.
2. Upgrades are undertaken with minimal impact to the production service. 
3. The latest version of the software rectifies the information errors present in the previous two versions.

Project Boundaries / Exclusions

This project will not make any changes to the PURE project model. Any required project model changes will be delivered by the project/s that require that functionality.

This project assumes that the six separate PURE versions outlined above will be sufficient to resolve all "show-stopper" issues.  If any further versions are required, then estimates will be revised, and the additional effort will have to be authorised by the Project Sponsor and the Programme Manager.

IS will not carry out any application testing.  Rather, the business will perform their own regression tests. 

IS will perform technology testing and will support the business testing.  If the testing requirement exceeds the time estimated for support, then estimates will be revised, and the additional effort will have to be authorised by the Project Sponsor and the Programme Manager.

If further major PURE versions are released while the project is in progress, these will be held until the Live environment has been successfully upgraded, and the project closed.  Future upgrades will then be completed through the usual support arrangements. 

Project Assumptions and Constraints

Assume that there is no software development required.  The only resource required will be from Development Technology and Production Management.