Loan managementPDF

Loan Management System 2018-19
____________________________________________________________________________
CHAPTER 1
INTRODUCTION
All organizations whether large or small have a form of record(s) for their finances. Financial
institutions are organizations that offer money lending services to people and business
organizations have written records of their clients. A loan management system is a database
management system used to automate the loan services of financial institutions. It serves the
purpose of easy file retrieval and entry. The automation of loan services not only provides secure
services of the loan details to the customer and the organization but also serves the organization
huge sums of money that would have been spent on stationary in a case where a file system is
used. In short the system will enable money lending organizations to provide good customer
relations by being able to preserve the integrity of the loan details, to enable easy file access and
retrieval and increase security on customer details. This project is concerned with the design,
development and implementation of a database that will enable money lending organizations to
record the lending of money, proposed period of servicing the loan, reasons for borrowing,
customer details and generating reports about loans.
Dept of CSE, YDIT 1

oan Management System
L 2018-19
__________________________________________________________________________________
BACKGROUND AND MOTIVATION
The managing of huge data effectively and efficiently for efficient results, storing of confidential
information such as the customers details and the loan details, in such a way that the database
can be modified proves to be cumbersome. * High costs spent on stationary for the loan
application forms * The system is error prone.
* It is easy to tamper with the files with the current system. * Lack of properly integrated system
to capture customer details and loan application details at the same time. * Either no reports
generating in the current system or they are generated with great difficulty. Reports take time to
generate in the current system.
Daily many new customers visit the bank, so adding the new customer’s details
and keeping the records using it is very easy. There are many other options also like changing
repo rate, adding new accounts etc.
New and unique ids are given to everyone who gets registered over this system and to the
customers who take the loan. There are also the options to check the customer’s loan amount,
interest rate and the unpaid amount.
Amount paid by any customer or can be saved on it and it is easy to calculate daily that the
money is collected.Bank staff members like a manager, the cashier can the also check the details
of their customers like if any customer has not paid the monthly amount from the last three
months then it will notify itself to the user.
It is easy to calculate money and handle account on monthly basis also. This system also has an
option to use the backup, that means if we are backing up the database it can never be lost.
Dept. of CSE,YDIT 2
L 2018-19
__________________________________________________________________________________
METHODOLOGY
The methodology of online loan management system this is that it does what it is meant for. A
methodology describes what a software system should do, while non- methodology place
constraints on how the system will do so.
methodology specify a function that a system or system component must be able to perform. It
can be documented in various ways. The most common ones are written descriptions in
documents and use cases.
Few of its methodology of online loan management system are as given below:-User data should
be fed into the system: this system is doing that properly in user entity.Admin can verify the user
and can help them register on loan management system.The user can add the customers: users
are able to add customers, which are taking a loan from the bank.
Dept. of CSE,YDIT 3
L 2018-19
__________________________________________________________________________________
CHAPTER 2
SYSTEM ANALYSIS
2.1 Existing System

here is need for upgrading existing system with loan management software which can solve
problems that we face in existing system. This software application can save time, provide better
service, clear analysis about data and report generation.
Main objective of this project is to provide solution for organizations for managing
employees loans details with response to monthly salary and leaves and hikes. This system will
provide detailed explanation for every month payments with cuttings and final salary. Employees
can download reports for analysis.
2.2 Proposed System

In the Previous System,Details are Stored Manually in papers,to share the
details between employees was a Financial drawback. Updations in the details is a tedious task.
But a new system was proposed to overcome the above drawbacks.
Functionalities and advantages of proposed system are:
Ø Data is Centralized which has overcome the Sharing problem in previous system.
Ø As data is Maintained electronically, it’s easy for a person to update the details, which has
overcome the tedious updation in previous system.
Ø Maintenance is easy and performance is good.
Ø Mainly the system has automated the Transportation Process.
Dept. of CSE,YDIT 4
L 2018-19
__________________________________________________________________________________
2.2.1 SCOPE OF THE PROJECT

The problem occurred before having computerized system includes:
File lost When computerized system is not implemented file is always lost because of human
environment.Sometimes due to some human error there may be a loss of records.
File damaged When a computerized system is not there file is always lost due to some accident
like spilling of water by some member on file accidentally.
Besides some natural disaster like floods or fires may also damage the files.
Difficult to search record
When there is no computerized system there is always a difficulty in searching records if the
records are large in number .
Space consuming
After the number of records become large the space for physical storage of file and records also
increases if no computerized system is implemented.
Cost consuming
As there is no computerized system the to add each record paper will be needed which will increase the
cost for the management of library.
Dept. of CSE,YDIT 5
L 2018-19
__________________________________________________________________________________
2.2.2 PROJECT FEATURES

