User Stories
Table of Contents
- User Story 1: Account Transition
- User Story 2: Continuous Account Access
- User Story 3: Account Purge and Closure
- User Story 4: Third-Party Integration
- User Story 5: Automated Testing
- User Story 6: UX Design Compliance
Introduction
This document provides a comprehensive set of user stories for the installation of Temenos' Transact core banking product to replace 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 to ensure a smooth transition from the legacy system to Temenos' Transact without disrupting account access for clients.
Scope
This document pertains to the project aimed at replacing Test Republic Bank's 30-year-old Cobol-based legacy mainframe banking system with Temenos' Transact cloud-based SaaS solution.
User Stories
User Story 1: Account Transition
- As a: System Administrator
- I want to: Migrate all account information from the legacy system to Temenos' Transact
- So that: Account data is securely and accurately transferred to the new system
Description
The legacy system holds account information for 100,000 retail checking and savings accounts, as well as other financial products like CDs, Money Market accounts, mortgages, credit cards, car loans, and personal loans. This data must be migrated to Temenos' Transact without errors.
Acceptance Criteria
- All account data is accurately migrated to Temenos' Transact
- Data integrity is maintained during the migration process
- Migration is completed by New Year's Eve, 2025
Notes
Ensure data validation and verification processes are in place to maintain data integrity during migration.
User Story 2: Continuous Account Access
- As a: Client
- I want to: Have uninterrupted access to my accounts during the transition
- So that: I can manage my finances without any disruptions
Description
Clients must have continuous access to their accounts while the transition from the legacy system to Temenos' Transact is underway.
Acceptance Criteria
- Clients experience no downtime in accessing their accounts
- All account functionalities are available during the transition
- Communication plans are in place to inform clients about the transition process
Notes
Implement a robust fallback mechanism to ensure continuous account access.
User Story 3: Account Purge and Closure
- As a: System Administrator
- I want to: Purge and close accounts with $100 or less, and refund the account owners
- So that: The system is optimized and inactive accounts are removed
Description
Accounts with a balance of $100 or less must be purged, closed, and the account holders refunded by check.
Acceptance Criteria
- Accounts with $100 or less are identified and purged
- Refund checks are issued to the account holders
- Account closure is completed by New Year's Eve, 2025
Notes
Ensure proper communication with account holders regarding the closure and refund process.
User Story 4: Third-Party Integration
- As a: System Administrator
- I want to: Ensure Temenos' Transact works with Paymentus and LendingPad
- So that: Third-party payment and loan origination processes are seamless
Description
Temenos' Transact must integrate smoothly with third-party software from Paymentus and LendingPad.
Acceptance Criteria
- Successful integration with Paymentus for payment processing
- Successful integration with LendingPad for loan origination
- All functionalities are tested and validated
Notes
Coordinate with third-party vendors for integration testing.
User Story 5: Automated Testing
- As a: QA Engineer
- I want to: Use Selenium code for automated testing
- So that: All testing processes are efficient and reliable
Description
Automated testing using Selenium is required to ensure the system functions correctly after migration.
Acceptance Criteria
- Selenium scripts are developed and tested
- Automated tests cover all critical functionalities
- Tests are run regularly to ensure system stability
Notes
Maintain updated Selenium scripts to match any changes in the system.
User Story 6: UX Design Compliance
- As a: UI/UX Designer
- I want to: Ensure the UX uses only different shades of blue
- So that: The visual design complies with the brand guidelines
Description
The UX of Temenos' Transact must use only different shades of blue to align with the bank's branding.
Acceptance Criteria
- All UI elements use shades of blue
- No other colors are used in the design
- Design is approved by the branding team
Notes
Conduct user testing to ensure the design is user-friendly and visually appealing.
Acceptance Criteria
The general acceptance criteria for the user stories include successful data migration, continuous client access, seamless third-party integration, automated testing, and design compliance with brand guidelines.
Definitions, Acronyms, and Abbreviations
- SaaS: Software as a Service
- CD: Certificate of Deposit
- UX: User Experience
- QA: Quality Assurance
- UI: User Interface
- LOS: Loan Origination System
Appendix
Include any additional information or documents relevant to the User Stories document.
Approval
- Prepared by: Mike Meier
- Email: mikemeier@mad-tech.ai
- Date: 05/07/2025
- Approved by: [Approver's Name]
- Date: [Approval Date]