0% found this document useful (0 votes)
153 views20 pages

FSD Sample02

The document provides functional specifications for an e-statement solution. It describes the purpose, intended audience, project scope, and overall description of the project including user roles. The system will allow management of product types, customer products, statements, users, email campaigns, welcome letters, logs, and security features.

Uploaded by

ZYSHAN
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
153 views20 pages

FSD Sample02

The document provides functional specifications for an e-statement solution. It describes the purpose, intended audience, project scope, and overall description of the project including user roles. The system will allow management of product types, customer products, statements, users, email campaigns, welcome letters, logs, and security features.

Uploaded by

ZYSHAN
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 20

Version

3.0
October 20, 2014

ESTS
e-Statement Solution
e-Statement Solution
Functional Specification Document

Prepared By:

ABC

ABC Solutions
Pakistan
e- Solution for XYZ FSD/3.0

Attention:

This document has a restricted distribution and may be used by Bank recipients only to determine and
evaluate the Requirement Specifications for e-Statements Application. Its contents may not otherwise be
disclosed.

– All rights reserved Page 2 of 20


e- Solution for XYZ FSD/3.0

Revision History
Version Primary Author(s) Description of Version Date Completed

– All rights reserved Page 3 of 20


e- Solution for XYZ FSD/3.0

Table of Contents
Revision History..............................................................................................................................3
Introduction......................................................................................................................................6
Purpose........................................................................................................................................6
Document Conventions...............................................................................................................6
Intended Audience and Reading Suggestions..............................................................................6
Project Scope...............................................................................................................................6
Overall Description..........................................................................................................................7
Project Perspective.......................................................................................................................7
User Roles....................................................................................................................................8
Administrator...........................................................................................................................8
ID Management.......................................................................................................................8
IT .............................................................................................................................................8
Retail Banking Operations.......................................................................................................9
Debit Cards Operations............................................................................................................9
Credit Cards Operations..........................................................................................................9
Operating Environment...............................................................................................................9
Design and Implementation Constraints......................................................................................9
External Interface Requirements...................................................................................................10
User Interfaces...........................................................................................................................10
Hardware Interfaces...................................................................................................................10
Software Interfaces MIS – Enterprise Data Warehouse System............................................10
System Features.............................................................................................................................12
Basic Products...........................................................................................................................12
Product Type Management........................................................................................................12
Customer Products Management...............................................................................................16
Customer Product Frequency Management...............................................................................16
MIS Reports...............................................................................................................................16
Users Management....................................................................................................................16
Bulk Email Campaign Management..........................................................................................17
Campaign Addresses Management........................................................................................17
Bulk Email Reply Tracking...................................................................................................18
Welcome Letter Management....................................................................................................18
Welcome Letter Dispatch Management & Logs.......................................................................18
Welcome Letter Resending........................................................................................................18
Audit Log Management.............................................................................................................18
Security Features.......................................................................................................................19
Nonfunctional Requirements.....................................................................................................20
Performance Requirements....................................................................................................20
Security Requirements...........................................................................................................20
Add Architecture Diagram
Acceptance & Approval................................................................................................................22

– All rights reserved Page 4 of 20


e- Solution for XYZ FSD/3.0

This page is intentionally kept blank.

– All rights reserved Page 5 of 20


e- Solution for XYZ FSD/3.0

Introduction

Purpose
ABC Bank is one of the leading banks in Pakistan which wishes to introduce an enhanced e-
Statement Solution which could allow it to effectively and efficiently create and send e-
Statements of various products to the customers via email.

In order to fulfill this requirement, ABC is proposing a web based state of the art e-Statements
solution which will be a complete e-Statements generation and management platform which will
provide a one window solution for eStatements Generation, eStatements Dispatch, Bounced
Email Tracking and customer communication management. This document provides detailed
functional specifications of application.

Document Conventions
The requirements are documented in the order requested by the client (XYZ). The font used for
this SRS is Garamond. Size of font for the text is 12, for sub headings are 14 and for headings is
16.

Intended Audience and Reading Suggestions


Before reading the document one should be clear in mind that this Functional Specification
document, FSD, covers functional and nonfunctional aspects of the application. This document is
targeted for the project stakeholders, including but not limited to:

 Client
 Lead Software Development.
 Project Manager.
 Software Engineers.
 QA.

The FSD contains contents, which can be read individually or in the order in which they are
given according to the reader’s requirements. Every section in the document is grouped under
headings, which can be referenced directly from the table of contents.

Project Scope
The development of eStatement Application will involve the features that are specifically
mentioned in this document as per XYZ requirements. Any feature or requirement that is not
explicitly mentioned in this document will be considered out of scope.

– All rights reserved Page 6 of 20


e- Solution for XYZ FSD/3.0

Overall Description
Project Perspective
e-Statement application will be a comprehensive web based solution which will provide a single
platform to XYZ for eStatement generation, dispatch, bounced email tracking and customer
communication management in a convenient and secure way. The e-Statement application will
include the following key modules and features:

 Product Type Management


 Customer Products Management
 Customer Product Frequency Management
 MIS Reports
 Bulk Statement Generation
 Statement Re Generation
 Users Management
 Bulk Email Campaign Management
 Welcome Letter Management
 Welcome Letter Dispatch Management & Logs
 Welcome Letter Resending
 Audit Log Management
 Security Features

