Veer Narmad South Gujarat University,

Surat.

Department of Information and

Communication Technology

M.Sc. (Information Technology) Programme

Project Report

8th Semester

M.Sc. (Information Technology)

5 Year Integrated Course

Year 2021 – 2022

Loan4You

Guided By : Submitted By :

Dr.Veena Jokhakar (InternalGuide) Gandhi Bianca V.(E1811018000610028)

Jaguwala Harsh A. (E1811018000610038)
 Veer Narmad South Gujarat University, Surat.

Department of Information and

Communication Technology

M.Sc. (Information Technology) Programme

Certificate

with Exam Seat Number: 2018013447

This is to certify that Mr./Ms Jaguwala Harsh AjayKumar
E1811018000610038 has worked on his/her part time project work
and PG Registration Number:
partial fulfillment of the requirements for 8th
entitled Loan4You at Department of ICT as a

Year Integrated course/, durir

Semester M.Sc.-
(Information Technology) |5
academic Year 2021-2022.

Date: 15/6/2022

Place: Dept. of ICT, VNSGU, Surat.

Internal Project Guide Head of the Department

M.Sc.(1.T.) 8th Semester Department of I.C.T.
Department of I.C.T. Veer Narmad South Gujarat University,
Veer Narmad South Gujarat University, Surat
Surat

PROJECT OF M. Sc. (1.T.) PROGRAMME

VEER NARMAD SOUTH GUJARAT UNVERSITY

Acedenic Yea
Approved Ly

EXAMINERS
Sr. No Topics Page no
1 Introduction
Eg. Current System – about the existing system (manual or s/w) 2

2 Proposed System
2.1 Scope
2.2 Objective 3
2.3 Advantages
2.4 Limitation
3 Environment Specification
3.1 Hardware & Software Requirements 4-5
3.2 Development Description
4 System Planning
4.1 Feasibility Study
4.2 Software Engineering Model 6-9
4.3 Risk Analysis
4.4 Project Schedule
4.4.1 Timeline Chart
5 System Analysis
5.1 Detailed SRS(Module wise specification with
Sections : description,i/ps,events,o/p,validations,constraints)
5.2 UML Diagram
5.2.1 Use Case Diagram 10-21
5.2.3 Class Diagram
5.2.4 Activity Diagram
5.2.5 Sequence Diagram
5.3 E-R Diagram
6 Software Design
6.1 Database Design 22-27

7 Testing
7.1 Unit Testing 28
7.2 Integration Testing
8
Interface Design sitemap followed with page snapshots 29-47

9 Future Enhancement 48
10 Reference 49
1. Introduction

Project Profile:

Institute Name : J . P . Dawer Institute of

Information Science and
Technology

Project Title: Loan4You

Group Members: Gandhi Bianca V.

Jaguwala Harsh A.

Internal Guide: Dr.Veena Jokhakar

Current System:
• Project definition:

Loan Management system

• Description:

It is JAVA based Loan management system in which Admin can

give the loan to the customer under certain conditions. Whole
system is managed by Admin.
2. Proposed System
2.1 Scope

In this system , The scope of this project is to provide

good communication between the client and the employee.
Client applying for loan and employee will check the client
details according to that employee will give loan.

2.2 Objective

❖ Admin
Admin can manage Client , Companies , employee and other
entities of database.

❖ Employee
Employee will manage their profile, can create customers, can
also assigned new call, coordinator, executor. Employee also
check about client existing loan and also check about call
history.

❖ Client
Client will manage their profile, can register as a member and
also decide to take loan and contact about company and loan
information.

2.3 Advantages:
Paper work, document work is less.

2.4 Limitations:
Not enough call Interaction.
3. Environment specification
3.1 Hardware and software Requirements:
• Hardware Configuration:

Processor 2.5 GHz

Hard Disk 1 TB
RAM 8 GB
Network Secured Internet Connection

• Softwre Configuration:
o Apache Net beans 12.0
o Google Chrome, Mozilla Firefox
o Xampp

• Project Configuration

Operating System: Windows10

Front - end: Java, Ajax
Back – end: My SQL
Other: HTML 5, CSS3, Bootstrap,
JSF
3.2 Development Description:
Loan4you is developed using Java web and JSF as front-end and Mysql for
database Management.

