Seminar Report

on
“E-Bank Manager”
Submitted by
[Group member’s name]
Arnav Dhiwar
Anish Nalawade
Aditya Shahade
Sanket Deokate

Under the guidance of

Prof. K. H. Kolambe

In partial fulfilment of
Diploma in Information Technology
[2020-2021]
At

DEPARTMENT OF INFORMATION TECHNOLOGY

MIT POLYTECHNIC
PUNE-411038
Affiliated to

MSBTE

Acknowledgement
1
I take immense pleasure in thanking Prof. Dr. R.S kale, our principal for having permitted me to
carry out project work.
I would like to thank my Head of the IT Department Prof. M. P. Fatangare for her constructive
criticism throughout my project.
I would like to thank Department project coordinator Prof. K. H. Kolambe for their support and
advice to get and complete my project work.
I wish to express my deep sense of gratitude to our Internal Guide, Prof. K. H. Kolambe, Lecturer,
and Department of Information Technology for their valuable guidance and useful suggestions,
which helped me in completing the project work, in time.
Finally, yet important, I would like to express my heartfelt thanks to my beloved parents for their
blessings and my friends for their help and wishes for successful completion of this project

ABSTRACT

We are creating an Easy loan (website) through which everyone can get a loan easily.

Users usually go to bank to get a loan, but sometimes because of bank policies one has to pay more
interest on bike, car and home loan, which increases the nu mber installation and the user has to
pay much more price.

We have created a platform through which individuals, communities, and organizations can get
loans with low interest. Users can compare the different types of banks with their interest rate,
services and policies. So, everyone can get the loan with low interest and with the best services.

2
 TABLE OF CONTENTS

Sr. No PAGE NO.

CONTENTS

1 INTRODUCTION 5

1.1 Motivation

1.2 Background

1.3 Need Of The Project

2 LITERATURE SURVEY 6
3 SCOPE OF PROJECT 8

3.1 Project objectives

1. Project Features

2. Project Cost (Overall Cost)

4 PROPOSED METHODOLOGY 12

4.1 System Architecture

4.2 Introduction
4.2.1 Working
4.2.2 Description of certain components

5 DETAILS DESIGN AND WORKING PROCESSES 15

5.1 Hardware Software Requirement

3
 5.2 DFD’s (0, 1, 2) level

5.3 Use Case Diagrams

5.4 Activity diagram

5.5 Timeline Chart

6 Screen Shots and Application 28

6.1 Screen Shot

6.2 Application

7 Conclusion 33

References and Bibliography 33

LIST OF TABLES

Table No. Title Page No.

1 Cost Estimation 11
2 Hardware Requirement 15
3 Software Requirement 15
4 Timeline Chart Table 21
5 Software (User Side) 25
6 Software (Worker Side) 26

4
 LIST OF FIGURES

FIGURE Title Page No.

NO.
1 System Architecture of E-Bank Manager 13
2 0 Level DFD 16
3 1 Level DFD 17
4 2 Level DFD 18
5 Use Case Diagram of E-Bank Manager 19
6 Activity Diagram of E-Bank Manager 20
7 Timeline Chart (X-axis:Task , Y-axis: No. of days) 21
8 SCREENSHOTS AND APPLICATIONS 28,29,30,31

CHAPTER 1 INTRODUCTION

1.1 Motivation
The motivation for doing this project was primarily an interest in undertaking a challenging
project in an interesting area of research. The opportunity to learn about a new area of computing
not covered in lectures was appealing. This area is possibly an area that has helped and made us
believe about the vast fields of computing and programming.
The project has clearly been inspired from various tech leading companies around the globe such
as Amazon, Alibaba, Trivago, Airbnb, Facebook, Google etc.
The evolution of the concepts in the field of programming and computing has been immense and
the project takes great satisfaction to provide its best results.

1.2 Background
The background of the project is clear as a sky. This project works on CPC(Cost Per Click)
business model where the consumer lands on the website and searches for its right bank and
clicks on it, where the consumer is redirected to the chosen bank’s website and can take further

