Deployment
Deployment Strategy
Live deployment planned for Monday 26th September 2016 (according to Milestone delivery date).
Dependencies
New version of eRecruitment Successful applicants code is dependant on 'HRS089 eRecruitment Upgrade' eRecruitment Successfull applicants code being deployed first. HRS089 upgrade scheduled to be completed on Saturday 24th. The Successful Applicants code would next run on Monday 26th September at 1pm.
Communication
To be done by HR systems team to end users.
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 | DSOR (Release 1-n) | Y | John Chan 30/07/2015 |
|
Implementation Risk Assessment | A risk assessment has been undertaken for the Implementation Plan and selected deployment dates. (e.g. roll back) Roll back plan | ASOR (Release 1-n) | Y | John Chan 30/07/2015 |
|
System Design Specification (SDS) | Document complete and accurate.
Action: The Document must be copied to the Wiki
| ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
System Description Document | Document complete and accurate.
Action: The Document must be copied to the Wiki No SDD for the HR service | ASOR (Final Release / Handover) | N/A | John Chan 30/07/2015 |
|
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. No Load testing taken place as the numbers accessing UOE Self Service would not be increasing. Dev Tech mentioned that when Self Service was implemented, Load testing had been done back then and would not need to be done again
| ASOR (Final Release / Handover) | N/A | John Chan 30/07/2015 |
|
Performance | The application has been tested against stated performance criteria. Performance has been assured by user and support staff testing. No performance issues highlighted during UAT. | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
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 | John Chan 30/07/2015 | Post Deployment Task: for JC/Pam S to check SVN. |
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) No changes | ASOR (Release 1-n) | N/A | John Chan 30/07/2015 |
|
Change Control(s) | A change control entry has been created for the LIVE implementation request. | ASOR / (Release 1-n) | N | John Chan 30/07/2015 | Morna to raise Change Control |
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. To be reviewed during ASOR. | ASOR (Final Release / Handover) | N | John Chan 30/07/2015 |
|
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) | N | John Chan 30/07/2015
| No offical handover. JC to speak to AF to see if we want one. |
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 | John Chan 30/07/2015 |
|
Password Manager (InfoKeep) | InfoKeep has been updated with all relevant account details including external supplier accounts New functional account details entered in InfoKeep. Apps > HR | ASOR (Release 1-n) | Y | John Chan 30/07/2015 |
|
Environment comparison | Database comparison between TEST and LIVE (might be required before and after go-live) | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
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
No new specific client requirements to access Online Paylips required from with HR Self Service. | ASOR (Release 1-n) | N/A | John Chan 30/07/2015 |
|
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 No new client technologies involved. | ASOR (Release 1-n) | N | John Chan 30/07/2015 |
|
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 | John Chan 30/07/2015 |
|
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. No changes to existing certificates being used. | ASOR (Final Release / Handover) | N/A | John Chan 30/07/2015 |
|
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 | ASOR (Release 1-n) | Y | Tech Mgmt to review |
|
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 | Tech Mgmt to review |
|
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 | Tech Mgmt to review |
|
|
|
|
|
|
|
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 No changes to current existing patching schedule
| ASOR (Final Release / Handover) | N/A | John Chan 30/07/2015 |
|
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 No changes to existing infrastructue required. | ASOR (Release 1-n) | N/A | John Chan 30/07/2015 |
|
Start/Stop scripts | Are Server Start-up/Shutdown scripts in place? Including start-up procedure documented, enabled and tested. No changes to existing infrastructue required.
| ASOR (Release 1-n) | N/A | John Chan 30/07/2015 |
|
Ports | Port allocation file been updated:
https://www.wiki.ed.ac.uk/display/insite/Port+Allocation+on+Unix+Servers No changes to port numbers. | ASOR (Release 1-n) | N/A | John Chan 30/07/2015 |
|
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. No changes to backup and Recovery procedures. | ASOR (Release 1-n) | N/A | John Chan 30/07/2015 |
|
DR Copy | DR copy to Edzell configured and tested(unless existing database which is already setup). No DR testing required as part of this project as only software changes and application configuration settings | ASOR/Release1 | N/A | John Chan 30/07/2015 |
|
Logs | For all logs the following is in place:
| ASOR (Release 1-n) | N/A | John Chan 30/07/2015 |
|
| 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 No HLA document found. | ASOR (Final Release / Handover) | N/A | John Chan 30/07/2015 |
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 No changes to SLA required. | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
Time Recording Code | A Time Recording code for the application, if required, has been confirmed and set up. Existing TR code to be used. | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
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 No changes to DR/BC required and therefore no testing required to be done. | ASOR (Release 1-n) | Y | John Chan 30/07/2015 |
|
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 | John Chan 30/07/2015 |
|
Hardware and Software Licensing | All required licensing is in place including maintenance/support arrangements with external suppliers. Additional Self Service licences with Oracle have been purchased. | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
Browser Compatibility | Browser compatibility has been tested and compatibility information updated See for details | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
Portal Compatibility | Portal compatibility, where required, has been confirmed the Portals Service Owner. No changes to existing HR staff portal required.
| ASOR (Final Release / Handover) | N/A | John Chan 30/07/2015 |
|
Help Desk | The new application is recognised with the UniDesk (A business contact queue is defined where initial calls are raised with) All helpdesk calls related to HR with be dealt with HR Systems Team. | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
User Guide Documentation | Appropriate documentation has been produced for users of the new application. To be handled by HR Systems team | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
Training Material | Training material, if required, has been produced and is of an appropriate standard. To be handled by HR Systems team | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
Demonstration or Walkthrough | Demonstration or walkthrough of the new application has taken place for other stakeholder. | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
Deployment Date(s) | Agreed date has been confirmed that allows adequate time for completion of Acceptance Sign Off Review. Planned deployment date at the top of this page. | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
Deployment Resources | IS and business area resources required for deployment, including those needed for post implementation checking and sign off have been secured. Project Manager to book resources via ASTA | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
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. Morna Findlay responsible from the IS side. Susan McLaren will manage comms between users and HR/ | ASOR (Final Release / Handover) | Y | John Chan 30/07/2015 |
|
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) | N | John Chan 30/07/2015 | Morna Findlay to raise. |
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. HR to update their website pages and are responsible for their content. | ASOR (Final Release / Handover) | N/A | John Chan 30/07/2015 |
|