1.

INTRODUCTION

1.1 Introduction Mobile Banking System

In the course of the most recent couple of years, the mobile and remote market has been
one of the quickest developing markets on the planet and it is as yet developing at a fast pace.
With mobile innovation, banks can offer a wide scope of services to their clients, for example,
balance enquiry, mini statement, cheque status and so on.

Mobile Banking is an application that lives on a mobile phone, which lets one access
their ledgers with only a couple of presses away. This application gives the financial
organizations a chance to offer some benefit added administrations to their clients. Mobile
Banking is the most encouraging approach to arrive at progressively number of clients who can't
habitually visit banks or ATMs to get the data about their record. What's more, because of its
capacity to give benefits anytime any where the clients of Mobile Banking quickly increases.
Versatile Banking is being utilized to pull in low-pay populaces in rustic areas.

Here we are first accepting a login procedure, a typical procedure of getting username
and passwords for clients. We are likewise thinking about that they have the financial balances
that implies they are having manual exchanges with the specific bank, so a decent client of this
bank whom we won't have any desire to lose for the explanation of security rupture in.

1.2 Need for Mobile Banking

Without a sound and successful financial framework in India it can't have a solid
economy. The financial arrangement of India ought in addition to the fact that hassle be free it
ought to have the option to address new difficulties presented by the innovation and some other
outside and interior elements.

The data framework is fundamental worry to the banks in the present business condition.
The matter of agreeable bank has expanded exceptionally as of late because of the sharp
increment in quantities of urban co-usable banks. This exponential development of Co

1
employable Banks in India is credited for the most part to their greatly improved nearby reach,
individual association with clients, and their capacity to get the nerve of the neighborhood
customers. A product advancement technique alludes to the system that is utilized to structure,
plan, and control the way toward building up a data framework. Every one of the accessible
philosophies and procedures are most appropriate to explicit sorts of tasks, in view of different
specialized, hierarchical and accessible assets.

With reference to above applicable data the fundamental target is to examine its
enlistment instruments in urban agreeable bank considering programming building idea. With the
assistance of this underlying data the followings are a portion of the target of the examination.

 To think about the Information Technology in perspective on research concentrate

 To ponder the utilization of Information innovative methods in the framework

 To examine the input of the past exchange framework.

 To think about the current exchange framework

 To examine the every single ward parameter.

 To contemplate the work culture of client, worker and the executives To think about the
criticism of the current exchange framework

 To think about the administration gave by the framework in perspective on client

connection To examine the perspective on the executives, worker and clients survey

 To think about the Software Engineering in perspective on research work To examine the
criticism of executed innovation

 To ponder on gathered information and data by applying different techniques

2
 2. SYSTEM ANALYSIS

2.1 Existing System

The initial step of starter study in the framework examination procedure includes the
identification of requirements for computerization. The inspiration driving this task is to defeated
every one of the deformities in the current framework.

A few imperfections in existing framework are: Each time Customer needs to visit the
bank at whatever point he need to play out any exchanges.

2.2 Proposed System

Highlights of proposed framework:

 No need of visiting bank each and every time.

 All banking administrations like checking balance, mini statement, applying for

cheques are given in portable.

2.3 Feasibility Study

The next step in analysis is to verify the feasibility of the proposed system. “All projects are
feasible given unlimited resources and infinite time“. But in reality both resources and time are
scarce. Project should confirm to time bounce and should be optimal in there consumption of
resources. This place a constant is approval of any project.

Feasibility has applied to Mobile Banking pertains to the following areas:

 Technical feasibility
 Operational feasibility
 Economical feasibility

3
Technical Feasibility - To determine whether the proposed system is technically feasible, we
should take into consideration the technical issues involved behind the system. Mobile Banking
uses the web technologies, which is rampantly employed these days worldwide. The world
without the web is incomprehensible today. That goes to proposed system is technically feasible.

Operational Feasibility - To determine the operational feasibility of the system we should take
into consideration the awareness level of the users. This system is operational feasible since the
users are familiar with the technologies and hence there is no need to gear up the personnel to
use system. Also the system is very friendly and to use.

Economic Feasibility - To decide whether a project is economically feasible, we have to

consider various factors as:
 Cost benefit analysis
 Long-term returns
 Maintenance costs