• Functional Development Description

➢ Show Profile
➢ User
➢ User Role
➢ Show Call
➢ Show Loginfiles

• Non-Functional Development Description

Usability:
• This section includes all of those requirements that effect
usability.
• We get the response within seconds.
• The software must have a simple, user-friendly interface so
customers can save time and confusion.

Reliability:
• The system is more reliable because of the qualities that are
inherited from the chosen platform java.
• The code built by using java is more reliable.

Interface:
• The user interface is based on the web browser. The application
is developed using JSF.
• The Interface design is aimed at a flexible front-end
communication to provide the user with clear information in
navigating a user-friendly interface is planned.
4. System Planning
4.1 Feasibility Study
● Feasibility study involves research relating to different aspects that go into
developing software.
● Feasibility study of the problem definition or requirement was done to
determine if the requirement can be solved effectively given the budgetary,
operational, technical and scheduled constraints in place.
● The aim of feasibility study is to identify the best solution under the
circumstances by identifying the effects of this solution on the organization.
● The feasibility of our project was judged on the basis of Time, Technology,
Available Resources and Project Size.
● Schedule Feasibility: The project would take 1 month and 15 days to
complete the core functionalities. So as far as the time is concerned, this project
is feasible.
● Technology: This project is build using JAVA with JSF etc. in Net Beans.
As we are already familiar with this development platform and the development
IDE, the technical risk is negligible. So this project is technically feasible.

● Resources: This project required:

• A Development server, in our case the ‘PayaraServer’.
• A Development IDE, in our case ‘Apache Net Beans’.
• A Database Server, in our case phpMyAdmin.
Also, we require proper tools for developing the documentation and All these
resources were available, so the project is feasible in context to the expected
resources for development.
Based on the above study it can be stated that designing and developing this
system is feasible if executed well within stated guidelines. So, based on these
positive results, the new system was approved for development.
4.2 Software Engineering Model:
Development of a Loan4You can be approached using a waterfall model.
Often considered the classic approach to the systems development life cycle, the
waterfall model describes a development method that is linear and sequential.
Waterfall development has distinct goals for each phase of development.

1. Requirements:
Firstly I gathered all in required information and requirements from
various websites.

2. Design
Firstly, We Design the database as per the requirement.

3. Implement:
After the above two steps, steps to implement our project was started. The
modules described below were first designed according to the
requirements and then they were made working.

4. Integration & Testing:

All the units developed in the implementation phase are integrated into
the system after their thorough checking. The entire system is tested for
any faults and failures.

5. Development:
Once the system is tested for both functional requirements and non-
functional requirements , the product is ready to deploy in the company
environment .

6. Maintenance:
Whichever tools we have used in your system, after some time it needs to
be updated. So, maintenance is necessary for the system.
4.3 Risk Analysis
Risk Management Information system (RMIS) is a computerized system
used for data collection and processing, information analysis and
generation of statistical trend reports for the identification and monitoring
of events, claims and finances.
Risk management in its best form may be to use it in a proactive manner
in identifying and managing the risks.
Here risks may arise like a server crashing down or risk may arise of a
Company make fake profile or sharing wrong data.
4.4 Project Schedule
4.4.1 TimeLine Chart:
5. System Analysis:
5.1 Detailed SRS :
The purpose of SRS is to write the functional and non-
functional system requirements that represent the
characteristic of Loan4You. This system must be designed as
user required. So, the complete requirement must be found.

Features:
Admin:
- Admin Can add , view , update , delete Client.
- Admin Can add , view , update , delete Branch.
- Admin Can add , view , update , delete Bank.
- Admin Can add , view , update , delete Loan Type.
- Admin Can add , view , update , delete Employee.
- Admin Can add , view , update , delete Calls.
- Admin Can add , view ,update , delete Existing Loan.
- Admin Can add , view ,update , delete Company.
- Admin Can add , view ,update , delete Documents.
- Admin Can add , view ,update , delete Login Files.
- Admin Can add, view ,update , delete Call History.
Client:

- Client Can do their Login.

- Client Can apply for Loans.
- Client Can view Profile.
- Client Can view Document.
- Client Can view Existing Loan.
- Client Can view Login Files.
- Client Can view Call History.

Employee:

- Employee Can do their Login.

