LOAN MANAGEMENT SYSTEM PROJECT REPORT

LOAN MANAGEMENT SYSTEM PROJECT REPORT

PROJECT REPORT

LOAN MANAGEMENT SYSTEM PROJECT REPORT (LGI Monitoring)

LOAN MANAGEMENT SYSTEM PROJECT FULL REPORT

PROJECT SOURCE CODE

LOAN CLAIM PROCESSING PROJECT IN ASP.NET 

SOURCE CODE

LOAN APPROVAL SYSTEM IN JAVA WITH SOURCE CODE

• FREE DOWNLOAD ALL THE PROJECT REPORTS WITH SOURCE CODE FROM HERE

Most of the bank out-sources pre-loan process to loan agencies to reduce the burden and let the agencies pickup the information from customers and verify it before it is being forwarded to the actual bank for approval of loan.

Lending Tree is an interface which facilitates a customer to apply for a loan from on-line and to track the status from time-to-time along with aiding the loan approval agency to verify and accept/reject the customer file. Lending Tree is unique in such a way, it not only helps the customers but also the loan agency to check the pending, assign it to a departments, complete the formalities and procedures between the departments and  arrive at decisions to very fact in addition to providing a transparency system for every one.

The customer can directly apply for a loan by selecting a bank and loan type from the list available. The application is received by loan agency who will have three departments- PickUp, Verifiaction and Legal. This system can be controlled by the administrator. First he will look at the application received and allot the application for a particular employee of pickup department. The employee will go and make a physical verification of the documents at the customers and receives the documents necessary for the loan. Then he logs into this system and forwards the application to the verification department which will verify the whereabouts of the person, his organization, his salary particulars etc. and then forwards the application with a status verified. Then application reaches the legal department. The legal department people will verify the builder details and when satisfied sends their report to the administrator.

The administrator or final approving authority views both types of reports, Viz, the reports from verification department and the report legal department. This will help him to take a decision regarding whether to forward it to the bank or not. The same is communicated to the customer.

The customer can at any time view the status of his application and can send any messages to the administrator and can get clarifications from him. Thus the lending tree s/w helps to simplify the loan system along with making the work easy.

There are 5 types of users who can get immense benefits from system:

• The customer - seeking the loan and information related to banks and loans
• The administrator of loan agency who will take track the decision of bank to approve or disapprove and also controls the overall system functionality
• The PickUp department users who picks up the details and documents from customers
• The verification department user who make a physical verification of the details submitted by the customer
• The legal department user who verifies the legality of the documents of the builder and construction.

Technologies Used: J2Se, Servlets, JSP, JDBC and Java Script.

Existing System: LOAN MANAGEMENT SYSTEM PROJECT

                        Here the existing system is a manual one using which the banking agent can’t maintain the effectively by sharing across different branches with proper security and can’t track details easily. It doesn’t provide proper co-ordination between different departments of the company. It doesn’t allow the customer to check the status of his file in proper way which leads customer dis-satisfaction.

Ø  Doesn’t provide faster and effective system

Ø  Doesn’t provide good co-ordination between departments

Ø  Doesn’t provide effective forwarding system to move the file from one level to another

Ø  Doesn’t user-friendly interface

Ø  Difficulty in generating different reports as per the business requirement

Ø  Doesn’t facilitate the services from online

Proposed System: LOAN MANAGEMENT SYSTEM PROJECT

The online automated system with web-based architecture can support issues like.

Ø  This system maintains the information related different departments and stored at a central DB, which leads easy accessibility and consistency

Ø  Interest rates of different banks and the other details are also available at the click of a mouse.

Ø  Customer can apply for a loan and track his file details from online.

Ø  The decision process in faster and more consistent

Ø  Provides good communication between two departments

Ø  Provides a facility to generate the reports very easily.

FEASIBILITY  REPORT: LOAN MANAGEMENT SYSTEM PROJECT

Feasibility study  is  the  high  level  capsule  version  of  the  entire  requirement  analysis  process. The objective  of  feasibility  study  is  to  determine  whether  the  proposed  system  can  be   developed  with  available  resources.

