Functional Specification Document (FSD)
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 details the functional requirements for the implementation of Temenos' Transact core banking product with Test Republic Bank's legacy mainframe banking system.
Purpose
The purpose of this FSD is to provide a detailed description of the functional requirements necessary to successfully implement Temenos' Transact product, ensuring a seamless transition from the legacy system without disrupting client access.
Scope
The scope of this FSD includes the installation and configuration of Temenos' Transact, data migration from the legacy system, integration with third-party systems, automated testing, and user interface design.
Definitions, Acronyms, and Abbreviations
- Legacy System: Test Republic Bank’s existing Cobol-based mainframe system.
- Transact: Temenos' core banking product.
- SaaS: Software as a Service.
- UX: User Experience.
- LOS: Loan Origination System.
- Selenium: A tool for automating web applications for testing purposes.
References
- Temenos Transact Documentation
- Test Republic Bank Legacy System Documentation
- Paymentus Integration Guide
- LendingPad LOS Integration Guide
Overview
The project aims to migrate all account information from Test Republic Bank’s legacy mainframe system to Temenos’ Transact, a cloud-based SaaS solution. The migration must ensure continuous client access to accounts and integrate with existing third-party systems. The project completion deadline is New Year's Eve, 2024.
Functional Requirements
Requirement 1: Data Migration
- ID: FR-001
- Description: Migrate all account data from the legacy system to Temenos' Transact.
- Priority: High
- Source: Project Stakeholders
- Rationale: Ensure all account information is transferred accurately to the new system.
- Acceptance Criteria: All account data is correctly migrated and verified.
- Dependencies: Legacy system data extraction, Transact data import features.
Requirement 2: Account Access Continuity
- ID: FR-002
- Description: Ensure clients have continuous access to their accounts during migration.
- Priority: High
- Source: Project Stakeholders
- Rationale: Prevent any disruption to client access.
- Acceptance Criteria: No reported client access issues during the migration process.
- Dependencies: Parallel operation of legacy and new systems during migration.
Requirement 3: Account Purging and Refunds
- ID: FR-003
- Description: Purge accounts with $100 or less, close them, and issue refunds.
- Priority: Medium
- Source: Project Stakeholders
- Rationale: Clean up inactive or low-value accounts.
- Acceptance Criteria: All qualifying accounts are purged and refunds issued.
- Dependencies: Accurate account balance data, refund processing systems.
Requirement 4: Integration with Paymentus
- ID: FR-004
- Description: Integrate Transact with the Paymentus third-party payments software.
- Priority: High
- Source: Project Stakeholders
- Rationale: Ensure seamless payment processing.
- Acceptance Criteria: Successful end-to-end payment transactions.
- Dependencies: Paymentus API, Transact integration capabilities.
Requirement 5: Integration with LendingPad LOS
- ID: FR-005
- Description: Integrate Transact with LendingPad Loan Origination System.
- Priority: High
- Source: Project Stakeholders
- Rationale: Ensure loan processing continuity.
- Acceptance Criteria: Successful loan origination and management.
- Dependencies: LendingPad API, Transact integration capabilities.
Requirement 6: Automated Testing with Selenium
- ID: FR-006
- Description: Develop Selenium code for automated testing of the Transact implementation.
- Priority: High
- Source: Project Stakeholders
- Rationale: Ensure reliability and efficiency of testing.
- Acceptance Criteria: Comprehensive test coverage and successful test runs.
- Dependencies: Selenium framework, test case definitions.
Requirement 7: User Interface Design
- ID: FR-007
- Description: Design the user interface using different shades of blue only.
- Priority: Low
- Source: Project Stakeholders
- Rationale: Consistent branding and user experience.
- Acceptance Criteria: UI matches design specifications.
- Dependencies: UI design guidelines, Temenos Transact UI customization capabilities.
Data Requirements
- Migrate all account data including checking, savings, CDs, Money Market accounts, mortgages, credit cards, car loans, and personal loans.
- Ensure data integrity and accuracy during migration.
User Interface Requirements
- The UI must only use different shades of blue.
- The design should be intuitive and user-friendly.
Non-Functional Requirements
- Performance: The system must handle up to 100,000 accounts without performance degradation.
- Security: Ensure data security during and after migration.
- Usability: The system should be easy to use for both clients and bank employees.
- Reliability: The system must be available 99.99% of the time.
Assumptions
- The legacy system data is accurate and complete.
- Temenos’ Transact can handle the volume of data and transactions.
- Third-party systems (Paymentus, LendingPad) will be available for integration.
Constraints
- The project must be completed by New Year's Eve, 2024.
- Continuous client access must be maintained during the migration.
- Only shades of blue can be used in the UI design.
Acceptance Criteria
- Successful migration of all account data with no data loss.
- No disruption in client access to accounts.
- Seamless integration with Paymentus and LendingPad.
- Automated tests developed and executed with Selenium.
- UI design meets specifications.
Appendix
- Detailed data mapping from legacy system to Transact.
- Integration specifications for Paymentus and LendingPad.
Approval
- Prepared by: Mike Meier
- Email: mikemeier@mad-tech.ai
- Date: 10/10/2024
- Approved by: [Approver's Name]
- Date: [Approval Date]