The proposed Mobile Banking is computer based. It requires average computing capabilities
and access to internet, which are very basic requirements hence it doesn’t incur additional
economic overheads, which renders the system economically feasible.

2.4 Hardware Requirements

The hardware specification is necessary to support the proposed system, which have been identified,
ordered, delivered, installed and tested at the time of installation.

 Processor : Pentium IV
 Hard Disk : 40GB
 RAM : 512MB or more
 Mouse : Optical
 Printer : HP Laser

4
2.5 Software Specification

The software specification is the one says about the development environment of the package.

 Operating System : Windows 7

 User Interface : HTML, CSS,
 Client-side Scripting : JavaScript
 Programming Language : PHP
 Database : MYSQL
 Server Deployment : Apache

5
 3. SYSTEM DESIGN

Design is the process of translating requirements defined during analysis into several
designs activities for user requirements. The designer select requirements needed to implement
the system in this phase; the design of the database also takes place. After identifying the
problem, limitations are opportunities to improve the efficiency system. A detail design of the
proposed system is done. In database design several objectives are considered such as
,Controlled Redundancy, Data Independence, More Information at low cost, Accuracy and
Integrity, Recovery and Failure, Security and Performance.

System Flow Diagram

Design Engineering deals with the various UML [Unified Modeling language] diagrams
for the implementation of project. Design is a meaningful engineering representation of a thing
that is to be built.

Software design is a process through which the requirements are translated into
representation of the software. Design is the place where quality is rendered in software
engineering. Design is the means to accurately translate customer requirements into finished
product

A system flow diagram (SFD) is a description of the system or portion of a system. It

provides a logical diagram of how the system operates. It also reflects the relationship between
input processing and output.

It is a flow model or diagram used to describe conceptual flow model by providing

graphical notations which documents properties that binds them the basic graphical elements of
SFD’s or have representing the process and arrow representing relationships.

The transformation of the data from input to output, through process, may be described
logically and independently of the physical component.

6
Context Analysis Diagram

DFD’s may be partitioned into levels. A Level 0 DFD, also called a context model,
represents the entire software element as a single bubble with input and output arrows. But
context analysis considers the entire environment of a business, its internal and external
environment. This is an important aspect of business planning. One kind of context analysis,
called SWOT analysis, allows the business to gain an insight into their strengths and weaknesses
and also the opportunities and threats posed by the market within which they operate. The main
goal of a context analysis, SWOT or otherwise, is to analyze the environment in order to develop
a strategic plan of action for the business.

Data Flow Diagram

The Data Flow Diagram is a graphical representation which depicts the information
regarding the flow of control and the transformation of the data from the input to the output.
They show end-to-end processing. That is the flow of processing from when data enters the
system to where it leaves the application can be traced.

The DFD may be used to represent the system or software at any level of abstraction. In
fact DFD’s may be partitioned into levels. A Level 0 DFD, also called a context model,
represents the entire software element as a single bubble with input and output arrows.

DFD is a graphical tool used for requirement analysis. DFD depicts information flow
without explicit representation procedural logic. DFD also depicts real time systems with the
help of some extended notation.

Four rules for constructing a dataflow diagram

 Squares, circles and files must bear names.

 Decomposed data flow squares and circles can have same names.
 Choose meaningful names for data flow.
 Draw all data flows around the outside of the diagram.

A data flow diagram is used commonly during analysis stage. Data flow diagrams are
useful in understanding a system and can be effectively used in partitioning during analysis.

7
 This level shows the overall DFD of IMEGS. This level is relationship to High Level of
Data Flow Diagram.

Entity Relationship Diagram

They provide the data at the logical level. They are characterized by that fact that they
provide fairly flexible structuring capabilities and allow data constraints to be specified
explicitly.

The entity relationship data model is based on a perception of a real world that consists of
a set of basic object entities and relationships among the objects. It was developed to facilities
database design.

The ER data model is one of several semantic data model. The semantic aspect of model
lies in the attempt to represent the meaning of data .ER model is externally used in meaning and
interactive of real world enterprises.

ER Model has some means of describing the physical database model, it is basically
useful in the design & communication of the logical database model. In this model, objects of
similar structure are collected into an entity set.

8
 The relationship between entity sets is requested by a named ER relationship. The
database structure employing the ER model is usually shown pictorially using entity –
relationship (ER) diagrams.

Diagrams created by this process are called entity-relationship diagrams, ER diagrams, or