- Employee Can manage Documents.
- Employee Can manage Client.
- Employee Can manage Calls.
- Employee Can manage Employee.

5.2 UML Diagram :

 5.2.1 Use Case Diagram :
• Admin
• Employee
• Customer
5.2.2 Class Diagram
5.2.3 Activity Diagram
Admin:
Client:
5.2.4 Sequence Diagram
Admin:
Employee:
Client(Customer)
5.3 ER Diagram
6. Software Design
6.1 Database Design

State_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
StateIdPK State id Int Primary Key
StateName State Name Varchar Not Null

Branch_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
BranchIdPK Branch id Int Primary Key
BranchName Name of Branch Varchar Not Null
BranchAddress Address of Branch Varchar Not Null

Bank_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
BankIdPK Bank id Int Primary Key
BankName Name of Bank Varchar Not Null
BankAddress Address of Bank Varchar Not Null
IFSCcode Ifsc code Varchar Not Null
ManagerName Name of the manager Varchar Not Null
ContactNo ContactNo of the Varchar Not Null
manager
Company_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
CompanyIdPK Company id Int Primary Key
CompanyName Name of Company Varchar Not Null
OwnerName Name of the owner Varchar Not Null
ContactNo Contact no Varchar Not Null
Manager Name Name of the manager Varchar Not Null

Loantype_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
LoanTypeIdPK LoanType id Int Primary Key
LoanTypeName Name of Loan Varchar Not Null

Document_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
DocumentIdPK Document id Int Primary Key
CallIDFK CallIDFK Int NotNull
DocumentType DocumentType Varchar Not Null
Path Image of the Varchar Not Null
Document
Addedby addedby Varchar Not Null
Addeddate addeddate Varchar TimeStamp

UserGroup_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
UserGroupname User group Name Varchar Not Null
UserName User Name Varchar Not Null
City_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
CityIdPK City id Int Primary Key
StateIdFk State Id Int Foreign Key
CityName City Name Varchar Not Null

CallAssignTelecaller_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
CTAssignIdPK Telecaller id Int Primary Key
TelecallerIdFk Employee id Int Foreign Key
CallIdFk Call Id Int Foreign key

CallAssigncoordinator_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
CCOAssignIdPK Call Coordinator id Int Primary Key
CoordinatorIdFk Employee id Int Foreign Key
CallIdFk Call Id Int Foreign key

CallAssignExecutive_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
CEAssignIdPK Call Executive id Int Primary Key
ExecutiveIdFk Employee Id Int Foreign Key
CallIdFk Call id Int Foreign Key
CallHistory_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
CallHistoryIdPK Call History id Int Primary Key
CallIdFk Call Id Int Foreign Key
Question Question Varchar Not Null
Answer Answer Varchar Not Null
Status Status No Varchar Not Null
Remark Remark of the call Varchar Not Null
Addeddate addeddate Varchar Not Null

Employee_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
EmployeeIdPK Employee id Int Primary Key
BrancIDFK Branch id Int Foreign Key
CityIdFk City Id Int Foreign Key
EmployeeFname Employee first Name Varchar NOT NULL
EmployeeType Email Type Varchar NOT NULL
MobileNo1 Contact Number Varchar NOT NULL
MobileNo2 Contact Number Varchar N
Address Address of Employee Varchar NOT NULL
Email Email Of Employee Varchar NOT NULL
Dob Dob of Employee Varchar NOT NULL
Gender Gender of Employee Varchar NOT NULL
Image Image of Employee Varchar NOT NULL
JoiningDate Date of Employee Varchar NOT NULL
Client_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
ClientIdPK Client id Int Primary Key
CompanyIdFk Company Id Int Foreign Key
CityIdFk City Id Int Foreign Key
ClientFname Employee first Name Varchar NOT NULL
Mobile1 Email Type Varchar NOT NULL
Mobile2 Contact Number Varchar NOT NULL
CurrentAddress Address of Employee Varchar NOT NULL
PermanentAddress Email Of Employee Varchar NOT NULL
Dob Dob of Employee Varchar NOT NULL
Email Gender of Employee Varchar NOT NULL
Salary Image of Employee Varchar NOT NULL
Gender Gender Varchar NOT NULL
Image Images of Customer Varchar NOT NULL