Our system has two main interfaces. One is for customers and the other is for the user which
manages all the bank accounts. Along with these, we have other interfaces which can be
discussed as below:
Admin:
Admin is the one who verifies the user or the customer which is going to register itself on the
loan management system. There can be only one account of admin and all other accounts can be
either of user or customer.
Admin cannot see the details of the bank loan accounts, only user and customer can see it.
Admin can only add or delete accounts.
Login:
After registration one can log in the system as the operator of the system on the behalf of user.
After this, he has the other user interfaces available for further actions like adding and deleting
doctors and other staff members etc.
Adding New Accounts:
The first option that is provided in the loan management system is adding new customers or
users which are most important. When a new customer goes to a bank, then he or she might have
an account or might want to open one.
A customer who has account in the bank can only take loan so even if a user comes to take a
loan, his or her account must be opened in the bank first. So, adding new customers’ details in
the database is most important and then the user does the other tasks.
Dept. of CSE,YDIT 6
L 2018-19
__________________________________________________________________________________
In the details person’s address, phone number, disease or problem and some other things are
asked.
Keeping Loan details:
Another function that this software provides is keeping the details of the customer loan. For
example, how many instalments have been paid by the user and how many are left.
How many instalments were not paid by the customer in the past etc. when will the loan be over
and what kind of loan is taken by the customer.
Maintaining Records:
A customer can ask for the details of its anytime. May be later in any other loan if he requires it.
It is very important to maintain the records of patients properly. This feature is given in this loan
management system.
It keeps all the data saved and by entering the customer id or name it can be fetched whenever it
is required.
Monthly installments and interest rate:
As the repo rate gets increased or decreased by the RBI then the banks also increase their interest
rate. Therefore, it is very important to know the interest rate to the customer according to which
customer will pay the amount.
A number of the instalments might get increased or decreased if the customer wants.
Dept. of CSE,YDIT 7
L 2018-19
__________________________________________________________________________________
Bank details:
As this system can be used for any bank so there is an option to add the details about the bank
and then the details about the bank branches according to which the customers taking a loan from
specific bank branches will be added.
This system is designed keeping the things in mind that there might be many different banks
using this system. After adding the details about a particular bank which are required only once
all other details and bank branches can be added.
If there is a customer who wants to take a loan from a bank branch which is not present in the
loan system then the loan cannot be given as it might be a fraud case.
User Panel
1. User Registration- User can register through user registration form
2. User Login- User can login through login form
3. Forgot Password-user can retrieve password through forgot password link
4. User Dashboard
5. User Profile-User can manage own profile
6. Change Password- User Can change own password
7. User access log- User can watch last login details
Dept. of CSE,YDIT 8
L 2018-19
__________________________________________________________________________________
CHAPTER 3
REQUIREMENT SPECIFICATIONS
3.1 DETAILS OF SOFTWARE
3.1.1 HTML
HTML is used to create and save web document. E.g. Notepad/Notepad++
3.1.2 CSS
(Cascading Style Sheets) Create attractive Layout.
3.1.3 JavaScript
It is a programming language, commonly use with web browsers.
3.1.4 PHP
Hypertext Preprocessor (PHP) is a technology that allows software developers to
create dynamically generated web pages, in HTML, XML, or other document types, as per client
request. PHP is open source software.PHP is a server-side scripting language designed primarily
for web development but also used as a general-purpose programming language. Originally
created by Rasmus Lerdorf in 1994, the PHP reference implementation is now produced by The
PHP Development Team. PHP originally stood for Personal Home Page, but it now stands for
the recursive acronym PHP: Hypertext Preprocessor.
PHP code may be embedded into HTML or HTML5 markup, or it can be used in combination
with various web template systems, web content management systems and web frameworks.
PHP code is usually processed by a PHP interpreter implemented as a module in the web server
or as a Common Gateway Interface (CGI) executable. The web server software combines the
results of the interpreted and executed PHP code, which may be any type of data, including
images, with the generated web page. PHP code may also be executed with a command-line
interface (CLI) and can be used to implement standalone graphical applications.
The standard PHP interpreter, powered by the Zend Engine, is free software released under the
PHP License. PHP has been widely ported and can be deployed on most web servers on almost
every operating system and platform, free of charge.
The PHP language evolved without a written formal specification or standard until 2014, leaving
the canonical PHP interpreter as a de facto standard. Since 2014 work has gone on to create a
formal PHP specification.
During 2014 and 2015, a new major PHP version was developed, which was numbered PHP 7.
The numbering of this version involved some debate. While the PHP 6 Unicode experiment had
never been released, several articles and book titles referenced the PHP 6 name, which might
Dept. of CSE,YDIT 9
L 2018-19
__________________________________________________________________________________
have caused confusion if a new release were to reuse the name. After a vote, the name PHP 7
was chosen.
The foundation of PHP 7 is a PHP branch that was originally dubbed PHP next generation
(phpng). It was authored by Dmitry Stogov, Xinchen Hui and Nikita Popov, and aimed to
optimize PHP performance by refactoring the Zend Engine to use more compact data structures
with improved cache locality while retaining near-complete language compatibility. As of 14
July 2014, WordPress-based benchmarks, which served as the main benchmark suite for the
phpng project, showed an almost 100% increase in performance. Changes from phpng are also
expected to make it easier to improve performance in the future, as more compact data structures
and other changes are seen as be better suited for a successful migration to a just-in-time (JIT)
compiler.[44] Because of the significant changes, the reworked Zend Engine is called Zend
Engine 3, succeeding Zend Engine 2 used in PHP 5.
Because of major internal changes in phpng, it must receive a new major version number of
PHP, rather than a minor PHP 5 release, according to PHP's release process. Major versions of
PHP are allowed to break backward-compatibility of code and therefore PHP 7 presented an
opportunity for other improvements beyond phpng that require backward-compatibility breaks,
including wider use of exceptions, reworking variable syntax to be more consistent and
complete, and the deprecation or removal of various legacy features.PHP 7 also introduced new
language features, including return type declarations for functions, which complement the
existing parameter type declarations, and support for the scalar types (integer, float, string, and
boolean) in parameter and return type declarations.
3.1.5 MYSQL
MySql is a database, widely used for accessing querying, updating, and managing data in
databases.
MySQLis an open-source relational database management system (RDBMS). Its name is a
combination of "My", the name of co-founder Michael Widenius's daughter, and "SQL", the
abbreviation for Structured Query Language. The MySQL development project has made its
source code available under the terms of the GNU General Public License, as well as under a
variety of proprietary agreements. MySQL was owned and sponsored by a single for-profit firm,
the Swedish company MySQL AB, now owned by Oracle Corporation. For proprietary use,
several paid editions are available, and offer additional functionality.
MySQL is a central component of the LAMP open-source web application software stack (and
other "AMP" stacks). LAMP is an acronym for "Linux, Apache, MySQL, Perl/PHP/Python".
Applications that use the MySQL database include: TYPO3, MODx, Joomla, WordPress,
phpBB, MyBB, and Drupal. MySQL is also used in many high-profile, large-scale websites,
including Google (though not for searches), Facebook, Twitter, Flickr, and YouTube.
Dept. of CSE,YDIT 10
L 2018-19
__________________________________________________________________________________
MySQL is written in C and C++. Its SQL parser is written in yacc, but it uses a home-brewed
lexical analyzer. MySQL works on many system platforms, including AIX, BSDi, FreeBSD,
HP-UX, eComStation, i5/OS, IRIX, Linux, macOS, Microsoft Windows, NetBSD, Novell
NetWare, OpenBSD, OpenSolaris, OS/2 Warp, QNX, Oracle Solaris, Symbian, SunOS, SCO
OpenServer, SCO UnixWare, Sanos and Tru64. A port of MySQL to OpenVMS also exists.
3.2 SYSTEM REQUIREMENTS