ERDs. The relationship between entity sets is represented by E-R relationship mapping from one
entity set to another.

Use Case Diagram

A use case diagram is a type of behavioral diagram created from a Use-case analysis.
This diagram represents interaction between admin and customer. The administrator maintain
details about customer

Use Case Relationships

Three relationships among Use Case are supported by the UML standard, which
describes graphical notation for these relationships and created by boot.

9
Include: In one form of interaction, a given Use Case may include another. Include is a Directed
Relationship between two Use Cases, implying that the behavior of the included Use Case is
inserted into the behavior of the including Use Case.

The first Use Case often depends on the outcome of the included Use Case. It is useful
for extracting truly common behaviors from multiple Use Cases into a single description. The
notation is a dashed arrow from the including to the included Use Case, with the label
<<included>>. The usage resembles a macro expansion where the included Use Case behavior is
placed inline in the base Use Case behavior. There are no parameters or return values.

To specify the location in a flow of events in which the base Use Case includes the
behavior of another, the user simply write include followed by name of Use Case the user want
to include, as in the following flow for track order.

Extend: In another form of interaction, a given Use Case (the extension) may extend another.
The relationship indicates the behavior of the extension Use Case may be inserted in the
extended Use Case under some conditions. The notation is a dashed arrow from the extension to
the extended Use Case, with the label <<extend>>. It can be useful for dealing with special cases
(when A extends B, A is a special case of B), or in accommodating new requirements during
maintenance and extension.

Modelers use the <<extend>> relationship to indicate Use Case it was optional to the
base Use Case. Depending on the modeler’s approach optional may mean potentially not
executed with the base Use Case or it may mean not required to achieve the base Use Case goal.

Sequence Diagram for Login Process

10
 user request mobile web server database
simulator

enter userid and password

userid,password is sent for process

process the values and check from the database

value return from the database

if valid login in to the form

if invalid same window displayed

Request for Change password:

11
 Request for mobile webserver Database
password simulator

Request for password

process the request

Retype and confirm

process the user values

check from the database

forward result

return to mobile browser

Collabration diagram for login process:

12
 2: userid,password is sent for process
mobile web
simulator server
5: if valid login in to the form
6: if invalid same window displayed

1: enter userid and password 4:3: value

process thefrom
return values
theand check from the database
database

databas
user e
request

Collabration for Change password:

2: process the request

1: Request for password

3: Retype and confirm
Request for mobile
password simulator

7: return to mobile browser

4: process the user values

5: check from the database

webserv Databas
er e
6: forward result

3.1 Input Design

13
 The input design is the process of entering data to the system. The input design goal is to
enter to the computer as accurate as possible. Here inputs are designed effectively so that errors
made by the operations are minimized. The inputs to the system have been designed in such a
way that manual forms and the inputs are coordinated where the data elements are common to
the source document and to the input. The input is acceptable and understandable by the users
who are using it. Once identified, appropriate input media are selected for processing.

The input design also determines the user to interact efficiently with the system. Input
design is a part of overall system design that requires special attention because it is the common
source for data processing error. The goal of designing input data is to make entry easy and free
from errors.

The main objectives that are done during the input design are:

 Data is collected from the source

 Transfer of data to an input form is done
 Data is converted to a computer acceptable form
 The converted data is verified
 Data is checked for its accuracy
 Data is transmitted to the computer
 Validation of input data is done

Form Name: Balance Enquiry

14
Fig 4.1.2 Balance Enquiry

15
Form Name: Login Page

Fig 4.1.3 Login Page

16
Form Name: Cheque Book Request

Fig 4.1.4 Cheque Book Request

17
Form Name: Pay Bill

Fig 4.1.5 Paybill

18
Form Name : Mini Statement

Fig 4.1.6 Mini Statement

19
Form Name : Transferring Amount

Fig 4.1.7 Transferring Amount

20
3.2 Output Design

Computer output is most important and direct source of information to the user. Efficient
of intelligible output should improve the system relationship with the user and help in decision-
making. Major forms of output are hard copy from the printer and soft copy from the CRT unit.

The output design was done so that results of processing could be communicated to the
users. The various outputs have been designed in such a way that they represent the same format
that the office and management used to.

Computer output is the most important and direct source of information to the user.
Efficient, intelligible output design should improve the systems relationships with the user and
help in decision making. A major form of output is the hardcopy from the printer.

 Scalability of the device according to the output format required

 The need of hard copy
 The response time taken
 The detail specification needed

