Sie sind auf Seite 1von 28

ABSTRACT

The concept of this project is to design the loan management system.


Instead of going to a bank physically we can apply for loan in front of the
computer Using the internet facility. The project consists of three modules.
Here the customer logins with the registered username and password that he has
to get it from the bank. It is a mean through which we can manage the safety &
security of investment activities and at the same time it binds the various
customers. The key to successful loan management is a routine monitoring that
you do every day, every week, every month or every quarter for each loan The
frequency of monitoring activities is determined by how quickly something
could go wrong. Look at the credit file and other sources of information
concerning the status of the loan. Once you have spotted the trouble sign, first
review the current status of the loan and check your security

1
1. INTRODUCTION

OVERVIEW OF THE PROJECT

PROBLEM DEFINITION:
The concept of this project is to design the loan management system.
Instead of going to a bank physically we can apply for loan in front of the
computer Using the internet facility.
The project consists of three modules

 LOGIN SECTION
Here the customer logins with the registered username and password
that he has to get it from the bank. It is a mean through which we can
manage the safety & security of investment activities and at the same
time it binds the various customers.
 CHECKING ACCOUNT
The key to successful loan management is a routine monitoring
that you do every day, every week, every month or every quarter for each
loan The frequency of monitoring activities is determined by how quickly
something could go wrong.

 LOAN ACTIVITIES
Look at the credit file and other sources of information concerning
the status of the loan. Once you have spotted the trouble sign, first review
the current status of the loan and check your security

2
2. SYSTEM ANALYSIS

2.1 EXISTING SYSTEM:

A loan is a type of debt. Like all debt instruments, a loan entails the
redistribution of financial assets over time, between the lender and the
borrower. In a loan, the borrower initially receives or borrows an amount of
money, called the principal, from the lender, and is obligated to pay back or
repay an equal amount of money to the lender at a later time. Typically, the
money is paid back in regular installments, or partial repayments; in an annuity,
each installment is the same amount. The loan is generally provided at a cost,
referred to as interest on the debt, which provides an incentive for the lender to
engage in the loan. In a legal loan, each of these obligations and restrictions is
enforced by contract, which can also place the borrower under additional
restrictions known as loan covenants. Although this article focuses on monetary
loans, in practice any material object might be lent.

2.2 PROPOSED SYSTEM:


Online banking allows customers to conduct financial transactions on a
secure website operated by their retail or lending loan, credit union or building
society. It have many features and capabilities in common, but traditionally also
have some that are application specific Some online banking platforms support
account aggregation to allow the customers to monitor all of their accounts in
one place whether they are with their main bank or with other institutions.
Advantages:
 Easily available
 security
 Good support

3
3. SYSTEM SPECIFICATION

3.1 HARDWARE SPECIFICATION

 Processor : Pentium IV
 Motherboard : Intel Motherboard
 Main Memory : 256 MB
 Hard disk : 40 GB
 Floppy disk : 1.44 MB
 Monitor : Display type: 15.0’’ color
 Keyboard : Multi-media Keyboard

3.2 SOFTWARE SPECIFICATION

 Operating System : Windows 98/XP/NT


 Language : ASP.NET
 Development kit : Visual Studio 2008

4
4. ABOUT THE SOFTWARE

4.1 .NET FRAMEWORK

The Microsoft .NET Framework is a software framework for Microsoft


Windows operating systems. It includes a large library, and it supports several
programming languages which allows language interoperability (each language
can utilize code written in other languages.) The .NET library is available to all
the programming languages that .NET supports. The framework's Base Class
Library provides user interface, data access, database connectivity,
cryptography, web application development, numeric algorithms, and network
communications. The class library is used by programmers, who combine it
with their own code to produce applications. Programs written for the .NET
Framework execute in a software (as contrasted to hardware) environment,
known as the Common Language Runtime (CLR). The CLR is an application
virtual machine so that programmers need not consider the capabilities of the
specific CPU that will execute the program. The CLR also provides other
important services such as security, memory management, and exception
handling. The class library and the CLR together constitute the .NET
Framework. The .NET Framework is intended to be used by most new
applications created for the Windows platform. In order to be able to develop
and not just run applications, it is required to have Microsoft's SDK for
Windows 7 or .NET Framework 4 (or newer) or Visual Studio 2010 installed on
your computer.

5
FEATURES

Interoperability
Because computer systems commonly require interaction between new
and older applications, the .NET Framework provides means to access
functionality that is implemented in programs that execute outside the
.NET environment. Access to COM components is provided in the
System.Runtime.InteropServices and System.EnterpriseServices
namespaces of the framework; access to other functionality is provided
Using the P/Invoke feature.