3.2.1 HARDWARE CONFIGURATION
Operating system: Window 10
Hard disks: 40GB
RAM: 256 MB
3.2.2 SOFTWARE CONFIGURATION
HTML, CSS, PHP

My-SQL server & Apache (Xampp)
L 2018-19
__________________________________________________________________________________
CHAPTER 4
SYSTEM DESIGN
4.1 USE CASE DIAGRAM

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case analysis. Its purpose is to present a graphical
overview of the functionality provided by a system in terms of actors, their goals (represented as
use cases), and any dependencies between those use cases.
The main purpose of a use case diagram is to show what system functions are performed for
which actor. Roles of the actors in the system can be depicted.
Use Case diagrams are formally included in two modeling languages defined by the OMG: the
Unified Modeling Language (UML) and the Systems Modeling Language (SysML).
Interaction among actors is not shown on the use case diagram. If this interaction is essential to a
coherent description of the desired behavior, perhaps the system or use case boundaries should
be re-examined. Alternatively, interaction among actors can be part of the assumptions used in
the use case.
Use cases
Use case describes a sequence of actions that provide something of measurable value to an actor
and is drawn as a horizontal ellipse.
Actors
An actor is a person, organization, or external system that plays a role in one or more interactions
with the system.
System boundary boxes (optional)
A rectangle is drawn around the use cases, called the system boundary box, to indicate the scope
of system. Anything within the box represents functionality that is in scope and anything outside
the box is not.
L 2018-19
__________________________________________________________________________________
FIG 4.1 : USE CASE DIAGRAM FOR LOAN MANAGEMENT SYSTEM
L 2018-19
__________________________________________________________________________________
4.2 ER DIAGRAM
What is an Entity Relationship Diagram (ERD)?