21
Form Name: Dashboard Page

Fig 4.1.1 Dashboard.

3.3 Database design

Database design is the process of producing a detailed data model of a database. This
logical data model contains all the needed logical and physical design choices and physical
storage parameters needed to generate a design in a Data Definition Language, which can then be
used to create a database. A fully attributed data model contains detailed attributes for each
entity.

22
 The term database design is used to describe many different parts of the design of an
overall database system. The logical design of the base data structures used to store the data. In
the relational model these are the tables and views. In an object database the entities and
relationships map directly to object classes and named relationships. However, the term database
design could also be used to apply to the overall process of designing, not just the base data
structures, but also the forms and queries used as part of the overall database application within
the database management system (DBMS).

The process of doing database design generally consists of a number of steps which will
be carried out by the database designer.

 Determine the relationships between the different data elements.

 Superimpose a logical structure upon the data on the basis of these relationships.

Steps in Database Design

The process of SQL Server Management Studio database design is divided into different
parts. It consists of a series of steps. They are

 Requirement Analysis
 Conceptual Database Design (ER-Diagram)

 Logical Database Design (Tables, Normalization etc.)

 Physical Database design (Table Indexing, Clustering etc.)

Requirement Analysis

In the phase a detailed analysis of the requirement is done. The objective of this phase is
to get a clear understanding of the requirements. It makes use of various information gathering
methods for the purpose. Some of them are

23
  Interview
 Analysing documents

 Survey

 Site visit

 Joint Applications Design (JAD) and Joint Requirements Analysis (JRA)

 Prototyping

Conceptual Database Design

The requirement analysis is modelled in this conceptual design. The ER Model is used at
the conceptual design stage of the database design. The ER diagram is used to represent this
conceptual design. ER diagram consists of Entities, Attributes and Relationships.

Logical Database Design

Once the relationships and dependencies are identified the data can be arranged into
logical structures and is mapped into database management system tables. Normalization is
performed to make the relations in appropriate normal forms.

Physical Database Design

It deals with the physical implementation of the database in a database management

system. It includes the specification of data elements, data types, indexing etc. All these
information are stored in the data dictionary.

The MySQL Permission Model

In order to fully implement a secure MySQL database, it is necessary to learn the MySQL
access control system. There are four privilege levels that apply:

 Global: these privileges apply to all databases on a server.

 Database: these privileges apply to all tables in a database.
 Table: these apply to all columns within a table.

24
  Column: these apply to individual columns in a table.

Database Backups

Another area that often gets lost in the layers of security is the critical area of database
backup and recovery. As a part of whatever backup type is used, testing recovery of data is
mandatory. Further, check pointing has been improved to be done more frequently, also easing
the recovery process. With frequent check pointing, as well as transaction logging and making
regular backup copies, backup and recovery of databases is made more straightforward.

Specifically, the InnoDB transactional model allows for commit, rollback and crash
recovery. By adding locking capabilities for users, having many users access the database at the
same time becomes faster and more stable. To ensure that InnoDB is available with your
installation, configure your package with the ‘with-innodb’ flags. You will also want to specify
InnoDB options in your ‘my.cnf’ file. Details on these set-up options can be found at the MySQL
Documentation on InnoDB Start-up Options.

The following Fig 4.1 describes the Xampp Control Panel Application form which shows
the start the MySQL connectivity.

25
Fig 4.1 Xampp Control Panel Application

Privileges in MySQL Server

The privileges can get very granular, so it is important that they are used in a well-planned
fashion. The types of privileges include:

 Alter
 Delete
 Create
 Drop
 Execute
 Select
 Update
Once a database is completely set up, these privileges should be reviewed prior to going to
any usage of the database to ensure that the privileges were set up appropriately.

PHP Connect to the MySQL Server

Open a Connection to the MySQL Server

26
 Before we can access data in a database, we must open a connection to the MySQL
server.In PHP, this is done with the mysql_connect () function.

Syntax:

mysql_connect (host, username, password, dbname);

Close a Connection to the MySQL Server

The connection will be closed automatically when the script ends. To close the
connection before, use the mysql_close() function. The following form describes the front page
of the Xampp Windows where we will make the PHP MySQL Connectivity.

Fig 4.2 Xampp Front Page

