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 document outlines the business requirements for the implementation of Temenos' Transact core banking product at Test Republic Bank, replacing our legacy mainframe banking system. The purpose is to ensure a smooth transition with no disruption to client services.

Business Objectives

• Replace the legacy COBOL-based mainframe banking system with Temenos' Transact cloud-based SaaS solution.
• Ensure continuous access to accounts for clients during the transition.
• Go live with Temenos' Transact on New Year's Eve, 2024, with full functionality.

Project Scope

In-Scope:

• Migration of all account data from the legacy system to Temenos' Transact.
• Integration of Temenos' Transact with third-party systems (Paymentus and LendingPad).
• Automated testing using Selenium.
• UX design with shades of blue only.

Out-of-Scope:

• Changes to third-party systems (Paymentus and LendingPad) outside of integration needs.
• Any new functionality development in the legacy system.

Stakeholder Analysis

Internal Stakeholders:

• Project Sponsor: John Doe, CTO
• Project Manager: Jane Smith
• IT Department: Responsible for technical implementation
• Operations Team: Responsible for account management and customer service
• Marketing Team: Responsible for customer communications

External Stakeholders:

• Temenos: Vendor of Transact
• Paymentus: Third-party payment software provider
• LendingPad: LOS provider
• Clients: End-users of the banking services

Requirements

Functional Requirements

1. Requirement ID: FR-001

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

2. Requirement ID: FR-002

   • Description: Ensure continuous access to accounts for clients during migration.
   • Priority: High
   • Source: Business Need

3. Requirement ID: FR-003

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

4. Requirement ID: FR-004

   • Description: Integrate Temenos' Transact with Paymentus and LendingPad.
   • Priority: High
   • Source: Integration Requirement

5. Requirement ID: FR-005

   • Description: Implement Selenium code for automated testing.
   • Priority: Medium
   • Source: Testing Requirement

Non-Functional Requirements

1. Requirement ID: NFR-001

   • Description: Ensure the UX uses only shades of blue.
   • Priority: Low
   • Source: UX Design Guideline

2. Requirement ID: NFR-002

   • Description: System must go live on New Year's Eve, 2024.
   • Priority: High
   • Source: Project Timeline

Assumptions

• All necessary data for migration is accurately captured and available.
• Third-party vendors (Paymentus and LendingPad) will cooperate and provide necessary support for integration.
• Adequate resources (human and technical) are allocated to the project.

Constraints

• Legacy system is COBOL-based and over 30 years old, which may present technical challenges.
• Project timeline is fixed with a go-live date on New Year's Eve, 2024.

Risks

• Risk: Data migration issues could disrupt client access to accounts.

  • Mitigation: Conduct thorough testing and validation phases.

• Risk: Integration with third-party systems may face unforeseen technical challenges.

  • Mitigation: Early engagement with vendors and contingency planning.

Glossary

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

Appendices

• Project Plan
• Data Migration Strategy
• Testing Plan

Approval

• Prepared by: Mike Meier

• Email: mikemeier@mad-tech.ai

• Date: 10/10/2024

• Approved by: [Approver's Name]

• Date: [Approval Date]