Dashboard
Documents
Archive
Settings
New Project
New Proposal
New Document
Code Review
Code Documenter

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
  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 provides a detailed specification for the Test Bank Core Banking Software Replacement project. It outlines the functional requirements, data requirements, user interface requirements, non-functional requirements, assumptions, constraints, acceptance criteria, and the approval process.

Purpose

The purpose of this FSD is to define the functional requirements for replacing Test Bank's 40-year-old core banking system with the latest Temenos Transact core banking software (R24 release), integrating third-party software systems for payments and loans, and ensuring seamless transition without disrupting the bank's current 250,000 members.

Scope

This FSD pertains to the implementation of new core banking, payments, and loans software for Test Bank, including the integration of Temenos Transact, Paymentus payments, and LendingPad loan origination system.

Definitions, Acronyms, and Abbreviations

  • COBOL: Common Business-Oriented Language
  • Temenos Transact: Core banking software by Temenos
  • TPH: Temenos Payments Hub
  • LOS: Loan Origination System
  • API: Application Programming Interface
  • UX: User Experience

References

  • Temenos Transact R24 Documentation
  • Paymentus Integration Guide
  • LendingPad Integration Guide
  • Selenium Documentation

Overview

The project aims to replace Test Bank's outdated core banking system with the latest Temenos Transact software, integrate Paymentus for payment processing, and LendingPad for loan origination. The project must be completed within six months to go live on New Year's Eve, 2024, without disrupting current members.

Functional Requirements

Requirement 1: Core Banking System Replacement

  • ID: FR-001
  • Description: Replace the existing core banking system programmed in COBOL with Temenos Transact R24.
  • Priority: High
  • Source: Business Need
  • Rationale: Modernize the core banking system to improve efficiency and support new functionalities.
  • Acceptance Criteria: Successful installation and configuration of Temenos Transact R24, with all existing functionalities replicated.
  • Dependencies: None

Requirement 2: Payment Processing Integration

  • ID: FR-002
  • Description: Integrate Paymentus for payment processing instead of Temenos Payments Hub (TPH).
  • Priority: High
  • Source: Business Decision
  • Rationale: Use a specialized third-party solution for payment processing.
  • Acceptance Criteria: Paymentus integration completed, tested, and operational without issues.
  • Dependencies: Core Banking System Replacement (FR-001)

Requirement 3: Loan Origination System Integration

  • ID: FR-003
  • Description: Integrate LendingPad for loan origination instead of Temenos' LOS.
  • Priority: High
  • Source: Business Decision
  • Rationale: Use a specialized third-party solution for loan origination.
  • Acceptance Criteria: LendingPad integration completed, tested, and operational without issues.
  • Dependencies: Core Banking System Replacement (FR-001)

Requirement 4: Account Purge and Closure

  • ID: FR-004
  • Description: Purge all accounts with $100 or less, close these accounts, and refund the account holders by check.
  • Priority: Medium
  • Source: Business Policy
  • Rationale: Clean up inactive or low-balance accounts to streamline the transition.
  • Acceptance Criteria: All targeted accounts successfully purged, closed, and refunded.
  • Dependencies: Core Banking System Replacement (FR-001)

Requirement 5: API Integration

  • ID: FR-005
  • Description: Develop and implement code to connect Temenos' Transact APIs.
  • Priority: High
  • Source: Technical Requirement
  • Rationale: Ensure seamless integration with Temenos Transact.
  • Acceptance Criteria: All required API connections established and tested.
  • Dependencies: Core Banking System Replacement (FR-001), Payment Processing Integration (FR-002), Loan Origination System Integration (FR-003)

Requirement 6: Automated Testing

  • ID: FR-006
  • Description: Develop Selenium code for automated testing.
  • Priority: High
  • Source: Technical Requirement
  • Rationale: Ensure thorough testing and quality assurance.
  • Acceptance Criteria: Selenium tests developed, executed, and passed.
  • Dependencies: Core Banking System Replacement (FR-001), API Integration (FR-005)

Requirement 7: User Interface Design

  • ID: FR-007
  • Description: The UX should only use different shades of blue when clients log on.
  • Priority: Medium
  • Source: Branding Requirement
  • Rationale: Maintain consistent branding and user experience.
  • Acceptance Criteria: User interface designed with only shades of blue.
  • Dependencies: Core Banking System Replacement (FR-001)

Data Requirements

  • Detailed data migration plan from the old COBOL system to Temenos Transact.
  • Data mapping for Paymentus and LendingPad integrations.
  • Purge criteria for accounts with $100 or less.

User Interface Requirements

  • The user interface must conform to the branding requirement of using only shades of blue.
  • The design should be intuitive and user-friendly to ensure a seamless transition for existing members.

Non-Functional Requirements

  • Performance: The system must handle the load of 250,000 members without degradation.
  • Security: Ensure all data and transactions are secure and comply with regulatory standards.
  • Usability: The system should be easy to use for both staff and members.
  • Reliability: The system must be reliable and available 24/7.

Assumptions

  • All stakeholders are available for feedback and approvals within the project timeline.
  • Necessary hardware and software resources are available for the project.
  • There are no significant changes to regulatory requirements during the project period.

Constraints

  • The project must be completed within six months to go live on New Year's Eve, 2024.
  • No disruption to current 250,000 members during the transition.

Acceptance Criteria

  • Successful installation and configuration of Temenos Transact R24.
  • Seamless integration of Paymentus and LendingPad.
  • All accounts with $100 or less purged, closed, and refunded.
  • All API connections established and tested.
  • Selenium tests developed, executed, and passed.
  • User interface designed with only shades of blue.

Appendix

  • Detailed project timeline
  • Contact information for key stakeholders
  • Backup and recovery plans

Approval

Document Link
Test Bank Core Banking Software Replacement Functional Specification Document (FSD)