User Stories for Transact New Implementation II
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 Transact New Implementation II project. The goal of this project is to install Temenos' Transact core banking product and integrate it with our legacy mainframe banking system.
Purpose
The purpose of this document is to capture user requirements in a simple and understandable format to ensure a successful implementation of Temenos' Transact core banking product without any disruption to client accounts.
Scope
The scope of this document includes the installation of Temenos' Transact product, integration with legacy systems, and ensuring seamless operation for clients of Test Republic Bank.
User Stories
User Story 1: Seamless Transition
- As a: Bank Operations Manager
- I want to: Ensure that client accounts are seamlessly transitioned from the legacy system to Temenos' Transact without any disruption
- So that: Clients can have uninterrupted access to their accounts during the transition period
Description
The legacy mainframe banking system, which is over 30 years old and Cobol-based, holds all account information for various account types. We need to move all accounts to a cloud-based SaaS solution, Temenos' Transact, while ensuring clients have continuous access to their accounts.
Acceptance Criteria
- All account data is accurately migrated to Temenos' Transact.
- No client experiences downtime or disruption in accessing their accounts.
- The transition is completed by New Year's Eve, 2025.
Notes
- Accounts include retail checking and savings accounts, CDs, Money Market accounts, mortgages, credit cards, car loans, and other personal loans.
User Story 2: Account Purging
- As a: Data Analyst
- I want to: Purge accounts with $100 or less and refund the account owners by check
- So that: We can streamline the data migration process and reduce system load
Description
Accounts with a balance of $100 or less will be purged from the legacy system, closed, and the owners will be refunded by check.
Acceptance Criteria
- All accounts with $100 or less are identified and purged.
- Account owners receive refunds by check.
- The process is completed before the Transact go-live date.
Notes
- Ensure compliance with regulatory requirements for account closure and refund processing.
User Story 3: Third-Party Integration
- As a: IT Integration Specialist
- I want to: Ensure that Temenos' Transact integrates seamlessly with Paymentus and LendingPad
- So that: Our clients can continue to use third-party payment and loan origination services without interruption
Description
Temenos' Transact must work with our third-party payments software from Paymentus and our LOS from LendingPad.
Acceptance Criteria
- Successful integration with Paymentus and LendingPad.
- No disruption in third-party services for clients.
Notes
- Conduct thorough testing to ensure smooth integration.
User Story 4: Automated Testing
- As a: QA Engineer
- I want to: Use Selenium code to automate testing
- So that: We can efficiently verify all functionalities of Temenos' Transact
Description
Automated testing using Selenium will be implemented to ensure all functionalities of Temenos' Transact operate correctly.
Acceptance Criteria
- Selenium scripts cover all critical functionalities.
- Automated tests are executed and pass without issues.
- Testing is completed before the go-live date.
Notes
- Include regression testing in the automated test suite.
User Story 5: User Experience Design
- As a: UI/UX Designer
- I want to: Design the user interface using only different shades of blue
- So that: We maintain a consistent and visually appealing experience for clients
Description
The UX design should only use different shades of blue and no other color.
Acceptance Criteria
- All UI elements use varying shades of blue.
- The design is reviewed and approved by stakeholders.
- The design is implemented before the go-live date.
Notes
- Ensure the design is accessible and user-friendly.
Acceptance Criteria
- All user stories are completed and meet their specific acceptance criteria.
- The project is completed by New Year's Eve, 2025.
- There is no disruption to client accounts during the transition.
Definitions, Acronyms, and Abbreviations
- SaaS: Software as a Service
- LOS: Loan Origination System
- QA: Quality Assurance
- UI/UX: User Interface/User Experience
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/28/2025
- Approved by: [Approver's Name]
- Date: [Approval Date]