The complete features are discussed in detail in the following sections.

– All rights reserved Page 7 of 20


e- Solution for XYZ FSD/3.0

User Roles
The eStatement Application will have the following user roles.

Super User

The Super user account will be the main administrative account it has dual password
functionality. It has following rights

 Application Administrators Creation


 High Level Parameter Settings

Application Administrator

Each Business unit has their own administrators. These Administrators IDs will be created by
Super User Account.
Application Administrator has following rights

 Product Type Management


 Customer Products Management
 Customer Product Frequency Management
 Bulk Email Campaign Management
 Role creations
 Assignment of privilege’s to roles
 Users Management
 Assignment of Roles to Users
 ID Management Reports
 Bulk Statement Re-Generation and Sending
 View Bulk Sending Logs
 View MIS Reports

Operating Environment
e-Statement Application will be a browser based web application, it will be easily accessible
through a PC having a core i5 processor or higher with Windows 7 or Higher OS and a modern
web browser (Internet Explorer 7+, Google Chrome 12+ or Mozilla Firefox 3+)

Design and Implementation Constraints


e-Statement Application will be developed by using Rapid Application Development (RAD)
Methodology. e-Statement Application will be designed and implemented on DotNet. By using

– All rights reserved Page 8 of 20


e- Solution for XYZ FSD/3.0

DotNet we will be able to implement the required features in the proposed timeline with ability
for quick future enhancements.

– All rights reserved Page 9 of 20


e- Solution for XYZ FSD/3.0

External Interface Requirements


User Interfaces

e-Statement will be a web based application which will allow the users to interact through a
modern web browser.

Hardware Interfaces
N/A

Software Interfaces

MIS –Enterprise Data Warehouse System


MIS is an enterprise data warehouse system that integrated with XYZ core banking system and
collects all customers’ transactional data through Batch process after execution of daily COB. It
is also used to provide interface for MIS reports to different XYZ departments.

Since all customer and transaction information of all products (SOA, Debit Cards and Credit
cards) is stored in MIS except international Customer Account information so relevant views
will be created on the these customer and transaction tables. (See Annexure A)

Credit Card System


XYZ will provide integration details of Card Database. Required views are enclosed (Annexure
A).

Interface Requirement

XYZ I.T will provide a separate user (Query Only) for e-Statement application connection for
both databases MIS and Card System.

In this user, XYZ team will provide the below mentioned views to provide the information
required for e-statements of (Bank Accounts & Credit Cards).

 Customer’s Account Information (MIS & Card System)


 Customer’s Transactions Information (MIS & Card System)
 E-statement Frequency Information (MIS & Card System)
 Reward Points ( Card System Only)
 Branch Information (MIS Only)

– All rights reserved Page 10 of 20


e- Solution for XYZ FSD/3.0

 Product Information

e-Statements application will use these views to fetch all information to generate eStatements for
Core Banking account (SOA), Debit card customer and credit card customers.

Microsoft Exchange Server

The application will be integrated with Microsoft Exchange Server for sending e-Statement via
Email and monitor e-Statements Inbox for bounced back statements. The Integration with
Exchange Server will be done using SMTP and IMAP Service.

SMS Gate Way Interface

They will be used as SMS Gate way and XYZ will provide details for SMS gateway integration

SSL Implementation
Though it is internal application however XYZ can run it on secure layer(SSL).

– All rights reserved Page 11 of 20


e- Solution for XYZ FSD/3.0

System Features

Basic Products
eStatement Application will cater to e-Statement of 2 basic products which are as under:

 Core Systems (Statement of Accounts)


 Credit Cards

Product Type Management


The business administrator will be able to create and manage multiple product types against
basic products. While defining the product type, the administrator will be able to specify the
following information:

Customer Product Frequency Management


The administrator will be able to manage eStatement frequency against each customer product.
The frequencies available against each basic product type are as follows:

While defining the frequency, the administrator will select the customer and his product and
select the available frequencies for that product. The product frequency information will contain
the following fields:

MIS Reports
The application will use own Reporting Engine for generation of MIS Reports. These reports
will be exportable in Excel format. The following reports will be implemented:

a. Details of all the customer subscribed, details of all the customers Complete data with
- Names
- Account / card numbers
- E mail addresses
- Frequency
- Product type
- Date of sign ups
- CNIC
- Package
b. E-Statement summary report
i. Main summary

– All rights reserved Page 12 of 20


e- Solution for XYZ FSD/3.0

ii. Sent
1. Total Accounts
2. Total email Addresses
3. Total Customers
4. Total Cards
5. Customer/Product Type count
iii. Bounced
c. Card e-Statements summary report
d. Audit trail report- will show details of cycles executed, with dates and staff ID/codes.
e. Bounced emails
i. Customer wise
ii. Reason wise
f. User management (List of user active / Disabled).

Bulk Statement Generation


System will generate statements of all products automatically on assigned interval in secure PDF
format and will also send through email on registered email address.