Common Runtime Engine


The Common Language Runtime (CLR) is the execution engine of the
.NET Framework. All .NET programs execute under the supervision of
the CLR, guaranteeing certain properties and behaviors in the areas of
memory management, security, and exception handling.

Language Independence
The .NET Framework introduces a Common Type System, or CTS. The
CTS specification defines all possible data types and programming
constructs supported by the CLR and how they may or may not interact
with each other conforming to the Common Language Infrastructure
(CLI) specification. Because of this feature, the .NET Framework
supports the exchange of types and object instances between libraries and
applications written Using any conforming .NET language.

Base Class Library


The Base Class Library (BCL), part of the Framework Class Library
(FCL), is a library of functionality available to all languages Using the
.NET Framework. The BCL provides classes which encapsulate a
number of common functions, including file reading and writing, graphic
rendering, database interaction, XML document manipulation and so on.

Simplified Deployment
The .NET Framework includes design features and tools that help
manage the installation of computer software to ensure that it does not
6
interfere with previously installed software, and that it conforms to
security requirements.

Security
The design is meant to address some of the vulnerabilities, such as buffer
overflows, that have been exploited by malicious software.
Additionally, .NET provides a common security model for all
applications.

Portability
The design of the .NET Framework allows it to theoretically be platform
agnostic, and thus cross-platform compatible. That is, a program written
to use the framework should run without change on any type of system
for which the framework is implemented. While Microsoft has never
implemented the full framework on any system except Microsoft
Windows, the framework is engineered to be platform agnostic, and
cross-platform implementations are available for other operating systems
Microsoft submitted the specifications for the Common Language
Infrastructure (which includes the core class libraries, Common Type
System, and the Common Intermediate Language), the C# language, and
the C++/CLI language to both ECMA and the ISO, making them
available as open standards. This makes it possible for third parties to
create compatible implementations of the framework and its languages
on other platforms.

4.2ASP.NET

7
ASP.NET is a web application framework developed and marketed by
Microsoft to allow programmers to build dynamic web sites, web applications
and web services. It was first released in January 2002 with version 1.0 of the
.NET Framework, and is the successor to Microsoft's Active Server Pages
(ASP) technology. ASP.NET is built on the Common Language Runtime
(CLR), allowing programmers to write ASP.NET code Using any supported
.NET language. The ASP.NET SOAP extension framework allows ASP.NET
components to process SOAP messages.
ASP.NET uses a visited composites rendering technique. During
compilation, the template (.aspx) file is compiled into initialization code which
builds a control tree (the composite) representing the original template. Literal
text goes into instances of the Literal control class, and server controls are
represented by instances of a specific control class. The initialization code is
combined with user-written code (usually by the assembly of multiple partial
classes) and results in a class specific for the page. The page doubles as the root
of the control tree.Actual requests for the page are processed through a number
of steps. First, during the initialization steps, an instance of the page class is
created and the initialization code is executed.
This produces the initial control tree which is now typically manipulated
by the methods of the page in the following steps. As each node in the tree is a
control represented as an instance of a class, the code may change the tree
structure as well as manipulate the properties/methods of the individual nodes.
Finally, during the rendering step a visitor is used to visit every node in the tree,
asking each node to render itself Using the methods of the visitor. The resulting
HTML output is sent to the client. After the request has been processed, the
instance of the page class is discarded and with it the entire control tree. This is
a source of confusion among novice ASP.NET programmers who rely on class
instance members that are lost with every page request/response cycle

4.3 MS ACCESS

8
Microsoft Office Access, previously known as Microsoft Access, is a
pseudo-relational database management system from Microsoft that combines
the relational Microsoft Jet Database Engine with a graphical user interface and
software-development tools. It is a member of the Microsoft Office suite of
applications, included in the Professional and higher editions or sold separately.
In mid-May 2010, the current version Microsoft Access 2010 was released by
Microsoft in Office 2010.

Microsoft Office Access 2007 was the prior version. Access stores data
in its own format based on the Access Jet Database Engine. It can also import
or link directly to data stored in other applications and databases. Software
developers and data architects can use Microsoft Access to develop application
software, and "power users" can use it to build simple applications.[citation needed]
Like other Office applications, Access is supported by Visual Basic for
Applications, an object-oriented programming language that can reference a
variety of objects including DAO (Data Access Objects), ActiveX Data
Objects, and many other ActiveX components. Visual objects used in forms and
reports expose their methods and properties in the VBA programming
environment, and VBA code modules may declare and call Windows operating-
system functions.