There are three steps to be followed for determining the feasibility study of proposed system.

Ø  Technical  Feasibility

Ø  Operational  Feasibility

Ø  Economical  Feasibility

Technical Feasibility: It  is  concerned  with  hardware  and  software  feasibility. In  this  study, one  has  to  test  whether the  proposed  system  can  be  developed  using  existing  technology  or  not. If  new  technology  is  required ,what  is  the  likely  hood  that  it  can  be  developed ?The  organization  for  which   the  system  to  be  developed    is  not  provided online services .Hence  there  is  a  requirement  of  new  hardware  and  software  technology  for  the  deployment  of  proposed  system. As  per  client  requirements  the  system  to  be  developed  should  have  speed  response  because  of  fast  change  info, programming  productivity, reliability, security, scalability, integration  and  availability. To meet these requirements  I  as  a  developer  found  jsp1.1  as  a  right  choice  because  of  its  features  platform independence,modularity  and  reusability.

Operational Feasibility:  Operational  feasibility  determines  whether  the  proposed  system  satisfied  the  user  objectives  and  can  be  fitted  in  to  current  system  operation.The  proposed  system  “Lending Tree”  can  be  justified  as  operationally  feasible  basing  on  the  following.

Ø  The  methods  of  processing  and  presentation  are  completely  acceptable  by  the  clients  because  they  meet  all  the  user  and  client  requirements.

Ø  The  clients  have  been  involved  during  the  preparation  of  requirement  analysis  and  design  process.

Ø  The  system  will  certainly  satisfy  the  user  objectives  and  it  will  also  enhance  their  capability.

Ø  The  system  can  be best  fitted  into  current  operation  and  requires  little  training  to  both  administrator  and  dealer. With  the  help  of   this  system  customer  to  place  order  requires  simple  data  entry  through  forms  provided.The  proposed  system  is  completely user  friendly.

Economical Feasibility: This includes an evaluation of  all  incremental  costs  and  benefits  expected  if  proposed  system  is  implemented. costs-benefit  analysis  which  is  to be  performed  during  economical  feasibility  delineates costs  for  project  development  and  weighs  them  against  benefits  of  system. In this the proposed system replaces   the manual process of receiving  orders  which  benefits  the  organization  to  get  more  orders  and  good  response. So developing this system is economically feasible to organization.

Application design

Users:

The major functionality of this product is divided into two categories.

                 1. Administrative User Functions.

                 2. PickUp Dept User Functions.     

                 3. Verification Dept User Functions.        

                 4. Legal Dept User Functions

                5.  Customer Functions

Administrative User Functions: Administrators can perform the following task.

·        Create/Update/Delete New Banks Info

·        View the list of banks

·        Create/Update/Delete New Departments.

·        View List of Departments

·        Create/Update/Delete Employee Info

·        View the list of Banks

·         Manage loans info related to different banks

·         View the list applications and assign it to pickup dept employees

·         Sending messages to customers

·         View the pending applications

·         Update the status of the application

·         Generate reports

PickUp Dept User Functions: This user can perform the following task

·        View the list of applications assigned to him

·        Store the list of documents info that the customer has submitted

·         Forward the application to verification

Verification Dept User Functions: This user can perform the following task

·        View the list applications forwarded by different employees of PickUp Dept

·        Verify the details

·        Forward applications to Administrator

Legal Dept User Functions: This user can perform the following task

• Register Builder Info
• Store the documents info
• Generate APF no for the builder

Customer Functions: This user can perform the following task

·         View the list of banks and their interest rates info

• Apply for loan in a bank
• Check the loan application status
• Messages
  

Number of Modules:

The system after careful analysis has been identified to present itself with the following modules:

1.Administrator Module: This module is responsible for coordinating the other modules. It allows the administrator create, update/delete and view the banks information and it allows admin to create create/update/delete and view different departments and it can create logins for different employees in each and every department and it can manage loan interest rates of different banks etc. It facilitates to view the new applicant details and assign it to different employees in pickup department initially. It allows the administrator to view customer application finally from verification department and builder details from legal department and then store bank final opinion in this application. It also allows to generate different reports for business analysis. It provides messaging facility for the administrator for commnication.

