1. T System.
Business Requirements Document
<Company Name>
T System
Business Requirements
Document
Sample - Business Requirement Document Page 1 of 11

2. T System.
Business Requirements Document
MODIFICATION HISTORY
Version Version Updated By Change History Approved
Date By
Approval/Sign-off
Name Title Company/ Approved
Organisation Date
Sample - Business Requirement Document Page 2 of 11

3. T System.
Business Requirements Document
Table of Contents
1. Introduction and Goals of Business Requirement Document...............................................5
2. Standard Operating Procedures.............................................................................................5
3. Business Overview................................................................................................................6
3.1 Customer Operations.......................................................................................................6
3.2. Summary of Operational Functions for current T System Mobile Internet (1.0)...........7
3.2.1 Current State And The Need For Change...........................................................7
3.2.2 Desired State.......................................................................................................7
4. Operational Fundamentals of T System Mobile Internet (2.0)............................................8
4.1 Mobile banking Locations...............................................................................................8
4.1.1Mobile banking Functions Per Site...........................................................................8
4.2 Master Customer Data................................................................................................8
4.2.1ABDG Personel for Master Customer Data..............................................................9
4.3 User Profile......................................................................................................................9
4.4 View Account...................................................................................................................9
5. Reports...............................................................................................................................10
6. Business Continuity Planning.............................................................................................10
7. Curent T 1.0 Master Customer Data (AS-IF Process).........................................................10
8. Appendix A – To Be Processes Flows.................................................................................11
8.1 Master Customer Data (Note – this is a sample, not the exact follow).........................11
9. Appendix B - ABDG Personal Contact...............................................................................11
Sample - Business Requirement Document Page 3 of 11

4. T System.
Business Requirements Document
Glossory
Abbreviation Defination
Sample - Business Requirement Document Page 4 of 11

5. T System.
Business Requirements Document
1. Introduction and Goals of Business Requirement Document
This Business Requirement document will be the main working document for the
implementation team during the Project.
The goals of this Business Requirement are to provide:
• Details of requirements in DSB application service gateway, software and systems
integration and T solution
• An operational overview for bank staff involved with the project
• Details on Business Processes and Scenarios
The Business Requirments document will be revised as and when required throughout the
implementation phase of the project to reflect changing requirements and agreed solutions. It
will take the form of a controlled document to ensure sign-off and approval/processes are
maintained.
Please refer to Glossory for a list of abbreviations and terminology.
2. Standard Operating Procedures
An overview of the Standard Operating Procedures that will be required for the work that will
be carried out for ABDG Bank are contained in the below diagram.
<Insert diagram similar to the below or alternatively create a table listing the details of all
the SOPs that will be required>
Sample - Business Requirement Document Page 5 of 11

6. T System.
Business Requirements Document
3. Business Overview
3.1 Customer Operations
<This section covers the overview of the Internet mobile business in ABDG> E.g.
DSB operates in the Asia Pacific region through a mobile banking business model for
commercial partners and consumers Residential customers.
On behalf of ABDG, T System provides ABDG mobile internet application to operate for 4
Asian countries (Singapore, Malaysia, Thailand, Hong Kong) to manage the consumer banking for
ABDG customers in Asia Pacific region.
Consumer data bank is hosted in DSB Singapore HQ. This data bank provides the full
consumer data to provide 'one stop' portal to manage all consumers' profiles and transactional
data are managed in this data bank as well.
<Insert the high-level network view of the existing solution> Note: this is not the exact copy.
Use for sample
Sample - Business Requirement Document Page 6 of 11

7. T System.
Business Requirements Document
3.2. Summary of Operational Functions for current T System Mobile Internet (1.0)
The function that the mobile internet service for DSB Bank is
• User Profile
• View account summary
◦ Savings
◦ Currents
• Fund transfer
• own bank acc
• Other ABDG acc
• Add new payee
• Bill Payment
• Transactional Reports?
3.2.1 Current State And The Need For Change
<This section describes why there is a need of change to the existing mobile banking
process> E.g.
ABDG Credit Card department is currently using two different extranet channels for data
consolidation. Of these two, the latter is becoming obsolete. The current platform does no
longer meet the current industry standards in terms of security and robustness.
Enhancements of existing platform are considered too complicated and too expensive due to
the fragmented architecture.
Hence, a decision was taken in March 2010 to build the existing Care business capabilities on
top of T mobile banking platform, enhancing the existing ABDG consumer banking
functionalities. This project is part of ABDG consumer banking strategic intent to provide one
single point of access towards mobile banking channel for corporate and consumers
This is also a strategic controlled step towards a consolidated common Business-to-Business
platform. The financial benefits will be achieved through harmonization and simplification of
processes.
3.2.2 Desired State
The credit card services is incorporated to T solution 2.0 shall be starting Mid May and the
portal shall be available to 4 Asian countries, piloting and deployment from mid august
onwards. Hence, there is a need for the deployment of these services in the region, and the
resources to manage the same.
Sample - Business Requirement Document Page 7 of 11

