Deployment

Deployment Strategy

 

Dependencies

 

Communication

 

Deployment Checklists

Application checklist 

 

Component

Success Criteria

Project Stage Required (Agile)

Ok (Y/N)

Reviewed By (Date)

Outstanding Actions (Who)

Implementation Plan

Feedback from previous test implementations completed and successful full implementation undertaken for UAT

K:\ISAPPS\dsg\DevelopmentTechnology\ServiceDocs\IS\eIntranet\

DSOR (Release 1-n)

Y

HB 5/12/2014

 

Implementation Risk Assessment

A risk assessment has been undertaken for the Implementation Plan and selected deployment dates. (e.g. roll back)

Database migrated to oracle 11G so rollback possible. Application server implemented as overlay, so rollback starightforward.

ASOR (Release 1-n)

Y

HB 5/12/2014

 

System Design Specification (SDS)

Document complete and accurate.

 

Action: The Document must be copied to the Wiki

Not required Third-party application.

ASOR (Final Release  / Handover)

N/A

HB 5/12/2014

 

System Description Document

Document complete and accurate.

 

Action: The Document must be copied to the Wiki

Not required Third-party application.

ASOR (Final Release  / Handover)

N/A

HB 5/12/2014

 

Scalability/Load Testing

Adequate load testing has taken place. The results have been recorded and analysed to ensure that the application will cope with the anticipated load.

Not required Third-party application.

ASOR (Final Release  / Handover)

N/A

HB 5/12/2014.

 

Performance

The application has been tested against stated performance criteria. Performance has been assured by user and support staff testing.

Not required Third-party application.

ASOR (Final Release  / Handover)

N/A

HB 5/12/2014

 

Source Code

 

Source control must be checked out till go-live and checked-in after go live

Source code has been secured with VSS or other source control tool.

Where code is provided by a third party (e.g. supplier) it has been established who is responsible to maintain source code

Application sourcea and maintained by Netcall, formerly Serengeti Systems

DSOR (Final Release  / Handover)

Y

HB 5/12/2014

 

Configuration Management Database

The relevant details regarding new or changed infrastructure components have been added to the configuration management database (This is currently maintained in the Change Control System)

Change control entries updated

ASOR (Release 1-n)

Y

HB 5/12/2014

 

Change Control(s)

A change control entry has been created for the LIVE implementation request.

ASOR / (Release 1-n)

Y

HB 5/12/2014

 

Test Log Review

A review of the test log (JIRA) has taken place to ensure all required actions have been completed.   If this is not the case, then confirmation on criticality of outstanding issues and action plan for resolution is required.

All critical JIRAs resolved. Remainder in progress

ASOR (Final Release  / Handover)

Y

HB 5/12/2014

 

Production Management Handover

Handover to Production Management is completed and the team are in are in position to support the application post deployment.

Handover delated due to staff availability.  Now agreed and scheduled.

ASOR (Final Release  / Handover)

Y

HB 5/12/2014

 

Support Accounts

Read access accounts or update current read access accounts have been set up for support staff(requires business owner approval)

Upgrade requires all users to have accounts. Bulk import performed during upgrade. Processes for ongoing account management under implementation by Service Management.

ASOR (Final Release  / Handover)

Y

HB 5/12/2014

 

Password Manager (InfoKeep)

InfoKeep has been updated with all relevant account details including external supplier  accounts

Existing accounts retained. Infokeep updated to reflect database migration.

ASOR (Release 1-n)

Y

HB 5/12/2014

 

Environment comparison

Database comparison between TEST and LIVE (might be required before and after go-live)

Test environment refreshed during upgrade.

ASOR (Final Release  / Handover)

Y

HB 5/12/2014

 

Client requirements

 

Does the application have specific client requirements, such as JVM/JRE versions, JInitiator?

If so have these requirements been raised with Desktop services

Wiki pages to be updated:

[1] https://www.wiki.ed.ac.uk/display/insite/Corporate+applications+with+client+based+requirements

[2] https://www.wiki.ed.ac.uk/display/insite/Client+side+requirements+for+corporate+applications

ASOR (Release 1-n)

N/A

HB 5/12/2014

 

Technologies