Statement password will be sent through SMS by using XYZ SMS Gateway.

Statement Re-generation
Statement re-generation will be possible through provided Web based User interface. User will
submit re-generation request of multiple/Single Account and system will re-generate requested
account statement and will send through email.

Password will be sent through SMS by using XYZ SMS Gateway

Users Management
The application will allow the ID management role users to create users, update their profiles and
reset their passwords.

Bulk Email Campaign Management


The authorized users will be able to create and manage bulk email campaigns into the
application. They will be able to specify campaign details and will be able to specify campaign
audience which will be existing subscribed customers.

– All rights reserved Page 13 of 20


e- Solution for XYZ FSD/3.0

Bulk Email Reply Tracking

The application will be able to track email responses received against a particular bulk email.
The responses received will be processed and saved into the database. The authorized users will
be able to view the responses and send reply to customer if required. These responses and replies
will be recorded into the application as conversations.

Welcome Letter Management


The administrator will be able to manage welcome letter as a report. Welcome letter will be
generated on subscription of eStatement..

Welcome Letter Dispatch Management & Logs


Once the application will send the welcome letter as soon as a customer is subscribed for
eStatements, the application will also record the welcome letter sending date and status in logs.

Welcome Letter Resending


The application will allow the administrator or authorized user to resend welcome letter if it is
bounced back. The resending action will also be recorded in logs.

Audit Log Management


The application will include a comprehensive log management module which will automatically
log all activities into the system which will include as following

 Production Management
 E-Statement Generation
 E-Statement Dispatch
 E-Statement Resend
 Welcome Letter Dispatch
 Welcome Letter Resend
 User Management Logs
 User Access Logs
 Bounced Back Email Logs
 E-statement re-generation Logs

– All rights reserved Page 14 of 20


e- Solution for XYZ FSD/3.0

Security Features
In order to ensure maximum security, the following security features will be put in place:
 Super User Account has dual password functionality.
 Password complexity – The user password should be at least 7 characters long and should
contain at least 1 number and 1 special character.
 Account lockout after 3 invalid login attempts - User’s account will be automatically
locked if 3 incorrect login attempts are made.
 User can reset his password by using forget password option. System will resend his
password on his registered email address.
 Restrict multiple logins – User will not be able to login from multiple locations at the
same time.
 e-Statement will be generated as PDF file which is password protected. Password will be
randomly generated and communicated to customers thru SMS on their registered
telephone no.
 Passwords will be kept in database in encrypted format for the audit log purpose,
however, if customer complains for SMS not received. User department has to re-
generate the statement for new password communication.

– All rights reserved Page 15 of 20


e- Solution for XYZ FSD/3.0

Nonfunctional Requirements
Performance Requirements

EStatement application shall run on a PC with a modern browser and the application response
time should not less than XYZ standard.

Security Requirements

EStatement application should be accessible only to authorized users. Every user should be able
to access only those features that are allowed by their role.

Hardware Requirement

Strong server machine at least have 6 core Intel CPU and 64 GB RAM.

Software Requirement

 Windows 2008 Server


 IIS7
 Microsoft .net frame work 4.0 and above
 SQL server 2008 or above

– All rights reserved Page 16 of 20


e- Solution for XYZ FSD/3.0

Process Flow Diagram

– All rights reserved Page 17 of 20


e- Solution for XYZ FSD/3.0

Annexure A
Views for Account Statement
 Account Profile

Field Description Field Name Data Type


Account #
Title of account
Title of Account Prefix
Address
Nature of Account/Product
ID
Currency
Date of Account Opening
Branch ID
Branch Name
E-Statement Registration
Date
Email Address
Cell #

Query Criteria: Product_id, Statement frequency (Weekly, Monthly, Half Yearly, Yearly)
and e-statement enabled = “YES”
 Account Header

Field Description Field Name Data Type


Account #
Opening Balance
Closing Balance

Query Criteria: Account #, Start Date and End Date

 Account Transactions

Field Description Field Name Data Type


Account #
Transaction Date
Value Date
Cheque #/ Instrument #
Description
Amount
Nature of Transaction
(Debit/Credit)
Query Criteria: Account #, Start Date and End Date

– All rights reserved Page 18 of 20


e- Solution for XYZ FSD/3.0

Views for Card Statement

 Account Profile

Field Description Field Name Data Type


Card Account #
Title of account
Title of Account Prefix
Address
Product ID
E-Statement Registration
Date
Email Address
Cell #

 Card Statement Header

Field Description Field Name Data Type


Card Account #
Statement Date
Current Balance
Minimum Payment Amount
Payment Due Date
Credit Limit
Available Limit
Available Cash Limit
Reward Points Cary Forward
Reward Points Earned
Reward Points Adjustment
Reward Points Expired
Reward Points Redeemed
Reward Points Available

 Card Statement Details

Field Description Field Name Data Type


Card Account #
Transaction Date
Posting Date
Description
Amount in US$
Amount

– All rights reserved Page 19 of 20


e- Solution for XYZ FSD/3.0

Nature of Transaction
(Debit/Credit)

– All rights reserved Page 20 of 20

You might also like