2.PickUp Module: This module allows the pickup department to view their applications which are assigned to them, collect the documents according to the checklist and forward it to verification department.

3.Verification Module: This module allows the employees of verification department employees to view the forwarded application from pickup department and check the details as per the documents and forward it to next level.

4.Legal Module: This module allows the employee of legal departments to check verify legal documents of the builder, verify the check list and then generate the APF no for the builder.

 5.Customer Module: This module allows the customer to view the interest rates of the banks which we are dealing, apply for a loan, check the status of the loan at any point of time and communicate with the administrator if necessary. It allows messaging facility for communication.

Requirements at the Server-side:

            Hard Ware requirements:

1.      Intel Pentium processor family with a speed of 800 MHz. or above

2.      256 MB RAM

3.      40 GB above hard disk as per the requirements of the org

Hardware Requirements

Pentium IV processes architecture

1.   256 MB RAM.

2.   40 GB Hard Disk Space.

3.   Ethernet card.

Software specification

·                     Windows XP as operating system

·                     Apache Tomcat-5.0 web server

·                     Oracle 10g as database server

·                     Jdk1.5.0 as Java Software

SRS Document

Intended Audience And Reading Suggestions

The document is prepared keeping is view of the academic constructs of my Bachelors Degree / Masters Degree from university as partial fulfillment of my academic purpose the document procedure that that has been followed by me, while the system was studied and developed. The general document was provided by the industry as a reference guide to understand my responsibilities in developing the system, with respect to the requirements that have been pin pointed to get the exact structure of the system as stated by the actual client.

The system as stated by my project leader the actual standards of the specification were desired by conducting a series of interviews and questionnaires. The collected information was organized to form the specification document and then was modeled to suite the standards of the system as intended.

Document Conventions:

The overall documents for this project use the recognized modeling standards at the software industries level.

·    ER-Modeling to concentrate on the relational states existing upon the system with respect to Cardinality.

·    The Physical dispense, which state the overall data search for the relational key whereas a transactions is implemented on the wear entities.

·    Unified modeling language concepts to give a generalized blue print for the overall system.

Scope of The Development Project: LOAN MANAGEMENT SYSTEM PROJECT

Database Tier:  The concentration is applied by adopting the Oracle10g database. SQL is taken as the standard query language. The overall business rules are designed by using the power of PL/SQL components like dynamic queries, stored procedures stored functions etc.

User Tier: The use interface is developed is a browses specific environment to have web based architecture. The components are designed using HTML standards and Java server pages power the dynamic of the page design.

Data Base Connectivity Tier

The communication architecture is designed by concentrated on the standards of servlets and JSP. The database connectivity is established using the Java Database connectivity.

Role Of Oracle In Database

Oracle 10g is one of the many database services that plug into a client / server model.  It works efficiently to manage resources, a database information, among the multiple clients requesting & sending.

Structured Query Language (SQL)

SQL is an inter-active language used to query the database and access data in database. SQL has the following features:

1.  It is a unified language.

2.  It is a common language for relational database

3.  It is a non-procedural language.

Introduction To Oracle

ORACLE is a comprehensive operating environment that packs the power of a mainframe system into user microcomputer. It provides a set of functional programs that user can use as tools to build structures and perform tasks. Because application developed on oracle are completely portable to environment and then move it into a multi user platform. Users do not have to be an expert to appreciate ORACLE, but the better user understands the programmer, the more productivity and creativity you will use the tools it provides.

What is a Relational Database Management System

A relational database management system (RDBMS) can perform a wide array of tasks. It acts as a transparent interface between the physical storage and a logical presentation of data. It provides a set of more or less flexible and sophisticates tools for handling information. User can use this tool to:

ü  Define a database

ü  Query the database

ü  Add, edit and delete data

ü  Modify the structure of database

ü  Secure data from public access

ü  Communicate within the networks

ü  Export and Import data

Because it gives so much control over data, a relational DBMS can also save as the foundation for products that generate application and extract data.