27
Create a Database in MySQL Server

The CREATE DATABASE statement is used to create a database table in MySQL.We

must add the CREATE DATABASE statement to the mysql_query () function to execute the
command. The following form describes to create a database named "product details".

The Fig 4.3 describes how to create a new database in the My_SQL database. It contains
the database name and also the locations were the database is created and where it is accessed.

Fig 4.3 Creating a New Database in MySQL

Create a Table in the MySQL Server

The CREATE TABLE statement is used to create a table in MySQL. We must add the
CREATE TABLE statement to the mysql_query () function to execute the command. The
following figure describes how to create a tables in the database.

28
 The following Fig 4.4 describes to create a new table in the database job scheduling. It
includes the table name and the entities used in the table, its size and also its type.

Fig 4.4 Create a New Table in the Database

There are several GUI consoles available to make the management of MySQL database
easier. For instance, MySQL Explorer allows several management processes to be done via an
interface that runs on several windows platforms. The MySQL team also has a version in beta
called MySQL Control Center.

29
Insert Data Into a Database Table

The INSERT INTO statement is used to add new records to a database table. The
following form describes to create a new data into the database table which is already created.

Fig 4.5 Insert a data into a Database Table

3.4 Sample Code Design

Login.php

@extends('layouts.app')
@section('content')
<div class="container">
<div class="row justify-content-center">

30
 <div class="col-md-8">
<div class="card">
<div class="card-header">{{ __('Login') }}</div>

<div class="card-body">
<form method="POST" action="{{ route('login') }}">
@csrf

<div class="form-group row">

<label for="email" class="col-md-4 col-form-label text-md-right">{{ __('E-Mail Address') }}

</label>

<div class="col-md-6">
<input id="email" type="email" class="form-control @error('email') is-invalid
@enderror" name="email" value="{{ old('email') }}" required autocomplete="email" autofocus>

@error('email')
<span class="invalid-feedback" role="alert">
<strong>{{ $message }}</strong>
</span>
@enderror
</div>
</div>

<div class="form-group row">

<label for="password" class="col-md-4 col-form-label text-md-right">{{ __('Password') }}

</label>

<div class="col-md-6">
<input id="password" type="password" class="form-control @error('password') is-
invalid @enderror" name="password" required autocomplete="current-password">

31
 @error('password')
<span class="invalid-feedback" role="alert">
<strong>{{ $message }}</strong>
</span>
@enderror
</div>
</div>

<div class="form-group row">

<div class="col-md-6 offset-md-4">
<div class="form-check">
<input class="form-check-input" type="checkbox" name="remember"
id="remember" {{ old('remember') ? 'checked' : '' }}>

<label class="form-check-label" for="remember">

{{ __('Remember Me') }}
</label>
</div>
</div>
</div>

<div class="form-group row mb-0">

<div class="col-md-8 offset-md-4">
<button type="submit" class="btn btn-primary">
{{ __('Login') }}
</button>

@if (Route::has('password.request'))
<a class="btn btn-link" href="{{ route('password.request') }}">
{{ __('Forgot Your Password?') }}
</a>

32
 @endif
</div>
</div>
</form>
</div>
</div>
</div>
</div>
</div>
@endsection

33
 4. SYSTEM TESTING

The most important phase in system development life cycle is system testing. The
number and nature of errors in a newly designed system depends on the system specification and
the time frame given for the design.

A newly designed system should have all the subsystems working together, but in reality
each subsystems work independently. During the phase, all the subsystems are gathered into one
pool and tested to determine whether it meets the user requirements.

Testing is done in two level-Testing of individual modules and test the entire system.
During the system testing, the system is used experimentally to ensure the software will run
according to the specifications and in the way the user expects. Each test case is designed with
the intent of finding errors in the way the system will process.

Testing is vital to the success of the system. System testing makes a logical assumption
that if all the parts of the system are correct; the goal will be successfully achieved non- testing
leads to error that may not appear until months later. This creates two problems.

 The time lag between the cause and appearance of the problem.
 The effort of system error on files and records within the system.

The Testing Steps are:

 Unit testing
 Integrated testing
 Validation testing

34
  White Box testing

