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 requirements for replacing Test Bank's existing core banking system with the latest Temenos Transact core banking software, version R24. This includes the integration of third-party systems for payments and loans, and ensuring a seamless transition for the bank's 250,000 members.

Business Objectives

• Replace the 40-year-old COBOL-based core banking system with Temenos Transact R24.
• Integrate Paymentus for payments and LendingPad for loan origination.
• Complete the project within six months to go live by New Year's Eve, 2024.
• Ensure no disruption to current members during the transition.
• Purge and close all accounts with $100 or less, refunding their owners by check.
• Automate testing using Selenium.
• Implement a UX that exclusively uses different shades of blue for clients.

Project Scope

In-Scope:

• Implementation of Temenos Transact core banking software (R24).
• Integration of Paymentus for payments.
• Integration of LendingPad for loan origination.
• Migration and purging of accounts with $100 or less.
• Development of API connections.
• Automation of testing using Selenium.
• Design and implementation of a blue-themed UX for clients.

Out-of-Scope:

• Any enhancements to the existing COBOL system.
• Use of Temenos Payments Hub (TPH).
• Use of Temenos' Loan Origination System (LOS).
• Non-banking related system integrations.

Stakeholder Analysis

Internal Stakeholders:

• Project Manager
• IT Department
• Customer Service Team
• Compliance and Risk Management Team

External Stakeholders:

• Temenos (Software Vendor)
• Paymentus (Payments System Provider)
• LendingPad (Loan Origination System Provider)
• Bank Members (Customers)

Requirements

Functional Requirements

1. Requirement ID: FR-001

   • Description: Migrate core banking operations to Temenos Transact R24.
   • Priority: High
   • Source: Business Need

2. Requirement ID: FR-002

   • Description: Integrate Paymentus for payment processing.
   • Priority: High
   • Source: Business Need

3. Requirement ID: FR-003

• Description: Integrate LendingPad for loan origination.
• Priority: High
• Source: Business Need

4. Requirement ID: FR-004

   • Description: Purge and close all accounts with $100 or less, issuing refunds by check.
   • Priority: Medium
   • Source: Compliance

5. Requirement ID: FR-005

   • Description: Develop API connections for Temenos Transact.
   • Priority: High
   • Source: Technical Requirement

6. Requirement ID: FR-006

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

7. Requirement ID: FR-007
   • Description: Implement a blue-themed user interface.
   • Priority: Low
   • Source: Branding

Non-Functional Requirements

1. Requirement ID: NFR-001

   • Description: Ensure zero downtime during transition to new system.
   • Priority: High
   • Source: Business Continuity

2. Requirement ID: NFR-002

   • Description: System must be compliant with all relevant regulatory standards.
   • Priority: High
   • Source: Compliance

3. Requirement ID: NFR-003

• Description: The system should be able to handle at least 500,000 transactions per day.
• Priority: Medium
• Source: Performance

4. Requirement ID: NFR-004
   • Description: UX should use only shades of blue for client interfaces.
   • Priority: Low
   • Source: UX Design

Assumptions

• The necessary resources and budget will be available throughout the project.
• No significant changes in regulatory requirements will occur during the project timeline.
• All third-party vendors (Temenos, Paymentus, LendingPad) will provide timely support.

Constraints

• The project must be completed within six months.
• The system must go live by New Year's Eve, 2024.
• No disruption to the current 250,000 members is permissible.

Risks

• Risk: Delays in third-party vendor integration.

  • Mitigation: Regular communication and progress tracking with vendors.

• Risk: Potential data migration issues.

  • Mitigation: Comprehensive testing and validation of data migration process.

• Risk: Unforeseen technical challenges.

• Mitigation: Allocate buffer time and have contingency plans in place.

Glossary

• COBOL: Common Business-Oriented Language, a programming language.
• API: Application Programming Interface.
• UX: User Experience.
• TPH: Temenos Payments Hub.
• LOS: Loan Origination System.

Appendices

• Appendix A: Project Timeline
• Appendix B: Vendor Contracts
• Appendix C: Detailed Functional Specifications

Approval

• Prepared by: Super User
• Email: SuperUser@awesomesauce.com
• Date: 10/24/2024
• Approved by: [Approver's Name]
• Date: [Approval Date]