5
actions.Payment is made by the bank to the website’s payment portal when the customer clicks
on view loan to get redirected to their chosen banks.
This type of business model was inspired from the company Trivago where it uses CPC to
redirect customers to their favourite hotels.

1.3 Need of the Project

The need of the project is very much crucial in this era of computing and computer related
technologies. As these giant tech companies take part in such business models where the market
is high for CPC models. Many of the tech companies are not following such advantageous
models for their business but to increase the amount of profitability for a company CPC model
can be a great choice. This project was made as an inspirational start towards building such
models and their implementation in computing and other software related areas. This project was
intended to make people understand the vastness and some worth learning concepts of
programming. The tech companies will be using such CPC models in the coming future with
better software to understand the complexity and needs of the customer.

CHAPTER 2 LITERATURE SURVEY

Business Model of Trivago :-

Trivago is a giant comparison website which allows the customers to compare hotels and rooms
on various websites and hotels itself before booking.Trivago successfully understood the typical
Mentality i.e. Comparing prices on as many shops or websites before purchasing anything and
then choose the one with the lowest price and good quality.
The business model of Trivago is that it gets virtually all of its revenue from the cost-per-click
model. When consumers click on a link, Trivago gets paid.

There are 3 major Revenue streams Trivago has –

6
 ● Revenue from ListingsRevenue generated from the listings includes the fees paid by the
hotel booking websites for displaying their services and hotel rooms listed on trivago
platforms
● Revenue from ServicesRevenue generated from services includes the fees paid by the
hotel brands for managing their listing on trivago which includes their presence and
visibility.
● Revenue from Affiliate partners affiliate earning or we can call it referral earning
contributes up to 59 per cent of the total revenue is generated. Users come to Trivago
platform for hotel searches, then they click on one of the hotel offers/deals displayed in
the search results. Then he is redirected to the affiliate partner’s website. This Affiliate
partner can either be a hotel booking website or an individual hotel, pays Trivago a
certain sum of money for each such referral.

Each affiliate partner/advertiser can determine the amount that it wants to pay for each referral
redirect by bidding for advertisements on the website.
In Business terminology, this model is known as the Pay-Per-Click or PPC revenue model.

Business model of Airbnb:-

Airbnb is a community-based online platform for listing and renting local homes. It connects
hosts and travelers and facilitates the process of renting without owning any rooms itself.
Moreover it cultivates a sharing-economy by allowing property owners to rent out private flats.
Revenue Model:-
Airbnb receives commissions from two sources upon every booking, namely from the hosts and
guests. For every booking Airbnb charges the guest 6-12% of the booking fee. Moreover Airbnb
charges the host 3% for every successful transaction.

Business model of Google AdSense:-

As the website owner, we can control just what types of ads appear on the pages of your site.
With AdSense, publishers have access to reports and metrics which can show just how effective
the ad campaigns are for the website. It’s very easy to use, and there are no signup fees involved.

7
We’ll get to display ads that are associated with the interests of your visitors, and you get paid
depending on the number of visitors who click on the ads on your site. You can also put in a
custom search bar on your site, and earn money from the ads that appear on the search results
page.

Business model of Facebook Ads:-

Facebook generates substantially all of its revenue from selling advertising to marketers. Ads are
displayed on Facebook's main social-networking site, as well as Instagram, Messenger, and other
third-party affiliated websites or mobile applications. Marketers pay for ads based on the number
of impressions delivered or the number of actions, such as clicks, undertaken by the user.

CHAPTER 3 SCOPE OF PROJECT

3.1 Project objectives

In the relatively recent past, getting a loan was entangled, tedious and upsetting. It was not
precisely simple to analyze costs – continually abandoning you uncertain in the event that you
got the best value for your money.

This change in the knowledge lessened the purchasing fear, as well as ensures banks convey an
awesome affair, reliably. Out of the blue, consumers could get a solid downplaying of what they
would get before they get a loan.

E-Bank Manager is a local bank search website, where site users can compare bank prices. It
allows users to compare bank deals and find the best prices quickly and easily.

Users usually go to the bank to get a loan, but sometimes because of bank policies one has to pay
more interest on bike, car and home loan , which increases the number installation and users have
to pay much more price. We have created a platform through which individuals, communities, and