Unit Testing: Testing of individual programs or modules is known as unit testing. Unit testing is
done both during documentation and testing phase. Unit testing focuses on verification of effort
on the smallest of software design. Modules using the detailed design description as a guide,
important control paths are tested to uncover errors within the boundary of the module. The
relative complexity is test and errors detected as a result are limited by the constraints scope
established for unit testing. Unit testing is always white box oriented and the step can be
conducted in parallel for multiple modules.

Integration Testing: Integration testing is a systematic technique for constructing the program
structure while at the same time conducting test to uncover errors associated with interfacing.
The objective is to take unit - tested modules and build a program structure that has been
dictated by design. Careful test planning is required to determine the extent and nature of
system testing to be performed and to establish criteria by which the result will be evaluated.

All the modules were integrated after the completion of unit test. While Top - Down
Integration was followed, the modules are integrated by moving downward through the control
hierarchy, beginning with the main module. Since the modules were unit - tested for no errors,
the integration of those modules was found perfect and working fine. As a next step to
integration, other modules were integrated with the former modules.

35
Validation Testing: The most common web application security weakness is the failure to
properly validate input coming from the client or environment before using it. The weakness
leads to almost all of the major vulnerabilities in web applications, such as cross site
scripting, SQL injection, interpreter injection.

Data from an external entity or client should never be trusted, since it can be arbitrarily
tampered with by an attacker. Validation doesn't just mean putting your pages through some web
driven testers. It also means test-driving it with friends, relatives, co-workers, and strangers.
Everyone has a different system and way of working, so ask for others to test-drive your styles or
themes before you make them public.

White Box Testing: White box testing is a test case method that uses control structure and
procedural design to drive test cases using white box testing method. Software engineer can test
cases that:
 Exercise all logical decisions on their true or false sites.
 Guarantee that all independent paths with a module have been exercised at least once.
 Exercise internal data structure to ensure validity.
 Execute all loops at their boundaries and their operational bounds.

White box testing sometimes called as glass box testing is a test case design method that uses
the control structures of the procedural design to derive test cases.

Using White Box testing methods, the software engineer can derive test case, that guarantee
that all independent paths with in a module have been exercised at least once, exercise all logical
decisions on the true and false sides, execute all loops at their boundaries and within their
operational bounds, exercise internal data structures to ensure their validity. “Logic errors and
incorrect assumptions are inversely proportional to the probability that a program path will be
executed“.

Black Box Testing: Black box testing, also called as behavioral testing, focuses on the
functional requirements of the software. That is, black box testing enables the software

36
engineer to derive sets of input conditions that will fully exercise all functional requirements
for a program.

Black box testing focuses on the fundamental requirements on software and on input
and output of the module. It enables the software engineers to derive set of input condition that
will truly exercise all functional requirements of a program. Black box testing is rather a
contemporary approach that is likely to uncover different class of errors.

It attempts to find out errors in the following category:

 Incorrect and missing functions

 Performance errors
 Initialization and termination errors

5. SYSTEM IMPLEMENTATION AND MAINTENANCE

System Implementation

System implementation is the process of developing the system based on the user
requirement that has to be enforced in any system while development. Security window prohibits
unauthorized users entering the system. Implementation is the stage of the project when the
system design is turned into fully working system. This stage consists of following steps.

 Testing the developed program with the sample data.

 Detecting and correction of internal errors.
 Testing the system to see if it meets the user requirements.
 Feeding the real time data.
 Making changes as desired by the user.
 Training user personal.

37
 The purpose of System Implementation can be summarized as follows: making the new
system available to a prepared set of users (the deployment), and positioning on-going support
and maintenance of the system within the Performing Organization (the transition).

At a finer level of detail, deploying the system consists of executing all steps necessary to
educate the Consumers on the use of the new system, placing the newly developed system into
production, confirming that all data required at the start of operations is available and accurate,
and validating that business functions that interact with the system are functioning properly.

A key difference between System Implementation and all other phases of the lifecycle is that
all project activities up to this point have been performed in safe, protected, and secure
environments, where project issues that arise have little or no impact on day-to-day business
operations. Once the system goes live, however, this is no longer the case.

System Maintenance

The system has been designed and developed according to the current requirements of the
user. At the same time the system is very flexible and extensible, Hence, future enhancements, if
needed can be made without much difficulty, so new applications can be developed and it be
integrated with the existing one very easily.

The following future enhancements may be worthwhile to make the tool usable to a wider
section of users.

 Currently only text-based reports are handled. It can be extended to include graphics
