Problem Statement

A bank encompasses several branches and each branch further has many
customers who hold one or more accounts in that branch. Bank offer five types
of deposit accounts namely Savings, Current, Fixed deposit, Joint, Minor. Any
person who holds an account has either of these accounts. Any person if wants
to become a new customer to the bank also has to choose among these types.
New customer to the bank can either open an individual account, a joint
account or a minor account (in case the applicant is under 18 years of age) as
per his/her wish.

Every savings bank account whether minor/joint or individual has very basic
features of cash deposit and cash withdrawal. There is no restriction on the
number and the amount of deposits, however a mandatory uniquely identified
PAN number is required for doing cash transactions exceeding Rs.49,999. The
bank pays an interest annually on the savings lying in the savings bank account.
It also provides the facility of fund transfer through which the money from one
customer’s account is transferred to other account. The money transfer can be
done within the same bank or with the account holder of any different bank
however, transferring money to another bank’s account holder charges some
minor penalty.

Current bank account is another type of bank account having its own distinct
features that are managed differently. It is mainly opened by businessmen to
carry out their business deals promptly and smoothly. No restrictions are made
on the number and the withdrawals as long as the account holder has funds in
his/her account. Bank pays no interest on the funds kept in the current
account.

In fixed deposit bank accounts, whole deposit is made at once and it lasts for
15 days to 10 years with high rates of interests. No withdrawals are allowed
however, the bank allows the customer to close the account before maturity in
the case of emergency but with a certain deduction in rate of interest. The
fixed deposit can be renewed after its maturity.

All these bank details and records can’t be managed manually. Therefore, a
need for software is realized that can manage all the details at both customer
and bank authorities’ side. The main aim of the software is to automate all the
functioning of bank both at the customer’s and bank authorities’ side. Thus,
Banking Management System is introduced to resolve this issue. Two views will
be managed having their own different functioning; one for the customer and
other one for the bank authorities.
Among the bank authorities, different persons will manage data and records
for different bank related works with each person having a different view of
the bank database. For each work, the bank has different manager who has
access only to the details that are related to his section of work. The bank
manager has all the details and has access to all the data and records managed
by different section managers.

For every cash deposit and cash withdrawal made by the customer holding
savings bank account, the bank authority respective to this section will update
the bank database and the customer’s account database by entering all the
transaction details (customer name, account number, phone number,
deposited/withdrawal amount and PAN number in case of transaction is more
than Rs.49,999). All these type of bank transactions details get updated in bank
database both for the customer and bank authorities and can be found in the
“Account Details” section of the database for that particular account. All the
details related to the transaction are automatically updated to the bank’s
database with the help of account number.

For fixed deposit account, the bank offers a rate of interest on every fixed
deposit made by the customer and the rate of interest varies accordingly with
the time period for which FD is made. If the fixed deposit account is opened
from the main account balance, the amount is deducted from the bank
balance and new fixed deposit account is opened for every fixed deposit made
by the customer. The details of amount deduction get updated in “account
details” section of database of particular account, and the FD details are
updated in “FIXED DEPOSIT” section of bank database by bank authority
seeking this section by giving all the details of customer and fixed deposit
request made by that customer.

And the software will enable the bank authorities to update/modify customer
details or information relates to customer account whenever any customer
requests for the same. The customer has to fill KYC form of the bank along with
all the ID proofs and other related documents to provide the bank with all
details if he wants to make modifications, bank authorities will then verify the
documents and update the desirable changes to the “customer’s details”
section of the bank database.

1 Introduction
1.1 Purpose

The main purpose of this software is to simplify the tedious task of banking by
providing this service in a user-friendly environment. It also aims at increasing
the efficiency and reducing the drawbacks of existing manual banking process,
thus making it more convenient for the customers to do banking as when they
require.
This project is supported by a well-designed DBMS in which customers account
information is integrated together. A friendly UI is also provided so that the
requests made by the user give correct results by accessing the information
stored in the database.

1.2 Scope

This software allows the users to apply for new account and to update the
previous account. It gives them the facility to deposit money in the account or
withdrawal money from the account. It also gives the facility to apply for loan.

1.3 Definitions

 BMS – Banking Management System

 UI – User Interface
 DBMS – Database Management System

4 DATA FLOW DIAGRAM

4.1 DFD Level 0
 EMI’S

