User Stories
Table of Contents
- User Story 1: Data Migration
- User Story 2: Continuous Account Access
- User Story 3: Account Closure and Refund
- User Story 4: Third-Party Integrations
- User Story 5: Automated Testing
- User Story 6: User Experience Design
Introduction
This document outlines the user stories for the implementation of Temenos' Transact core banking product, integrating it with Test Republic Bank's legacy mainframe banking system.
Purpose
The purpose of this document is to capture user requirements in a simple and understandable format, ensuring a smooth transition from the legacy mainframe system to the cloud-based Temenos Transact solution.
Scope
This document pertains to the full implementation of the Temenos Transact product, including data migration, continuous account access, third-party integrations, automated testing, and user experience design.
User Stories
User Story 1: Data Migration
- As a: Data Migration Specialist
- I want to: Migrate all account information from the legacy mainframe system to Temenos Transact
- So that: Clients’ data is securely transferred to the new cloud-based system
Description
Migrate all account information, including retail checking, savings accounts, CDs, money market accounts, mortgages, credit cards, car loans, and other personal loans, from the legacy system to Temenos Transact.
Acceptance Criteria
- All account information is successfully migrated to Temenos Transact.
- Data integrity is maintained during the migration.
- The migration process is completed by New Year's Eve, 2025.
Notes
Legacy system is over 30 years old and Cobol-based.
User Story 2: Continuous Account Access
- As a: Bank Client
- I want to: Have uninterrupted access to my accounts during the migration
- So that: I can manage my finances without any disruption
Description
Ensure that clients have continuous access to their accounts during the transition from the legacy system to Temenos Transact.
Acceptance Criteria
- Clients can access their accounts without interruption during the migration.
- The transition is seamless, with no downtime.
Notes
Accounts must not be disrupted while being transitioned.
User Story 3: Account Closure and Refund
- As a: Bank Administrator
- I want to: Close accounts with $100 or less and refund the balance to the owners
- So that: The system is optimized by purging inactive accounts
Description
Identify and close all accounts with a balance of $100 or less, and issue refund checks to the account owners.
Acceptance Criteria
- All accounts with a balance of $100 or less are identified and closed.
- Refund checks are issued to the account owners.
- The process is completed by New Year's Eve, 2025.
Notes
The goal is to optimize the system by purging inactive accounts.
User Story 4: Third-Party Integrations
- As a: Integration Specialist
- I want to: Ensure Temenos Transact integrates with Paymentus and LendingPad
- So that: The core banking system can support third-party payments and loan origination services
Description
Integrate Temenos Transact with Paymentus for payments and LendingPad for loan origination services.
Acceptance Criteria
- Successful integration with Paymentus.
- Successful integration with LendingPad.
- All integrations are functional by New Year's Eve, 2025.
Notes
Third-party integrations are crucial for supporting payments and loan origination.
User Story 5: Automated Testing
- As a: QA Engineer
- I want to: Implement Selenium automation code for testing
- So that: Testing processes are efficient and reliable
Description
Develop and implement Selenium automation scripts for testing the Temenos Transact system.
Acceptance Criteria
- Selenium automation scripts are developed and tested.
- Automated tests cover all critical functionalities.
- Testing is automated and efficient by New Year's Eve, 2025.
Notes
Automation is key to ensuring the reliability of the system during and after migration.
User Story 6: User Experience Design
- As a: UX Designer
- I want to: Design the user interface using different shades of blue
- So that: The interface aligns with the bank's branding guidelines
Description
Design the user interface of Temenos Transact using different shades of blue, ensuring it meets branding guidelines.
Acceptance Criteria
- The user interface design uses only shades of blue.
- The design is consistent with the bank's branding guidelines.
- The UX design is completed by New Year's Eve, 2025.
Notes
The UX should only use different shades of blue, no other color.
Acceptance Criteria
- All user stories are successfully implemented by New Year's Eve, 2025.
- No disruption in clients' access to their accounts.
- Successful integration with third-party systems.
- Automated testing is fully functional.
- The user interface design meets branding guidelines.
Definitions, Acronyms, and Abbreviations
- Temenos Transact: A core banking product.
- Cobol: A programming language used in legacy systems.
- SaaS: Software as a Service.
- Paymentus: A third-party payment platform.
- LendingPad: A loan origination system.
- UX: User Experience.
- QA: Quality Assurance.
Appendix
Include any additional information or documents relevant to the User Stories document.
Approval
- Prepared by: Mike Meier
- Email: mikemeier@mad-tech.ai
- Date: 04/29/2025
- Approved by: [Approver's Name]
- Date: [Approval Date]