and images. Also music and audio clips are considerable.
 User level authentication and authorization may be of use in certain circumstances.

38
 6. SCOPE FOR FUTURE ENHANCEMENT

Banks need to take a shot at making portable financial mindfulness among the clients.
They have to advance the advantages of portable banking and its adequacy. In this venture, we
plan to decide client recognition about portable financial administrations of banks. Client has
various perspectives on portable financial administrations gave by their specialist co-ops. We
look at the desires for clients from banks towards versatile financial framework. In this paper we
likewise assess the effect of versatile depending on client experience in the wake of utilizing
portable banking. This paper mirrors the adjustment in exchanges method of clients through
versatile banking. This paper likewise shares the activities taken by clients in their financial use
in the wake of changing to portable banking.

39
 7. CONCLUSION

The Mobile Banking venture has been effectively finished. The objective of the
framework is accomplished and the issues are understood. This undertaking is created thusly that
is easy to use and needed support is given at various levels.

The essential target is to give the intelligent support of the considerable number of
Customers. Various sorts of administrations are given to both the administrator and client. Client
can benefit this administration whenever.

In the present situation major efficient and specialized changes are experiencing in
modern and money related insurgency through the new data preparing innovation. Particularly in
account division it has a critical job for by and large improvement. Subsequent to recognizing the

40
subject (examine region) and alluding the pertinent literary works, it has been discovered that in
the vast majority of the writing, the data innovations have a wide application region.
Notwithstanding, in fund area significant changes have been made. Because of these
exceptional changes we have done the examination on urban agreeable bank framework.
Subsequent to finishing bit by bit method for robotization process, presently it is required to take
the audit of the framework.

8. BIBLIOGRAPHY

BOOKS REFERRED:

 Anil Desai, “MYSQL server backup and recovery”, Tata mc-grawHill Publication,
second edition,2005.
 Joel Murach, “Murach's PHP and MySQL” , Tata mc-grawHill Publication, Fourth
Edition,2006.
 Luke welling, “PHP and MYSQL web development, Hungry publication, fourth
edition, 2002.
 Lynn Beighley,”Head first PHP and MYSQL” Tata mc-grawHill Publication, First
edition,2005.
 Mario Lurig,”Beginner to Intermediate php5”phphaven publication, fifth
edition,2008.

41
  Rasmus Lerdorf, “Programming PHP”, McGraw-Hill publication, second edition,
2006.
 Robin Nixon,”Learningphp,mysql and javascript” ShroffPublishers,First edition,
2004.
 Richard E fairly, “Software engineering concepts”, Tata Mc-grawHill Publication,
second edition, 2000.
 Steven Holzner, “The Complete Reference PHP”, TATAMcGRAW-
HILLPublication,fourth edition,2007.

WEBSITES:

 www.codproject.com

 www.w3schools.com

 www.php.net.com

 www.phpjunkyard.com

 www.phplearnable.com

9. TABLE DESIGN

Database design is a collection of interactive data store. It is an effective method of

defining, storing and retrieving the information in the database multiple applications and the
users can use the data contained in the database. It prevents fraudulent and unauthorized user
from accessing the data and ensures the privacy of data.

The database design is a must for any application developed especially more .for the data
store projects. Since the chatting method involves storing the message in the table and produced
to the sender and receiver, proper handling of the table is a must.

The tables maintained are user login, vendor details, purchase details, product details,
quality checking details, buyer details, and payment details.

42
 A database is a collection of inter-Related with minimum redundancy to serve the user
quickly and efficiently. The data are stored in tables .Proper care has taken to design table to
achieve data security, data integrity and data consistency.

Database design is a collection of interactive data store. It is an effective method of

defining, storing and retrieving the information in the database. Users can use the data
contained in the database to produce reports. It prevents fraudulent and unauthorized users
from accessing data and ensures the privacy of data.

A well designed database is essential for the good performance of the system .Several
tables are referenced or manipulated at various instance. The table also known as relation;
provide information pertaining to a specified entity.

Normalization of table is carried out to extent possible, while the normalizing tables, care
should be taken to make sure that the number of tables does not exceed the optimum level, so
that table maintenance is convenient and effective.

TABLE NAME: ADMIN

PRIMARY KEY: USER_NAME

FIELD NAME TYPE&SIZE DESCRIPTION

Username varchar(20) User name
Password varchar(40) Password

43