User Stories

Table of Contents

  1. Introduction
  2. Purpose
  3. Scope
  4. User Stories
  5. Acceptance Criteria
  6. Definitions, Acronyms, and Abbreviations
  7. Appendix
  8. Approval

Introduction

This document outlines the user stories for the project "Transact New Implementation," which aims to integrate Temenos' Transact core banking product with the legacy mainframe banking system of Test Republic Bank.

Purpose

The purpose of this User Stories document is to capture the user requirements for the integration and migration project in a simple and understandable format.

Scope

This document covers the requirements for migrating all account information from the legacy mainframe banking system to Temenos' Transact product, ensuring continuous access to client accounts, integrating third-party systems, and automating testing.

User Stories

User Story 1: Data Migration

  • As a: Data Engineer
  • I want to: Migrate all account information from the legacy mainframe system to Temenos' Transact
  • So that: Clients' account information is accurately transitioned to the new system

Description

Migrate all account data (including checking, savings, CDs, Money Market accounts, mortgages, credit cards, car loans, and other personal loans) from the legacy system to the cloud-based Transact product.

Acceptance Criteria

  • All account information is migrated without data loss.
  • Accounts with $100 or less are identified and flagged for closure.
  • Data migration is completed by New Year's Eve, 2025.

Notes

  • Ensure data integrity and consistency during migration.

User Story 2: Continuous Access

  • As a: Client
  • I want to: Have uninterrupted access to my accounts during the migration
  • So that: I can manage my finances without any disruptions

Description

Ensure that clients have continuous access to their accounts while migrating data from the legacy system to Transact.

Acceptance Criteria

  • Clients experience no downtime during the migration.
  • Access to accounts is available 24/7 throughout the transition period.

Notes

  • Implement a phased migration strategy to minimize impact.

User Story 3: Account Closure and Refund

  • As a: Bank Administrator
  • I want to: Automatically close accounts with $100 or less and refund the balance to the account holders
  • So that: We can streamline the migration process and manage active accounts efficiently

Description

Identify and close accounts with $100 or less, and send refund checks to the account holders.

Acceptance Criteria

  • Accounts with $100 or less are closed automatically.
  • Refund checks are issued to the account holders within 30 days of closure.

Notes

  • Ensure compliance with regulatory requirements for account closure and refunds.

User Story 4: Third-Party Integration

  • As a: System Integrator
  • I want to: Ensure that Transact integrates seamlessly with Paymentus and LendingPad
  • So that: Our third-party payment and loan origination systems work flawlessly with the new core banking system

Description

Integrate Temenos' Transact with Paymentus for payment processing and LendingPad for loan origination.

Acceptance Criteria

  • Paymentus integration is tested and functional.
  • LendingPad integration is tested and functional.
  • No disruption in third-party services during the transition.

Notes

  • Coordinate with third-party vendors for integration and testing.

User Story 5: Automated Testing

  • As a: QA Engineer
  • I want to: Develop Selenium scripts to automate testing
  • So that: We can ensure the system's reliability and performance through automated testing

Description

Create Selenium scripts to automate the testing of the new Transact system.

Acceptance Criteria

  • Selenium scripts cover all critical functionalities.
  • Automated tests are run successfully with no critical issues.

Notes

  • Maintain and update scripts as needed during and after migration.

User Story 6: User Interface Design

  • As a: UI/UX Designer
  • I want to: Design the user interface using different shades of blue only
  • So that: The system adheres to the bank's branding guidelines

Description

Design the user interface for Temenos' Transact using only different shades of blue.

Acceptance Criteria

  • The UI uses only different shades of blue.
  • The design is approved by the branding team.

Notes

  • Ensure the UI is user-friendly and accessible.

Acceptance Criteria

  • Data migration is completed without data loss.
  • Continuous access to accounts is maintained during migration.
  • Accounts with $100 or less are closed and refunds issued.
  • Seamless integration with Paymentus and LendingPad.
  • Automated testing using Selenium is implemented and functional.
  • User Interface adheres to branding guidelines.

Definitions, Acronyms, and Abbreviations

  • Transact: Temenos' core banking product.
  • SaaS: Software as a Service.
  • QA: Quality Assurance.
  • UI/UX: User Interface/User Experience.
  • LOS: Loan Origination System.

Appendix

Include any additional documents or information relevant to the User Stories document.

Approval

  • Prepared by: Mike Meier
  • Date: 04/28/2025
  • Approved by: [Approver's Name]
  • Date: [Approval Date]
Document Link:
Transact New Implementation User Stories
Please wait while cAItalyst edits your document.
Oops! Something went wrong while submitting the form.