ACCOUNT OPEN/UPDATE REQUEST EMPLOYEE

MONEY DEPOSIT/WITHDRAWL
CUSTOMER LOAN APPLICATION

DOCUMENTS

DETAILS

Verification

ASK DETAILS

ASK DOCUMENTS

RESPONSE TO LOAN
BANKIN
MONEY WITHDRAWL/RECEIVE RECIPT Request to
G
RESPONSE TO REQUEST SYSTEM verification

LOAN REMAINDER

Retrieve info

Update info

BANK DATABASE

4.2 DFD Level 1

TRANSACTION
UPADTE BALANCE BANK
MANAGEMENT RETRIVE BALANCE DATABASE
SYSTEM
 RETRIEVE OLD DATA

UPDATE OLD DATA

ACCOUNT OPEN CUSTOMER RESPONSE TO

MANAGEMENT VERIFICATION

WITHDRAW\ ACCOUNT DETAILS SYSTEM

DEPOSIT MONEY

ACCOUNT DOCUMENT ACCOUNT DETAIL

WITHDRAW\ DOCUMENTATION

DEPOSIT RECEIPT

ASK DOCUMENTS
CUSTOMER ASK ACCOUNT DETAILS

RESPONSE TO OPEN\UPDATE REQUEST

LOAN DETAILS/ DOCUMENTS

EMPLOYEE
VERIFICATION

EMI’S

LOAN DETAILS RESPONSE TO

LOAN
LOAN DOCUMENTS VERIFICATION
MANAGEMENT
LOAN APPLICATION
SYSTEM

LOAN REMAINDER RETRIEVE LOAN SUMMARY

ASK LOAN DOCUMENTS

ASK LOAN DETAILS UPDATE LOAN SUMMARY

RESPONSE TO LOAN REQUEST

1.4 OVERVIEW
The rest of the documents deals with all the main features of this software. It
not only describes various functions but also gives details about how these
functions are related to each other. Apart from the data flow diagrams the
document also contains cost estimates for developing this system. Various
risks associated with the system have also been mentioned along with the
ways to mitigate them.

The timeline chart describing how the entire project was scheduled has been
attached followed by the architectural design of the software. At the end a
pseudo code for the customer management module has been provided. A flow
graph has been generated corresponding to this module, cyclomatic
complexity has been computed and test cases that were used to test the
system have also been mentioned.

1.5 process model

We choose waterfall model because of the following reasons:

 It is respectively simple and easier to understand approach as compared
to other models
 The requirements are well stated and understood before in hand.
 In this model we have to complete one stage before proceeding to next.
So, we have clearly defined stages and well understood milestones.
 The advancement in program does not need to be checked upon by the
customer during the process. So this model does not create problem.
 The requirements are fixed and work can proceed to completion in a
linear manner.
 The waterfall model provides a linear approach.

2. SOFTWARE REQUIREMENT SPECIFICATION

2.1 Overall Description
2.1.1 Product perspective
The manual banking system suffers from the following drawbacks:
  The existing system involves a lot of paper work and manual
calculation. This has led to inconsistency and inaccuracy in the
maintenance of data.
 The data which is stored on the paper only, may be lost, stolen or
destroyed due to natural calamity like fire and water.
 The existing system is sluggish and time-consuming causing
inconvenience to customers and the banking staff.
 Since the number of customers have drastically increased therefore
maintaining and retrieving detailed records of the customer is
extremely difficult.
 A bank has many branches in the country, an absence of a link
between these branches lead to lack of coordination and
communication.

Hence the banking management system is proposed with the following

product perspective:
 The computerization of the banking system will be reducing a lot of
paperwork and hence the load on the bank administrative staff.
 The machine performs all calculations. Hence chances of the error are
null.
 The customer, balance details can easily be retrieved and any
required addition, deletion or updating can be performed.
 The system provides for user-ID validation, hence unauthorized
access is prevented.

2.1.2 Product functions

The “BMS” software is an independent web-based application. There are

various user interfaces related with this software. These interfaces help the
user to interact with the software and provide the necessary information for
online ticket reservation.
The entire functionality of this software can be subdivided into fields/modules.
The names of the fields involved in the banking management system are –
1. CUSTOMER MANAGEMENT
2. LOAN SYSTEM
3. TRANSACTION SYSTEM

MODULE 1: CUSTOMER MANAGEMENT