A Database Management system may be called fully relational if it supports:

1.    Relational Databases and

2.    A language that is at least as powerful as the relational algebra

Client Server Technologies - LOAN MANAGEMENT SYSTEM PROJECT

Client Server

Over view:

With the varied topic in existence in the fields of computers, Client Server is one, which has generated more heat than light, and also more hype than reality. This technology has acquired a certain critical mass attention with its dedication conferences and magazines. Major computer vendors such as IBM and DEC, have declared that Client Servers is their main future market. A survey of DBMS magazine reveled that 76% of its readers were actively looking at the client server solution. The growth in the client server development tools from $200 million in 1992 to more than $1.2 billion in 1996.

Client server implementations are complex but the underlying concept is simple and powerful. A client is an application running with local resources but able to request the database and relate the services from separate remote server. The software mediating this client server interaction is often referred to as MIDDLEWARE.

The typical client either a PC or a Work Station connected through a network to a more powerful PC, Workstation, Midrange or Main Frames server usually capable of handling request from more than one client. However, with some configuration server may also act as client. A server may need to access other server in order to process the original client request.

The key client server idea is that client as user is essentially insulated from the physical location and formats of the data needs for their application. With the proper middleware, a client input from or report can transparently access and manipulate both local database on the client machine and remote databases on one or more servers. An added bonus is the client server opens the door to multi-vendor database access indulging heterogeneous table joins.

What is a Client Server

Two prominent systems in existence are client server and file server systems. It is essential to distinguish between client servers and file server systems. Both provide shared network access to data but the comparison dens there! The file server simply provides a remote disk drive that can be accessed by LAN applications on a file by file basis. The client server offers full relational database services such as SQL-Access, Record modifying, Insert, Delete with full relational integrity backup/ restore performance for high volume of transactions, etc. the client server middleware provides a flexible interface between client and server, who does what, when and to whom.

Why Client Server

Client server has evolved to solve a problem that has been around since the earliest days of computing: how best to distribute your computing, data generation and data storage resources in order to obtain efficient, cost effective departmental an enterprise wide data processing. During mainframe era choices were quite limited. A central machine housed both the CPU and DATA (cards, tapes, drums and later disks). Access to these resources was initially confined to batched runs that produced departmental reports at the appropriate intervals. A strong central information service department ruled the corporation. The role of the rest of the corporation limited to requesting new or more frequent reports and to provide hand written forms from which the central data banks were created and updated. The earliest client server solutions therefore could best be characterized as “SLAVE-MASTER”.

Time-sharing changed the picture. Remote terminal could view and even change the central data, subject to access permissions. And, as the central data banks evolved in to sophisticated relational database with non-programmer query languages, online users could formulate adhoc queries and produce local reports with out adding to the MIS applications software backlog. However remote access was through dumb terminals, and the client server remained subordinate to the Slave\Master.

Front end or User Interface Design

The entire user interface is planned to be developed in browser specific environment with a touch of Intranet-Based Architecture for achieving the Distributed Concept.

The browser specific components are designed by using the HTML standards, and the dynamism of the designed by concentrating on the constructs of the Java Server Pages.

Communication or Database Connectivity Tier

The Communication architecture is designed by concentrating on the Standards of Servlets and Enterprise Java Beans. The database connectivity is established by using the Java Data Base Connectivity.

The standards of three-tire architecture are given major concentration to keep the standards of higher cohesion and limited coupling for effectiveness of the operations.

Features of The Language Used

In my project, I have chosen Java language for developing the code.

About Java

Initially the language was called as “oak” but it was renamed as “Java” in 1995. The primary motivation of this language was the need for a platform-independent (i.e., architecture neutral) language that could be used to create software to be embedded in various consumer electronic devices.

Ø  Java is a programmer’s language.

Ø  Java is cohesive and consistent.

Ø  Except for those constraints imposed by the Internet environment, Java gives the programmer, full control.

Finally, Java is to Internet programming where C was to system programming.

Importance of Java to the Internet