8. T System.
Business Requirements Document
4. Operational Fundamentals of T System Mobile Internet (2.0)
4.1 Mobile banking Locations
ABDG mobile banking services is provided for 4 Asian countries in Asia Pacific. All
these services are used to enhance consumers' banking behaviour from handling
transactions directly from mobile devices such as PDA, smartphone to DSB properity
ASP solution
• Singapore
• Hong Kong
• Malaysia
• Thailand
4.1.1Mobile banking Functions Per Site
ABDG mobile banking services is managed by T system configuration profile. This is
to control what are the appropriate service available to be implemented for required
sites/country
Country T Mobile Banking Functionalities
Singapore Account Summary
Fund Transfer
Malaysia Account Summary
Bill Payment
4.2 Master Customer Data
The vendor will receive will retrieve the Master Customer data from ABDG ASP
Dragon via Master Database webservice. ABDGl will make the Master information for
new sign- up accounts available to the vendor at least 1 working day.
The Master Customer information will include all mandatory elements for create a
new mobile internet user. The mandatory elements are:
• Unique user Banking ID
• Bank Branch
• Full Name
• Bank Account Number
• Bank Account ID
• Bank Account Priority
• Effective Bank Active Date
• Effective Bank End Date
• Bank Account Status
• Credit Card Number
• Credit Card Type
One user account may contain more than one banking account number. ABDG will
provide which are the banking Ids belong to the desired unique user banking ID.
Sample - Business Requirement Document Page 8 of 11

9. T System.
Business Requirements Document
• Unique user banking ID cannot be duplicated. It is unique for each user sign-
up
• One user banking ID can have more than one banking number under the
same user banking ID
• A bank account number has a set of effective active and end date information
Refer to Appendix B, section 8.1 Master Customer Data for the To-Be process flow.
4.2.1ABDG Personel for Master Customer Data
All master customers records that are viewable to a user will have the Dell Default Contact
details recorded against them. Contact information is found in Appendix B
4.3 User Profile
< Describe the needed information that are displayed and allow user to update their data
online)
• Full Name
• Address
• Telephone (Home)
• Telephone (Office)
• Mobile Number
• Email Address
4.4 View Account
<Describle the purpose of this function and how it can be configured based on user profile
setting> E.g. The account summary page is shown with the following information
• Account Number
• Last Balance
• Last Updated Date for Transaction
User can define up to 3 account summary to be viewed on this page
4.4.1 Exceptions
• If the user is unable to see this page, an error message is prompted.
• Error message is logged into T system log containing the information
• Date of Error
• Unique user banking ID
• Error Type
• Time of Error
• Vendor to submit the daily error report to ABDG IT Support for further action
Refer to Appendix A for the To-Be process flow
Refer to Appendix B for the ABDG contact persons for any exception
Sample - Business Requirement Document Page 9 of 11

10. T System.
Business Requirements Document
5. Reports
<Name of reports to send back to ABDG>?
Refer to Appendix B Reports for the exact format
Report Name Monthly Weekly Daily Sent back T?
6. Business Continuity Planning
To ensure business continuity in the event of a catastrophic system crash, data snapshot will
be stored at the close of business each day.
Last transactional records are maintained up until the system resumes normal operation, at
which point the last records would be manually keyed into ABDG system.
7. Curent T 1.0 Master Customer Data (AS-IF Process)
• ABDG instruct Vendor operations to update new ABDG user accounts list via e-mail and with
excel
attachment
• Vendor IT Operations upload this list into T user administration and maintains intial user
profile setup
• Once profile is setup, vendor sends back the same excel attachement with the profile setups
to ABDG for updating and validation
• When it is validated, DSB is to raise a ticket ot helpdesk with T IT support to activate the
account. The final copy of the spreadsheet is sent out and keep with both ABDG and vendor.
Sample - Business Requirement Document Page 10 of 11

11. T System.
Business Requirements Document
8. Appendix A – To Be Processes Flows
8.1 Master Customer Data (Note – this is a sample, not the exact follow)
9. Appendix B - ABDG Personal Contact
Name Organisation Support Function Email Phone Contact
Joe Xie Consumer Master Customer joe.xie@abdg.com 422761015
Databank Data
Sample - Business Requirement Document Page 11 of 11