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

This Business Requirements Document (BRD) outlines the requirements and scope for the project "Transact New Implementation II". The purpose of this project is to install Temenos' Transact core banking product with our legacy mainframe banking system at Test Republic Bank.

Business Objectives

• Transition all accounts from the legacy mainframe banking system to Temenos' Transact SaaS solution.
• Ensure seamless access to accounts for clients during the transition.
• Achieve a go-live date of New Year's Eve, 2025, with all facets of Temenos' Transact product fully operational.
• Close and refund accounts with $100 or less.
• Integrate Transact with Paymentus and LendingPad.
• Implement Selenium code for automated testing.
• Ensure the UX uses only different shades of blue.

Project Scope

In-Scope:

• Migration of 100,000 retail checking and savings accounts, along with CDs, Money Market accounts, mortgages, credit cards, car loans, and personal loans.
• Seamless transition ensuring no disruption to client access.
• Closing and refunding accounts with $100 or less.
• Integration with third-party software from Paymentus and LendingPad.
• Implementation of Selenium for automated testing.
• UX design adhering to specified color scheme.

Out-of-Scope:

• Migration of non-retail accounts.
• Any enhancements or new features not specified in the requirements.

Stakeholder Analysis

Internal Stakeholders:

• Project Manager
• IT Team
• Banking Operations Team
• Customer Service Team

External Stakeholders:

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

Requirements

Functional Requirements

1. Requirement ID: FR001

   • Description: Transition all accounts from the legacy mainframe banking system to Temenos' Transact.
   • Priority: High
   • Source: Business Objective

2. Requirement ID: FR002

   • Description: Ensure clients have continual access to their accounts during the transition.
   • Priority: High
   • Source: Business Objective

3. Requirement ID: FR003

   • Description: Close and refund accounts with $100 or less.
   • Priority: Medium
   • Source: Business Objective

4. Requirement ID: FR004

   • Description: Integrate Temenos' Transact with Paymentus.
   • Priority: Medium
   • Source: Business Objective

5. Requirement ID: FR005

   • Description: Integrate Temenos' Transact with LendingPad.
   • Priority: Medium
   • Source: Business Objective

6. Requirement ID: FR006

   • Description: Implement Selenium code for automated testing.
   • Priority: High
   • Source: Business Objective

Non-Functional Requirements

1. Requirement ID: NFR001

   • Description: The UX should only use different shades of blue.
   • Priority: Low
   • Source: Business Objective

2. Requirement ID: NFR002

   • Description: System must be fully operational by New Year's Eve, 2025.
   • Priority: High
   • Source: Business Objective

Assumptions

• Data migration will be completed without data loss.
• All third-party integrations will function as expected.
• Sufficient resources will be available for the transition.

Constraints

• Legacy system limitations due to its age and technology.
• Fixed go-live date of New Year's Eve, 2025.

Risks

• Potential data migration issues.
• Integration challenges with third-party software.
• Disruption to client access during the transition.

Glossary

• SaaS: Software as a Service
• UX: User Experience
• LOS: Loan Origination System

Appendices

• Additional documents and references relevant to the project.

Approval

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