1.1. High-Level Scope for EPFS

Total: 53 . Chart by: Status

Test Item

Description

Date

Onboarding

Choose Subscription

Accounts

  • Interest rates computation

Pockets (Saving Goals)

  • Creation of Pockets

  • Transfer from Pockets to Main Account

  • Account and Financial Reporting - manually done for now - output of data (data lake then feed)

Transactions

  •    Intrabank SaFi to SaFi account

  •    Transaction History

  •     Interbank transfers (Paynamics)

    • Transfer In (Other bank to SaFI)

    • Transfer Out ( SaFi to Other bank)

  •     Cash In via OTC (Paynamics)

  •     Cash Out via OTC (Paynamics)

Back Office

  • Basic BO funtionalities

    • Customer Search

    • Customer Profile Change

    • Account Details

    • Role based Access

    • Reconciliation Report - Manual

Risk Engine

  • Step-up (scenario) - Face Recognition

  • Transaction Blocking

Customer Service

  • Bank should be contactable by the customer


1.2. TEST RISKS AND MITIGATION FACTORS

Risk

Problem

Impact

Mitigation Plan

SCHEDULE

Testing schedule is tight. If the start of the testing is delayed due to design tasks, the test cannot be extended beyond the UAT scheduled start date. 

High

High

  • The QA team can control the preparation tasks (in advance) and the early communication with involved parties. 

  • Some buffer has been added to the schedule for contingencies, although not as much as best practices advise. 

RESOURCES

Not enough resources

Medium

High

Holidays and vacation have been estimated and built into the schedule; deviations from the estimation could derive in delays in the testing.  

DEFECTS

Defects are found at a late stage of the cycle or at a late cycle; defects discovered late are most likely be due to unclear specifications and are time consuming to resolve.  

Medium

High

Defect management plan is in place to ensure prompt communication and fixing of issues. 

SCOPE

Scope completely defined

Medium

Scope is well defined but the changes are in the functionality are not yet finalized or keep on changing. 

TESTING

Delayed Testing Due To new Issues

Medium

High

During testing, there is a good chance that some “new” defects may be identified and may become an issue that will take time to resolve. 

There are defects that can be raised during testing because of unclear document specification. These defects can yield to an issue that will need time to be resolved. 

If these issues become showstoppers, it will greatly impact on the overall project schedule. 

If new defects are discovered, the defect management and issue management procedures are in place to immediately provide a resolution.

CATASTROPHIC EVENTS

Natural Disasters

Low

Medium

Teams and responsibilities have been spread to two different geographic areas. In a catastrophic event in one of the areas, there will resources in the other areas needed to continue (although at a slower pace) the testing activities.

STAGING ENVIRONMENT

Non-availability of Staging environment and accessibility

Medium

High

Due to non availability of the environment, the schedule gets impacted and will lead to delayed start of Test execution. 

The development team is committed to fix all the issues immediately.