Using this module, the user first provide his details like his name, father name,
address, phone no., email etc. and can open a new account or can update an
existing account.
MODULE 2: LOAN SYSTEM
This module is for customer to apply for loan by providing required documents
and details like time period of loan, amount of loan and get the detailed
description of EMIs.
MODULE 3: TRANSACTION SYSTEM
This module allows the customers to deposit and withdrawal money from their
account using some private info like signature, OTP.

Various interfaces involved in BMS have been designed and implemented using
C++. All the information about customer is maintained in C++ files which act as
databases for the software.

2.1.3 User characteristics

. The user of the system should be comfortable working with English language.
. The user must have a basic knowledge of computers and internet.

2.1.4 General constraint

The database of the software is not accessible to every user of the software.
Making changes in the database requires permissions that have been given to
certain specific individuals.

2.1.5 Assumptions and Dependencies

The BMS is assumed to be compatible with the computer systems on which it

has been loaded for customer use.

2.1.6 User Classes and Characteristics

BMS caters to a diverse range of users with varying roles and

responsibilities, including:
• Bank Staff: This class includes tellers, loan officers, customer
service representatives, branch managers, and executives. They
need different levels of system access to perform tasks related
to customer accounts, transactions, approvals, and auditing.
Each staff member has specific roles within the system, such as
account creation, transaction processing, loan origination, and
account management.
• Customers: The bank's clients represent a vital user class. They
require access to their accounts, transaction history, and the ability
to make transactions online, such as deposits, withdrawals,
transfers, and bill payments. Customers must have secure and
easy-to-use interfaces for their banking needs.
• Administrators: Administrators oversee the system's
configuration and maintenance. They manage user access levels,
security protocols, system updates, and ensure overall system
health. Their responsibilities include system setup,
troubleshooting, and managing software updates.
• Auditors: Auditors represent another crucial user class. They
review and monitor financial transactions for compliance and
security, ensuring that the bank operates within legal and
regulatory frameworks. Auditors have access to advanced
auditing tools and reports.
2.1.7 Operating Environment

The Banking Management System is designed to operate efficiently within a

Windows-based environment, ensuring compatibility with a wide range of
Windows operating systems, including Windows 7 and subsequent versions.
The system can be run on standard desktop computers or servers, depending on
the bank's requirements. It is expected to be hosted on a dedicated server within
the bank's premises and accessed through a secure network to maintain the
highest level of data security.

2.2 Data Dictionary

The data dictionary, or Meta data repository, as defined in the IBM Dictionary
of Computing, is a “centralized repository of information about data such as
meaning, relationships to other data, origin, usage, and format.”
The term may have one of several closely related meanings pertaining to
databases and database management systems (DBMS). A document describing
a database or collection of databases, an integral component of a database
management systems (DBMS) that is required to determine its structure, and a
piece of middleware that extends or supplants the native data dictionary of a
database management system (DBMS).
Our banking system dictionary can be of the following type.
Data Description
Documents Account documents | Loan
documents
Details Account details | Loan details
Account documents ID Proof + Residence Proof + Date of
Birth Proof
Loan documents ID Proof + Residence Proof + Birth
Proof + Salary slip + PAN Card + Loan
application
Account details Name + Address + Phone number +
Account number + Signature
Loan details Loan time period + Loan amount +
Loan type
Name First name + Middle name + Last
name
Account number Digit + Digit + Digit + Digit + Digit +
Digit
Deposit receipt Date of deposit + Amount deposited
Address House no. + Village name + State
name + PIN code
Response Approval | Rejection
Loan reminder Reminder message + Last date to pay
EMI
2.3 Software Interface

The BMS interfaces with several key software components to deliver its
functionality, including:
 • Database Management System: BMS connects to a robust and
secure database management system, such as Oracle, MySQL, or
SQL Server, to store and retrieve customer data, transaction
records, and system logs. This integration ensures data integrity,
reliability, and accessibility.
• Web Services: To facilitate online banking, BMS interfaces with
web services for customer account access and transaction
processing. This includes features like online account
management, fund transfers, and account statements. Web
services allow customers to interact with the bank 24/7 from
various devices, including web browsers and mobile applications.
• Payment Gateways: The system integrates with payment
gateways to enable electronic fund transfers, online payment
processing, and integration with external financial networks like
SWIFT and ACH.
Third-Party APIs: BMS can incorporate third-party APIs for services such as
credit scoring, identity verification, and payment processing, enhancing its
capabilities and extending the range of services provided to customers.

