NRS IM/IT APPLICATION DELIVERY CHECKLIST
V 2.3.0
This Application Delivery Checklist document describes the IMB workflow for Delivery of new applications or changes to existing applications. Overall, Delivery consists of Planning, Deposit, Quality Assurance, DLVR Deployment, DLVR System Testing, TEST Deployment, UAT and PROD Deployment tasks.
The scope of the document is to describe SDLC detailed tasks where IMB Deliveries has involvement, to describe the sunny-day scenario, and not to describe in detail improvement or other iteration loops. This document describes the normal and simplest set of tasks involved in going from Planning to PROD Deployment.
This checklist should be consulted for all applications being deposited and deployed to CSNR’s infrastructure. In general, new applications must execute all steps. For application version updates or redeliveries resulting from system testing or quality assurance identified improvements some steps are not required, that is those that are for initial application setup only.
Once change management for an application has been initiated, the normal process begins with planning the release and booking of two available time slots. The first booking sets a target time for the Vendor to deploy to DLVR. Note: this is only required if the Vendor requires assistance from IMB Deliveries; do not book this time if you do not need assistance during the delivery. The second booking requests IMB Deliveries, DBA Services, Data Architecture and Security to QA the readme, scripts, java components, etc associated with the release after it has been successfully delivered. Preferably, these two initial bookings are to be made a minimum of one day and on average one week apart, to allow for required code changes discovered on DLVR deployment.
The normal process then follows with planning for UAT (TEST) and PROD deployments and booking of two more available time slots. The TEST deployment booking requests IMB Deliveries to deploy to TEST. The PROD deployment booking requests IMB Deliveries to deploy to PROD. Preferably, these two bookings are to be booked a minimum of a day and on average one week apart, to allow for required code changes discovered during UAT.
Application Name: / ______Application Acronym: / ______
Application Version: / ______
IMB Business Portfolio Manager: / ______/ Phone No. / ______
Application Administrator: / ______/ Phone No. / ______
External Project Manager: / ______/ Phone No. / ______
Vendor Delivery Personnel: / ______/ Phone No. / ______
Vendor Developer: / ______/ Phone No. / ______
Application Requirements / Application Type / Responsibility / Date
Request acronym check from IMB Deliveries (for new applications only) / All / IMB Business Portfolio Manager
Perform acronym check and advise IMB Business Portfolio Manager / All / IMB Deliveries
Executive direction regarding if this is an IMB Deliveries responsible Application / All / Management
IMB Business Portfolio Manager
Update IRS and VMAD / All / IMB Deliveries
IMB Business Portfolio Manager
Supply vendor with CSNR Application Development Standards. / IMB Business Portfolio Manager
Application, Account and Access Setup / Application Type / Responsibility / Date
Ensure vendor has Cisco Connectivity Client for VPN access. Contact CSNR Service Desk for more information. / All / IMB Business Portfolio Manager
Send request for new application accounts to Application Delivery email account. (Application Delivery Booking CSD:EX) / All / IMB Business Portfolio Manager
Ensure vendor has IDIR/VPN account, if not, send request to CSNR Service Desk to create account. / All / IMB Business Portfolio Manager or Application Administrator
[OFM 11g] Send request to WTS UNIX FM to have your local vendor (IDIR) account mapping to the application service account. / All / IMB Deliveries
Set up application account, $HOME and directory structure on Delivery server. Set up code repository for application. / All / IMB Deliveries
Notify IMB Business Portfolio Manager and Vendor that application account setup is complete and supply account name and password as required. / All / IMB Deliveries
QA Preparation / Application Type / Responsibility / Date
In VMAD, enter a new version for the application with a new unique label. IMB Deliveries will be notified of this by VMAD and if required will work with the IMB Business Portfolio Manager to determine a valid label. / All / IMB Business Portfolio Manager
Verify all required data sources as dictated by the Web Mapping Application Development Standards / WMA / Vendor
Provide Data Model to DA for net new applications, or email notification to IMB Business Portfolio Manager for changes to existing data models. Note: any new or changed ORACLE database objects must be reviewed and passed by DA before any DDL delivery scripts are sent to IMB Deliveries. / All / Data Model / Vendor
Using VMAD, schedule application DLVR, QA, TEST and PROD events. / All / IMB Business Portfolio Manager
DLVR Deployment / Application Type / Responsibility / Date
Vendor deploys the application to the DLVR application server. / All / Vendor
For IMB Delivery assisted deliveries notify IMB Deliveries by phone or email when a section requiring assistance is reached. IMB Deliveries will respond by email with detail regarding completion of the step or steps. / All / Vendor, IMB Deliveries
Using VMAD, enter a DLVR status for the application version. VMAD will inform participants and IMB Deliveries that code has been deployed. / All / Vendor
Update IRS with other applicable information to maintain Server, URL and Instance information. / All / IMB Deliveries
If the Application Administrator was not listed as a participant in VMAD, notify the Application Administrator that the application is available for system testing in DLVR. / All / IMB Business Portfolio Manager
QA Cycle / Application Type / Responsibility / Date
Supply CSNR with application source code and/or data model. Vendor deposits the application source code into one of the file system managed or Subversion managed Source code Archives. Note that VMAD will automatically detect this and record the event with a DEPOSIT status record. / All / Vendor
Using VMAD, Enter a NOTIFY record for the application version. VMAD will automatically notify IMB Deliveries that the change has been deposited for QA. / All / Vendor
IMB Deliveries will QA changes for conformance to IMB Deliveries standards. IMB Deliveries detects Model changes and/or Java changes and dispatches these to DA and to Database and Middleware Services for QA. / All / IMB Deliveries
DA QA’s new data model or changes to existing data model. / All / Data Model / DA
DA notifies IMB Deliveries and IMB Business Portfolio Manager of model QA success or failure. / All / Data Model / DA
Database and Middleware Services QAs new or changed Java applications. / Java / Database and Middleware Services
Database and Middleware Services notifies IMB Deliveries of Java QA success or failure. / Java / Database and Middleware Services
Web mapping application source code and data sources QA (Allow 5 business days) / WMA / IMB and ILMB
If QA fails, IMB Deliveries enters that as a status in VMAD and by email notifies Vendor and IMB Business Portfolio Manager of any changes required. / All / IMB Deliveries
If QA succeeds, IMB Deliveries enters that as a status in VMAD. VMAD notifies participants of the success. / All / IMB Deliveries
Cycle this section until QA has passed. / All / All
Run WMA stats gathering procedure and generate report / WMA / ILMB
System testing in DLVR / Application Type / Responsibility / Date
Vendor, the Application Administrator and the IMB Business Portfolio Manager, system tests the application in DLVR. / All / Vendor
If required, make code or readme changes, re-deposit and re-deploy the application to the DLVR environment. / All / Vendor (IMB Deliveries assistance)
When re-deposit and re-deployments are complete, using VMAD enter a NOTICE and a DLVR status for the application version. / All / Vendor
If required because of changes, re-QA the release. This is called "Mini-QA" and only the changes are reviewed. If Mini-QA succeeds IMB Deliveries will enter this to VMAD and VMAD will notify participants. If Mini-QA fails IMB Deliveries will enter this to VMAD then will notify the Vendor and IMB Business Portfolio Manager that further changes are required. / All / IMB Deliveries
Sign-off that requested application changes have been completed by Vendor. / All / IMB Business Portfolio Manager and Application Administrator
TEST Deployment / Application Type / Responsibility / Date
Using VMAD, confirm TEST deployment by entering a TEST-CONFIRMED application version status. / All / IMB Business Portfolio Manager
Deploy application in Ministry’s TEST environment. / All / IMB Deliveries
Using VMAD, enter a TEST application version status. VMAD will notify participants of the event. / All / IMB Deliveries
User Acceptance Testing / Application Type / Responsibility / Date
Perform User Acceptance testing. / All / IMB Business Portfolio Manager/Application Administrator
Sign-off application UAT. / All / IMB Business Portfolio Manager/Application Administrator
UAT improvement cycle sub-workflow.
If UAT fails then many tasks described above are iterated to bring the version status back to TEST Deployment and UAT. If UAT fails please request details on the detailed workflow from IMB Deliveries. / All / All
PROD Deployment / Application Type / Responsibility / Date
Sign-off application as ready for PROD. / All / Application Administrator
Using VMAD, confirm PROD deployment by entering a PROD-CONFIRMED application version status. / All / IMB Business Portfolio Manager
Deploy application in Ministry’s PROD environment. / All / IMB Deliveries
Using VMAD, enter a PROD application version status. VMAD will notify participants of the event. / All / IMB Deliveries
After PROD Deployment tasks.
The Application Administrator verifies the PROD deployment.
If there are issues, communication between IMB Deliveries, the IMB Business Portfolio Manager and potentially Database and Middleware Services is required to plan rectification.
Please note that "rollback" is a last resort very seldom if ever resorted to as it involves recovery to the previous night's backups of the database, file system and application. The usual case is to proceed with a normal patch release or in some cases an "emergency" patch release. / All / All
DELIVERY GLOSSARY
Quality Assurance (QA) Insure new application code conforms to IMB Deliveries, Architecture, Data Model and Database and Middleware Services Standards.
Deployment Configuration and deployment of application components to a Delivery, Test, Production or Train operational environment.
WMA/IMF/GeoBC/ILMB/Warehouse DLVR Deployment Configuration and Deployment Web Mapping applications or ILMB replicated data sets to CSNR/ILMB Delivery environments. IMB Deliveries involvement is always required to complete deployment due to need for coordination with ILMB.
1