On the basis of the below given case study draft a BRD (Business Requirements Document) answering the following headings in detail: 1. Project Name/Description

2. In-Scope & Out-of-Scope

3. Functional Requirements (Explain in detail)

4. Non-Functional Requirements (Explain in detail)

5. Assumptions

6. Constraints Axle Commercial Bank - TFSA Case Study

In January 2019, Axle Commercial Bank had a major re-structure and hired Nagesh Carrey as the new Chief Information Officer (CIO) of the organization to bring the bank into the digital age. His team consisted of four different verticals led by senior Leaders:

• Vice President for Infrastructure and Network Services
• Vice President for Software and Applications
• Vice President for Product Engineering
• Director for Project Management Office (PMO)

One of the first things that worried Nagesh was how subservient Axle's web portal compared to its competitors. He found automation has not been fully utilized and many trivial functions are being done manually. He specifically noticed that one of the most popular financial instruments called Tax Free Savings Account (TFSA) cannot even be purchased through their web portal after 10 years of its introduction. Nagesh has decided to schedule an early morning meeting with Peter Cho, the Director of Project Management Office.

At an 8:00 am meeting between Nagesh and Peter, a decision was made to explore the feasibility of enabling the TFSA function within the Axle's web portal; Peter was tasked with this accountability to see through a successful deployment of the TFSA function from feasibility to implementation. Peter very well understood that this project is the key for his on-going success and building a positive relationship with the new CIO. As soon as he strolled back to his office, he instantaneously placed a call to the head of Product Engineering to gain some insight on the TFSA product. Product engineering team has assigned Mark Marquez as the product owner to assist with this initiative. Mark has produced a brief description on the details of TFSA within the next few days:

In 2008 Canadian Federal budget, Finance Minister Jim Flaherty introduced a creative unique account called "Tax Free Savings Account (TFSA)" which provides Canadian residents 18 years and older a vehicle to invest, where income earned on those contributions is not taxed. This financial instrument is different from other registered vehicles such as "Registered Retirement Savings Plan (RRSP)", where the contributions for the RRSP can be deducted from your taxes. Even though, the contribution to your TFSA does not have a tax shelter, any investment income from TFSA will be tax deductible and withdrawals are tax deductible. Unused TFSA contributions can be carried forward to the future years (including any contribution gap caused by the withdrawal). However, there is a limitation on how much you can contribute to TFSA each year (refer to Appendix A). TFSA assets can generally be transferred to spouse or common-law partner tax-free.

Based on this information, Peter Cho has decided to undertake this project within a year; starting from September 2019 and complete it by August 2020. He has also gone ahead and hired a new Scrum Master, Jane Khan; who recently graduated from Humber College's Project Management Post Graduate program. Jane has a bachelor's degree in Finance from a reputed University in Toronto and specialized in Scrum Methodology by attending the IT Project Management course during her post-graduate program. She is also a certified SAFe Agilist.

After a brief one week on-boarding at Axle, Jane instantly sprang into action setting up meetings with the Product Owner and various stakeholders from multi-disciplinary teams to understand the overall scope, constraints, dependencies and risks at a very high-level.

Based on the conversations, it was identified that all customers who have access to the Axle's web should be able to open a TFSA account with their existing credentials. The system should validate if the client is at-least 18 years old and a Canadian Resident. As soon as the TFSA is approved, the client should be able to see the link for this account under the "Investment" section in their site along with all other investment products that they already own. When a customer clicks on the TFSA link, it should publish the account details in a particular format presented in Appendix B.

Axle is planning to release an update every 4 months with the following vision:

Release 1: Launch of TFSA site with basic functionality; web customers can use their TFSA funds only to invest in Axle's hi-interest savings instrument or Mutual Funds.

Release 2: Web customers will be able to purchase most of Axle's investment products through TFSA funds: Guaranteed Investment Certificate (GIC), Exchange Traded Funds (ETF), Bonds and Stocks

Release 3: Automatic reporting to Canadian Revenue Agency (CRA): At the end of each year, Axle will automatically send each investor record to CRA through an .xml file.

Vice President for Infrastructure & Network Services (Jaiman Victor) raised concerns that the current server that is hosting the web portal may not be able handle the added load once the TFSA product is introduced and hence an additional server needs to be added to the current server farm; he indicated that the challenge is with the processing power and not with the storage capacity. He also indicated that an addition of new server will impact their Disaster Recovery Site situated in Brampton, Ontario and requires a similar upgrade there as well. He also encouraged the project team to stress test the new environment as they are expecting 10,000 customers to open TFSA account in the first year with an annual growth of 5%. Historical information suggests that there is a possibility of up-to 100 users accessing the TFSA link concurrently. Jaiman also confirmed that the existing dedicated "T1" lines between CRA and Axle has adequate bandwidth to handle any additional network transmission. Chief Privacy Officer made a request to ensure that all transmissions are adequately encrypted based on bank's policies and to perform a "penetration testing" to comply with the audit requirements.

A bit overwhelmed with all the information, Jane has decided to reach out to the functional managers to finalize her scrum teams and to embark on the journey.