8
organizations can get loans with low interest. Users can compare the different types of banks with
their interest rate, services and policies. So, everyone can get the loan with low interest and with
the best services.

Using our E-Bank Manager , users can list their banks through profiles on the website. Registration
is free, through a simple online form E-Bank Manager is completely free to use, allowing you to
list your bank and benefit from increased exposure.

The Maths is simple, when a user clicks on the link at our platform, we get paid in return.

The E-Bank Manager initially curates the accessibility by simply enabling its customers to make
contributions to the content of their website. Further, they are motivated to add banking brands
and text descriptions. Complete missing profiles, as well as edit the profile for ensuring the quality
of the content.

The website fosters customization by simply allowing the brands on its platform to personalize
their user profiles. Convenience is offered by giving the visitors the facility to search for banks
and compare the prices as per the brands.

1. Project Features

These are some key features of this project:-

● Easy way to access banks and get secured loan amounts in less time.
● Get the best deals on loans.
● Fluidity in accessing the website.
● Purely coded in web related languages hence the code becomes more secure.
● Registration system which includes login and logout portal.
● Informative web design

9
Why it’s important: One consumer out of two uses meta search when searching for a bank loan to
apply online. A recent report revealed that 50% of people around the globe online loan appliers
completed a loan application on or through a meta search site at least once in the past year.

When we single out millennial consumers, the percentage of consumers who go through a
metasearch site to apply for their loan online is higher still at 63%.

The direct applying journey has moved to meta search. To stay competitive and tap into this direct
business potential, E-Bank Manager is a loan applying engine that’s integrated with top bank
metasearch sites so that we can advertise their direct rates on our high-potential website.

We get paid for the visits(clicks) we receive. In other advertising models, the advertiser pays a fee
for having the ad shown, but does not have the guarantee that it is generating results. On the other
hand, with pay per click, there is a direct link between cost and performance (visits).

2. Cost of the project.

COCOMO Model
Boehm proposed COCOMO (Constructive Cost Estimation Model) in 1981.COCOMO is one of
the most generally used software estimation models in the world. COCOMO pred icts the efforts
and schedule of a software product based on the size of the software.The necess ary steps in this
model are:

1. Get an initial estimate of the development effort from evaluation of thousands of delivered
lines of source code (KDLOC).
2. Determine a set of 15 multiplying factors from various attributes of the project.
3. Calculate the effort estimate by multiplying the initial estimate with all the multiplying
factors i.e., multiply the values in step1 and step2.

The initial estimate (also called nominal estimate) is determined by an equation of the form used
in the static single variable models, using KDLOC as the measure of the size.
Embedded: A development project is treated to be of an embedded type, if the software being
developed is strongly coupled to complex hardware, or if the stringent regulations on the
operational method exist. For Example: ATM, Air Traffic control.
For three product categories, Bohem provides a different set of expression to predict effort (in a
unit of person month)and development time from the size of estimation in KLOC(Kilo Line of
code) efforts estimation takes into account the productivity loss due to holidays, weekly off, coffee

10
breaks, etc. Basic COCOMO Model: The basic COCOMO model provides an accurate size of the
project parameters. The following expressions give the basic COCOMO estimation model:
Effort=a 1*(KLOC) a 2 PM
Tdev=b1*(efforts)b2 Months
Where KLOC is the estimated size of the software product indicate in Kilo Lines of
Code,a1,a2,b 1,b 2 are constants for each group of software products,
Tdev is the estimated time to develop the software, expressed in months, Effort is the total effort
required to develop the software product, expressed in person months (PMs).In our system,

Cost:

Project Expense Cost(In Rupees)

Category

Man Power

Order Quantity 0

Production 200
Time(hrs)

Labor Rate(Rs/Hr) 200

Number of Workers 3

Total 20,000.00

Software cost

MIT App Inventor 0

Total 0

Total Cost 20,000.00

11
 Table 1: Cost Estimation Table

CHAPTER 4 PROPOSED MYTHOLOGY

4.1 System Architecture

