Functional Specification Document (FSD) for Transact New Implementation II
Table of Contents
- Introduction
- Purpose
- Scope
- Definitions, Acronyms, and Abbreviations
- References
- Overview
- Functional Requirements
- Data Requirements
- User Interface Requirements
- Non-Functional Requirements
- Assumptions
- Constraints
- Acceptance Criteria
- Appendix
- Approval
Introduction
This document provides a detailed functional specification for the implementation of Temenos' Transact core banking product with Test Republic Bank's legacy mainframe banking system.
Purpose
The purpose of this document is to outline the functional requirements necessary to successfully implement Temenos' Transact core banking product, ensuring a seamless transition from the legacy system without disrupting client access.
Scope
The scope of this document covers the migration of all account data from the legacy mainframe banking system to the cloud-based Temenos' Transact system, the integration with third-party software, and the establishment of automated testing procedures.
Definitions, Acronyms, and Abbreviations
- Temenos' Transact: A cloud-based core banking product.
- SaaS: Software as a Service.
- LOS: Loan Origination System.
- UX: User Experience.
References
- Legacy Mainframe System Documentation
- Temenos' Transact Product Specifications
- Paymentus Integration Guide
- LendingPad Integration Guide
- Selenium Testing Documentation
Overview
Test Republic Bank's legacy mainframe system is over 30 years old and holds all account information. This project aims to transition all accounts to Temenos' Transact product by New Year's Eve, 2025, ensuring no disruption to clients.
Functional Requirements
Requirement 1: Account Migration
- ID: FR-001
- Description: Migrate all account data from the legacy mainframe system to Temenos' Transact.
- Priority: High
- Source: Project Stakeholders
- Rationale: Ensure all client accounts are accurately transferred to the new system.
- Acceptance Criteria: Successful data migration with no data loss or corruption. Clients must have uninterrupted access to their accounts during the transition.
- Dependencies: Legacy system data extraction and Temenos' Transact data import capabilities.
Requirement 2: Account Purging
- ID: FR-002
- Description: Purge accounts with balances of $100 or less, close these accounts, and refund the owners by check.
- Priority: Medium
- Source: Project Stakeholders
- Rationale: Clean up dormant or low-balance accounts to optimize the new system.
- Acceptance Criteria: All accounts with $100 or less are successfully purged, closed, and refunds issued.
- Dependencies: Legacy system data access and check issuance process.
Requirement 3: Third-Party Integration
- ID: FR-003
- Description: Integrate Temenos' Transact with Paymentus and LendingPad.
- Priority: High
- Source: Project Stakeholders
- Rationale: Ensure continuous functionality of third-party payments and loan origination services.
- Acceptance Criteria: Seamless integration with Paymentus and LendingPad with no disruption to services.
- Dependencies: API availability and compatibility of Paymentus and LendingPad with Transact.
Requirement 4: Automated Testing
- ID: FR-004
- Description: Develop Selenium scripts for automated testing of the new system.
- Priority: High
- Source: Project Stakeholders
- Rationale: Ensure system reliability and performance through automated testing.
- Acceptance Criteria: Comprehensive Selenium test suite covering all critical functionalities.
- Dependencies: Access to the new system for test script development and execution.
Requirement 5: User Interface Design
- ID: FR-005
- Description: The user interface should only use different shades of blue.
- Priority: Low
- Source: UX Team
- Rationale: Maintain a consistent and visually appealing user experience.
- Acceptance Criteria: All UI elements use different shades of blue, with no other colors present.
- Dependencies: UI design guidelines and implementation.
Data Requirements
- Data entities: Client accounts, transaction history, account balances.
- Attributes: Account number, client name, account type, balance, transaction details.
- Relationships: Clients may have multiple accounts; transactions belong to accounts.
User Interface Requirements
- UI should be intuitive and user-friendly.
- Consistent use of different shades of blue.
- Responsive design for seamless access across devices.
Non-Functional Requirements
- Performance: The system should handle concurrent access by up to 100,000 users.
- Security: Ensure data encryption and compliance with banking regulations.
- Usability: The system should be easy to use, with minimal training required for staff.
Assumptions
- All necessary data from the legacy system is accessible for migration.
- Temenos' Transact's API supports integration with Paymentus and LendingPad.
- Sufficient resources are available for automated testing.
Constraints
- The project must be completed by New Year's Eve, 2025.
- No disruption to client access during the migration process.
- Use only different shades of blue in the UI.
Acceptance Criteria
- Successful migration of all accounts from the legacy system to Temenos' Transact.
- No client access disruption during the transition.
- Seamless integration with Paymentus and LendingPad.
- Fully automated testing using Selenium.
- UI design adheres to the specified color scheme.
Appendix
- Legacy System Data Schema
- Temenos' Transact API Documentation
- Paymentus Integration Guide
- LendingPad Integration Guide
- Selenium Testing Framework Documentation
Approval
- Prepared by: Mike Meier
- Email: mikemeier@mad-tech.ai
- Date: 04/28/2025
- Approved by: [Approver's Name]
- Date: [Approval Date]