T24 Country Model Bank

Integration and Release Management for C & G-Packs

222

Role of CMB IPRMIntegration, Packaging and Release Management Team (IPRM) in L2 performs the following activities,

Creating required environments for the all projects with its required Operating System and Integrating the required development components in multiple environments and troubleshoot issues faced, if any.

Manages and controls the pack deployment between environments within Temenos as well as packaging and release of components (C/G-Packs) to various clients.

Maintaining the sources of the delivered components that have been released to the clients.

Databases used:• SVN – Source Code Management• RTC – Managing the Development/ Defect Work items

Tools used Packaging and Release Mechanism• Build Control - Packaging• Cruise Control – Code release

CMB IPRM

Environment Type Description

Development As the name suggests the development activities are carried out in this environment

Testing environment This is where Functional testing & Regression Testing are carried out.All components – Source Codes and Data Records that passes testing are promoted from this environment. BCON units/DL.DEFINE are created from this environment.

Master environment The BCON units/DL.DEFINE created from Testing environment is released in this environment before releasing to the Client to check the deployment issues.

333

Before Delivery – towards initiating the development and Functional Testing of the C/G-Packs

The LT/LRTs are created and controlled by the CMB IPRM Team. In this regard, request for creation of LT/LRTs are received from the development team and processed by creating them in all the L2 environments

Once the Coding has been completed and developers review the code using OCRT (pre-check of codes) and fix any issues, the developer will provide the following to the CMB-IPRM team

- A Text file containing list of sources & data records with version number of SVN repository index for the sources and data records and then those have to be cleared before moving to unit testing.

- Installation Guide explaining the Pre-installation steps and post installation steps in deploying components for a successful release in the specific environment.

CMB IPRM

Stages of CMB IPRM’s involvement in Development/Delivery Life Cycle`

444

During Delivery – towards Integrating the C/G-Packs on to Master and Release to client/Region

Once the Testing has been completed and testing team provides a sign-off and the IAG team provides a ‘Go’ or ‘Conditional-Go’ for the enhancement, the codes tested are integrated in the master environment and thereon delivered to the client with the following mandatory documentation

- Installation Guide - Test Results Document - User Guide - Scope, where required.

After Delivery – Client Defects - Towards integration of Defect Fixes and delivery of the Fixes to the Client

Post delivery of an enhancement, if any client issues (PACS ticket) are logged through TCSP , the development team provides the required fix and the required text file for SVN version update and with the tested document and installation guide.

CMB IPRM will release the fix pack in test environment for the testing team to test and sign-off the fix. Once the fix is tested and signed-off, the CMB IPRM team will integrate the fix in the Master environment

and delivery the fix to the Client along with the following documentation - Installation Guide - Test Results Document

CMB IPRM

555

G-Pack Pack Requests Client / RDH/ PDM/ ISB team will raise a Request for Generic Packages through mail and specify the

details of the Requirement in a PRF(Pack Request Form). CMB IPRM team will ensure that the Pack requested has been licensed to the concerned client. If license is available, CMB IPRM team will deliver the requested pack compatible to client specific T24

release & software configuration through FTP / Mail. If license is not available the client still requires the pack, an approval from Regional Director is

obtained and the pack will be delivered accordingly. CMB IPRM will update these details in GPack Delivery List and will be updated in Share Point.

Environment Management Before initiating the development activities for a Country Model, the concerned DM or the Project lead

will be requesting for the below mentioned environments, as may be appropriate.- Development Environment(s)- Testing environment(s)- Master Environment For this purpose, the request is received through the specific Environment Management Request form. In some country model environments, depending upon the OS and Database configuration (e.g

WINDOWS with MSSQL) , the back-up as well restoration process is handled by the CMB IPRM/Environment Management team which is common for L2 and L3.

CMB IPRM

666

CMB IPRM

Maintenance / Update of IPRM controlled environments In some instances, there will be a need to change the Core parameter values which is different from the

initial set-up delivered to a client or required to be updated in the Test and Master environment for delivery to a client.

The CMB IPRM team will handle such request through a Parameter Change request / update IG with clear instructions and screenshot to update the IPRM controlled environments. The updated IG will then be delivered to the client to make the necessary set-up changes at the client end.