Java has had a profound effect on the Internet. This is because; Java expands the Universe of objects that can move about freely in Cyberspace. In a network, two categories of objects are transmitted between the Server and the Personal computer. They are: Passive information and Dynamic active programs. The Dynamic, Self-executing programs cause serious problems in the areas of Security and probability. But, Java addresses those concerns and by doing so, has opened the door to an exciting new form of program called the Applet.

Java can be used to create two types of programs

Applications and Applets: An application is a program that runs on our Computer under the operating system of that computer. It is more or less like one creating using C or C++. Java’s ability to create Applets makes it important. An Applet is an application designed to be transmitted over the Internet and executed by a Java –compatible web browser. An applet is actually a tiny Java program, dynamically downloaded across the network, just like an image. But the difference is, it is an intelligent program, not just a media file. It can react to the user input and dynamically change.

Features Of Java

Security

Every time you that you download a “normal” program, you are risking a viral infection. Prior to Java, most users did not download executable programs frequently, and those who did scanned them for viruses prior to execution. Most users still worried about the possibility of infecting their systems with a virus. In addition, another type of malicious program exists that must be guarded against. This type of program can gather private information, such as credit card numbers, bank account balances, and passwords. Java answers both these concerns by providing a  “firewall” between a network application and your computer.

When you use a Java-compatible Web browser, you can safely download Java applets without fear of virus infection or malicious intent.

Portability

For programs to be dynamically downloaded to all the various types of platforms connected to the Internet, some means of generating portable executable code is needed .As you will see, the same mechanism that helps ensure security also helps create portability. Indeed, Java’s solution to these two problems is both elegant and efficient.    

The Byte code

The key that allows the Java to solve the security and portability problems is that the output of Java compiler is Byte code. Byte code is a highly optimized set of instructions designed to be executed by the Java run-time system, which is called the Java Virtual Machine (JVM). That is, in its standard form, the JVM is an interpreter for byte code.

Translating a Java program into byte code helps makes it much easier to run a program in a wide variety of environments. The reason is, once the run-time package exists for a given system, any Java program can run on it.

Although Java was designed for interpretation, there is technically nothing about Java that prevents on-the-fly compilation of byte code into native code. Sun has just completed its Just In Time (JIT) compiler for byte code. When the JIT compiler is a part of JVM, it compiles byte code into executable code in real time, on a piece-by-piece, demand basis. It is not possible to compile an entire Java program into executable code all at once, because Java performs various run-time checks that can be done only at run time. The JIT compiles code, as it is needed, during execution.

Java, Virtual Machine (JVM)

Beyond the language, there is the Java virtual machine. The Java virtual machine is an important element of the Java technology. The virtual machine can be embedded within a web browser or an operating system. Once a piece of Java code is loaded onto a machine, it is verified. As part of the loading process, a class loader is invoked and does byte code verification makes sure that the code that’s has been generated by the compiler will not corrupt the machine that it’s loaded on. Byte code verification takes place at the end of the compilation process to make sure that is all accurate and correct. So byte code verification is integral to the compiling and executing of Java code.

Database design         

Database Tables: The total number of database tables that were identified to build the system is 6. The major part of the

Database is categorized as

   1. Transactional components: The Transactional components are useful in recording the transactions made by the system. All the projects information was handled by these components

   2. Data Dictionary components: These components are used to store the major information like Employee details, project details, requirement details, availability details, allocations details etc.

   3. General components: These components are used to store the general information like login information etc.

Database Tables:

To create the application the following tables are used

Banks:      Contains details of Banks

Dept:                    Contains details of different departments

Emp:                     Contains employee information

Customers:          Contains customers information

Customer_Loan_Details:           Contains customers loan information

Customers_Verification:            Contains customer verification details info

Bank_Loan:  Contains Banks loan information

Admin:  Contains admin details

Messages : Contains messages information

Banks:

Column Name	Type (size)	Constraint
BankID	Number (12)	Primarykey
BankName	Varchar2 (12)
Branch	Varchar2 (12)
Address	Varchar2 (12)

Dept:

Column name	Type (size)	Constraint
DeptID	Number (12)	Primarykey
DeptName	Varchar2 (12)

Emp:

