Deployment

Implementation Plan

Feedback from previous test implementations completed and successful full implementation undertaken for UAT.  RMC - Completed Successfully in Test and TRN

DSOR 

 Y

6/9/13

Implementation Risk Assessment

A risk assessment has been undertaken for the Implementation Plan and selected deployment dates. (e.g. roll back) RMC - Deployment has to happen at this point there is no rollback SSP resource will fix any issues with the implementation.

ASOR 

Y

6/9/13

System Design Specification (SDS)

Document complete and accurate.

Action: The Document must be copied to the Wiki RMC - All of the technical documentation is within greenhooper of what was implemented against each individual story,

ASOR (Final Release  / Handover)

n/a

6/9/13

System Description Document

Document complete and accurate.

Action: The Document must be copied to the Wiki.

RMC - Not a seperate SDD as part of EUCLID. However is a document describing functionaly what has been delivered.

ASOR (Final Release  / Handover)

Functional Description instead of SDD.

6/9/13

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. RMC - No load testing carried have focused on providing perfomance for the size of queries which are required and metrics to support this.

ASOR (Final Release  / Handover)

n/a

6/9/13

Performance

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

RMC - Metrics have been provided to SACS support and to the business

ASOR (Final Release  / Handover)

Y

6/9/13

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 RMC - Link to a project within SITS which documents what is being implemented as per standard SITS deployment.

DSOR (Final Release  / Handover)

n/a

6/9/13

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 

n/a - As per EUCLID

6/9/13

Change Control(s)

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

RMC - Through SACS Support 

ASOR / (Release 1-n)

n/a

6/9/13

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.

RMC - This has been an Agile Project so there are outstanding issues which are currently in a bcklog which will be moved to the next project.  Business have agreed this process. These are in the SACS version of greenhopper not in JIRA.

ASOR (Final Release  / Handover)

n/a

6/9/13

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)

In Progress

6/9/13

Support Accounts

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

RMC - As per EUCLID.

ASOR (Final Release  / Handover)

n/a 

6/9/13

Password Manager (InfoKeep)

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

ASOR (Release 1-n)

n/a

6/9/13

Environment comparison

Database comparison between TEST and LIVE (might be required before and after go-live) No datebase changes except one index being created.

ASOR (Final Release  / Handover)

n/a

6/9/13

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 

n/a

6/9/13

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 

n/a

6/9/13

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 

As per EUCLID

6/9/13

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)

n/a

6/9/13

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)

As per EUCLID

6/9/13

Time Recording Code

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

ASOR (Final Release  / Handover)

As per EUCLID

6/9/13

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)

As per EUCLID

6/9/13

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 - As per EUCLID

6/9/13

Hardware and Software Licensing

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

ASOR (Final Release  / Handover)

As per EUCLID

6/9/13

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)

As per EUCLID

6/9/13

Portal Compatibility

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

ASOR (Final Release  / Handover)

n/a

6/9/13

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)

As per EUCLID

6/9/13

User Guide Documentation

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

RMC - Full training and user guides have been provided as per SACS support

ASOR (Final Release  / Handover)

Yes

6/9/13

Training Material

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

RMC - Full training and user guides have been provided as per SACS support. Training is also being produced for each of the colleges.

ASOR (Final Release  / Handover)

Yes

6/9/13

Demonstration or Walkthrough

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

RMC - A walkthrough will be arranged with applications management

ASOR (Final Release  / Handover)

No

6/9/13

RMC

Deployment Date(s)

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

ASOR (Final Release  / Handover)

Y

6/9/13

Deployment Resources

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

Yes - All resourcing has been booked included post implementation support cover from SSP.

ASOR (Final Release  / Handover)

Y

6/9/13

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.

RMC - Comms will come from SACS. Post Implementation support is arranged within SSP.

ASOR (Final Release  / Handover)

Y

6/9/13

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.

RMC - Will follow normal SACS process for changes to be implemented into EUCLID.

ASOR 

Y

6/9/13

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)

N - As per EUCLID.

6/9/13