User Stories
Table of Contents
- User Story 1: Account Migration
- User Story 2: Continuous Account Access
- User Story 3: Account Closure and Refund
- User Story 4: Integration with Payment Systems
- User Story 5: Automated Testing
- User Story 6: User Experience Design
Introduction
This document outlines the user stories for the project "Temenos Transact Implementation Test Republic 3." The project aims to install Temenos' Transact core banking product with our legacy mainframe banking system.
Purpose
The purpose of this document is to capture user requirements for the seamless transition from Test Republic Bank's legacy mainframe banking system to Temenos' Transact cloud-based SaaS solution.
Scope
The scope includes the migration of all account information from a 30-year-old Cobol-based legacy system to Temenos' Transact product. This involves ensuring continuous account access, account closure for low-balance accounts, integration with third-party systems, automated testing, and a specific UX design.
User Stories
User Story 1: Account Migration
- As a: Data Migration Specialist
- I want to: Migrate all account information from the legacy system to Temenos' Transact
- So that: All accounts are available on the new system without data loss
Description
The legacy mainframe system holds all account information for 100,000 retail checking and savings accounts, as well as CDs, Money Market accounts, mortgages, credit cards, car loans, and other personal loans. This data must be accurately migrated to Temenos' Transact without any data corruption or loss.
Acceptance Criteria
- All account data is successfully migrated to Temenos' Transact
- No data loss or corruption during migration
- Migration process is completed by New Year's Eve, 2024
Notes
- The legacy system is Cobol-based and over 30 years old
- Continuous monitoring during migration to ensure data integrity
User Story 2: Continuous Account Access
- As a: Bank Customer
- I want to: Have uninterrupted access to my accounts during the transition
- So that: I can manage my finances without any disruption
Description
During the migration process, clients must have uninterrupted access to their accounts. This means ensuring that the transition does not affect the day-to-day operations of the bank or its customers.
Acceptance Criteria
- All accounts remain accessible to clients during the transition
- No downtime experienced by customers
- Continuous monitoring to ensure access is maintained
Notes
- This is critical to maintaining customer trust and satisfaction
User Story 3: Account Closure and Refund
- As a: Bank Administrator
- I want to: Close accounts with $100 or less and refund their owners
- So that: We can streamline our account management and reduce overhead
Description
Accounts with a balance of $100 or less need to be purged from the system. The accounts should be closed, and the owners refunded their money by check.
Acceptance Criteria
- All accounts with $100 or less are identified and closed
- Refund checks are issued to account owners
- Process is completed by New Year's Eve, 2024
Notes
- Ensure customer notifications are sent regarding account closures
User Story 4: Integration with Payment Systems
- As a: Integration Engineer
- I want to: Ensure Temenos' Transact works with Paymentus and LendingPad
- So that: Our payment processing and loan origination systems function seamlessly
Description
Temenos' Transact must integrate with our third-party payments software from Paymentus and our LOS from LendingPad. This ensures that payment processing and loan origination continue to function without issues.
Acceptance Criteria
- Successful integration with Paymentus and LendingPad
- No disruptions in payment processing or loan origination
- Integration tested and validated before New Year's Eve, 2024
Notes
- Continuous integration testing to ensure compatibility
User Story 5: Automated Testing
- As a: QA Engineer
- I want to: Use Selenium code for automated testing
- So that: We can efficiently test the system and ensure it meets all requirements
Description
Automated testing using Selenium code is necessary to validate that all functionalities of Temenos' Transact are working as expected. This includes testing account migrations, integrations, and user interfaces.
Acceptance Criteria
- Selenium code written and executed for automated testing
- All tests pass successfully before go-live date
- Continuous integration and testing pipeline established
Notes
- Automate as many test cases as possible to ensure efficiency
User Story 6: User Experience Design
- As a: UX Designer
- I want to: Design the user interface using only different shades of blue
- So that: The design guidelines are adhered to and provide a consistent look and feel
Description
The user interface should only use different shades of blue, without incorporating any other colors. This ensures a consistent and visually appealing user experience.
Acceptance Criteria
- User interface designed using only shades of blue
- Consistent look and feel across all screens
- Design approved by stakeholders before go-live
Notes
- Adhere to brand guidelines and design principles
Acceptance Criteria
The general acceptance criteria for the user stories are:
- Successful data migration without loss or corruption
- Continuous account access for customers
- Integration with third-party systems validated
- Automated testing completed with all tests passing
- User interface designed as per guidelines
- All tasks completed before New Year's Eve, 2024
Definitions, Acronyms, and Abbreviations
- SaaS: Software as a Service
- LOS: Loan Origination System
- QA: Quality Assurance
- UX: 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: 10/21/2024
- Approved by: [Approver's Name]
- Date: [Approval Date]