2.4 Hardware Requirements

The Banking Management System requires specific hardware resources to

operate effectively. The following hardware requirements should be met for
optimal system performance:
• CPU: An Intel Core i5 or equivalent processor is
recommended to handle the system's computational
demands efficiently.
• RAM: A minimum of 8 GB of RAM is necessary to ensure
smooth operation when handling multiple users and large
datasets.
• Storage: The system should be equipped with a minimum of
500 GB of SSD storage, ensuring fast data retrieval and ample
space for logs and backups.
• Network: A high-speed and stable internet connection is
essential for seamless access to web-based components, secure
data transfers, and communication with external financial
networks.
• Security: Robust security measures, including firewall
 protection and antivirus software, should be in place to
safeguard the system from potential threats, ensuring data
integrity and privacy.

2.5 Functionalities

The Banking Management System provides a wide array of functionalities

to meet the dynamic needs of the banking industry. Key functionalities
include:
• Customer Account Management: BMS enables bank staff to
create, modify, and close customer accounts with comprehensive
customer profiles that include personal information, identification
documents, and account preferences.
• Transaction Processing: The system supports various types of
transactions, including deposits, withdrawals, transfers, bill
payments, and check clearances. Real-time transaction tracking
and confirmation features enhance customer and staff
experience.
• Loan Management: BMS facilitates the origination, approval,
and tracking of loans. This includes comprehensive loan
application processing, risk assessment, and loan
documentation.
• Online Banking: The system provides customers with 24/7 access
to their accounts through secure online banking interfaces. This
includes account balances, transaction history, electronic fund
transfers, and bill payments. Customers can also apply for loans
and set up automated transfers.
• Reporting and Auditing: BMS generates a wide variety of reports
for bank staff and auditors, offering insights into customer
account activities, financial transactions, and system
performance. It also supports auditing and compliance reporting
to meet regulatory requirements.
• Security: The system implements robust security measures,
including user authentication, encryption of sensitive data,
and access control to safeguard customer information and
financial data.
• Notifications: BMS sends notifications to customers for transaction
alerts, account updates, and promotional messages through
various communication channels, including email and SMS.
 • Customer Support: The system integrates a customer support
portal, allowing customers to submit inquiries, raise issues, and
track their resolution status. Bank staff can access customer
support tickets and prioritize service requests.

3 Project Management
3.1 Cost Estimations
3.1.1 Functional Point Estimation
S.no QUESTIONS GRADE
. VALUE
1 Does the system require reliable backup and recovery? 5
2 Are specialized data communications required to transfer 3
information to or from the application?
3 Are there distributed processing functions? 3
4 Is performance critical? 0
5 Will the system run in an existing, heavily utilized 5
operational environment?
6 Does the system require on-line data entry? 5
7 Does the on-line data entry require the input transaction 5
to be built over multiple screens or operations?
8 Are the ILFs update online? 5
9 Are the inputs, outputs, files, or inquiries complex? 2
10 Is the internal processing complex? 2
11 Is the code designed to be reusable? 3
12 Are conversions and installations included in the design? 0
13 Is the system designed for multiple installations in 5
different organizations?
14 Is the application design to facilitate change and for ease 5
of use by the user?

3.2 Functional Requirements

A. User Authentication and Authorization :

• The BMS allows new users to register and create accounts.

• Login: Users should be able to login using username and password.
• Roles: Different user roles should have different levels of access and
privileges.
B. Account Management :

• The BMS allows customers to open all types of accounts like

savings, fixed deposit, etc.
• Account holders will be able to view their transaction history
and their available balance.
• They will be able to transfer funds between their own
accounts or to others accounts.

C. Loan Management :

• Customers should be able to apply for loans and view their loan status.
• The system should calculate loan interest rates and provide repayment
schedules.
• Loan officers should be able to review and approve loan applications.

D. Customer Support :

• Users should be able to contact customer support through the

system, including email or chat.
• Customer support agents should have access to customer data to
provide assistance.

E. Account Statements and Reports :

• Account holders should be able to generate and download account

statements.
• Managers should have access to various reports, such as
daily transaction summaries, account balances, and audit
logs.

F. Online Banking for Mobile Devices :

• The system should be accessible via web browsers and mobile