An entity relationship diagram (ERD) shows the relationships of entity sets stored in a database.
An entity in this context is a component of data. In other words, ER diagrams illustrate the
logical structure of databases.
At first glance an entity relationship diagram looks very much like a flowchart. It is the
specialized symbols, and the meanings of those symbols, that make it unique.
ER Diagram Uses
When documenting a system or process, looking at the system in multiple ways increases the
understanding of that system. ERD diagrams are commonly used in conjunction with a data flow
diagram to display the contents of a data store. They help us to visualize how data is connected
in a general way, and are particularly useful for constructing a relational database.
L 2018-19
__________________________________________________________________________________
FIG 4.2: ER DIAGRAM FOR LOAN MANAGEMENT SYSTEM
L 2018-19
__________________________________________________________________________________
4.3 RELATIONAL DATABASE DESIGN
4.3.1 LOAN
L_ id GRP_id L_amount L_interest L_duration
4.3.2 APPLICANT DETAILS

VOTER_id APPL_name L_category ACC_no. ACC_ status
4.3.3 BANK
BANK_id BANK_name MNGER_id MNGER_name status
4.3.4 PAYMENT HISTORY

L_id APPL_ name DIV_id installments interests installment status
4.3.5 TRIGGER TABLE

L_id VOTER_id BANK_id amt_remaining
4.3.6 USER TABLE

id username name password email active code
L 2018-19
__________________________________________________________________________________
4.4 DATABASE NORMALIZATION

4.4.1 FIRST NORMAL FORM
The relation is in 1NF if it has no repeating groups.All tables has no repeating groups as they are
in 1NF.
4.3.1 LOAN

4.3.3 BANK

4.3.5 TRIGGER TABLE

4.3.6 USER TABLE

L 2018-19
__________________________________________________________________________________
4.4.2 SECOND NORMAL FORM:

A relation is in second normal form if it is already in first normal form and it has no partial
dependency.
1.LOAN:
The absence of partial dependency in relation takes it into 2NF without any modification.
2.APPLICANT DETAILS:
3.BANK:
4.TRIGGER:
No partial dependenCies.
5.USER TABLE:
Tables:
4.3.1 LOAN

4.3.3 BANK

4.3.5 TRIGGER TABLE

4.3.6 USER TABLE

L 2018-19
__________________________________________________________________________________
.4.3 THIRD NORMAL FORM:

4
A relation is said to be in third normal form if it is already in first and second normal form and
has no transitive dependency.
1.LOAN:
In question depends upon category L_id name with another table so it is in third normal form.
2.APPLICANT DETAILS:
In application details depends upon group name with another table so it is in third normal form.
3.BANKS:
In every attribute depends on primary key i.e. mnger_id. so it is in third normal form.
5.TRIGGER TABLE:
In trigger every attribute depends on primary key i.e.id so it is in third normal form.
6.USER:
In user every attribute depends on primary key i.e. id so it is in third normal form.
Tables:
4.3.1 LOAN

4.3.3 BANK

4.3.5 TRIGGER TABLE

4.3.6 USER TABLE

