User Stories
Table of Contents
- Introduction
- Purpose
- Scope
- User Stories
- Acceptance Criteria
- Definitions, Acronyms, and Abbreviations
- Appendix
- Approval
Introduction
This document contains the user stories for the implementation of Temenos' Transact core banking product to replace Test Republic Bank's legacy mainframe banking system. The goal is to ensure a seamless transition to the new system while maintaining continuous access to all accounts.
Purpose
The purpose of this document is to capture user requirements in a simple and understandable format to guide the implementation and ensure all stakeholders are aligned.
Scope
This document pertains to the implementation of Temenos' Transact core banking product, its integration with existing third-party systems, and the migration of all accounts from Test Republic Bank's legacy mainframe system.
User Stories
User Story 1: Migration of Accounts
- As a: System Administrator
- I want to: Migrate all account information from the legacy mainframe system to Temenos' Transact
- So that: All account data is accurately transferred to the new system without any loss
Description
The system administrator needs to ensure that all account information, including checking, savings, CDs, Money Market accounts, mortgages, credit cards, car loans, and personal loans, is migrated from the legacy system to Temenos' Transact.
Acceptance Criteria
- All account data is successfully transferred to the new system
- No data loss occurs during the migration
- Data is accurately reflected in Temenos' Transact
Notes
- Special attention must be given to data integrity and consistency checks during the migration process.
User Story 2: Continuous Access
- As a: Client
- I want to: Have continuous access to my accounts
- So that: My banking activities are not disrupted during the transition
Description
Clients must have uninterrupted access to their accounts throughout the migration process to ensure no disruption in their banking activities.
Acceptance Criteria
- Clients can access their accounts without any downtime
- All functionalities remain available during the transition period
Notes
- A robust fallback mechanism must be in place in case of any issues during the migration.
User Story 3: Closure of Low-Balance Accounts
- As a: System Administrator
- I want to: Purge accounts with a balance of $100 or less and refund the owners by check
- So that: The system is optimized and unnecessary accounts are closed
Description
Accounts with a balance of $100 or less need to be identified, closed, and the account holders refunded their money by check.
Acceptance Criteria
- Accounts with $100 or less are identified and closed
- Refund checks are issued to the account holders
- Closed accounts are removed from the system
Notes
- Ensure proper communication with account holders regarding the closure and refund process.
User Story 4: Integration with Third-Party Systems
- As a: System Integrator
- I want to: Ensure Temenos' Transact integrates seamlessly with Paymentus and LendingPad
- So that: All third-party functionalities continue to operate without disruption
Description
Temenos' Transact must be integrated with third-party systems Paymentus (for payments) and LendingPad (Loan Origination System).
Acceptance Criteria
- Successful integration with Paymentus and LendingPad
- No disruption in payment processing and loan origination functionalities
Notes
- Thorough testing is required to ensure seamless integration.
User Story 5: Automated Testing
- As a: QA Engineer
- I want to: Implement Selenium code for automated testing
- So that: The testing process is efficient and comprehensive
Description
Selenium code must be developed to automate testing processes ensuring all functionalities are tested accurately.
Acceptance Criteria
- Selenium scripts cover all critical functionalities
- Automated tests run successfully without errors
Notes
- Maintain detailed documentation of Selenium scripts for future reference and updates.
User Story 6: UX Design
- As a: UX Designer
- I want to: Design the user interface using different shades of blue
- So that: The UI is visually consistent with the bank's branding guidelines
Description
The user interface of Temenos' Transact must be designed using only different shades of blue to align with the bank's branding.
Acceptance Criteria
- UI utilizes only shades of blue
- Design is visually appealing and user-friendly
Notes
- Ensure the design adheres to accessibility standards.
Acceptance Criteria
- All user stories meet their specific acceptance criteria.
- The system is fully operational by New Year's Eve, 2025, with no impact on clients.
- Successful migration and integration with third-party systems.
- Automated testing and UI design are completed as per requirements.
Definitions, Acronyms, and Abbreviations
- CD: Certificate of Deposit
- SaaS: Software as a Service
- LOS: Loan Origination System
- QA: Quality Assurance
- UI: User Interface
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/06/2025
- Approved by: [Approver's Name]
- Date: [Approval Date]