User Stories for Test Republic Transact Implementation 2
Table of Contents
- User Story 1: Account Data Migration
- User Story 2: Continuous Account Access
- User Story 3: Account Closure and Refund
- User Story 4: Third-Party Integration
- User Story 5: Automated Testing
- User Story 6: User Experience (UX) Design
Introduction
This document provides a comprehensive list of user stories for the project "Test Republic Transact Implementation 2." The objective of this project is to install Temenos' Transact core banking product and integrate it with Test Republic Bank's legacy mainframe banking system.
Purpose
The purpose of this User Stories document is to capture the user requirements in a simple and understandable format to facilitate the successful implementation of Temenos' Transact while ensuring minimal disruption to ongoing banking operations.
Scope
This document pertains to the integration of Temenos' Transact with Test Republic Bank's legacy mainframe banking system, ensuring the seamless transition of accounts and continued access for clients.
User Stories
User Story 1: Account Data Migration
- 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 available in the new cloud-based system without any loss
Description
The legacy mainframe system holds account information on 100,000 retail checking and savings accounts, CDs, Money Market accounts, mortgages, credit cards, car loans, and personal loans. This data needs to be migrated to Temenos' Transact.
Acceptance Criteria
- All account data from the legacy system is successfully migrated to Temenos' Transact.
- Data integrity is maintained during the migration.
- Migration is completed without any data loss.
Notes
- The legacy system is Cobol-based and over 30 years old.
User Story 2: Continuous Account Access
- As a: Bank Client
- I want to: Have uninterrupted access to my account during the migration
- So that: I can continue to perform banking transactions without any disruption
Description
Clients must have continuous access to their accounts during the transition from the legacy system to Temenos' Transact.
Acceptance Criteria
- Clients are able to access their accounts at all times during the migration.
- No downtime is experienced by clients during the transition.
Notes
- The transition must be smooth and not impact the client's banking experience.
User Story 3: Account Closure and Refund
- As a: System Administrator
- I want to: Identify and close accounts with a balance of $100 or less and refund the account holders by check
- So that: These accounts are purged from the system before migration
Description
Accounts with a balance of $100 or less must be closed, and the account holders refunded by check.
Acceptance Criteria
- Accounts with a balance of $100 or less are identified and closed.
- Refund checks are issued to the account holders.
- Closed accounts are purged from the system.
Notes
- Ensure proper documentation and communication with account holders regarding the closure and refund process.
User Story 4: Third-Party Integration
- As a: Integration Specialist
- I want to: Ensure that Temenos' Transact works seamlessly with Paymentus and LendingPad
- So that: Third-party payments and loan origination services are uninterrupted
Description
Temenos' Transact must integrate with Paymentus for third-party payments and LendingPad for loan origination services.
Acceptance Criteria
- Successful integration with Paymentus.
- Successful integration with LendingPad.
- No disruptions in third-party payments and loan origination services.
Notes
- Coordinate with Paymentus and LendingPad for integration requirements and testing.
User Story 5: Automated Testing
- As a: QA Engineer
- I want to: Implement Selenium code for automated testing of Transact
- So that: All functionalities are thoroughly tested before go-live
Description
Automated testing using Selenium code must be implemented to ensure all functionalities of Temenos' Transact are tested.
Acceptance Criteria
- Selenium test scripts are developed and executed.
- All functionalities are thoroughly tested and validated.
- Test results meet the acceptance criteria.
Notes
- Ensure comprehensive test coverage for all functionalities of Temenos' Transact.
User Story 6: User Experience (UX) Design
- As a: UX Designer
- I want to: Design the user interface using only different shades of blue
- So that: The UX meets the branding guidelines of Test Republic Bank
Description
The user interface of Temenos' Transact must be designed using only different shades of blue.
Acceptance Criteria
- The user interface is designed using only different shades of blue.
- The design meets the branding guidelines of Test Republic Bank.
- User feedback on the design is positive.
Notes
- Coordinate with the branding team to ensure compliance with branding guidelines.
Acceptance Criteria
The general acceptance criteria for the user stories include successful data migration, uninterrupted account access, proper account closure and refunds, seamless third-party integration, comprehensive automated testing, and compliance with UX design guidelines.
Definitions, Acronyms, and Abbreviations
- SaaS: Software as a Service
- CD: Certificate of Deposit
- LOS: 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: 10/10/2024
- Approved by: [Approver's Name]
- Date: [Approval Date]