Deployment

Implementation Plan

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

DSOR (Release 1-n)

Y

20-Aug-15 APW

Implementation Risk Assessment

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

ASOR (Release 1-n)

Y

28-Jul-15 APW

Application deployed to Live for a week before real go-live.

System Design Specification (SDS)

Document complete and accurate.

Action: The Document must be copied to the Wiki

ASOR (Final Release  / Handover)

Y

28-Jul-15 APW

Copied to Wiki @ https://www.wiki.ed.ac.uk/display/insite/Uniware+Feed

System Description Document

Document complete and accurate.

Action: The Document must be copied to the Wiki

ASOR (Final Release  / Handover)

N

20-Aug-15 APW

Reviewed @ https://www.wiki.ed.ac.uk/display/insite/System+Description+Document+-+Uniware+Feed (Apps Mgmt)

Thalia sent a list of alterations to be completed by Adam as she is on leave. Adam has yet to update the SDD

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.

ASOR (Final Release  / Handover)

Y

28-Jul-15 APW

Load tested in Test daily with entire student population.

Performance

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

ASOR (Final Release  / Handover)

Y

28-Jul-15 APW

Very fast full export of all active card holders when deployed in Live

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

DSOR (Final Release  / Handover)

N

20-Aug-15 APW

Adam to ensure a production branch has been setup (Apps Mgmt)

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)

ASOR (Release 1-n)

Y

29-Jul-15 APW

Stefan confirmed that Project Rfc not required in UniDesk for new interfaces.

Change Control(s)

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

ASOR / (Release 1-n)

Y

20-Aug-15 APW

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.

ASOR (Final Release  / Handover)

N

20-Aug-15 APW

There are still outstanding 'Must Have' JIRAs

Production Management Handover

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

Completed 29-Jul-15.

Support Accounts

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

ASOR (Final Release  / Handover)

Y

28-Jul-15 APW

No new support access requirements.

Password Manager (InfoKeep)

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

ASOR (Release 1-n)

Y

28-Jul-15 APW

Credentials used to transfer files to Uniware has been added to UniDesk.

Environment comparison

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

ASOR (Final Release  / Handover)

Y

28-Jul-15 APW

An issue was discovered and raised as a support issue in P1507-015.

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)

Y

28-Jul-15 APW

n/a

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

ASOR (Release 1-n)

Y

28-Jul-15 APW

OK - no new technologies

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.

ASOR (Release 1-n)

Y

28-Jul-15 APW

n/a

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.

ASOR (Final Release  / Handover)

Y

28-Jul-15 APW

n/a

Technical Architecture Document(TAD)

Documentation complete and accurately reflects the environment subjected to UAT.

Action: TAD needs to be copied to Wiki

ASOR (Release 1-n)

Y

29-Jul-15 APW

Copied to wiki @ https://www.wiki.ed.ac.uk/display/insite/Uniware+Feed

Operational Document

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

Action: TAD needs to be copied to Wiki

ASOR (Release 1-n)

Y

20-Aug-15 APW

Security

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

ASOR (Release 1-n)

Y

29-Jul-15 APW

There was a security concern raised about Uniware forcing us to use a username/password to connect via sftp rather than public/private keys. Agreed nothing we could do about this at the present time.

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

n/a

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

and

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

ASOR (Release 1-n)

Y

29-Jul-15 APW

n/a

Start/Stop scripts

Are Server Start-up/Shutdown scripts in place?

Including start-up procedure documented, enabled and tested.

ASOR (Release 1-n)

Y

29-Jul-15 APW

n/a

Ports

Port allocation file been updated:

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

ASOR (Release 1-n)

Y

29-Jul-15 APW

n/a

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.

ASOR (Release 1-n)

Y

29-Jul-15 APW

Copy of cron script is available on failover site should it be necessary to restore service.

DR Copy

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

ASOR/Release1

Y

21-Aug-15 APW

Specified in TAD

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)

ASOR (Release 1-n)

Y

20-Aug-15 APW

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

ASOR (Final Release  / Handover)

Y

21-Aug-15 APW

Replaces exisiting service, so no new SLA required.

Time Recording Code

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

Use existing Accommodation Services code

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

ASOR (Release 1-n)

Y

21-Aug-15 APW

As mentioned in TAD - no requirement for resilience and not tested.

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.

ASOR (Release 1-n)

Y

29-Jul-15 APW

Hardware and Software Licensing

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

ASOR (Final Release  / Handover)

Y

21-Aug-15 APW

Lauren in Accommodation Services has confirmed that they have a support agreement in place with Uniware.

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

n/a

Portal Compatibility

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

Help Desk

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

n/a

User Guide Documentation

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

Accommodation Services's responsibility.

Training Material

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

Accommodation Services's (AS's) responsibility.

Demonstration or Walkthrough

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

AS's responsibility

Deployment Date(s)

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

Acceptance Sign Off occurred in advance of deployment - however project will not be officially signed-off until 14th August, so deployment acceptance review will review that all tasks have been completed.

Deployment Resources

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

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

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.

ASOR (Final Release  / Handover)

Y

20-Aug-15 APW

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.

ASOR (Release 1-n)

Y

20-Aug--15 APW

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.

ASOR (Final Release  / Handover)

Y

29-Jul-15 APW

AS's responsibility.