Column name	Type (size)	Constraint
EmpID	Number (12)	Primary key
EName	Varchar2 (12)
Design	Varchar2 (14)
Dept	Varchar2 (13)
Address	Varchar2 (12)
Phone	Number (15)
Email	Varchar (25)

Customers:

Column name	Type (size)	Constraint
CustName	Varchar2 (25)
CustAddress	Varchar2 (50)
Qualification	Varchar2 (30)
Occupation	Varchar2 (30)
CompanyBS	Varchar2 (30)
ComAddress	Varchar2 (50)
ContactNo	Number (20)	PrimaryKey
Salary	Number (20)
Designation	Varchar2 (40)
Gender	Varchar2 (10)
State	Varchar2 (30)
AssignTo	Varchar2 (30)
EmailID	Varchar2 (30)
BuilderName	Varchar2 (30)
BankName	Varchar2 (30)
CDate	Date
SanctionDate	Date

Customer_Loan_Details

Column name	Type (size)	Constraint
CustName	Varchar2 (30)
Email	Varchar2 (30)
Ags	Date
Wo	Varchar (30)
Ps	Varchar (30)
Ol	Int (11)
Ap	Varchar (50)
Pi	Varchar (50)
Itr	Decimal (18,0)
Pan	Varchar (50)

Customers_Verification:

Column name	Type (size)	Constraint
CustName	Varchar2 (30)
Email	Varchar (30)
Phone	Number (12)
Ap	Varchar2 (12)
Cd	Varchar2 (12)
Pe	Varchar2 (13)

Messages:

Column name	Type (size)	Constraint
MsgID	Number (20)	PrimaryKey
From	Varchar2 (50)
To	Varchar2 (50)
MsgSubject	Varchar2 (50)
Msg	Varchar2 (100)
CDate	Date

Admin:

Column name	Type (size)	Constraint
LName	Varchar2 (20)	PrimaryKey
Password	Varchar2 (20)

Bank_Loans:

Column name	Type (size)	Constraint
BankName	Varchar2 (20)
LoanType	Varchar2 (20)
InterestRate	Number (10,5)
LoanID	Number(10)	PrimaryKey

Builder_Details:

Column name	Type (size)	Constraint
BuilderName	Varchar2 (20)
OffAddress	Varchar2 (30)
RegNo	Number (20)	PrimaryKey
PanNumber	Varchar2 (20)
Phone	Number (12)
Email	Varchar2 (50)
Website	Varchar2 (50)
LP	Varchar2 (20)
PNo	Varchar2 (20)
Noc	Varchar2 (20)
BP	Varchar2 (20)
EC	Varchar2 (20)
APF No	Number (30)
Reason	Varchar2 (100)

Cust:

Column name	Type (size)	Constraint
CName	Varchar2 (40)	PrimaryKey
Cpwd	Varchar2 (20)

Design Document

·         The entire system is projected with a physical diagram which specifics the actual storage parameters that are physically necessary for any database to be stored on to the disk. The overall systems existential idea is derived from this diagram.

·         The relation upon the system is structure through a conceptual ER-Diagram, which not only specifics the existential entities but also the standard relations through which the system exists and the cardinalities that are necessary for the system state to continue.

ER-Diagrams

·         The entity Relationship Diagram (ERD) depicts the relationship between the data objects. The ERD is the notation that is used to conduct the date modeling activity the attributes of each data object noted is the ERD can be described resign a data object descriptions.

·         The set of primary components that are identified by the ERD are

          u Data object        u Relationships

           u Attributes         u Various types of indicators.

·         The primary purpose of the ERD is to represent data objects and their relationships.

Unified Modeling Language Diagrams

·         The unified modeling language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

·         A UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows.

·         User Model View

                                         i.    This view represents the system from the users perspective.

                                       ii.    The analysis representation describes a usage scenario from the end-users perspective.

Structural model view

u    In this model the data and functionality are arrived from inside the system.

u     This model view models the static structures.

Behavioral Model View

u    It represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the user model and structural model view.

Implementation Model View

u  In this the structural and behavioral as parts of the system are represented as they are to be built.