L 2018-19
__________________________________________________________________________________
CHAPTER 5
SYSTEM IMPLEMENTATION
5.1 MODULE DESCRIPTION
Our system has two main interfaces. One is for customers and the other is for the user which
manages all the bank accounts. Along with these, we have other interfaces which can be
discussed as below:
Admin:
Admin is the one who verifies the user or the customer which is going to register itself on the
loan management system. There can be only one account of admin and all other accounts can be
either of user or customer.
Admin cannot see the details of the bank loan accounts, only user and customer can see it.
Admin can only add or delete accounts.
Login:
After registration one can log in the system as the operator of the system on the behalf of user.
After this, he has the other user interfaces available for further actions like adding and deleting
doctors and other staff members etc.
Adding New Accounts:
The first option that is provided in the loan management system is adding new customers or
users which are most important. When a new customer goes to a bank, then he or she might have
an account or might want to open one.
A customer who has account in the bank can only take loan so even if a user comes to take a
loan, his or her account must be opened in the bank first. So, adding new customers’ details in
the database is most important and then the user does the other tasks.
L 2018-19
__________________________________________________________________________________
In the details person’s address, phone number, disease or problem and some other things are
asked.
Keeping Loan details:
Another function that this software provides is keeping the details of the customer loan. For
example, how many instalments have been paid by the user and how many are left.
How many instalments were not paid by the customer in the past etc. when will the loan be over
and what kind of loan is taken by the customer.
Maintaining Records:
A customer can ask for the details of its anytime. May be later in any other loan if he requires it.
It is very important to maintain the records of patients properly. This feature is given in this loan
management system.
It keeps all the data saved and by entering the customer id or name it can be fetched whenever it
is required.
Monthly installments and interest rate:
As the repo rate gets increased or decreased by the RBI then the banks also increase their interest
rate. Therefore, it is very important to know the interest rate to the customer according to which
customer will pay the amount.
A number of the instalments might get increased or decreased if the customer wants.
Bank details:
L 2018-19
__________________________________________________________________________________
As this system can be used for any bank so there is an option to add the details about the bank
and then the details about the bank branches according to which the customers taking a loan from
specific bank branches will be added.
This system is designed keeping the things in mind that there might be many different banks
using this system. After adding the details about a particular bank which are required only once
all other details and bank branches can be added.
If there is a customer who wants to take a loan from a bank branch which is not present in the
loan system then the loan cannot be given as it might be a fraud case.
L 2018-19
__________________________________________________________________________________
CHAPTER 6
SNAPSHOTS OF THE APPLICATION
ADMIN LOGIN PROFILE
FIG 6.1
This page is used to operate the user's account admin. This page is used by the admin to login by
entering username and password to enter into the welcome page of the data record.
L 2018-19
__________________________________________________________________________________
DASHBOARD
FIG 6.2
This page is used to know the details of the product available.
L 2018-19
__________________________________________________________________________________
ALL GROUPS
FIG 6.3
In this page ,we can see all the groups and add any of the new groups.
L 2018-19
__________________________________________________________________________________
ALL LOANS
FIG 6.4
In this page ,we can manage and approve all loans.
L 2018-19
__________________________________________________________________________________
ALLOT NEW LOANS
FIG 6.5
In this page , we can manage all user and allot new loans to the applicant.
L 2018-19
__________________________________________________________________________________
ADMIN PASSWORD UPDATE
FIG 6.6
I n this page,add manage admin passwords and update it.
L 2018-19
__________________________________________________________________________________
PAYMENT HISTORY
FIG 6.7
in this page the admin can manage all payment history about installments and interests of loan
taken.
L 2018-19
__________________________________________________________________________________
CHAPTER 7
SYSTEM TESTING
TEST CASES
LOGIN
No Test cases Case Type Expected Actual Result Pass/Fail
Result
1 1 Login Website 1.Correct Successful login Successful Pass
Username and
Password
2.Login with Login Stayed in Pass

wrong unsuccessful ndex.php
Username and
Password
2 Validation Test Required field Field should not User have to Pass
case validation be empty enter the value
TABLE 7.1
UPLOAD DATA IN DATABASE
Result
1 1 Upload Data 1.Insert Query Successful Successful Pass
Executed Upload
L 2018-19
__________________________________________________________________________________
1 2.Insert wrong Unsuccessful Successful Pass

Query Upload
TABLE 7.2
VIEW DATA OF DATABASE
Result
1 1 View Data SelectQuery Successful Successful Pass
Executed
2.Select wrong Unsuccessful Successful Pass

