Business Requirements Document (BRD)
Table of Contents
- Introduction
- Business Objectives
- Project Scope
- Stakeholder Analysis
- Requirements
- Assumptions
- Constraints
- Risks
- Glossary
- Appendices
- Approval
Introduction
This document outlines the business requirements for the implementation of Temenos' Transact core banking product to replace Test Republic Bank's legacy mainframe system. The legacy system is over 30 years old and Cobol-based, holding account information for 100,000 retail checking and savings accounts, alongside other account types. The transition must ensure no disruption to client access and go live on New Year's Eve, 2025.
Business Objectives
- Migrate all accounts from the legacy mainframe system to Temenos' Transact SaaS solution.
- Ensure continuous client access to their accounts during the transition.
- Achieve a seamless go-live date of New Year's Eve, 2025, with all functionalities operational.
- Integrate Transact with third-party systems Paymentus and LendingPad, and implement Selenium for automated testing.
- Implement a blue-themed user experience (UX).
Project Scope
In-Scope:
- Migration of all account types from the legacy system to Transact.
- Continuous client access during the transition.
- Integration with Paymentus and LendingPad.
- Automated testing via Selenium.
- Blue-themed UX design.
- Purging and closing accounts with $100 or less, with refunds issued by check.
Out-of-Scope:
- Any enhancements or custom developments outside standard Transact functionalities.
- Non-retail banking products and services not currently managed by the legacy system.
Stakeholder Analysis
Internal Stakeholders:
- Project Manager
- IT Department
- Customer Service Team
- Compliance Team
- Marketing Team
External Stakeholders:
- Temenos (Transact Vendor)
- Paymentus (Payments Software Vendor)
- LendingPad (Loan Origination System Vendor)
- Clients of Test Republic Bank
Requirements
Functional Requirements
FR-001: Migrate all retail checking, savings, CDs, Money Market accounts, mortgages, credit cards, car loans, and personal loans to Transact.
- Priority: High
- Source: Business Need
FR-002: Ensure continuous client access to accounts during the transition.
- Priority: High
- Source: Business Need
FR-003: Purge accounts with $100 or less, close them, and issue refunds by check.
- Priority: Medium
- Source: Business Requirement
FR-004: Integrate Transact with Paymentus for payment processing.
- Priority: High
- Source: Business Requirement
FR-005: Integrate Transact with LendingPad for loan origination.
- Priority: High
- Source: Business Requirement
FR-006: Implement Selenium for automated testing.
- Priority: Medium
- Source: Business Requirement
Non-Functional Requirements
NFR-001: Transact must provide 24/7 availability.
- Priority: High
- Source: Business Need
NFR-002: The system must ensure data integrity and security during the migration.
- Priority: High
- Source: Business Need
NFR-003: The UX must use only different shades of blue.
- Priority: Low
- Source: Branding Requirement
Assumptions
- All required data for migration is available and accurate.
- Temenos' Transact product supports integration with Paymentus and LendingPad.
- Adequate resources (time, budget, personnel) are available for the project.
Constraints
- Go-live date is fixed to New Year's Eve, 2025.
- Legacy system data must be accurately and completely migrated to avoid any data loss.
- UX design constraints to only use shades of blue.
Risks
- Potential data loss during migration.
- Disruption in client access during the transition.
- Delays in integration with third-party systems.
- Insufficient testing leading to post-implementation issues.
Glossary
- Transact: Temenos' core banking SaaS solution.
- Paymentus: Third-party payment processing software.
- LendingPad: Loan Origination System.
- Selenium: Automated testing software.
Appendices
- Detailed project timelines
- Detailed integration plans with Paymentus and LendingPad
Approval