ExisitingLoan_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
ExsitingLoanIdPK Employee id Int Primary Key
BankIdFk Bank id Int Foreign Key
ClientIDFK Client id Int Foreign Key
CallIDFK Call id Int Foreign Key
LoanType LoanType Varchar Not NULL
CallIdFk Call Id Int Foreign Key
ClientIdFk Client Id Int Foreign Key
EMI EMI Varchar NOT NULL
PendingEMI Pendingemi Varchar NOT NULL
Interest Interest Varchar NOT NULL
Amount Total Amount Varchar NOT NULL
Tenure Tenure Varchar NOT NULL
PendingEMI Pending EMI Varchar NOT NULL
Intrest Intrest Varchar NOT NULL
Amount Amount Varchar NOT NULL
Tenure Tenure Varchar NOT NULL
Outstanding Outstanding Varchar NOT NULL
Login_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
LoginIdPK Login id Int Primary Key
CallIdFk Call Id Int Foreign Key
BankIdFk Bank Id Int Foreign Key
LoginDate Login date Varchar Foreign Key
LoginCity Login City Varchar NOT NULL
LoanAmount Loan Amount Varchar NOT NULL
LoanType Loan Type Varchar NOT NULL
Remark Remark Varchar NOT NULL
Tenure Tenure Varchar NOT NULL
RateOfIntrest Rate of Intrest Varchar NOT NULL
ProvidentFund Pf Varchar NOT NULL
Insurance Insurance Varchar NOT NULL
FinalRemark Final Remark Varchar NOT NULL
RejectedBy Rejected By Varchar NOT NULL
Status Status Varchar NOT NULL
DisburseDate Date Varchar NOT NULL
AddedBy addedby Varchar NOT NULL
AddedDate addeddate Varchar NOT NULL

Call_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
CallIdPK Login id Int Primary Key
BranchIdFk BranchId Int Foreign Key
EmployeeIdFk TeamLeaderid Int Foreign Key
ClientIDFK Client id Int Foreign Key
LoanTypeIDFK Loantypeid Int Foreign Key
AddedBy AddedBy Varchar NOT NULL
AddedDate AddedDate Varchar NOT NULL

Auth_Master
ELEMENT NAME ELEMENT DATA TYPES CONSTRAINT
DESCRIPTION
AuthIdPK Auth id Int Primary Key
Username User Name Varchar NOT NULL
Password Password Varchar NOT NULL
UserType UserType Varchar NOT NULL
UserId Clientid Varchar NOT NULL
7.Testing
7.1 Unit Testing
This testing focuses on verification effort on the smallest unit of software design - the component or
module. Using the component- level design description as a guide, important control paths are
tested to uncover errors within the boundary of the module. The relative complexity of tests and the
error those tests uncover is limited by constrained scope established for the unit testing. The unit
testing focuses on internal processing logic and data structure with boundaries of the component.
This type of testing can be conducted in parallel for multiple components.

Test Cases:

7.2 Unit Testing (1=True, 0=False):

Testing Result
Loan Admin Site
✓ Manage Bank
Add/Edit Bank 1
View/Remove Bank 1
✓ Manage Branch
Add/Edit Branch 1
View/Remove Branch 1
✓ Manage Client
Add/Edit Client 1
View/Remove Client 1
✓ Manage Employee
Add/Edit Employee 1
View/Remove 1
Employee
✓ Manage Call
Add/Edit Call 1
View/Remove Call 1
Loan Client site
Add/Show Client 1
Show ExistingLoan Client 1
Add Loan 1
8.Interface Design sitemap followed with page snapshots
Client :
Register
Login

ApplyLoan
Profile

CallHistory
LoginFiles

ExistingLoan
Logout

Admin :
Dashboard
AddBank

ShowBank
AddBranch

ShowBranch
AddCall

ShowCall
CallAssigned

View
CallHistory
AddExistingLoan
Adddocument
LoginFiles
AddClient
ShowClient
AddCompany

ShowCompany
AddEmployee

ShowEmployee
AddLoanType

ShowLoantype
Employee(TeleCaller) :

Employee(Executive/Coordinator)
9. Future Enhancements
Notification.
Emi payment.
10. References
https://stackoverflow.com/
https://www.youtube.com/
https://www.javatpoint.com/