Is there any new software or technologies involved? (Y/N)

If yes state any additional actions taken to ensure adequate handover to the production support team

Upgrade to existing service. SSO and platform changes covered in handover.

ASOR (Release 1-n)

Y

HB 5/12/2014

 

Access outside University

By default all web based applications are accessible outside University without use of VPN etc Wiki list

If not accessible from outside University this needs to be approved by Production Management.

Existing EDLAN-only access retained.

ASOR (Release 1-n)

Y

HB 5/12/2014

 

Certificates

All changes to certificates or new certificates for this service have to be added to the certificate master list. The certificate master list is being managed by Applications Management This includes TEST and LIVE certificates and records type of certificate and expiry dates.

Existing certificates retained.

ASOR (Final Release  / Handover)

Y

HB 5/12/2014

 

 

Infrastructure checklist

 

Component

Success Criteria

Project Stage Required (Agile)

Ok (Y/N)

Reviewed By (Date)

Outstanding Actions (Who)

Technical Architecture Document(TAD)

Documentation complete and accurately reflects the environment subjected to UAT.

 

Action: TAD needs to be copied to Wiki

TAD located at K:\ISAPPS\dsg\DevelopmentTechnology\ServiceDocs\IS\eIntranet\Technical Architecture

Copied to WIKI

ASOR (Release 1-n)

Y

HB

5/12/2014

 

Operational Document

Describes fully operational tasks and ongoing maintenance.This document should be fully populated and any missing sections or issues should be highlighted.

 

Operational document included in TAD

ASOR (Release 1-n)

Y

HB

5/12/2014

 

Security

All security requirements, e.g. SSL encryption, IP based restrictions firewall requirements have been specified, tested and implemented in LIVE

Upgraded involved unplanned change of port from only  443 to 443 plus  2007.

Firewall changes arranged for NHS sites.

ASOR (Release 1-n)

Y

HB

5/12/2014

 

 

 

 

 

 

 

Patching

Ensure that all applications have an agreed patching schedule and this schedule is agreed with service owners. Different technologies have different patching strategies:

Oracle, Windows, Linux

Application servers unchanged. Database servers advised.

ASOR (Final Release  / Handover)

Y

HB

5/12/2014

 

Infrastructure diagrams

All infrastructure diagrams are updated with newest server and infrastructure detail:

 

https://www.wiki.ed.ac.uk/display/insite/Server+Layout+%28Unix%29

Existing application servers retained and therefore already present in diagram

and

 

https://www.wiki.ed.ac.uk/display/insite/Server+Layout+%28Windows%29

ASOR (Release 1-n)

Y

HB

5/12/2014

 

Start/Stop scripts

Are Server Start-up/Shutdown scripts in place?

Including start-up procedure documented, enabled and tested.

Start/stop scripts created and tested on all environments.

ASOR (Release 1-n)

Y

HB

5/12/2014

 

Ports

Port allocation file been updated:

 

https://www.wiki.ed.ac.uk/display/insite/Port+Allocation+on+Unix+Servers

ASOR (Release 1-n)

 

 

To be completed - DevTech

Backup and Recovery

All backups as noted in the TAD need to be confirmed operational.

 

A test recovery of user data needs to be done to validate the integrity of the recovery mechanism and process.

Database migrated to Oracle11g on oraat1 server. - Covered by standard 11g Dataguard backup process.

Application located on existing server and hence covered by existing process.

ASOR (Release 1-n)

Y

HB

22/12/2014

 

DR Copy

DR copy to Edzell configured and tested(unless existing database which is already setup).

See above

ASOR/Release1

Y

HB

22/12/2014

 

Logs

For all logs the following is in place:

  • Logs are rotated and old logs are archived or deleted to ensure server space is not reached
  • In production only minimal levels of logging is switched on (debug may be adequate on DEV, but not on Production)

Logging detailed in TAD/Operations document section 26.3

ASOR (Release 1-n)

Y

HB

22/12/2014

 

High level Architecture Document (HLA)

If an HLA document exists this document has to be reviewed and moved/stored on the Tech Collab wiki section

Third-party app No HLA.

ASOR (Final Release  / Handover)Y

HB