applications.
• It should provide a user-friendly interface for mobile users.
G. Automatic Alerts for Unusual Activities :

• The system should automatically detect and alert users to

unusual or suspicious account activities, such as large
transactions from new locations.

3.3 Technical Issues

• Database: The Banking Management system will use the MySQL

Database, which is open source and free to use.
• Operating System: The Development environment can be Windows 10.

3.4 Non-Functional Requirements

A. Security :

• The system should implement robust security measures

to protect against unauthorized access, data breaches,
and fraud.
• It should use encryption for data transmission and storage.
• Access control should be granular, and data should be
protected against SQL injection and other common
vulnerabilities.

B. Performance :

• The system should provide fast response times for common

operations (e.g., account balance inquiries, funds transfers).
• It should be able to handle a high number of concurrent users
and transactions during peak times.
• Response times should remain within acceptable limits even
during periods of heavy usage.
 C. Scalability :

• The system should be scalable to accommodate an increasing

number of users, accounts, and transactions.
• It should allow for the addition of new servers or resources as the
system grows.

D. Reliability :

• The system should have a high level of availability, with minimal

downtime for maintenance or upgrades.
• It should have a mechanism to ensure uninterrupted service in
case of hardware or software failures.

E. Recovery and Backup :

• The system should have a robust data backup and recovery

strategy to prevent data loss in case of system failures.
• Regular backups should be performed and tested for reliability.

F. Compliance :

• The system should adhere to relevant banking and financial

industry regulations, including Know Your Customer (KYC) and
Anti-Money Laundering (AML) requirements.
• It should comply with data protection and privacy laws, such as
GDPR or HIPAA, as applicable.

G. Usability :

• The user interface should be intuitive and user-friendly,

catering to users of varying technical abilities.
• The system should be accessible to individuals with disabilities
and comply with accessibility standards (e.g., WCAG).

H. Load Testing and Performance Monitoring :

• The system should be subject to load testing to ensure it can

 handle expected levels of usage.
• Continuous performance monitoring should be in place to
detect and address performance bottlenecks.

5 Use Case Diagrams

6 STATE DIAGRAM
7 Entity-Relationship Diagram (ERD)
Entity-Relationship Diagram Overview:

The ERD illustrates the primary entities, attributes, and relationships in the
Banking
Management System:

1. Entities:

a. Customer
- Customer ID (Primary Key)
- First Name
- Middle Name
- Last Name
- Date of Birth
- Gender
- Email
- Contact
- Permanent Account Number (PAN)
- Nationality
- Salary
- Gender
- Address

b. Account
- Account No (Primary Key)
- Customer ID (Foreign Key)
- Account Type (e.g., Savings, Checking)
- Balance
- Interest Rate
- Date Created
- Interest ID
- Interest Amount

c. Transaction
- Transaction ID (Primary Key)
- Account No (Foreign Key)
- Transaction Type (e.g., Deposit, Withdrawal, Transfer)
- Amount
- Transaction Date and Time
- Total Balance
d. Deposit Account
- Deposit Account No (Primary Key)
- Account No
- Closure type
- Interest ID
- Initial Amount
- Customer ID
- Deposit Account Type
- Interested Amount
- Current Balance
- Duration
- Interest Rate
- Open Date
- Close Date
- Days

e. Officer
- Employer ID (Primary Key)
- Username
- Password
- Email
- Nationality
- Salary
- Address
- Gender
- Contact
- Date of Birth
- First Name
- Middle Name
- Last Name

f. Manager
- Employer ID (Primary Key)
- Username
- Password
- Email
- Nationality
- Salary
- Address
- Gender
 - Contact
- Date of Birth
- First Name
- Middle Name
- Last Name

g. Interest
- Interest ID (Primary Key)
- Savings Interest
- Loan Interest
- RD Interest
- FD Interest
- Current Interest

h. Loan Account
- Account No (Primary Key)
- Loan ID
- Loan Type
- Date of Loan
- Duration
- Total Amount
- Remaining Amount
- Status
- Description
- Interest
8 Future Scope :

The future scope of a Banking Management System includes:

1. Digital Transformation: Banks will continue to invest in digital

technologies to improve customer experiences, streamline
operations, and enhance security.

2. Artificial Intelligence: AI will play a crucial role in customer

service, fraud detection, and data analysis for personalized
financial solutions.

