Functional Specification Document (FSD) for Temenos Transact Implementation - Test Republic Bank

Table of Contents

  1. Introduction
  2. Purpose
  3. Scope
  4. Definitions, Acronyms, and Abbreviations
  5. References
  6. Overview
  7. Functional Requirements
  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 outlines the functional specifications for the implementation of Temenos' Transact core banking product at Test Republic Bank. The goal is to migrate from a legacy mainframe system to a cloud-based SaaS solution without disrupting customer access.

Purpose

The purpose of this FSD is to detail the functional requirements for the successful migration and implementation of Temenos' Transact product, ensuring a seamless transition and continuous client access.

Scope

The scope includes migrating account information for 100,000 retail checking and savings accounts, as well as other financial products, from a legacy Cobol-based mainframe system to Temenos' Transact. The project also includes integration with third-party software and automated testing.

Definitions, Acronyms, and Abbreviations

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

References

  • Temenos Transact Product Documentation
  • Paymentus Integration Guide
  • LendingPad Integration Guide
  • Selenium Testing Documentation

Overview

Test Republic Bank aims to modernize its banking infrastructure by transitioning to Temenos' Transact core banking system. This project will ensure no disruption in client access and will go live on New Year's Eve, 2024.

Functional Requirements

Requirement 1: Account Migration

  • ID: FR-001
  • Description: Migrate all account information from the legacy mainframe system to Temenos' Transact.
  • Priority: High
  • Source: Business Need
  • Rationale: Modernization and improved system efficiency.
  • Acceptance Criteria: Successful migration of all accounts without data loss.
  • Dependencies: Legacy system data availability.

Requirement 2: Account Purging

  • ID: FR-002
  • Description: Purge accounts with $100 or less, close them, and refund the account holders by check.
  • Priority: Medium
  • Source: Business Need
  • Rationale: Data cleanup and system optimization.
  • Acceptance Criteria: Accounts with $100 or less are closed and refunds issued.
  • Dependencies: Accurate account balance data.

Requirement 3: Continuous Access

  • ID: FR-003
  • Description: Ensure clients have continuous access to their accounts during the transition.
  • Priority: High
  • Source: Client Requirement
  • Rationale: Maintain client trust and service continuity.
  • Acceptance Criteria: No reported access issues during migration.
  • Dependencies: System uptime and availability.

Requirement 4: Third-Party Integrations

  • ID: FR-004
  • Description: Integrate Temenos' Transact with Paymentus and LendingPad.
  • Priority: High
  • Source: Business Need
  • Rationale: Seamless operation with existing third-party systems.
  • Acceptance Criteria: Successful integration with no functional issues.
  • Dependencies: Third-party API availability.

Requirement 5: Automated Testing

  • ID: FR-005
  • Description: Implement Selenium code for automated testing of the new system.
  • Priority: High
  • Source: Technical Requirement
  • Rationale: Ensure system reliability and reduce manual testing.
  • Acceptance Criteria: Automated tests covering critical functionalities.
  • Dependencies: Selenium framework setup.

Requirement 6: User Interface

  • ID: FR-006
  • Description: The UX should only use different shades of blue.
  • Priority: Low
  • Source: Client Preference
  • Rationale: Consistent and appealing user interface.
  • Acceptance Criteria: UX uses only blue shades.
  • Dependencies: UI design guidelines.

Data Requirements

  • Complete data mapping from the legacy system to Temenos' Transact.
  • Data validation to ensure accuracy post-migration.
  • Secure data transfer protocols to protect sensitive information.

User Interface Requirements

  • Consistent use of different shades of blue.
  • Intuitive navigation and user-friendly design.
  • Accessibility features to ensure usability for all clients.

Non-Functional Requirements

  • Performance: The system should handle peak loads efficiently.
  • Security: Ensure data protection and compliance with regulations.
  • Usability: High user satisfaction with minimal learning curve.
  • Availability: 99.9% uptime during and after migration.

Assumptions

  • Legacy system data is accurate and up-to-date.
  • Third-party APIs are stable and accessible.
  • Adequate resources are available for project execution.

Constraints

  • Migration must be completed with no client access disruption.
  • Go-live date is fixed on New Year's Eve, 2024.
  • Budget and resource limitations.

Acceptance Criteria

  • Successful migration of all accounts and data.
  • No disruption in client access during the transition.
  • Full integration with Paymentus and LendingPad.
  • Automated testing implemented and passed.
  • UX design meets specified requirements.

Appendix

  • Detailed data mapping documents.
  • Integration guides for Paymentus and LendingPad.
  • Selenium test scripts and documentation.

Approval

  • Prepared by: Mike Meier
  • Email: mikemeier@mad-tech.ai
  • Date: 10/21/2024
  • Approved by: [Approver's Name]
  • Date: [Approval Date]