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.
1
NRS IM/IT APPLICATION DELIVERY CHECKLIST
V 2.3.0
Application Name: _________________________
Application
Acronym:
_________________________
Application
Version:
_________________________
IMB Business
Phone
_________________________
Portfolio Manager: _________________________ No.
Application
Administrator:
Phone
_________________________ No.
_________________________
External Project
Manager:
Phone
_________________________ No.
_________________________
Vendor Delivery
Personnel:
Phone
_________________________ No.
_________________________
Vendor Developer:
Phone
_________________________ No.
_________________________
Application Requirements
Application
Type
Responsibility
Request acronym check from IMB
Deliveries (for new applications only)
All
Perform acronym check and advise IMB
Business Portfolio Manager
Executive direction regarding if this is an
IMB Deliveries responsible Application
All
IMB Business
Portfolio
Manager
IMB Deliveries
Update IRS and VMAD
All
All
Supply vendor with CSNR Application
Development Standards.
Application, Account and Access
Setup
Ensure vendor has Cisco Connectivity
Client for VPN access. Contact CSNR
Service Desk for more information.
Send request for new application accounts
to Application Delivery email account.
(Application Delivery Booking CSD:EX)
Management
IMB Business
Portfolio
Manager
IMB Deliveries
IMB Business
Portfolio
Manager
IMB Business
Portfolio
Manager
Application
Type
Responsibility
All
IMB Business
Portfolio
Manager
IMB Business
Portfolio
Manager
All
Date
Date
2
NRS IM/IT APPLICATION DELIVERY CHECKLIST
V 2.3.0
Application, Account and Access
Setup
Application
Type
Responsibility
Ensure vendor has IDIR/VPN account, if
not, send request to CSNR Service Desk
to create account.
All
[OFM 11g] Send request to WTS UNIX FM
to have your local vendor (IDIR) account
mapping to the application service
account.
Set up application account, $HOME and
directory structure on Delivery server.
Set up code repository for application.
Notify IMB Business Portfolio Manager
and Vendor that application account setup
is complete and supply account name and
password as required.
All
IMB Business
Portfolio
Manager or
Application
Administrator
IMB Deliveries
All
IMB Deliveries
All
IMB Deliveries
Application
Type
Responsibility
All
IMB Business
Portfolio
Manager
WMA
Vendor
All / Data
Model
Vendor
All
IMB Business
Portfolio
Manager
QA Preparation
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.
Verify all required data sources as
dictated by the Web Mapping Application
Development Standards
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.
Using VMAD, schedule application DLVR,
QA, TEST and PROD events.
Date
Date
3
NRS IM/IT APPLICATION DELIVERY CHECKLIST
V 2.3.0
DLVR Deployment
Vendor deploys the application to the
DLVR application server.
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.
Using VMAD, enter a DLVR status for the
application version. VMAD will inform
participants and IMB Deliveries that code
has been deployed.
Update IRS with other applicable
information to maintain Server, URL and
Instance information.
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.
QA Cycle
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.
Using VMAD, Enter a NOTIFY record for
the application version. VMAD will
automatically notify IMB Deliveries that
the change has been deposited for QA.
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.
DA QA’s new data model or changes to
existing data model.
DA notifies IMB Deliveries and IMB
Business Portfolio Manager of model QA
success or failure.
Database and Middleware Services QAs
new or changed Java applications.
Application
Type
Responsibility
All
Vendor
All
Vendor, IMB
Deliveries
All
Vendor
All
IMB Deliveries
All
IMB Business
Portfolio
Manager
Application
Type
Responsibility
All
Vendor
All
Vendor
All
IMB Deliveries
All / Data
Model
All / Data
Model
DA
Java
Database and
Middleware
Services
Date
Date
DA
4
NRS IM/IT APPLICATION DELIVERY CHECKLIST
V 2.3.0
QA Cycle
Database and Middleware Services
notifies IMB Deliveries of Java QA success
or failure.
Web mapping application source code and
data sources QA (Allow 5 business days)
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.
If QA succeeds, IMB Deliveries enters that
as a status in VMAD. VMAD notifies
participants of the success.
Cycle this section until QA has passed.
Run WMA stats gathering procedure and
generate report
System testing in DLVR
Vendor, the Application Administrator and
the IMB Business Portfolio Manager,
system tests the application in DLVR.
If required, make code or readme
changes, re-deposit and re-deploy the
application to the DLVR environment.
When re-deposit and re-deployments are
complete, using VMAD enter a NOTICE
and a DLVR status for the application
version.
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.
Sign-off that requested application
changes have been completed by Vendor.
Application
Type
Responsibility
Java
WMA
Database and
Middleware
Services
IMB and ILMB
All
IMB Deliveries
All
IMB Deliveries
All
WMA
All
ILMB
Application
Type
Responsibility
All
Vendor
All
All
Vendor (IMB
Deliveries
assistance)
Vendor
All
IMB Deliveries
All
IMB Business
Portfolio
Manager and
Application
Administrator
Date
Date
5
NRS IM/IT APPLICATION DELIVERY CHECKLIST
V 2.3.0
TEST Deployment
Application
Type
Responsibility
All
All
IMB Business
Portfolio
Manager
IMB Deliveries
All
IMB Deliveries
Application
Type
Responsibility
Perform User Acceptance testing.
All
Sign-off application UAT.
All
UAT improvement cycle sub-workflow.
All
IMB Business
Portfolio
Manager/Appl
ication
Administrator
IMB Business
Portfolio
Manager/Appl
ication
Administrator
All
Using VMAD, confirm TEST deployment by
entering a TEST-CONFIRMED application
version status.
Deploy application in Ministry’s TEST
environment.
Using VMAD, enter a TEST application
version status. VMAD will notify
participants of the event.
User Acceptance Testing
Date
Date
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.
PROD Deployment
Application
Type
Responsibility
Sign-off application as ready for PROD.
All
Using VMAD, confirm PROD deployment
by entering a PROD-CONFIRMED
application version status.
Deploy application in Ministry’s PROD
environment.
Using VMAD, enter a PROD application
version status. VMAD will notify
participants of the event.
After PROD Deployment tasks.
All
All
Application
Administrator
IMB Business
Portfolio
Manager
IMB Deliveries
All
IMB Deliveries
All
All
Date
The Application Administrator verifies the
PROD deployment.
If there are issues, communication
6
NRS IM/IT APPLICATION DELIVERY CHECKLIST
V 2.3.0
PROD Deployment
Application
Type
Responsibility
Date
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.
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.
7