3. Blockchain: Blockchain technology can enhance security,

transparency, and efficiency in various banking processes, including
cross-border payments and identity verification.

4. Open Banking: Open banking regulations will promote collaboration

between banks and fintech companies, offering customers more
choices and personalized financial services.

5. Cybersecurity: With the increasing digitization of banking,

cybersecurity will remain a top priority to protect customer data
and financial assets.

6. Mobile Banking: Mobile apps will continue to evolve, providing

more features for managing accounts, making transactions, and
accessing financial advice.

7. Personal Finance Management: Banking systems may integrate

advanced tools to help customers manage their finances, make
informed decisions, and save money.

8. Regulatory Compliance: Banks will need to adapt to

evolving regulatory requirements, such as data privacy and
anti-money laundering regulations.

9. Sustainability and ESG: Banks will focus on environmental, social,

and governance (ESG) criteria in their operations and investment
decisions.
10. Financial Inclusion: Banking systems will work towards greater
financial inclusion, extending services to under-served populations and
remote areas.

11. Data Analytics: Advanced data analytics will enable banks to

gain insights into customer behaviour and preferences, allowing
for more targeted services.

These trends represent the evolving landscape of banking management

systems, driven by technological advancements, regulatory changes, and
shifting customer demands.
9 Conclusion :

The System Requirements Specification (SRS) for a Banking

Management System is a critical document that outlines the functional
and non-functional requirements of the software system. This document
serves as a foundation for the design, development, and testing phases
of the project, ensuring that the final system meets the needs and
expectations of both the bank and its customers. In this conclusion, we
will highlight the key takeaways and emphasize the importance of a
well-defined SRS for such a complex and sensitive domain. First and
foremost, the SRS for a Banking Management System has been
designed with a strong emphasis on security and data integrity. The
confidentiality, availability, and integrity of customer data are of
paramount importance in the banking industry. This document provides
a detailed outline of the security measures, user access controls, and
encryption standards that will be implemented to safeguard sensitive
information. By doing so, it ensures that customer trust is maintained
and regulatory compliance is upheld. Another crucial aspect of the SRS
is its comprehensive coverage of the system's functionality. It defines
the various features and modules that the Banking Management System
will offer, including customer account management, transaction
processing, loan management, reporting, and administrative tools. This
level of detail enables developers to understand the full scope of the
project and minimizes misunderstandings or misinterpretations during
the development process.

In conclusion, the System Requirements Specification for a Banking

Management System is an indispensable document that lays the
foundation for the successful development and deployment of a
sophisticated and secure banking software solution. It encompasses the
critical aspects of functionality, security, performance, and user
experience, all of which are essential in the banking industry. A well-
defined SRS reduces ambiguity, minimizes risks, and serves as a
roadmap for developers and stakeholders. By following the guidelines
and requirements set forth in this document, the bank can look forward
to a robust, secure, and customer-centric Banking Management System
that will not only meet their immediate needs but also adapt to future
challenges and opportunities in the ever-evolving world of banking.
 ACKNOWLEDGMENT

On the successful completion of our project BANKING

MANAGEMNET SYSTEM, we would like to express our sincere
gratitude to everyone who helped us in the completion of the
project.

We are sincerely thankful to our project guide our professor “Mr. Ajit
Chansauriya” for his interest, guidance and suggestion throughout
the course of the project. We feel honored and privileged to work
under him. He shared his vast pool of knowledge with us that helped
us steer through all the difficulties with ease.
This project would not have been possible without his guidance.
Table of Content

Problem Statement
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions
1.4 Overview
1.5 Process model

2. Software Requirement Specification

2.1 Overall description
2.1.1 Product perspective
2.1.2 Product functions
2.1.3 User characteristics
2.1.4 General constraint
2.1.5 Assumptions & Dependencies
2.1.6 User classes and characteristics
2.1.7 Operating environment
2.2 Data Dictionary
2.3 Software Interface
2.4 Hardware Requirements
2.5 Functionalities

3. Project Management
3.1 Cost estimation
3.2 Functional point estimations
3.3 Functional requirements
3.4 Technical issues
3.5 Non-functional requirements

4. Data Flow Diagram

4.1 DFD Level 0
 4.2 DFD Level 1

5. Use Case Diagram

6. State Diagrams

7. Entity – Relationship Diagram

8. Future Scope

9. Conclusion