The original concept of Access was for end users to be able to "access"
data from any source. Other uses include: the import and export of data to many
formats including Excel, Outlook, ASCII, dBase, Paradox, FoxPro, SQL
Server, Oracle, ODBC, etc. It also has the ability to link to data in its existing
location and use it for viewing, querying, editing, and reporting. This allows the
existing data to change and the Access platform to always use the latest data. It
can perform heterogeneous joins between data sets stored across different
platforms. Access is often used by people downloading data from enterprise
level databases for manipulation, analysis, and reporting locally.

5. PROJECT DESCRIPTION

5.1 PROBLEM DEFINITION

9
The concept of this project is to design the loan management
system. Instead of going to a bank physically we can apply for loan in front
of the computer Using the internet facility. Contact the Customer Find out
the actual reason. Sometimes a possible trouble sign turn out to be nothing
but a minor, e,g a loan repayment was delayed due to an oversight or the
book keeper was sick. However in case of a serious problem, Cos most
current financial performance and revised projections must be asked for

5.2 MODULE DESCRIPTION


The project consists of three modules

 LOGIN SECTION
Here the customer logins with the registered username and password
that he has to get it from the bank. It is a mean through which we can
manage the safety & security of investment activities and at the same
time it binds the various customers.
 CHECKING ACCOUNT
The key to successful loan management is a routine monitoring
that you do every day, every week; every month or every quarter for each
loan the frequency of monitoring activities is determined by how quickly
something could go wrong.

 LOAN ACTIVITIES
Look at the credit file and other sources of information concerning
the status of the loan. Once you have spotted the trouble sign, first review
the current status of the loan and check your security

10
6. CONCLUSION

Here the development process for loan management system is done and

the performance of the current system is better the older ones. so it can be used

for large scale sector banking It includes certain covenants which gives you a

right to take action if performance deteriorated to levels that increase risk to a

level to warrant taking action.

7. APPENDIX

7.1 SAMPLE SOURCE CODE

11
Login.aspx

Using System;
Using System.Data;
Using System.Configuration;
Using System.Collections;
Using System.Web;
Using System.Web.Security;
Using System.Web.UI;
Using System.Web.UI.WebControls;
Using System.Web.UI.WebControls.WebParts;
Using System.Web.UI.HtmlControls;
Using System.Data.OleDb;

Public partial class login : System.Web.UI.Page


{
Protected void Page_Load(object sender, EventArgs e)
{

}
Protected void Button1_Click(object sender, EventArgs e)
{

}
Protected void Button1_Click1(object sender, EventArgs e)
{
If (TextBox1.Text.Trim() == "admin" &
TextBox2.Text.Trim()=="admin")
{
Response.Redirect("manager.aspx");
}

}
}

12
Banking login

Using System;
Using System.Data;
Using System.Configuration;
Using System.Collections;
Using System.Web;
Using System.Web.Security;
Using System.Web.UI;
Using System.Web.UI.WebControls;
Using System.Web.UI.WebControls.WebParts;
Using System.Web.UI.HtmlControls;
Using System.Data.OleDb;

Public partial class manager : System.Web.UI.Page


