Business Requirements Document (BRD)

Table of Contents

1. Introduction
2. Business Objectives
3. Project Scope
4. Stakeholder Analysis
5. Requirements
   • Functional Requirements
   • Non-Functional Requirements
6. Assumptions
7. Constraints
8. Risks
9. Glossary
10. Appendices
11. Approval

Introduction

The purpose of this Business Requirements Document (BRD) is to outline the requirements for the installation of Temenos’ Transact core banking product with Test Republic Bank's legacy mainframe banking system. This document will serve as a guide for the transition and ensure that all stakeholder needs are met without disrupting existing services.

Business Objectives

The primary objectives of this project are:

• Transition from a 30-year-old Cobol-based legacy mainframe system to Temenos' Transact, a cloud-based SaaS solution.
• Ensure seamless access to accounts for clients during the transition.
• Go live with Temenos' Transact on New Year's Eve, 2025, with all accounts and functionalities operational.
• Integrate Transact with third-party payment software from Paymentus and the LOS from LendingPad.
• Automate testing using Selenium code.
• Ensure the UX design uses only different shades of blue.

Project Scope

In-Scope:

• Migration of all account information from the legacy system to Temenos' Transact.
• Ensuring continuous client access to accounts during the transition.
• Purging and closing accounts with $100 or less, and refunding the account holders.
• Integration with Paymentus and LendingPad.
• Development and deployment of Selenium code for automated testing.
• UX design adhering to the color scheme of different shades of blue.

Out-of-Scope:

• Modifications to the core functionalities of Temenos' Transact beyond the specified requirements.
• Any additional third-party integrations not mentioned above.

Stakeholder Analysis

Internal Stakeholders:

• Project Manager
• IT Department
• Customer Service Team
• Compliance Team
• Marketing Team

External Stakeholders:

• Temenos' Implementation Team
• Paymentus Integration Team
• LendingPad Integration Team
• Clients of Test Republic Bank

Requirements

Functional Requirements

1. Requirement ID: FR-001

   • Description: Migrate all account information from the legacy Cobol-based system to Temenos' Transact.
   • Priority: High
   • Source: Business Need

2. Requirement ID: FR-002

   • Description: Ensure clients have uninterrupted access to their accounts during the transition.
   • Priority: High
   • Source: Customer Experience

3. Requirement ID: FR-003

   • Description: Purge and close accounts with $100 or less and refund account holders by check.
   • Priority: Medium
   • Source: Business Policy

4. Requirement ID: FR-004

   • Description: Integrate Temenos' Transact with Paymentus for third-party payments.
   • Priority: High
   • Source: System Integration

5. Requirement ID: FR-005

   • Description: Integrate Temenos' Transact with LendingPad for loan origination.
   • Priority: High
   • Source: System Integration

6. Requirement ID: FR-006

   • Description: Develop and implement Selenium code for automated testing.
   • Priority: High
   • Source: Quality Assurance

7. Requirement ID: FR-007

   • Description: Ensure the UX uses only different shades of blue.
   • Priority: Medium
   • Source: Branding Guidelines

Non-Functional Requirements

1. Requirement ID: NFR-001

   • Description: The system must ensure data integrity during migration.
   • Priority: High
   • Source: Data Security

2. Requirement ID: NFR-002

   • Description: The system must be available 99.9% of the time during and after the transition.
   • Priority: High
   • Source: Service Level Agreement

3. Requirement ID: NFR-003

   • Description: The UX should be intuitive and user-friendly.
   • Priority: Medium
   • Source: User Experience

4. Requirement ID: NFR-004

   • Description: The integration with third-party systems should have a response time of less than 2 seconds.
   • Priority: High
   • Source: Performance Requirement

Assumptions

• All necessary data from the legacy system is available and accessible for migration.
• Temenos' Transact will support all required integrations without additional customization.
• All stakeholders will be available for necessary approvals and testing.

Constraints

• The migration must be completed by New Year's Eve, 2025.
• The project must stay within the allocated budget.
• Limited availability of legacy system documentation.

Risks

• Risk of data loss or corruption during migration.
• Potential downtime affecting customer access.
• Delays in integration with third-party systems.
• Incomplete or inaccurate legacy system data.
• Compliance risks related to data handling and migration.

Glossary

• SaaS: Software as a Service
• LOS: Loan Origination System
• UX: User Experience
• FR: Functional Requirements
• NFR: Non-Functional Requirements

Appendices

• Detailed migration plan
• Contact information for key stakeholders
• Project timeline and milestones

Approval

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