T24 Temenos Methodology Overview

10,969 views

Published on

This is a snapshot of a Temenos methodology that was used to complete a Temenos T24 Upgrade for a large private bank in Europe

0 Comments
13 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
10,969
On SlideShare
0
From Embeds
0
Number of Embeds
53
Actions
Shares
0
Downloads
0
Comments
0
Likes
13
Embeds 0
No embeds

No notes for slide
  • Unit testing is a software verification and validation method in which a programmer tests if individual units of source code are fit for use. A unit is the smallest testable part of an application.
  • Unit Testing is technical testing conducted by the Development team to verify that the code they have developed is technically correct, as per the specifications. This is minimal coverage testing focussed on a discrete piece of code in isolation.
  • T24 Temenos Methodology Overview

    1. 1. HUB 24 - Methodology Overview<br />START<br />Functional<br />Design<br />DST based<br />Development<br />System<br />Testing<br />Functional<br />Catalogue<br />Gap<br />Analysis<br />Local Code<br />Conversion<br />Migration Testing<br />Migration Design<br />Technical<br />Design<br />Non Functional<br />Testing<br />Architecture<br />Unit Testing<br />Build Team<br />UAT<br />Testing<br />Business<br />Process <br />Testing<br />Dress<br />Rehearsal<br />Implementation <br />Migration<br />Cutover<br />Training<br />END<br />BPT & UAT Testing Team<br />Implementation Team<br />DRAFT FOR COMMENT<br />V0.44<br />
    2. 2. HUB 24 - Test Strategy Overview<br />Unit Testing<br />Unit Testing is technical testing conducted by the Development team to verify that the code they have developed is technically correct, as per the specifications. This is minimal coverage testing focussed on a discrete piece of code in isolation.<br />System Testing<br />System testing is bottom-up testing drive by functional & technical design specifications covering all combined parts of a system. Interfaces to external systems are tested using stubs or automated testing tools in order to identify and remove defects as early in the development lifecycle.<br />Non Functional<br />Testing<br />Includes load testing, stress testing, scalability testing, security Testing, BCP, Testing, DR testing & Operational acceptance testing <br />Migration testing confirms the conversion of the business data into the required format. Business data is often incomplete, inconsistent or inaccurate so data clean-up may be required and the process of migration will need to be tested and the data reconciled.<br />Migration Testing<br />Business Process Testing is Top-down, driven by the key business processes. Where system testing is a bottom-up approach, driven by the technical and functional specifications. BPT is of critical importance to the project as it is the last stage of formal testing before the project passes over the bank for UAT. <br />Business Process <br />Testing<br />User acceptance testing is business process driven testing conducted by the business using the system(s) in a manner in keeping with day to day operations. UAT is the process to obtain confirmation by the business that the platform delivered (All components changed under the scope of the programme) meets the requirements within the scope of the project. <br />UAT<br />Testing<br />Dress<br />Rehearsal<br />Dress Rehearsal testing Is performed as similar to the day-to-day business activities in Production Environment<br />
    3. 3. Unit Testing<br />Unit Testing is technical testing conducted by the Development team to verify that the code is correct. <br />This is minimal coverage testing focussed on each discrete piece of development.<br />
    4. 4. Non Functional<br />Testing<br />Iterative Testing<br />Includes load testing, stress testing, scalability testing, security Testing, BCP & DR testing<br />Functional tests are matured in automated scripts for the purposes of non-functional testing<br />Essentially a virtual team, with resources being bought in from other teams as required.<br />Operational acceptance testing refers to the checking done to a system to ensure that processes and procedures are in place to allow the system to be used and maintained. This may include checks done to back-up facilities, procedures for disaster recovery, training for end users, maintenance procedures, and security procedures. <br />
    5. 5. System Testing<br />System testing is bottom-up testing based on functional & technical design specifications covering all combined parts of a system. <br />Interfaces to external systems are tested using stubs or automated testing tools when downstream systems are not available in order to identify and remove defects as early in the development lifecycle. <br />System Testing will test connectivity to external applications which will ensure end to end proper flow of transactions (Interface Testing). <br />System testing is conducted on an iteratively developing code base on a module by module basis. Ultimately a complete integrated system will be used to evaluate the system's compliance with specifications. <br />System Testing is focussed on heavily modified local and core code and does not provide coverage of functionality supplied by Temenos unchanged by KBL (which may or may not have changed between G12 and R9) which will be covered during BPT.<br />Regression testing is performed using automation tools for each code drop<br />Two weekly drops of code into the System Testing environment from Development with a fix related drop on alternate weeks<br />Emergency drops are provided when testing progress is brought to a standstill<br />
    6. 6. Business <br />Process Testing<br />Business Process Testing approaches the system from a Functional business process perspective from the start of a transaction (which might be a telephone call) through to the completion <br />BPT verifies that the integrated components functions correctly as part of the overall system and the existing Components of the System work as expected<br />Business Processes are key to E2E testing and they must be up to date and accurate covering all business areas and systems in use.<br />BPT is almost like UAT with an exception that it is done by testers. Similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use<br />BPT will generate transactions that exercise the external interfaces across all applications within the system as a whole to ensure the end to end business process is validated.<br />Test automation tools will allow complex processes to be built up and re-used reducing the total cost of testing and improving quality<br />The testing of the full business process, from the start of a transaction (which might be a telephone call) through to the completion (which might be the receipt of payment for an invoice after goods have been shipped).<br />BPT is inter system testing or interoperability testing to check software coexistence with other software and shared Hub services using business processes to ensure coverage.<br />
    7. 7. UAT<br />Process driven testing conducted by the end users in the bank<br />UAT is the process to obtain confirmation by business, through trial or review, that the development undertaken meets the expectation and requirements of the business. <br />UAT is one of the final stages of a project and occurs before the business accepts the new system.<br />
    8. 8. Dress Rehearsal<br />Dress Rehearsal testing Is performed similar to day-to-day business activities in Production Environment<br />Dress Rehearsal Environment is configured and parameterized as Production Environment.<br />Dress Rehearsal testing is considered to be the Final Stage to validate or compare the Go Live Production Environment . This is to check the day to day business Flows and System Stress, Load and performance. <br />

    ×