Environmental Model View

In this the structural and behavioral aspects of the environment in which the system is to be implemented are represented.

UML Diagrams:

 Program Design Language

·            The program design language is also called as structured English or pseudopodia. PDL is a generic reference for a design language PDL looks like a modern language. The difference between PDL and real programming language lies in the narrative text embedded directly within PDL statements.

The characteristics required by a design language are:

Ø   A fixed system of keywords that provide for all structured constructs date declaration and modularity characteristics.

Ø  A free syntax of natural language that describes processing features.

Ø  Date declaration facilities that should include both simple and complex data structures.

Ø  Subprogram definition and calling techniques that support various nodes of interface description.

PDL syntax should include constructs for subprogram definition, interface description date declaration techniques for structuring, conditions constructs, repetition constructs and I/O constructs.

PDL can be extended to include keywords for multitasking and/or concurrent processing interrupt handling, interposes synchronization the application design for which PDL is to be used should dictate the final form for the design language.

Testing - LOAN MANAGEMENT SYSTEM PROJECT

Testing is the process of detecting errors. Testing performs a very critical role for quality assurance and for ensuring the reliability of software. The results of testing are used later on during maintenance also.

Psychology of Testing

The aim of testing is often to demonstrate that a program works by showing that it has no errors. The basic purpose of testing phase is to detect the errors that may be present in the program. Hence one should not start testing with the intent of showing that a program works, but the intent should be to show that a program doesn’t work. Testing is the process of executing a program with the intent of finding errors.

Testing Objectives

The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. Stating formally, we can say,

Ø  Testing is a process of executing a program with the intent of finding an error.

Ø  A successful test is one that uncovers an as yet undiscovered error.

Ø  A good test case is one that has a high probability of finding error, if it exists.

Ø  The tests are inadequate to detect possibly present errors.

Ø  The software more or less confirms to the quality and reliable standards.

Levels of Testing

In order to uncover the errors present in different phases we have the concept of levels of testing. The basic levels of testing are as shown below…

                        Client Needs                                                   

                       

                     Requirements                                                    

                                               

                          Design                                                          

                            Code                                                           

System Testing

The philosophy behind testing is to find errors. Test cases are devised with this in mind. A strategy employed for system testing is code testing.

Code Testing:

This strategy examines the logic of the program. To follow this method we developed some test data that resulted in executing every instruction in the program and module i.e. every path is tested. Systems are not designed as entire nor are they tested as single systems. To ensure that the coding is perfect two types of testing is performed or for that matter is performed or that matter is performed or for that matter is performed on all systems.

Types Of Testing

Ø  Unit Testing

Ø  Link Testing

Unit Testing

Unit testing focuses verification effort on the smallest unit of software i.e. the module. Using the detailed design and the process specifications testing is done to uncover errors within the boundary of the module. All modules must be successful in the unit test before the start of the integration testing begins.

In this project each service can be thought of a module. There are so many modules like Login, HWAdmin, MasterAdmin, Normal User, and PManager. Giving different sets of inputs has tested each module. When developing the module as well as finishing the development so that each module works without any error. The inputs are validated when accepting from the user.

In this application developer tests the programs up as system. Software units in a system are the modules and routines that are assembled and integrated to form a specific function. Unit testing is first done on modules, independent of one another to locate errors. This enables to detect errors. Through this errors resulting from interaction between modules initially avoided.

Link Testing

Link testing does not test software but rather the integration of each module in system. The primary concern is the compatibility of each module. The Programmer tests where modules are designed with different parameters, length, type etc.

Integration Testing

After the unit testing we have to perform integration testing. The goal here is to see if modules can be integrated proprerly, the emphasis being on testing interfaces between modules. This testing activity can be considered as testing the design and hence the emphasis on testing module interactions.

In this project integrating all the modules forms the main system. When integrating all the modules I have checked whether the integration effects working of any of the services by giving different combinations of inputs with which the two services run perfectly before Integration.

System Testing

Here the entire software system is tested. The reference document for this process is the requirements document, and the goal os to see if software meets its requirements.