22/12/2014

 

 

 

Support checklist

 

Component

Success Criteria

 Project Stage Required (Agile)

Ok (Y/N)

Reviewed By (Date)

Outstanding Actions (Who)

Support Agreement (including any charging arrangements)

 

A support agreement (SLA or OLA) is in place for any new applications – including any hosting or support charges.

 

Action: SLA moved to wiki:

 

https://www.wiki.ed.ac.uk/display/insite/SLA+repository+-+Applications+Management

Upgrade to existing third-party application.

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

Time Recording Code

A Time Recording code for the application, if required, has been confirmed and set up.

Existing code ITSS20 - Document Management

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

Disaster Recovery and Business Continuity

Appropriate DR/BC provision is in place and has been fully tested. Application DR/BC details have been transferred to the DR Portfolio and DR level (1, 2 or 3) has been agreed

Existing level 3 retained as details at https://www.wiki.ed.ac.uk/display/insite/Contacts+for+systems+run+or+supported+by+IS-Applications

ASOR (Release 1-n)

Y

HB

22/12/2014

 

Test Environment

An adequate TEST environment has been established for the application which may be used by support to test future changes prior to releasing these in the LIVE environment.

Exisiting test environment refreshed from Live as part of upgade project.

ASOR (Release 1-n)

Y

HB

22/12/2014

 

Hardware and Software Licensing

All required licensing is in place including maintenance/support arrangements with external suppliers.

Product licensing and support contract maintained by Service Management, (Andrew McFarlane).

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

Browser Compatibility

Browser compatibility has been tested and compatibility information updated

See

http://www.ed.ac.uk/schools-departments/information-services/services/computing/application-development/application-support/supported-web-browsers/browser-application

 for details

Application compatible with UoE -supported browsers.

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

Portal Compatibility

Portal compatibility, where required, has been confirmed the Portals Service Owner.

 

ASOR (Final Release  / Handover)

N/A

HB

22/12/2014

 

Help Desk

The new application is recognised with the UniDesk (A business contact queue is defined where initial calls are raised with)

Existing application with existing support process.

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

User Guide Documentation

Appropriate documentation has been produced for users of the new application.

User operational documentation provided by customer groups.

IS Apps quicl access guide updated.

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

Training Material

Training material, if required, has been produced and is of an appropriate standard.

Upgrade addressed back-end update. Client interface unaffected.

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

Demonstration or Walkthrough

Demonstration or walkthrough of the new application has taken place for other stakeholder.

Client interface unaffected, but customer reps involved via UAT.

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

Deployment Date(s)

Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review.

Deployment date actually brought forward with customer agreement  to w/c 3/11/2014 in order to adress critical  SSL/TLS security issue with existing platform.

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

Deployment Resources

IS and business area resources required for deployment, including those needed for post implementation checking and sign off have been secured.

Upgrade performed by Serengeti/Netcall in liaison with DevTech.

ASOR (Final Release  / Handover)

Y

HB

22/12/20147

 

Deployment Ownership

Responsibilities for managing the go-live, including: comms with service owner and end users, ensuring go live timescales are met, managing issues arising and managing comms between all teams involved in go live.

Customer comms managed by Service Management, (Andrew McFarlane).

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

Service Announcement(s)

A Service announcement has been raised with the agreed deployment date on the alert system:

 

http://reports.is.ed.ac.uk/alerts/

 

Service announcements should be raised by Project Manager 10 days before go live, but no later than 4 days.

Service announcement raised by Service Management.

ASOR (Release 1-n)

Y

HB

22/12/2014

 

Web Sites and Other Document Sources

External and internal web sites have been reviewed to ensure that all application references are present, correct and up to date.

WIKI Tech collaboration Document Managment section updated.

ASOR (Final Release  / Handover)

Y

HB

22/12/2014

 

 

 

 

Project Info

Project
Upgrade Document Management System
Code
CMW010
Programme
ISG - Communication (COM)
Project Manager
Tim Gray
Project Sponsor
Alex Carter
Current Stage
Close
Status
Closed
Start Date
03-Feb-2014
Planning Date
n/a
Delivery Date
n/a
Close Date
n/a
Category
Compliance