The system architecture of this project is a conceptual model that defines the structure, behavior,
and more views of the system. An architecture description is a formal description and
representation of a system, organized in a way that supports reasoning about the structures and
behaviors of the system.
The system architecture of this project includes system components and the sub-systems
developed, that will work together to implement the overall system.
One can think of system architecture as a set of representations of an existing (or future) system.
These representations initially describe a general, high-level functional organization, and are
progressively refined to more detailed and concrete descriptions.
System architecture conveys the informational content of the elements consisting of a system, the
relationships among those elements, and the rules governing those relationships. The
architectural components and set of relationships between these components that an architecture
description may consist of hardware, software, documentation, facilities, manual procedures, or
roles played by organizations or people.
A system architecture primarily concentrates on the internal interfaces among the system's
components or subsystems, and on the interface between the system and its external
environment, especially the user. (In the specific case of computer systems, this latter, special,
interface is known as the computer human interface, AKA human computer interface, or HCI;
formerly called the man-machine interface.)

4.2 Introduction

The architecture of our project serves as a blueprint for a system. It provides an abstraction to
manage the system complexity and establish a communication and coordination mechanism
among components.
● It defines a structured solution to meet all the technical and operational requirements,
while optimizing the common quality attributes like performance and security.

12
 ● Further, it involves a set of significant decisions about the
organization related to software development and each of these
decisions can have a considerable impact on quality,
maintainability, performance, and the overall success of the
final product. These decisions comprise of −

● Selection of structural elements and their interfaces by which the system is composed.
● Behavior as specified in collaborations among those elements.
● Composition of these structural and behavioral elements into large subsystems.
● Architectural decisions align with business objectives.
● Architectural styles guide the organization.

4.2.1 Working

Fig.1. System Architecture of E-Bank Manager

The working of the system consists of users who register/login into the system where they are
directed towards the home page of the website and their details are stored in the systems database
13
, if the login process fails they are redirected to their login page and the same process it repeated
again. After successful login they can surf the entire home page displayed on their screen where
users can search for their banks and apply for their favourable loan schemes after all the process
of searching users finally clicks on the “view loan” button where it gets redirected towards the
“landing page”, at this phase the transaction takes place between the bank’s server and our server
if the transaction is successful the transaction details are stored in the database, but if the
redirection process fails the servers of the bank and our servers are alerted immediately and thus
the redirection process repeats itself until the transaction is successful. Afte r successfully landing
on the landing page the user can perform their actions and exit the site successfully. That is all
about the system architecture of this project.

4.2.2 Description of certain components

Users:- Users are a group of individuals or a singular individual who visits a website or visits a
certain application according to their needs.

Conditional symbol:- Checks whether the given condition is true or false.

Database:- Creates, updates, deletes and stores the information of users passed o n to it.

Servers:- Respond to the request made by the client and provide the information requested by the
client.

Containers:- These are holders which hold some specific entity which are allotted to them in our
case these are the home page , view loan page , landing page and exit page.

Dynamic connectors:- These are the arrows which connect to different components of this
architecture.

14
CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

5.1 Hardware Software Requirement

Hardware Requirement:
Name Details
Processor 1.6 GHz Dual-Core Intel Core i5

RAM 8 GB

Hard Drive Macintosh HD

Any other H/W -

Table 2.Hardware Requirements

Software Requirement:
Name Details
Operating System MacOS, Windows
Platform OSX
Tool Atom Text Editor, Sublime Text Editor
Language HTML,CSS, Node, Javascript

Table 3.Software Requirements

15
CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

5.2 DFD’s (0, 1, 2) level

a. DFD 0 Level:-

Fig.2. 0 Level DFD

DFD Level 0 is also called a Context Diagram. It’s a basic overview of the whole system
or process being analyzed or modeled. It’s designed to be an at-a-glance view, showing
the system as a single high-level process, with its relationship to external entities.

It’s designed to be an abstraction view, showing the system as a single process with its
relationship to external entities. It represents the entire system as a single bubble with
input and output data indicated by incoming/outgoing arrows.

16
 CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

b. DFD 1 Level:-

