User Stories
Table of Contents
- User Story 1: Core Banking System Replacement
- User Story 2: Third Party Payment System Integration
- User Story 3: Loan Origination System Integration
- User Story 4: Data Purging and Refund Process
- User Story 5: API Integration and Automated Testing
- User Story 6: User Experience Design
Introduction
The purpose of this document is to outline the user stories for Mike's Fantastic Banking Project, which aims to replace the legacy core banking system with Temenos Transact R24 and integrate third-party applications.
Purpose
This User Stories document captures user requirements in a simple, understandable format to ensure the successful implementation of Mike's Fantastic Banking Project.
Scope
This document pertains to the replacement of Fantastic Bank's 40-year-old core banking system programmed in COBOL with Temenos Transact R24, and the integration of third-party applications for payments and loan origination.
User Stories
User Story 1: Core Banking System Replacement
- As a: Project Manager
- I want to: Replace the old COBOL-based core banking system with Temenos Transact R24
- So that: The bank can utilize modern, efficient technology for core banking operations
Description
Fantastic Bank’s legacy core banking system, programmed in COBOL, needs to be replaced with Temenos Transact R24 within six months, without disrupting services for the bank's 250,000 customers.
Acceptance Criteria
- Temenos Transact R24 is fully implemented within six months
- Zero disruptions to current banking services for 250,000 customers
Notes
None
User Story 2: Third Party Payment System Integration
- As a: IT Integration Specialist
- I want to: Integrate Paymentus payments instead of the Temenos Payments Hub (TPH)
- So that: The bank can manage payments more efficiently with a preferred third-party system
Description
Fantastic Bank will integrate Paymentus payments, replacing the use of Temenos Payments Hub, to handle all payment transactions.
Acceptance Criteria
- Paymentus payments system is fully integrated and operational
- Payment processing is seamless and error-free
Notes
None
User Story 3: Loan Origination System Integration
- As a: Loan Officer
- I want to: Use LendingPad for loan origination instead of Temenos' LOS
- So that: The loan origination process is streamlined and more efficient
Description
Fantastic Bank will use LendingPad for their loan origination system, replacing Temenos' Loan Origination System (LOS).
Acceptance Criteria
- LendingPad is fully integrated and operational
- Loan origination process is smooth and efficient
Notes
None
User Story 4: Data Purging and Refund Process
- As a: Data Analyst
- I want to: Purge all accounts with $100 or less, close them, and refund the owners by check
- So that: The bank's data is clean and up-to-date
Description
All accounts with balances of $100 or less must be purged, closed, and their owners refunded by check.
Acceptance Criteria
- All accounts with $100 or less are purged and closed
- Refund checks are sent to the account owners
Notes
None
User Story 5: API Integration and Automated Testing
- As a: Software Developer
- I want to: Connect Temenos Transact's APIs and create Selenium code for automated testing
- So that: The integration is seamless and all testing is automated
Description
Develop the necessary code to connect Temenos Transact's APIs and create Selenium scripts for automated testing to ensure a smooth integration.
Acceptance Criteria
- All relevant APIs are connected and functioning
- Selenium scripts are created and all tests are automated
Notes
None
User Story 6: User Experience Design
- As a: UX Designer
- I want to: Design the user interface using different shades of blue
- So that: The user experience is consistent with the bank's visual branding guidelines
Description
The user interface for the new system should use only different shades of blue to align with the bank's branding guidelines.
Acceptance Criteria
- The UX design uses only shades of blue
- The interface is user-friendly and consistent with branding guidelines
Notes
None
Acceptance Criteria
General acceptance criteria for all user stories:
- All functionalities work as expected without disrupting current services
- The project is completed within the stipulated timeframe (six months)
Definitions, Acronyms, and Abbreviations
- COBOL: Common Business-Oriented Language
- TPH: Temenos Payments Hub
- LOS: Loan Origination System
- API: Application Programming Interface
- 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: 02/05/2025
- Approved by: [Approver's Name]
- Date: [Approval Date]