Functional Specification Document (FSD)

Table of Contents

1. Introduction
2. Purpose
3. Scope
4. Definitions, Acronyms, and Abbreviations
5. References
6. Overview
7. Functional Requirements
   • Requirement 1: Data Migration
   • Requirement 2: System Integration
   • Requirement 3: User Access
   • Requirement 4: Account Purging
   • Requirement 5: Automated Testing
   • Requirement 6: User Interface Design
8. Data Requirements
9. User Interface Requirements
10. Non-Functional Requirements
11. Assumptions
12. Constraints
13. Acceptance Criteria
14. Appendix
15. Approval

Introduction

This document details the functional requirements for the implementation of Temenos' Transact core banking product at Test Republic Bank. The project involves migrating from a legacy mainframe system to a cloud-based SaaS solution and ensuring seamless integration with existing systems.

Purpose

The purpose of this FSD is to outline the functional requirements necessary for the successful implementation of Temenos' Transact product, ensuring minimal disruption to client services during the transition.

Scope

The scope of this FSD includes the migration of account data from the legacy mainframe system to Temenos' Transact, integration with existing third-party systems, and ensuring continuous client access to accounts throughout the transition.

Definitions, Acronyms, and Abbreviations

• SaaS: Software as a Service
• LOS: Loan Origination System
• UX: User Experience
• FSD: Functional Specification Document

References

• Temenos Transact Product Documentation
• Test Republic Bank Legacy System Documentation
• Paymentus Integration Guide
• LendingPad Integration Guide

Overview

Test Republic Bank's legacy mainframe system, which is over 30 years old and COBOL-based, holds account information for 100,000 retail accounts. The project aims to migrate these accounts to Temenos' Transact cloud-based SaaS solution by New Year's Eve, 2025, ensuring no disruption to client access.

Functional Requirements

Requirement 1: Data Migration

• ID: FR-001
• Description: Migrate all account information from the legacy mainframe system to Temenos' Transact.
• Priority: High
• Source: Project Stakeholders
• Rationale: Ensure all account data is transitioned to the new system.
• Acceptance Criteria: All account data is accurately and completely migrated to Temenos' Transact.
• Dependencies: None

Requirement 2: System Integration

• ID: FR-002
• Description: Integrate Temenos' Transact with Paymentus and LendingPad.
• Priority: High
• Source: Project Stakeholders
• Rationale: Ensure continuity of third-party services.
• Acceptance Criteria: Successful integration testing with Paymentus and LendingPad.
• Dependencies: Availability of Paymentus and LendingPad APIs

Requirement 3: User Access

• ID: FR-003
• Description: Ensure uninterrupted client access to accounts during the migration.
• Priority: High
• Source: Project Stakeholders
• Rationale: Maintain customer trust and service continuity.
• Acceptance Criteria: No reported client access issues during migration.
• Dependencies: None

Requirement 4: Account Purging

• ID: FR-004
• Description: Purge accounts with $100 or less, close them, and refund owners by check.
• Priority: Medium
• Source: Project Stakeholders
• Rationale: Clean up data and reduce system load.
• Acceptance Criteria: All qualifying accounts are purged, closed, and refunds issued.
• Dependencies: Accurate account balance data

Requirement 5: Automated Testing

• ID: FR-005
• Description: Implement Selenium code for automated testing.
• Priority: Medium
• Source: Project Stakeholders
• Rationale: Ensure thorough testing and quality assurance.
• Acceptance Criteria: Successful execution of automated test scripts.
• Dependencies: Availability of Selenium infrastructure

Requirement 6: User Interface Design

• ID: FR-006
• Description: The UX should only use different shades of blue.
• Priority: Low
• Source: Project Stakeholders
• Rationale: Maintain brand consistency.
• Acceptance Criteria: UX design reviewed and approved by stakeholders.
• Dependencies: None

Data Requirements

• Data migration must include account information, transaction history, and customer details.
• Data integrity checks must be performed before and after migration.

User Interface Requirements

• The UI must be designed using only different shades of blue.
• The UI should be intuitive and user-friendly.

Non-Functional Requirements

• Performance: The system must handle peak loads without degradation.
• Security: Ensure data security during migration and system integration.
• Usability: The system must be easy to use for both clients and bank staff.

Assumptions

• APIs for Paymentus and LendingPad will be available and functional.
• The legacy system's data is accurate and up-to-date.
• The project will have access to necessary resources and tools.

Constraints

• The migration must be completed by New Year's Eve, 2025.
• Client access must not be disrupted during the transition.

Acceptance Criteria

• All account data is successfully migrated to Temenos' Transact.
• Integration with Paymentus and LendingPad is successful.
• Clients experience no disruption in access to their accounts.
• Accounts with $100 or less are purged and refunds issued.
• Automated testing scripts run successfully.
• The UX design meets the specified requirements.

Appendix

• Additional diagrams, flowcharts, and mockups related to the project.

Approval

• Prepared by: Mike Meier
• Date: 05/06/2025
• Approved by: [Approver's Name]
• Date: [Approval Date]