Fig.3. 1 Level DFD

In 1-level DFD, the context diagram is decomposed into multiple bubbles/processes. In this
level, we highlight the main functions of the system and break down the high -level process of 0-
level DFD into subprocesses.

We can see that on this level 1 DFD there are a number of data stores, and data -flows between
processes and the data stores.

It is important to notice that the same data-flows to and from the external entities appear on this
level 1 diagram and the level 0 context diagram. Each time a process is expanded to a lower
level, the lower level diagram must show all the same data-flows into, and out of the higher level
process it expands.

17
 CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

c. DFD 2 Level:-

Fig.4. 2 Level DFD

We have already seen how a level 0 context diagram can be decomposed (exploded) into a level
1 DFD. In DFD modeling terms we talk of the context diagram as the “parent” and the level 1
diagram as the “child”.

This same process can be applied to each process appearing within a level 1 DFD. A DFD that
represents a decomposed level 1 DFD process is called a level 2 DFD. There can be a level 2
DFD for each process that appears in the level 1 DFD.

A 2-level DFD goes one step deeper into parts of 1-level DFD. It can be used to plan or record
the specific/necessary detail about the system’s functioning.

18
CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

5.3 Use Case Diagram

Fig.5. Use Case Diagram of E-Bank Manager

The purpose of this use case diagram is to capture the dynamic aspect of a system.
Use case diagrams are used to gather the requirements of a system including internal and external
influences. These requirements are mostly design requirements. Hence, whe n a system is analyzed
to gather its functionalities, use cases are prepared and actors are identified.
When the initial task is complete, use case diagrams are modelled to present the outside view.
In brief, the purposes of use case diagrams can be said to be as follows
−

● Used to gather the requirements of a system.

● Used to get an outside view of a system.
● Identify the external and internal factors influencing the system.
● Show the interaction among the requirements of the actors.

19
CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

5.4 Activity diagram

Fig.6. Activity Diagram of E-Bank Manager

An activity diagram of this project is a behavioral diagram i.e. it depicts the behavior of a
system.
An activity diagram of this project portrays the control flow from a start point to a finish point
showing the various decision paths that exist while the activity is being executed.

20
 CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

5.5 Timeline Chart

Fig.7. Timeline Chart (X-axis:Task , Y-axis: No. of days)

Sr.No Task No.of days

1. Information Gathering 16
2. Requirement Analysis 10
3. Designing Analysis 9
4. Coding 5
5. Testing 5
6. Implementation 7

Table 4. Timeline Chart Table

5.6 Implementation

The following steps are involved in the implementation of the project:

Implementation is the process of building the web according to its design. A web implementor
creates hypertext markup language (HTML), Common Gateway Interface (CGI) programs,
and/or Java scripts and/or applets.

21
 CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

The implementation process resembles software development because it involves using a

specific syntax for encoding web structures or a programming language in a formal language in
computer files. Although there are automated tools to help with the construction of HTML
documents, a thorough grounding in HTML enriches the web implementor's expertise.

Key Implementation Practices

● At the outset, create an extendible directory and file structure to manage the web's files
and/or software components (CGI or Java programs).
● Use HTML tools where helpful.
● Check the web's implementation in various browsers.
● Use templates or web generating schemes for supporting a consistent look and feel.

Key Implementation Resources

● The HTML Station: summary and demonstration of HTML syntax.

● HTML index section on HTML from webreference.com. Includes links to editors, FAQs,
etc.
● HTML Writers Guild: an organization dedicated to creating good hypertext.

5.6.2 Types of testing

Testing

Software testing is defined as an activity to check whether the actual results match the expected
results and to ensure that the software system is Defect free. It involves execution of a software
component or system component to evaluate one or more properties of interest. Software testing
also helps to identify errors, gaps or missing requirements in contrast to the actual requirements.
It can be either done manually or using automated tools. Some prefer saying Software testing as a
White Box and Black Box Testing.

● Unit Testing

Unit testing is a level of software testing where individual units/ components of a software are
tested. The purpose is to validate that each unit of the software performs as designed. A unit is

22
 CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