Query ExecutedDisplay
TABLE 7.3
UPDATE DATA OF DATABASE

No Test cases Case Type Expected Result Actual ResultPass/Fail
1 Update Data 1.Update Query Successfully Successful Pass

Executed Updated
2.Update wrong Unsuccessfully Successful Pass

Query Executed Updated
TABLE 7.4
DELETE DATA OF DATABASE
No Test cases Case Type Expected Result Actual Result Pass/Fail
1 1 Delete Data 1.Delete QuerySuccessfully Successful Pass

Executed Deleted
2.Delete wrong Unsuccessfully Successful Pass

Query ExecutedDeleted
TABLE 7.5
L 2018-19
__________________________________________________________________________________
CONCLUSION
Finally, in Online loan management system, the outcome of all the hard work done for Loan
management system is here. It is a software which helps the user to work with the different banks
and their branches easily.This web application reduces the amount of manual data entry and
gives greater efficiency. The User Interface of it is very friendly and can be easily used by
anyone. It also decreases the amount of time taken to write customer’s details and other modules.
At the end, we can say that this, software is performing all the tasks accurately and is doing the
work for which it is made.
L 2018-19
__________________________________________________________________________________
BIBLIOGRAPHY
OOKS REFERRED
B
Database Management System : Ramez Elmasri and Shankant B.Navathe,Ramakrishna and
Gehrke.
EBSITES
W
www.google.com
www.w3school.com
www.youtube.com
www.wikipedia.com
www.mysql.com
www.php.net
www.lynda.com
www.udemy.com
www.tutorialspoint.com
www.zend.com
L 2018-19
__________________________________________________________________________________

Loan managementPDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Loan managementPDF

Caricato da

Copyright:

Formati disponibili

Loan Management System 2018-19

Dept of CSE, YDIT 1

BACKGROUND AND MOTIVATION

constraints on how the system will do so.

documents and use cases.

2.1 Existing System

2.2 Proposed System

2.2.1 SCOPE OF THE PROJECT

2.2.2 PROJECT FEATURES

Adding New Accounts:

Keeping Loan details:

Monthly installments and interest rate:

3.2 SYSTEM REQUIREMENTS

3.2.2 SOFTWARE CONFIGURATION

HTML, CSS, PHP

4.1 USE CASE DIAGRAM

​FIG 4.1 : USE CASE DIAGRAM FOR LOAN MANAGEMENT SYSTEM

What is an Entity Relationship Diagram (ERD)?

​FIG 4.2: ER DIAGRAM FOR LOAN MANAGEMENT SYSTEM

4.3 RELATIONAL DATABASE DESIGN

4.3.2 APPLICANT DETAILS

4.3.4 PAYMENT HISTORY

4.3.5 TRIGGER TABLE

4.3.6 USER TABLE

4.4 DATABASE NORMALIZATION

4.3.2 APPLICANT DETAILS

4.3.4 PAYMENT HISTORY

4.3.5 TRIGGER TABLE

4.3.6 USER TABLE

4.4.2 SECOND NORMAL FORM:

4.3.2 APPLICANT DETAILS

4.3.4 PAYMENT HISTORY

4.3.5 TRIGGER TABLE

4.3.6 USER TABLE

​ .4.3 THIRD NORMAL FORM:

4.3.2 APPLICANT DETAILS

4.3.4 PAYMENT HISTORY

4.3.5 TRIGGER TABLE

4.3.6 USER TABLE

Adding New Accounts:

Keeping Loan details:

Monthly installments and interest rate:

SNAPSHOTS OF THE APPLICATION

ADMIN LOGIN PROFILE

ALLOT NEW LOANS

ADMIN PASSWORD UPDATE

2.Login with Login Stayed in Pass

1 2.Insert wrong Unsuccessful Successful Pass

2.Select wrong Unsuccessful Successful Pass

UPDATE DATA OF DATABASE

1 Update Data 1.Update Query Successfully Successful Pass

2.Update wrong Unsuccessfully Successful Pass

1 1 Delete Data 1.Delete QuerySuccessfully Successful Pass

2.Delete wrong Unsuccessfully Successful Pass

Potrebbero piacerti anche

FIG 4.1 : USE CASE DIAGRAM FOR LOAN MANAGEMENT SYSTEM

FIG 4.2: ER DIAGRAM FOR LOAN MANAGEMENT SYSTEM

.4.3 THIRD NORMAL FORM: