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 document is to outline the business requirements for the implementation of Temenos' Transact core banking product to replace Test Republic Bank's legacy mainframe banking system. The legacy system is over 30 years old and COBOL-based, holding account information for 100,000 retail checking and savings accounts, as well as various other financial products.

Business Objectives

The primary business objectives are:

• Transition all accounts from the legacy system to the cloud-based Temenos' Transact system without disrupting client access.
• Ensure Temenos' Transact is fully operational by New Year's Eve, 2025.
• Integrate Transact with third-party software from Paymentus and LendingPad.
• Automate testing using Selenium.
• Ensure the UX adheres to a blue color scheme.

Project Scope

In-Scope:

• Migration of all account data from the legacy system to Temenos' Transact.
• Integration with Paymentus and LendingPad.
• Automation of testing through Selenium.
• UX design using different shades of blue.
• Purging and closing accounts with balances of $100 or less and refunding those clients.

Out-of-Scope:

• Enhancements to the legacy mainframe system.
• Development of new features outside the scope of Temenos' Transact.
• Integration with any other third-party systems not mentioned.

Stakeholder Analysis

Internal Stakeholders:

• Project Sponsor: Chief Technology Officer (CTO) of Test Republic Bank
• Project Manager: Mike Meier
• IT Department: Responsible for technical implementation and integration
• Customer Service Team: Ensuring client communication and support

External Stakeholders:

• Temenos: Provider of Transact
• Paymentus: Third-party payments software provider
• LendingPad: Loan Origination System (LOS) provider
• Clients: End-users of Test Republic Bank

Requirements

Functional Requirements

1. FR-001: Migrate all account data from the legacy system to Temenos' Transact.
   • Priority: High
   • Source: Business Objective
2. FR-002: Ensure seamless client access during the transition.
   • Priority: High
   • Source: Business Objective
3. FR-003: Purge and close accounts with balances of $100 or less and issue refunds by check.
   • Priority: Medium
   • Source: Business Objective
4. FR-004: Integrate Transact with Paymentus for payment processing.
   • Priority: High
   • Source: Business Objective
5. FR-005: Integrate Transact with LendingPad for loan origination.
   • Priority: High
   • Source: Business Objective

Non-Functional Requirements

1. NFR-001: Ensure that the system is fully operational by New Year's Eve, 2025.
   • Priority: High
   • Source: Project Deadline
2. NFR-002: UX design must use different shades of blue exclusively.
   • Priority: Medium
   • Source: Business Preference
3. NFR-003: Automate testing using Selenium.
   • Priority: Medium
   • Source: Testing Strategy
4. NFR-004: Ensure the system is scalable and can handle future growth.
   • Priority: Medium
   • Source: Business Objective

Assumptions

• All necessary resources and support from Temenos, Paymentus, and LendingPad will be available.
• There will be no major changes to the legacy system during the transition period.
• Data quality from the legacy system is sufficient for migration.

Constraints

• The project must be completed by New Year's Eve, 2025.
• The legacy system is COBOL-based, which may pose integration challenges.
• The UX design is limited to shades of blue.

Risks

• Risk: Data migration issues could disrupt client access.
  • Mitigation: Perform thorough testing and data validation.
• Risk: Integration with third-party systems may encounter unforeseen technical challenges.
  • Mitigation: Engage early with third-party vendors to identify and resolve issues.
• Risk: Project timeline may be impacted by unforeseen delays.
  • Mitigation: Regularly monitor project progress and adjust plans as needed.

Glossary

• COBOL: Common Business-Oriented Language
• LOS: Loan Origination System
• SaaS: Software as a Service
• UX: User Experience

Appendices

• Detailed project plan
• Data migration strategy
• Integration architecture diagrams

Approval

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