the smallest testable part of any software. It usually has one or a few inputs and usually a single
output.

● Integration Testing

Integration testing is a level of software testing where individual units are combined and tested
as a group. The purpose of this level of testing is to expose faults in the interaction between
integrated units. Test drivers and test stubs are used to assist in Integration Testing.

● Functional Testing

Functional testing is a type of software testing whereby the system is tested against the functional
requirements/specifications. Functions (or features) are tested by feeding them input and
examining the output. Functional testing ensures that the requirements are properly satisfied by
the application.

● System Testing

System testing is a level of testing that validates the complete and fully integrated software product.
The purpose of a system test is to evaluate the end-to-end system specifications. Usually, the
software is only one element of a larger computer-based system.

● Usability Testing

Usability testing is a way to see how easy to use something is by testing it with real users. Users
are asked to complete tasks, typically while they are being observed by a researcher, to see where
they encounter problems and experience confusion.

23
CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

5.6.3 Test Cases

Test Case ID: Test 1 Test Designed by: Anish Nalawade

Test Priority (Low/Medium/High): Medium Test Designed date: 15 Nov 2020

Module Name: Software (User Side) Executed by: Anish Nalawade

Test Title: Verify the User side of the system Test Execution date: 15 Nov 2020

Description: Testing the User side of system

Pre-conditions: buttons should work and can open other modules

24
CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

Act
Sr.n Test case Description Input Data Expecte ual Status
o. ID d Result Res
ult

It should It will
1. TC1 Username field Enter accept Pass
accept
for creating new username
the
account “username ”
usernam
e

Enter “abc” It should It will

2. TC2 Password field (valid id) accept accept Pass
for creating new and click on password passwor
sign in d
account
“Submit”

Enter It will
3. TC3 Open the login username It shall open the Pass
page and open the final
password final page page in
in which which
receiver is receiver
chosen is chosen

Table 5. Software Table ( User Side)

25
 CHAPTER 5 DETAILS DESIGN AND WORKING PROCESSES

Test Case ID: Test 2 Test Designed by: Anish Nalawade

Test Priority (Low/Medium/High): High Test Designed date: 25 Nov 2020

Module Name: Software (Worker side) Executed by: Anish Nalawade

Test Title: Verify the Worker side of the system Test Execution date: 25 Nov 2020

Description: Testing the Working side of system

Pre-conditions: buttons should work and can open other modules

Actual
Sr.no. Test Descripti Input Data Expected Result Status
case ID on Result

Enter email It should It will open

1. TC1 Open the addrs open the the page of Pass
register page of user user details
address and
page details and and path
password
path

Enter email, It should It will accept

2. TC2 Add user password. accept email email and Pass
details and password password

26
 It should save It should save It will save
3. TC3 Add the user the user the user Pass
user details when details. details.
details register button
is clicked

4. TC4 Check When we It should It will have Pass

user check the have user user
details database it information information
must have
user
information.

Table 6. Software Table ( Worker Side)

27
 CHAPTER 6 SCREENSHOTS AND APPLICATIONS

6.1 Screenshots

28
CHAPTER 6 SCREENSHOTS AND APPLICATIONS

29
CHAPTER 6 SCREENSHOTS AND APPLICATIONS

30
 CHAPTER 6 SCREENSHOTS AND APPLICATIONS

6.2 Applications

31
• Education

• Bank

• Business

• Tourism

32
 CHAPTER 7 CONCLUSION

Our proposed system will solve the problem of heavy interest on bank loans. We
show lots of banks to users to take loans according to their need and convenience.
Hence they can choose easily any bank according to need by comparing there interest
on loans, bank policies and Services

Future Scope

There are a lot of students, business community and travellers who wish to fulfill
their dreams, but they don't because of lack of money. We solve their problems by
giving them loans convenience and easily.

References and Bibliography

The HTML Station: summary and demonstration of HTML syntax.

https://www.december.com/html/

HTML index section on HTML from webreference.com. Includes links to editors, FAQs, etc.

https://www.webreference.com/html/

HTML Writers Guild: an organization dedicated to creating good hypertext.

https://www.hwg.org/

33