Here entire ‘ATM’ has been tested against requirements of project and it is checked whether all requirements of project have been satisfied or not.

Acceptance Testing

Acceptance Test is performed with realistic data of the client to demonstrate that   the software is working satisfactorily. Testing here is focused on external behavior of the system; the internal logic of program is not emphasized.

In this project ‘Network Management Of Database System’ I have collected some data and tested whether project is working correctly or not.

Test cases should be selected so that the largest number of attributes of an equivalence class is exercised at once. The testing phase is an important part of software development. It is the process of finding errors and missing operations and also a complete verification to determine whether the objectives are met and the user requirements are satisfied.

White Box Testing

This is a unit testing method where a unit will be taken at a time and tested thoroughly at a statement level to find the maximum possible errors. I tested step wise every piece of code, taking care that every statement in the code is executed at least once. The white box testing is also called Glass Box Testing.

I have generated a list of test cases, sample data. which is  used to  check  all  possible combinations of execution paths through the code at every module level.

Black Box Testing

This testing method considers a module as a single unit and checks the unit at interface and communication with other modules rather getting into details at statement level. Here the module will be treated as a block box that will take some input and generate output. Output for a given set of input combinations are forwarded to other modules.

 Criteria Satisfied by Test Cases

1)   Test cases that reduced by a count that is greater than  one, the number of additional test cases that much be designed to achieve reasonable testing.

2)   Test cases that tell us something about the presence or absence of classes of errors, rather than an error associated only with the specific test at hand.

  

S No	Test Case	Action taken
1	Enter Wrong username and password for Admin at the login form.	Displays error message
2	Enter correct username and password for Admin at the login form	Displays Home Page
3	Create users of departments PickUp, Verifiaction and Legal	New Users of these departments will be created
4	Register the customer info	Customer Info has to be registered
5	Create a loan information related to a bank	New Loan Info has to be stored Related to that bank
6	Register a customer	It registers a new customer
7	Login as customer with correct username and password.	Displays customer home page
8	Select a bank and get the interest rates	Displays Interests Rates
9	Apply for the loan	Posts the application
10	View the loan applications by logging as admin	Displays new application
11	Forward the application to Pickup from admin	Forwards to an employee in Pickup Dept
12	Forward the application to verification Dept from Pickup dept	Forwards to Verification Dept
13	Forward the application to Admin Dept from Verification Dept	Forwards to Admin
14	Enter Builder Info	Creates APF No
15	Update the status of the application by admin finally	Updates Status
16	Check the status	Displays current status of the application
17	Send a message to a user	It Sents a message

Installation

·            The database as it is developed by Oracle10g can be installed only by creating the tables in scott/tiger user with the help of LendingTree.sql file.

·            Using Web components like JSP and servlets needs proper deployment on a top of a webserver called Apache Tomcat

·            Copy the database driver inside common/lib of Tomcat

·            Start the Server

·            Open a browser and give the URL to access the application

Conclusions And Recommendations

The entire project has been developed and deployed as per the requirements stated by the bank agents consultancy, it is found to be bug free as per the testing standards that are implemented.  It helps Bank Agents and Customers of Lending Tree and provides effective communication between them to provide the services very promptly with proper procedures. Any specification-untraced errors will be concentrated in the coming versions, which are planned to be developed in near future. The system at present does not take care payments info through this application since it requires payment gateway. Our company is planning to integrate in future and do it as an enhancement.

Bibliography:

References for the Project Development were taken from the following Books and Web Sites.

 Oracle

PL/SQL Programming by Scott Urman

SQL complete reference by Livion

JAVA Technologies

JAVA Complete Reference

Java Script Programming by Yehuda Shiran

Mastering JAVA Security

JAVA2 Networking by Pistoria

JAVA Security by Scotl oaks

Head First EJB Sierra Bates

J2EE Professional by Shadab siddiqui

JAVA server pages by Larne Pekowsley

JAVA Server pages by Nick Todd

HTML

HTML Black Book by Holzner

JDBC

Java Database Programming with JDBC by Patel moss.

Software Engineering by Roger Pressman