{
Protected void Page_Load(object sender, EventArgs e)
{

}
Protected void Button1_Click(object sender, EventArgs e)
{
try
{
OleDbConnectioncn=newOleDbConnection("Provider=Microsoft.Jet.Ol
edb.4.0;Data Source=D:/db/loan.mdb");
OleDbCommand cmd = new OleDbCommand();
cmd.Connection = cn;
cmd.CommandText="select*fromloan1wherecusid="+TextBox1.Text.Tri
m()+" ";
if (cn.State == ConnectionState.Closed)
{
cn.Open();
}
13
string str;
str = cmd.ExecuteScalar().ToString();

if (str != null)
{
Response.Redirect("balance.aspx");
}
else
{
Response.Write("There is No such user");

}
}

catch (Exception ex)


{
Response.Write(ex.Message);

}
}
}

Account status

Using System;
Using System.Data;
Using System.Configuration;
Using System.Collections;
Using System.Web;
14
Using System.Web.Security;
Using System.Web.UI;
Using System.Web.UI.WebControls;
Using System.Web.UI.WebControls.WebParts;
Using System.Web.UI.HtmlControls;
Using System.Data.OleDb;

Public partial class balance : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{

}
protected void Button1_Click(object sender, EventArgs e)
{
try
{
OleDbConnection cn = new
OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data
Source=D:/db/loan.mdb");
OleDbCommand cmd = new OleDbCommand();
cmd.Connection = cn;
cmd.CommandText = "select * from loan1 where
cusid="+TextBox3.Text.Trim()+" ";
OleDbDataAdapter ad=new OleDbDataAdapter(cmd);
DataTable dt=new DataTable();
dt.Clear();
ad.Fill(dt);
if(dt.Rows.Count > 0)
{
TextBox1.Text=dt.Rows[0].ItemArray[2].ToString();
}

else
{
Response.Write("There is No such user");
15
}
}

catch (Exception ex)


{
Response.Write(ex.Message);

}
}
protected void Button2_Click(object sender, EventArgs e)
{
try
{
OleDbConnection cn = new
OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data
Source=D:/db/loan.mdb");
OleDbCommand cmd = new OleDbCommand();
cmd.Connection = cn;
cmd.CommandText = "select * from loan1 where cusid=" +
TextBox3.Text.Trim() + " ";
OleDbDataAdapter ad = new OleDbDataAdapter(cmd);
DataTable dt = new DataTable();
dt.Clear();
ad.Fill(dt);
if (dt.Rows.Count > 0)
{
TextBox2.Text = dt.Rows[0].ItemArray[3].ToString();
}

else
{
Response.Write("There is No such user");

}
}
16
catch (Exception ex)
{
Response.Write(ex.Message);

}
protected void Button3_Click(object sender, EventArgs e)
{
try
{
OleDbConnection cn = new
OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data
Source=D:/db/loan.mdb");
OleDbCommand cmd = new OleDbCommand();
cmd.Connection = cn;
cmd.CommandText = "select * from loan1 where cusid=" +
TextBox3.Text.Trim() + " ";
OleDbDataAdapter ad = new OleDbDataAdapter(cmd);
DataTable dt = new DataTable();
dt.Clear();
ad.Fill(dt);
if (dt.Rows.Count > 0)
{
string bal;
bal= dt.Rows[0].ItemArray[2].ToString();
int bal1 = int.Parse(bal);
if ( bal1 >= 50000)
{
Response.Redirect("LoanSection.aspx");
}
else if (bal1 > 1000000)
{
Response.Redirect("LoanSection.aspx");
}
17
else if (bal1 <= 10000)
{
Response.Redirect("notelgible.aspx");
}

else
{
Response.Write("There is No such user");

}
}

catch (Exception ex)


{
Response.Write(ex.Message);

}
}
}

Loan section

Using System;
Using System.Data;
Using System.Configuration;
Using System.Collections;
Using System.Web;
Using System.Web.Security;
Using System.Web.UI;
Using System.Web.UI.WebControls;
Using System.Web.UI.WebControls.WebParts;
18
Using System.Web.UI.HtmlControls;
Using System.Data.OleDb;

Public partial class LoanSection : System.Web.UI.Page


{
protected void Page_Load(object sender, EventArgs e)
{

}
protected void TextBox1_TextChanged(object sender, EventArgs e)
{

}
protected void Button1_Click(object sender, EventArgs e)
{
try
{
OleDbConnection cn = new
OleDbConnection("Provider=Microsoft.Jet.Oledb.4.0;Data
Source=D:/db/lend.mdb");
OleDbCommand cmd = new OleDbCommand();
cmd.Connection = cn;
cmd.CommandText = "select * from lend1 where ltype='" +
TextBox2.Text.Trim() + "' ";
OleDbDataAdapter ad = new OleDbDataAdapter(cmd);
DataTable dt = new DataTable();
dt.Clear();
ad.Fill(dt);
if (dt.Rows.Count > 0)
{
TextBox3.Text = dt.Rows[0].ItemArray[0].ToString();
TextBox4.Text = dt.Rows[0].ItemArray[1].ToString();
TextBox1.Text = dt.Rows[0].ItemArray[3].ToString();
}

else
19
{
Response.Write("There is No such user");

}
}

catch (Exception ex)


{
Response.Write(ex.Message);

}
}
protected void Button2_Click(object sender, EventArgs e)
{
Response.Redirect("sucsess.aspx");
}
}

7.2 INSTRUCTIONS TO RUN THE PROJECT

STEP1: INSTALL VISUAL STUDIO 2008

STEP2: IN FILE MENU OPEN THE PROJECT FILE

STEP3: FIRST BUILD THE APPLICATION

STEP4: COMPILE THE APPLICATION

STEP5: PLACE THE DATABASE FILE IN A CORRECT POSITION

20
STEP6: STOP THE PROCESS

21
7.3 SCREENSHOTS

Login page:

22
Bank account login:

23
Account status:

24
Loan details

Success page
25
26
DATABASE:

27
Not eligible:

28

Das könnte Ihnen auch gefallen