Business Requirements Document (BRD)
Table of Contents
- Introduction
- Business Objectives
- Project Scope
- Stakeholder Analysis
- Requirements
- Assumptions
- Constraints
- Risks
- Glossary
- Appendices
- Approval
Introduction
The purpose of this document is to outline the business requirements for "Mike's Fantastic Banking Project," which aims to replace the legacy core banking system of Fantastic Bank with the Temenos Transact R24 core banking system and associated third-party applications.
Business Objectives
- Replace the 40-year-old core banking system programmed in COBOL with Temenos Transact R24.
- Integrate third-party systems: Paymentus for payments and LendingPad for loan origination.
- Complete the project within six months without disrupting services for the bank's 250,000 customers.
- Purge and close accounts with $100 or less, refunding the account holders by check.
- Automate testing using Selenium.
- Ensure the user experience (UX) is designed using only different shades of blue.
Project Scope
In-Scope:
- Replacement of the legacy core banking system with Temenos Transact R24.
- Integration with Paymentus for payments.
- Integration with LendingPad for loan origination.
- Decommissioning of the legacy system.
- Automated testing using Selenium.
- UX design limited to shades of blue.
Out-of-Scope:
- Any enhancements to the Temenos Payments Hub (TPH) and Temenos' LOS.
- Changes unrelated to core banking, payments, or loan origination.
Stakeholder Analysis
Internal Stakeholders:
- Project Sponsor: Mike Meier
- IT Department
- Operations Team
- Customer Service Team
External Stakeholders:
- Temenos representatives
- Paymentus representatives
- LendingPad representatives
- Bank's 250,000 customers
Requirements
Functional Requirements
Requirement ID: FR001
- Description: Replace the legacy core banking system with Temenos Transact R24.
- Priority: High
- Source: Business Objective
Requirement ID: FR002
- Description: Integrate Paymentus for handling payments.
- Priority: High
- Source: Business Objective
Requirement ID: FR003
- Description: Integrate LendingPad for loan origination.
- Priority: High
- Source: Business Objective
Requirement ID: FR004
- Description: Purge and close accounts with $100 or less; issue refunds by check.
- Priority: Medium
- Source: Business Objective
Requirement ID: FR005
- Description: Develop Selenium scripts for automated testing.
- Priority: High
- Source: Business Objective
Non-Functional Requirements
Requirement ID: NFR001
- Description: The project must be completed within six months.
- Priority: High
- Source: Project Constraint
Requirement ID: NFR002
- Description: The transition must not disrupt services for the bank's 250,000 customers.
- Priority: High
- Source: Project Constraint
Requirement ID: NFR003
- Description: The UX should use only different shades of blue.
- Priority: Medium
- Source: Business Objective
Assumptions
- All third-party systems (Paymentus and LendingPad) will be compatible with Temenos Transact R24.
- The necessary resources and personnel will be available to complete the project on time.
Constraints
- The project must be completed within six months.
- No disruption should occur for the bank's 250,000 customers during the migration.
Risks
- Potential compatibility issues between Temenos Transact R24 and third-party systems.
- Risk of project delays due to unforeseen technical challenges.
- Risk of customer dissatisfaction if the migration impacts service quality.
Glossary
- COBOL: A programming language used in the legacy system.
- Temenos Transact R24: The latest version of the core banking system to be implemented.
- Paymentus: A third-party payment system.
- LendingPad: A third-party loan origination system.
- Selenium: A tool for automating web browser testing.
Appendices
- [Appendix A: Detailed Project Timeline]
- [Appendix B: Contact Information for Stakeholders]
Approval
Prepared by: Mike Meier
Email: mikemeier@mad-tech.ai
Date: 02/05/2025
Approved by: [Approver's Name]
Date: [Approval Date]