Deployment

Implementation Plan

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

DSOR (Release 1-n)

confirm release numbers are still valid 

1.0.0.b38 - this is not in svn

1.0.1.r33792. - confirmed

1.0.1.r33796 -  confirmed

confirm release numbers are still valid 

1.0.1.b29 (sqstage) -developer 

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)

TAD/Operaional Document

Documentation complete

Action: The Document must be copied to the Wiki

System Design Specification (SDS)

Document complete and accurate.

Action: The Document must be copied to the Wiki

ASOR (Final Release  / Handover)

System Description Document

Document complete and accurate.

Action: The Document must be copied to the Wiki

ASOR (Final Release  / Handover)

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)

Performance

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

ASOR (Final Release  / Handover)

Source Code

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

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

Action: ensure Production Branch created

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

1) sqimport

2)sqstage

DSOR (Final Release  / Handover)

Configuration Management Database

The relevant details regarding new or changed infrastructure components have been added to the CMDB in unidesk

ASOR (Release 1-n)

Change Control(s)

A Change & Release record  has been created in unidesk for the LIVE implementation request.

 Action: record unidesk number

ASOR / (Release 1-n)

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)

Production Management Handover

Handover to Applications Management and Technology Management is completed or arranged and the teams are in position to support the application post deployment.

Action: record handover dates

ASOR (Final Release  / Handover)

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)

efin/sciquser

sciquser required for live

efin/sciquest/eauth

sqstage required for live

Password Management (Password Manager Pro)

Password Manager Pro has been updated with all relevant account details including external supplier  accounts

ASOR (Release 1-n)

Environment comparison

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

ASOR (Final Release  / Handover)

Client requirements

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

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)

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)

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)

Vendor Access Required

Does vendor require db/app access (Y/N)

If yes, ensure access details are in TAD

ASOR (Final Release  / Handover)

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)

Deployment Date(s)

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

ASOR (Final Release  / Handover)

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)

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)

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)

service alert

cab approved

service alert

cab approved

Reporting and Analytics

New BI Universes or substantial changes to Universes/report offerings need to be documented in the Information Portal managed by GaSP.

https://www.wiki.ed.ac.uk/display/IP/Information+Portal+Home

ASOR (Release 1-n)

Technical Architecture/Operational Document(TAD)

Documentation complete and accurately reflects the environment subjected to UAT.

ASOR (Release 1-n)

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)

User Accounts

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)

Start/Stop scripts

Are Server Start-up/Shutdown scripts in place?

Including start-up procedure documented, enabled and tested

ASOR (Release 1-n)

Ports

Port allocation file been updated:

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

ASOR (Release 1-n)

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)

DR Copy

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

ASOR/Release1

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)

Support Agreement (including any charging arrangements)

A support agreement OLA is in place for any new applications – including any hosting or support charges. Where external suppliers are involved an SLA should be in place as well.

Action: SLA  moved to wiki:

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

ASOR (Final Release  / Handover)

Time Recording Code

A Time Recording code for the application, if required, has been confirmed and set up (in ASTA)

Action: Does application require a separate entry for business area in ASTA

ASOR (Final Release  / Handover)

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)

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)

Hardware and Software Licensing

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

ASOR (Final Release  / Handover)

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)

Portal Compatibility

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

ASOR (Final Release  / Handover)

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)

User Guide Documentation

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

ASOR (Final Release  / Handover)

Training Material

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

ASOR (Final Release  / Handover)

Demonstration or Walkthrough

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

ASOR (Final Release  / Handover)

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)