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 at Test Republic Bank. The project aims to migrate from the legacy mainframe banking system to a modern, cloud-based SaaS solution without disrupting client access to accounts.

Business Objectives

• Implement Temenos' Transact core banking product.
• Ensure seamless migration from the legacy mainframe system to the cloud-based solution.
• Maintain uninterrupted access to accounts for clients during the transition.
• Achieve a go-live date of New Year's Eve, 2024.

Project Scope

In-Scope:

• Migration of all account information from the legacy system to Temenos' Transact.
• Integration with third-party payments software from Paymentus.
• Integration with the Loan Origination System (LOS) from LendingPad.
• Development of Selenium code for automated testing.
• User Interface (UI) design using different shades of blue.

Out-of-Scope:

• Development of new features not included in Temenos' Transact product.
• Migration of accounts with $100 or less (these will be closed and refunded).

Stakeholder Analysis

Internal Stakeholders:

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

External Stakeholders:

• Temenos (Vendor)
• Paymentus (Third-party payments software)
• LendingPad (Loan Origination System)
• Clients of Test Republic Bank

Requirements

Functional Requirements

1. Requirement ID: FR-01

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

2. Requirement ID: FR-02

   • Description: Ensure uninterrupted access to accounts during the transition.
   • Priority: High
   • Source: Business Need

3. Requirement ID: FR-03

• Description: Close accounts with $100 or less and refund the amount by check.
• Priority: Medium
• Source: Business Need

4. Requirement ID: FR-04

   • Description: Integrate Temenos' Transact with Paymentus.
   • Priority: High
   • Source: Business Need

5. Requirement ID: FR-05

   • Description: Integrate Temenos' Transact with LendingPad.
   • Priority: High
   • Source: Business Need

Non-Functional Requirements

1. Requirement ID: NFR-01

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

2. Requirement ID: NFR-02

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

3. Requirement ID: NFR-03

• Description: Ensure the system is fully operational by New Year's Eve, 2024.
• Priority: High
• Source: Project Timeline

Assumptions

• Data migration tools and processes will be effective and reliable.
• Temenos' Transact will support all required functionalities.
• Third-party integrations (Paymentus and LendingPad) will work seamlessly.

Constraints

• The legacy system is over 30 years old and Cobol-based.
• Accounts must be accessible at all times during the transition.
• The project must be completed by New Year's Eve, 2024.

Risks

• Data migration errors leading to account discrepancies.
• Integration issues with third-party systems.
• Potential downtime during the transition period.

Glossary

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

Appendices

• [A] Detailed Project Plan
• [B] Communication Plan
• [C] Risk Management Plan

Approval

• Prepared by: Mike Meier
• Date: 10/21/2024
• Approved by: [Approver's Name]
• Date: [Approval Date]