new microfinance web portal(kdp)

Microfinance Web Portal

Introduction To Organization

Experior Technologies


Organization Profile

Experior Technologies is a global IT solutions company with great experience. We provide full-cycle services in the areas of software development, web-based enterprise solutions, web application and portal development. Combining our solid business domain experience, technical expertise, profound knowledge of latest industry trends and quality-driven delivery model we offer progressive end-to-end web solutions.

Experior methodology promotes a result-driven interactive approach and guarantees better customer service with regards to quality, cost and customer’s strategic goals, without compromising on any of these factors. Experior Technologies offers the following services to customers.

Customized Software Development

Web application Development

Application Migration

Business Application Development

Product Development

Support and Maintenance



Technology Platform:

At Experior Technologies we work on cutting edge technologies to build solutions, which match industry standards and yet are delivered at record time.

Our technical architects coupled with our domain expert work on the following Technology platform and domains:

PHP

JAVA/J2EE

Ajax



INTRODUCTION TO PROJECT



Project Profile

Project Title : Microfinance Web Portal

Organization : Experior Technologies,

203,HarshAvenue,Navjeevan Press Road,

Incometax, Ahmedabad - 380014 (India).

Project Guide : Mr. Kinnar Kansara

Team Size : Two

Team Members : Prakash Patel

Kalpesh Patel

Technologies Used : JAVA, JSP, Servlets, Ajax, jQuery

Database Tool : MySQL 5.5

Reporting Tool : iReport (Jasper Report)

IDEs’ Used : Net beans IDE

Project Duration : 6 months

Operating System : Windows XP2



Project Definition

Project Definition:-

Ability to define loan products, Loan Activity, Scheduler, Loan Disbursement and Repayments(Installment Collection),Loans overdue reports, Demand Collection and Balances Reports.

Features of Microfinance Web Portal:-

User Friendly design.

Automated calculation of installment collection data.

Normalization of data.

Facility to print report in .pdf file format.

Show the day by day meeting details.

There are total four modules in Microfinance Web Portal

1. Organization Master

a. Initial Parameters

In this module we fill the information about country, state and create the division, area, branch, SHG area, and SHG.

b. Admin Assignment

In this module we can create the user as well as assign/resign the role to user

c. Scheduler

In this module we can define the meeting scheduler for the SHG.



d. Accounts

In this module we can store the account year details, Loan Category, Loan Activity information.

e. Finance

In this module we can store the details of the loan product, banking details, funding agency details.

f. Other Parameters

For storing the member related information individual like person caste, religion, education, relationship, document details, reason details, position details, company details.

2. Form

a. Member Registration

Here we fill the member details like member name, address, birth date, annual income and other information.

b. Registration Approval

After the complete the registration as well as approve by MFI then a branch manager approve registration of member.

c. De-Registration

If member want to de-registration from the MFI after the loan installment completion or some reason like due to death. If members take the loan from MFI and collection is remain then member can’t de-registration.

d. Loan Application

After the registration approve by branch manager a member is able for take the loan so before fill up the loan application form.



e. Loan Application Approval

After the Completion of the Loan Application we must approval that application. With use of Loan Application Approval we approve that loan application.

f. Disbursement

This module basically is for the distributed money. Here admin and FCO Manager First Check the fund is available or not for the member’s loan application which ever approve. Here he/she check whether approve loan application are able for the disbursement.

g. Disbursement Approval

With the use of this module we approve the Disbursement.

3. Transaction

a. Collection

Collection is use to collect the amount from member whose take the loan. there are two to type collection one is particular Member Wise and second is Group wise Collection.

b. Collection Approval

Collection Approval is to approve that particular Collection. That purpose we use collection approval.

c. Pre Closure

Pre Closure is to pre close our loan than that time we need to calculate amount. With the use of the pre closure installment and pre closure no of installment for charges.

4. Report

Report module is used for getting the reports in pdf format like disbursement, Collection Demand Sheet and Collection Demand Position etc…



Purpose of the System

Microfinance is considered to be an effective tool in alleviating poverty by increasing income of poor households and reducing their vulnerabilities. Today, when the majority of the world’s population is living below subsistence level, more than 3,000 organizations are providing microfinance services to millions of the world’s poor. Yet most of the poor still have little or no access to financial services. Microfinance institutions (MFIs) have reached a mere 70 million out of 2 billion poor people.

The purpose to develop this application for Microfinance this system is fully computerized that include to define scheduler for the particular SHG, member registration, registration approval, Loan application, Loan approval, Disbursement and Loan Collection.

There are already some software’s of this kind in the market but since their demand was less until now so they provide enough facilities to be completely called as user friendly, more flexible, more reliable to interact with other software’s of its kind, simple and cheaper. So, a decision was taken to develop this application has many features apart from all those mentioned above. Thus the project will develop Microfinance Web Portal Started.



Scope of the System

The scope of this Project is to develop Microfinance Web Portal for MFI that is user friendly, provide a wide range of facilities related Microfinance Loan Product and Loan Service. Thus the Microfinance web portal can be described as follows:

It is web based multi user system.

It is perfect system for MFI that help in generation various type of repot like Disbursement Report, Branch wise Loan Collection Report, Collection Demand Sheet, Disbursement and Outstanding position, Collection Demand Position, demand sheet.

Provide to create SHG and scheduler accounting year wise.

Provide to create the loan product that includes the Interest, insurance, installment, pre-closer related details.

Provide the facility for new users can be created and assign and resign their roles.

Provide the detail help during Loan Collection, Loan Approval, and Disbursement like member details and their loan related data. So it is helpful member as well as Branch Manager and FCO.



Model 2 Architecture – MVC

The Model 2 architecture for designing JSP pages is in reality, Model View Controller (MVC) applied to web applications. Hence the two terms can be used interchangeably in the web world. MVC originated in Smalltalk and has since made its way into Java community. Model 2 architecture and its derivatives are the cornerstones for all serious and industrial strength web applications designed in the real world. Hence it is essential for you understand this paradigm thoroughly. Following Figure shows the Model 2 (MVC) architecture.

The main difference between Model 1 and Model 2 is that in Model 2, a controller handles the user request instead of another JSP. The controller is implemented as a Servlets. The following steps are executed when the user submits the request.

1. The Controller Servlet handles the user’s request. (This means the hyperlink in the JSP should point to the controller Servlet).

2. The Controller Servlet then instantiates appropriate JavaBeans based on the request parameters (and optionally also based on session attributes).

3. The Controller Servlet then by itself or through a controller helper communicates with the middle tier or directly to the database to fetch the required data.

4. The Controller sets the resultant JavaBeans (either same or a new one) in one of the following contexts – request, session or application.

5. The controller then dispatches the request to the next view based on the request URL.

6. The View uses the resultant JavaBeans from Step 4 to display data.

Note that there is no presentation logic in the JSP. The sole function of



the JSP in Model 2 architecture is to display the data from the JavaBeans set in the request, session or application scopes.

Advantages of Model 2 Architecture:

Since there is no presentation logic in JSP, there are no scriptlets. This means lesser nightmares. [Note that although Model 2 is directed towards elimination of scriptlets, it does not architecturally prevent you from adding scriptlets. This has led to widespread misuse of Model 2 architecture.]

With MVC you can have as many controller servlet in your web application. In fact you can have one Controller servlet per module. However there are several advantages of having a single controller servlet for the entire web application. In a typical web application, there are several tasks that you want to do for every incoming request. For instance, you have to check if the user requesting an operation is authorized to do so. You also want to log the user’s entry and exit from the web application for every request. You might like to centralize the logic for dispatching requests to other views. The list goes on. If you have several controller servlets, chances are that you have to duplicate the logic for all the above tasks in all those places. A single controller servlet for the web application lets you centralize all the tasks in a single place. Elegant code and easier to maintain.

Web applications based on Model 2 architecture are easier to maintain and extend since the views do not refer to each other and there is no presentation logic in the views. It also allows you to clearly define the roles and responsibilities in large projects thus allowing better coordination among team members.



SYSTEM ANALYSIS



Preliminary Investigation

3.1.1 Feasibility Study:-

In today’s fast growing technological environment, it is imperative for any organization to use the power of information technology. The benefits of computerization will not only make the process flow simple but also uplift standards of man-power working in an organization and increase efficiency and productivity.

This is the reason why the MFI has decided to make its credit department completely computerized and totally abolish the manual work.

As an outcome of feasibility analysis phase, the feasibility of the system is determined.

The feasibility of the system checks whether the system is able to efficiently provide the facilities for which it was intended and the likelihood of the system being widely acceptable to the targeted clients. Following are 3 aspects of feasibility study.

Operational Feasibility:-

The proposed system will meet the operational requirement of the clients like.

o System Performance

o Accessibility of information

o User acceptance

Technical Feasibility:-

There were several technical issues raised during the preliminary stage of accurate to generate the disbursement and its report, loan collection, mange loan collection, demand sheet,



report, and overdue information report in PDF files as printed form as per user’s requirements.

The system is also flexible enough to support future enhancements or up-gradations. The security aspect has also been sufficiently taken care of.

Economic Feasibility:-

It would be a system that can work in LAN and WAN environment. Since entire calculation for loan collection SHG wise is computerized the chances of errors are less and results are also more accurate, reliable and speedy.

The system is a generalized one, which can be used for calculating loan collection meeting by meeting whether for individual member wise as well as group wise for MFI.

Various report and PDF files would also be generated by the system which will be helpful to the MFI for maintaining its record. The system also easily upgradeable so any updates can be easily implement in it.



UML Diagram



Use Case Diagram



Class Diagram



All Classes



shg

schedulerloan_product

Member_regloan_applicationdisbursment

collection

Shg_Address_Area

Branch_MasterArea_MasterDivision_MasterState_MasterCountry_Master

1..* 1..* 1..* 1..*

1

*

1

*1

*

1*

1* 1*

1

*

Accounting_Year_Master

1

*

Loan_Category

1

*

1

*

Country Class



Country

-country_name: String-country_id: int

+insertCountry(_bean: InitialparamBean): boolean+selectCountryData(): ArrayList+deleteCountry(_bean: InitialparamBean): boolean+updateCountry(_bean: InitialparamBean): boolean

State Class

State

-state_name: String-state_id: int

+insertState(_bean: InitialparamBean): boolean+selectStateData(): ArrayList+deleteState(_bean: InitialparamBean): boolean+updateState(_bean: InitialparamBean): boolean

Division Class



Division

-division_name: String-division_id: int-division_code: String-division_starting_date: String

+insertDivisionData(_bean: InitialparamBean): boolean+selectDivisionData(): ArrayList+deleteDivisionData(_bean: InitialparamBean): boolean+updateDivisionData(_bean: InitialparamBean): boolean+getDivisionTable(): String

Area Class

Area

-area_name: String-area_id: int-area_code: int-area_starting_date: String

+insertAreaData(_bean: InitialparamBean): boolean+selectAreaData(): ArrayList+deleteAreaData(_bean: InitialparamBean): boolean+updateAreaData(_bean: InitialparamBean): boolean+getAreaTable(): String

Branch Class



Branch

-branch_name: String-branch_code: String-branch_starting_date: String-branch_id: int

+insertBranchData(_bean: InitialparamBean): boolean+selectBranchData(): ArrayList+deleteBranchData(_bean: InitialparamBean): boolean+updateBranchData(_bean: InitialparamBean): boolean+getBranchTable(): String

Accounting Year Master Class

AccountingYearMaster

-account_year_name: String-account_year: String-accounting_year_table: String-accounting_year_master_id: int

+get_accounting_year_table(): String+insertAccountingYear(_bean: AccountBean): boolean+selectAccountingYearData(): ArrayList+deleteAccountingYear(_bean: AccountBean): boolean+updateaccountingYear(_bean: AccountBean): boolean

Loan Category Master Class



LoanCategoryMaster

-loan_category_name: String-loan_category_master_id: int-loan_category_table: String

+get_loan_category_table(): String+insertLoanCategory(_bean: AccountBean): boolean+selectLoanCategoryData(): ArrayList+deleteLoanCategory(_bean: AccountBean): boolean+updateLoanCategory(_bean: AccountBean): boolean

Member Registration Class



Member Reg.

-member_reg_id: int-shg_master_id: int-member_name: String-member_gender: String-member_permanenet_address: String-member_permanenet_pin_code: int-member_permanenet_phone_no: String-member_present_address: String-member_present_pin_code: int-member_present_phone_no: String-member_birth_date: String-member_age: int-member_marital_status: int-no_of_children: int-no_of_dependents: int-group_start_date: String-member_reg_date: String-monthly_income: int-photo_id_no: String-personal_proof_id: int-photo_validity_date: String-address_id_no: String-address_validity_date: String-member_photo: String

+insertMemRegData(_bean: MemRegBean): boolean+updateMemRegData(_bean: MemRegBean): boolean+selectMemberRegistrationData(): ArrayList+deleteMemRegData(_bean: MemRegBean): boolean+updateMemStaToDereg(_bean: MemRegBean): boolean+get_religionformem_update(_bean: MemRegBean): String+get_casteformem_update(_bean: MemRegBean): String+get_member_approval_table(): String+get_mem_disapproval_data(_bean: MemRegBean): boolean

Loan Collection Class



Loan Collection

-scheduler_id: int-collection_type: String-repayment_date: String-collection_receipt_no: int-collection_amount: double

+loan_collection_for_groupwise(_bean: LoanCollectionBean): LoanCollectionBean+get_member_name_for_loan_collection(_bean: LoanCollectionBean): String+insertLoanCollectionData(_bean: LoanCollectionBean): boolean+insertGroupWiseLoanCollectionData(arr: ArrayList): int+getcheck_loan_collection_status(_bean: LoanCollectionBean): boolean+update_loan_application_flag(_bean: LoanCollectionBean): boolean

Scheduler Class

scheduler

-meeting_type_flag: int-frequency_in_days: int-meeting_no: int-change_date: String-reason: String-time: String-next_meeting_date: String

+check_shg_master_id_is_used(_bean: SchedulerBean): ArrayList+check_schedule_id_is_used(_bean: SchedulerBean): String+get_scheduler_table(): String+get_scheduler_detail_table(_bean: SchedulerBean): String+selectScheduleData(): ArrayList+checkMeetingTypeFlag(_bean: SchedulerBean): ArrayList+scheduler_check(_bean: SchedulerBean): int+updateSchedulerData(_bean: SchedulerBean): boolean+deleteSchedulerData(_bean: SchedulerBean): boolean+get_no_of_meeting_for_loan_application(_bean: SchedulerBean): String

Disbursement Class



Disbursement

-shg_master_id: int-disbursement_date: String-disbursement_approval_date: String-disbursement_id: int-scheduleAndInstallmentList: String

+get_shg_wise_loan_application_approveal_table(_bean: DisbursementBean): String+get_shg_wise_disbursement_pending_table(_bean: DisbursementBean): String+insertQuery(_bean: DisbursementBean): boolean+updateQueryForDisbursementDone(_bean: DisbursementBean): boolean+deleteQuery(_bean: DisbursementBean): boolean+selectSchedule_and_installment_details_for_view(_bean: DisbursementBean): String

Loan Application ClassExperior Technologies


Loan Application

-loan_application_id: int-member_reg_master_id: int-loan_product_master_id: int-account_type_id: int-documentation_fees_paid: double-documentation_billno: String-marks_of_identification: String-bank_account_no: String-bank_name: String-nominee_name: String-nominee_age: int-nominee_relation_id: int-nominee_address: String-surity1_name: String-surity1_relation_id: int-surity1_address: String-surity2_name: String-surity2_relation_id: int-surity2_address: String

+insertLoanApplicationData(_bean: LoanBean): boolean+deleteLoanApplicationData(_bean: LoanBean): boolean+updateLoanApplicationData(_bean: LoanBean): boolean+updateLoanApplicationDataApprove(_bean: LoanBean): boolean+updateLoanApplicationDataDisApprove(_bean: LoanBean): boolean+selectLoanApplicationData(): ArrayList+selectLoanApplicationDataIDWise(_bean: LoanBean): ArrayList+getDivisionDropDownForUpdate(_bean: LoanBean): String+getAreaDropDownForUpdate(_bean: LoanBean): String+getBranchDropDownForUpdate(_bean: LoanBean): String+getSHGDropDownForUpdate(_bean: LoanBean): String+getMemberDropDownForUpdate(_bean: LoanBean): String+getLoanCategoryDropDownForUpdate(_bean: LoanBean): String+getLoanProductNameDropDownForUpdate(_bean: LoanBean): String+getLoanActivityDropDownForUpdate(_bean: LoanBean): String

SHG Class



SHG

-shg_name: String-shg_address: String-shg_starting_date: String-shg_meeting_time: String-shg_meeting_date: String-shg_maximum_member: int-shg_branch_distance: int-shg_location: String-shg_group_starting_date: String-shg_president: String-shg_secretary: String-shg_total_savings: double-shg_fco_responsible: String-shg_fd_details_id: int-fd_bank_name: String-fd_bank_branch: String-fd_no: String-fd_maturity_date: String-fd_amount: double-shg_bond_details_id: int-bond_bank_name: String-bond: int-bond_cheque_no: int

+get_shg_name_update_for_scheduler(shg_master_id: String): String+insertBankFDDetails(ib: InitialparamBean): boolean+insertBankBondDetails(ib: InitialparamBean): boolean+insertSHGData(ib: InitialparamBean): boolean+UpdateSHGData(ib: InitialparamBean): boolean+deleteSHGData(shg_id: int): boolean+select_shg_max_id(): int+select_fd_details(shg_id: int): ArrayList+delete_fd_details(shg_id: int): boolean+select_bond_details(shg_id: int): ArrayList+delete_bond_details(shg_id: int): boolean+select_shg_data(): ArrayList+select_shg_data(shg_id: int): ArrayList+str_FD_for_table(_bean: InitialparamBean): InitialparamBean

Loan Product Class



LoanProduct

-loan_product_name: String-loan_category_master_id: int-loan_product_amount: double-loan_interest: double-loan_no_of_installment: int-loan_frequency_day: int-loan_preclosure_month: int-loan_documentation_fee: double-fund_register_fee: double-fund_currency: String-fund_insurence_amount: double-starting_installment_no: int-ending_installment_no: int-installment_principal: double-installment_interest_amount: double-installment_no: int

+get_loan_product_table(): String+selectLoanProductData(): ArrayList+insertLoanProductData(_bean: FinanceBean): boolean+deleteLoanProductData(_bean: FinanceBean): boolean+updateLoanProductData(_bean: FinanceBean): boolean+deleteInstallment(_bean: FinanceBean): boolean+getLoanProductNameForLoanApplication(_bean: FinanceBean): String+getLoanProductAmountForLoanApplication(_bean: FinanceBean): String+getLoanDocumentsFeesForLoanApplication(_bean: FinanceBean): String+getInsuranceForLoanApplication(_bean: FinanceBean): String+getLoanProductNoOFInstallmentForLoanApplication(_bean: FinanceBean): String+getInstallmentInterestData(_bean: FinanceBean): ArrayList+getLoanProductNoOFInstallmentDetailsTable(arr: ArrayList): String+checkLoanProductInLoanApplication(_bean: FinanceBean): int+getLoanNoOfMonthForCharges(_bean: FinanceBean): String+get_total_no_of_installment_for_loan_application(_bean: FinanceBean): String



Sequence Diagram



Sequence Diagram for Scheduler



Sequence Diagram for Member Registration



Sequence Diagram for Loan Collection



Sequence Diagram for Loan Product



SYSTEM DESIGN



Data Dictionary



1. user_master Table:

Primary Key:- user_master_id

Field Name Data Type Size Constrain Description

user_master_id int pk,auto Used for Unique Identification of User

user_name varchar 20 Not Null Name of the user

password varchar 20 Not Null Password of the user

mobile_no varchar 20 Null Mobile No of the user

Remarks varchar 20 Null Remarks of the user

role varchar 20 Not Null Role of the user

2. country_master Table:

Primary Key:- country_master_id


country_master_id int Pk,auto Used for Unique Identification of Country

country_name varchar 20 Not Null Name of the Country



3. state_master Table:

Primary Key:- state_master_id

Foreign Key:- country_master_id


state_master_id int pk,auto Used for Unique Identification of State

country_master_id int Fk Used for Unique Identification of Country

state_name varchar 20 Not Null Name of the State

4. division_master Table:

Primary Key:- division_master_id

Foreign Key:- state_master_id


division_master_id Int pk,auto Used for Unique Identification of Division

state_master_id Int Fk Used for Unique Identification of State

division_name varchar 20 Not Null Name of the Division

division_starting_date date Not Null Starting Date of the Division



5. area_master Table:

Primary Key:- area_master_id

Foreign Key:- division_master_id


area_master_id int pk,auto Used for Unique Identification of Area.

division_master_id int Fk Used for Ref. of Division

area_name varchar 20 Not Null Name of the Area

area_starting_date date Not Null Starting Date of the Area

6. branch_master Table:

Primary Key:- branch_master_id

Foreign Key:- area _master_id


branch_master_id int pk,auto Used for Unique Identification of Branch.

area_master_id int Fk Used for Unique Identification of Area.

branch_name varchar 20 Not Null Name of the Branch

branch_starting_date date Not Null Starting Date of the Branch



7. shg_area_master Table:

Primary Key:- shg_area_master_id

Foreign Key:- branch _master_id


shg_area_master_id int pk,auto Used for Unique Identification of SHG Area.

branch_master_id int Fk Used for Unique Identification of Branch.

shg_area_name varchar 20 Not Null Name of the SHG Area.



8. shg_master Table:

Primary Key:- shg_master_id

Foreign Key:- shg_area _master_id


shg_master_id Int pk,auto Used for Unique Identification of SHG.

shg_area_master_id Int Fk Used for Unique Identification of SHG Area.

shg_name Varchar 50 Not Null Name of the SHG

shg_address Varchar 100 Not Null Address of the SHG

shg_starting_date Date Not Null Starting Date of the SHG

shg_meeting_time time Not Null Meeting Time of shg

shg_meeting_date Date Not Null Meeting Date of the SHG

shg_maximum_member Int Not Null Maximum Member of the SHG

shg_branch_distance Int Not Null Branch Distance of the SHG

shg_location Varchar 50 Not Null Location of the SHG

shg_group_starting_date Date Not Null Group Starting Date of the SHG

shg_president Varchar 50 Not Null President of the SHG

shg_secretary Varchar 50 Not Null Secretary of the SHG

shg_total_savings Double Not Null Total Savings of the SHG

shg_fco_responsible varchar 50 Not Null FCO Responsible of the



SHG

9. shg_fd_details Table:

Primary Key:- shg_fd_details_id

Foreign Key:- shg_master_id


shg_fd_details_id int pk,auto Used for Unique Identification of SHG FD.

shg_master_id Int 11 fk Used for Unique Identification of SHG.

fd_bank_name varchar 20 Not Null Bank Name of the SHG FD

fd_bank_branch varchar 20 Not Null Bank Branch of the SHG FD

fd_no Int Not Null No of the SHG FD

fd_maturity_date Date Not Null Maturity Date of the SHG FD

fd_amount double Not Null Amount of the SHG FD



10. shg_bound_details Table:

Primary Key:- shg_fd_details_id

Foreign Key:- shg_master_id


shg_bond_details_id Int 11 pk,auto Used for Unique Identification of SHG Bond.

shg_master_id Int 11 Fk Used for Unique Identification of SHG.

bond_bank_name varchar 20 Not Null Bank Name of the SHG Bond.

bond Int Not Null Bond of SHG Bond.

bond_cheque_no Int Not Null Cheque No of SHG Bond.

11. branch_assignment Table:

Primary Key:- branch_assignment_id

Field Name Data Type Size Constraint Description

branch_assignment_id int PK,Auto for Unique Identification

branch_master_id int FK id of branch_master

user_master_id int FK id of user_master

branch_assignment_flag int For 1:Assign,0:Deassign

Foreign Key:- branch_master_id, user_master_id



12. fco_assignment Table:

Primary Key:- fco_assignment_id

Foreign Key:- shg_master_id, user_master_id


fco_assignment_id int PK,Auto for Unique Identification

shg_master_id int FK id of shg_master

user_master_id int FK id of user_master

fco_assignment_flag int For 1:Assign,0:Deassign

13. accounting_year_master Table:

Primary Key:- accounting_year_master_id


accounting_year_master_id int PK,Auto for Unique Identification

accounting_year_name varchar 20 Not Null Accounting Year Name

accounting_year int Not Null Accounting Year

14. scheduler_master Table:



Primary Key:- scheduler_id

Foreign Key:- shg_master_id, accounting_year_master_id


scheduler_id int PK,Auto for Unique Identification

shg_master_id int FK id of shg_master

accounting_year_master_id int FK id of accounting_year_master

next_meeting_date date Not Null Meeting Date of Scheduler

change_date date Change Date of Schedule

scheduler_reason varchar 20 Reason of Scheduler

meeting_type int Not Null 1:temporary,0:permanent

meeting_no int Not Null Meeting No of Scheduler

meeting_time varchar 11 Not Null Meeting Time of Scheduler

active_flag varchar 1 Not Null Status:-A:-Active D:-Deactive

15. loan_category_master Table:



Primary Key:- loan_category_master_id


loan_category_master_id int PK,Auto for Unique Identification

loan_category_name varchar 20 Not Null Loan Category Name

16. loan_activity_master Table:

Primary Key:- loan_activity_master_id

Field Name Data Type

Size Constraint Description

loan_activity_master_id int PK,Auto for Unique Identification

loan_activity_name varchar 20 Not Null Loan Activity Name

17. bank_master Table:

Primary Key:- bank_master_id


bank_master_id int PK,Auto for Unique Identification

bank_name varchar 20 Not Null Bank Name

bank_account_no int Not Null Bank Account No

18. funding_agency _master Table:



Primary Key:- funding_agency_master_id


funding_agency_master_id int PK,Auto for Unique Identification

funding_agency_name varchar 20 Not Null Funding Agency Name

19. installment_interest_master Table:

Primary Key:- installment_interest_id

Foreign Key:- loan_product_master_id


installment_interest_id int PK,Auto for Unique Identification

loan_product_master_id int FK id of loan_product_master

installment_no int Not Null Installment number

installment_principal double Not Null Loan amount at installment

installment_interest_amount double Not Null Interest amount at installment

installment_insurance double Not Null Insurance amount at insurance

20. loan_product_master Table:



Primary Key:- loan_product_master_id

Foreign Key:- shg_master_id, accounting_year_master_id


loan_product_master_id int PK,Auto for Unique Identification

loan_category_master_id int FK id of loan_category_master

loan_product_name varchar 20 Not Null Loan Product Name

loan_product_amount double Not Null Amount of loan product

loan_interest double Not Null Interest of loan product(Per Year)

loan_no_of_installment int Not Null Total Installment of Loan Product

loan_frequency_day int Not Null Frequency Day(14,30)

loan_preclosure_installment int Not Null Before this loan can’t close

fund_register_fee double Not Null Register fee

fund_currency varchar 20 Not Null Currency like Rs.

loan_no_of_installment_for_charges

int Not Null For charges purpose when member want to close the loan before finish all installment.

21.personal_religion_master Table:

Primary Key:- personal_religion_id




personal_religion_id int PK,Auto for Unique Identification

personal_religion_name varchar 20 Not Null Religion Name

22.personal_caste_master Table:

Primary Key:- personal_caste_id


personal_caste_id int PK,Auto for Unique Identification

personal_caste_name varchar 20 Not Null Caste Name

23.personal_marital_status_master Table:

Primary Key:- personal_marital_id


personal_marital_id int PK,Auto for Unique Identification

personal_marital_status varchar 20 Not Null describe the marital status

24.personal_education_detail_master Table:

Primary Key:- personal_education_id




personal_education_id int PK,Auto for Unique Identification

personal_education_detail varchar 20 Not Null education details like 12th,B.A

25.personal_occupation_master Table:

Primary Key:- personal_occupation_id


personal_occupation_id int PK,Auto for Unique Identification

personal_occupation_type varchar 20 Not Null Occupation type

26.personal_housetype _master Table:

Primary Key:- personal_housetype_id


personal_housetype_id int PK,Auto for Unique Identification

personal_house_type varchar 20 Not Null House type

27.personal_area_housetype_master Table:

Primary Key:- personal_area_housetype_id




personal_area_housetype_id int PK,Auto for Unique Identification

personal_area_house_type varchar 20 Not Null Area of house

28.personal_rooftype_master Table:

Primary Key:- personal_rooftype_id


personal_rooftype_id int PK,Auto for Unique Identification

personal_roof_type varchar 20 Not Null Roof Type

29.personal_ floortype_master Table:

Primary Key:- personal_floortype_id


personal_floortype_id int PK,Auto for Unique Identification

personal_floor_type varchar 20 Not Null Floor type

30. personal_floortype_master Table:




personal_proof_id int PK,Auto for Unique Identification

personal_proof_document varchar 20 Not Null Proof Document

Primary Key:- personal_floortype_id

31.personal_location_master Table:

Primary Key:- personal_location_id


personal_location_id int PK,Auto for Unique Identification

personal_location_name varchar 20 Not Null Location Name

32.personal_relationship_master Table:

Primary Key:- personal_relationship_id

Field Name Data Type

Size Constraint Description

personal_relationship_id int PK,Auto for Unique Identification

personal_relationship_name

varchar 20 Not Null Relationshi name

33.personal_deregistration_master Table:

Primary Key:- personal_deregistration_id




personal_deregistration_id int PK,Auto for Unique Identification

personal_deregistration_reason varchar 20 Not Null Reason of deregistration

34.personal_shgmember_position_master Table:

Primary Key:- personal_shgmember_position_id


personal_shgmember_position_id int PK,Auto for Unique Identification

personal_shgmember_position_name varchar 20 Not Null Position in SHG

35.personal_state_of_health_master Table:

Primary Key:- state_of_health_id


state_of_health_id int PK,Auto for Unique Identification

state_of_health_name varchar 20 Not Null Describe health status

36.account_type_master Table:

Primary Key:- personal_shgmember_position_id




account_type_id int PK,Auto for Unique Identification

account_type_name varchar 20 Not Null Account Type

37.disbursement_master Table:

Primary Key:- disbursement_master_id

Foreign Key:- loan_application_id


disbursement_master_id int PK,Auto for Unique Identification

loan_application_id int FK id of loan application

disbursement_date date Not Null id of schedular_master

disbursement_approve_date date Not Null Approval date

disbursement_flag varchar 1 Not Null Status of disbursement P:Pending,D: Done

38.member_reg_master Table:

Primary Key:- member_reg_master_id

Foreign Key:- shg_master_id, personal_marital_id, personal_religion_id, personal_caste_id, personal_education_id, personal_occupation_id,



member_position_in_shg, personal_housetype_id, personal_rooftype_id, personal_floortype_id, personal_proof_id


member_reg_master_id int PK,Auto for Unique Identification

shg_master_id int FK shg_master_id

member_name varchar 50 Not Null Member Name

member_gender varchar 10 Not Null Gender type

member_permanenat_address varchar 100 Not Null permananet Address

member_permanenat_district varchar 30 permananet district

member_permanenat_pin_code int Not Null Permanenat pin code

member_permanenat_phone_no varchar 20 Permanenat phone no

member_present_address varchar 100 Present address

member_present_district varchar 50 Present district

member_present_pin_code int Not Null Present pin code

member_present_phone_no varchar 20 Present phone no

spouse_name varchar 50 Not Null Spouse name

member_age int Not Null Member age


personal_marital_id int FK Id of personal_ marital_master

no_of_children int Total children



no_of_dependents int Total dependents

personal_religion_id int FK Id of personal_ religion_master

personal_caste_id int FK Id of personal_ caste_master

personal_education_id int FK Id of personal_ education_ master

personal_occupation_id int FK Id of personal_ occupation_master

member_reg_date date Not Null Registration date

member_status varchar Not Null A: Active , D:Deactive

sub_group_id int Not Null Sub group id (5 member in group)

member_position_in_shg int FK Id of personal_ shgmember_ position_master

distance_the_meeting_place float Distance in K.M

monthly_income double Not Null Monthly Income

personal_housetype_id int FK Id of Personal House Type

area_of_house int Member Area of House


house_area_unit float House Area Unit

personal_rooftype_id int FK Id of personal_ rooftype_master



personal_floortype_id int FK Id of personal_ floor_master

registration_fees double Registration Fees of the Member

bill_no int Bill No for the registration fees paid

total_mfi int Total MFI

details_of_agricultural_land varchar 50 Member Details of Agricultural land

livestock varchar 50 Live Stock

other_asset varchar 50 Other Asset

photo_id_no varchar 25 Not Null Photo Id No of the Member

personal_proof_id int FK Id of personal_ proof_master

photo_validity_date date Not Null Photo Validity Date of the Member

address_id_no varchar Not Null Address Id No

personal_address_proof_id int FK Id of personal_ proof_master


member_photo varchar 55 Not Null Photo of the Member

member_reg_status varchar 1 Not Null Determines Member Reg.



Status P:-Pending D:-Done

39.loan_application_master:

Primary Key:- loan_application_id

Foreign Key:- member_reg_id, loan_product_master_id, state_of_health_master_id, account_type_id, funding_agency_master_id, loan_activity_master_id


loan_application_id Int PK UniqueIdentification of Loan Application

member_reg_id Int FK UniqueIdentification of Mem.reg. master

loan_product_master_id Int FK UniqueIdentification of Loan Product Master

state_of_health_master_id Int FK UniqueIdentification of State of health master

account_type_id Int FK UniqueIdentification of account type master


funding_agency_master_id Int FK UniqueIdentification of Funding Agency Master



loan_activity_master_id Int FK UniqueIdentification of Loan Activity Master

insurance Double Not Null Insurance

loan_taken_other_mfi Varchar 11 Not Null Loan Taken For Other MFI at time of Loan Application

documentation_fees_paid Double Not Null Documentation fees paid

documentation_billno Int Not Null Documentation billno

marks_of_identification Varchar 20 Not Null Marks of identification

bank_account_no Varchar 15 Not Null Bank Account No.

bank_name Varchar 50 Not Null Bank Name

nominee_name Varchar 50 Not Null Name of Nominee

nominee_age Int Not Null Age of Nominee

nominee_relation Int Not Null Nominee relation

nominee_address Varchar 100 Not Null Nominee Address

nominee_bank_account_detail Varchar 30 Not Null Bank Account Detail of Nominee

surity1_name Varchar 50 Not Null First Surity Person Name

surity1_relation_id Int Not Null First Surity Relationship


surity1_address Varchar 100 Not Null First Surity Address Details

surity2_name Varchar 50 Not Null Second Surity Person



Name

surity2_relation_id Int Not Null Second Surity Relationship

surity2_address Varchar 100 Not Null Second Surity Address

loan_approval_flag varchar 2 Not Null For Whether The Loan Approve or Not,D:Done,P:Pending Default Pending

loan_application_date Date Not Null Date of loan Application

loan_approval_date Date Not Null Date of loan Approve(At Approve Time loan_approval_flag=D)

40.loan_collection_master Table:

Primary Key:- loan_collection_master_id

Foreign Key:- loan_application_id, scheduler_id, installment_interest_id




loan_collection_master_id int PK,Auto for Unique Identification

loan_application_id int FK id of loan application

scheduler_id int FK id of schedular_master

installment_interest_id int FK id of installment_ interest_master

collection_type varchar 1 Not Null Collection type 1:member wise,

2:Group wise

collection_amount double Not Null Collection amount

date_repayment date Not Null payment date

collection_receipt_no int Not Null receipt no

loan_collection_flag varchar 1 Not Null Collection status P:Pending,D: Done

41.preclosure_master Table:

Primary Key:- preclosure_master_id

Foreign Key:- loan_application_id




preclosure_master_id int PK,Auto for Unique Identification

loan_application_id int FK id of loan_ application_master

preclosure_date date Not Null loan close date

collected_amount date Not Null Collected amount



SNAP SHOTS

1. Login Page



Login page for logining into the system.Basically,there are three types of user in our system admin is master user, other are branch manager and FCO manager. If the user enters the correct username and password then user access the system based on its role. Following screen display the admin view of the System.

2. Home Page



Initial Parameter:- to define the country, state, division, area, branch, SHG_address_area, and SHG.

Admin assignment:- This view for creating the user and assign,unassign and reassign the user rights.

Scheduler:- To define the scheduler for the SHG.

Accounts:- To define the accounting year, loan category, loan activity.

Finance:- To define the funding agency, Loan Product.

Other Parameters:- to define the personal parameter for the member’s like the proof document, caste, marital status, education details, state of the health, account type, SHG member position etc.



3. Division Master

This page is Division Master Here we define the Division Code, Division Name, country Name, state Name and last division starting date.

The entire field is the compulsory for the system here states name comes based on the country select. All country names come automatically from the databases. If the admin fill the all field then click on the add button then you will get the following page.



4. Division Inserted Successfully

Here we can see insertion message in page right side. Also see all the record in Manage Division Master Table. The admin can easily manage the division. If admin click on the edit button the admin get the following changes in the page.



5. Division with Edit Mode

Here admin get the two button one for the Update and another for the Cancel. Here we select the Gujarat rather than Bihar and the click on the update button after that we get the following screen.



6. Division Updated Successfully

Here we can get proper Updating Message in page right side.



7. Division with Delete Mode

At here we have two division himmatnager and palanpur. if admin want to delete the palanpur then he can get the above screen shot and get the above two button Confirm Delete and Cancel button. At the delete time the admin can see the details with all disable field means admin are not able to do for changes the details at Delete Time. Confirm Delete for the Delete the Record and Cancel button for the Cancel the changes.

In our System we repeat above process many times for the admin to define the System parameters. So now we can display only few snap-shots for explanation when above process comes. Now we want go for the future explanation of the admin parameter.



8. Area Master

For defining the area of that particular division. Below screen display with the data.



9. Area Inserted Successfully



10.Branch Master

For Define the Branch. First fill the branch name then we needs to select division that comes from the database and area comes based on the division. Then after click on the ADD Button.



11.Branch Inserted Successfully and SHG Address Area Master



12.SHG Area Master

This page basically for to store the address of the particular SHG. There are many SHG in branch but may be possible different SHG have the same address. Here all fields are require for to store the details. We define the SHG area address following.



13.SHG Area Inserted Successfully



14.SHG Master

Here the admin store the details of particular SHG with its name, division to SHG address area details, meeting date, group starting date, starting date, meeting time maximum member in SHG, distance from the branch, location, president, secretary details also store the bond and FD details of the particular SHG. Fill the required field click on the save button and then we get



the below screen with message SHG inserted successfully and also get the data in manage shg details tables.

15.SHG Inserted Successfully



16.Manage Users Master



Above screen is used for user management. This system have one admin predefine or we can say that MIS. Then after admin created other users like Branch Manager and FCO (Field Credit Officer).This type user will created by Admin.we create one FCO User in above screen.

17.User Inserted Successfully



We fillup all the field and then after we click on add button we got this record in grid view.we see this record click on edit,button and delete button also.with the use of edit we edit or we can say that this record is updated and delete button is used to delete that perticular record.

18.FCO(Field Credit Officer) Assignment



Above screen will used for FCO Assignment. When we need to assign any user then this time we need to select division, area, branch , SHG and FCO in charge and then after we click on Assign button. Then this user assign as FCO In charge.



19.FCO Assignment Done Successfully

Above screen will display FCO assignment successfully.

20.FCO Assignments with Unassigned Mode

Above screen is used for Delete the FCO assignment. When admin click on Delete link then this type screen will display and when admin click on unassigned button then this FCO In charge will unassign that role.



21.Scheduler Master

Scheduler module is basically for to define the meeting schedule for the particular SHG with accounting year wise. Here we show the facilities of date picker for selecting date. Total meeting indicates how many meeting you want to generate. Here starting date indicates the first meeting for the SHG. The admin can change the date for to define the scheduler. At first time change meeting type, change date, and reason field are disable when define the scheduler. Below screen define the functionality with the time picker.



22.Scheduler Master with Date Picker

After filling and selecting required Field and then admin click on the save button then he gets the below screen with the proper message of insertion.



23.Scheduler Inserted Successfully

If suppose the admin want to see the details meeting list of the SHG and want to change the date. Then click on the edit button of the particular SHG then we get the following screen.



24.Scheduler with Edit Mode

Here an admin get the different screen an admin change and fill up the only Four details change meeting type, time ,change date and reason rest of the field are disable After changes the data and click on the update button an admin get the below screen with the proper data.


Get right side details and click the third record then get the left side details and the meeting type and date with proper reason.


25.Scheduler with Edit Mode

Now here we can see a third number meeting was change with temporary meeting type.



26.Loan Product Master

Above screen describe the loan product. In loan product an admin can define the loan product name, select the loan category, fill the loan amount, define interest in per(%) yearly. Define the pre-closer installment it’s indicates minimum collection loan installment from the member. Define the pre-closure installment charges it’s indicates if member want to close the loan. So how many installment interests member will pay to the organization.

Here an admin can create the installment two ways manual and automatically. In automatically installment first to second last installment principle, installment interest and insurance and remaining amount calculate in last installment. In manual an admin can create the installment manual for the loan product in manual may be



possible for the organization generate the different installment amount each and every installment.

Ex:- First installment 400 Rs., Second Installment 500 Rs, Third Installment 600Rs.

Here loan amount 8000 Rs., Loan Interest 18%, Total Installment 25, Frequency in Day 15. If Frequency in day is 15 then admin want to generate the installment above 12 otherwise not able. Here there are two loan frequencies in day 15 and 30.

Here we display the installment information on right side. So if an admin want to generate the installment list automatically the he/she first select the starting installment(1), and ending installment(25) then after enter the installment principle(Rs.320), installment interest (Rs.50), and installment insurance(Rs.0) the click on the Installment List button. Then he/she get the following screen.

27.Loan Product with Installment

So in automatically installment an admin can get the above installment in this view we can see at last installment is different then other installment because it include the



remaining amount. After then click on the create installment at that time an admin create the loan product. After that we can get the information right side loan product insertion message.

28.Member Registration Master



Above page include all details related member personal information like he/she name, permanent and present address details, marital status, spouse and children details, group id, member code, proof and address document, and property details. So a branch manager or FCO manager fill the required information and save for the further processing like loan application and disbursement. After successful insertion a branch manager or FCO Manager get the proper message page right side. At below we provide member search facility for to update and delete particular member information. Because search is very fast rather then display all member details.

29.Member Approval Master

After member registration an admin or branch manager are able to do registration approval for the member. Registration approval requires for loan application because only registration approve member is able for the loan application. Below page are for the member registration approval. For Display member list in the page so first select the SHG name then click on the submit button. After that we get the list of member.



30.Member Approval Master with All Data

Here admin want to approve registration of third member when admin click on the approve button he/she get the alert for approval if click on the ok button then registration approval successful. See the following screen.



32. Member Approval Successfully



33.Loan Application Master with scheduler Details

Here we display the scheduler details of particular SHG when click on the show scheduler button. It is just for to provide the notification to the member and branch manager.

Above screen we display the installment details for the notification purpose for both. Scheduler must greater than or equal to selected loan product installment other wise an admin or branch manager get the alert message.

When we select the member at that time all member related information will be fill its related field. We can see in following screen. In SHG first member get the president position.

At manage loan application we display only pending loan application.



34.Loan Application with Installment Details



35.Loan Application is already done



If application already done or running then following type of page will be display.

36.Loan Application Approval



After the loan application is done approval is require for the disbursement.

Above page show the loan application approval so we require first select the SHG name then after click on the submit button then he/she get the Loan Application List of particular SHG with check box.

37.Loan Application Approval Successfully



If suppose he/she select the above check box then all check boxes is selected and view button is for display the loan application in brief. Here we check all check box then click on the submit button. At background process first make the status done then provide the status message like “Submitted Successfully”.

38.Disbursement Master



This module is basically for the distributed money. Here admin and branch Manager First Check the fund is available or not for the member’s loan application which ever approve. Here he/she check whether approve loan application are able for the disbursement.

39.Disbursement with Data



When we click submit button then we got all above table data and check boxes.

And one view link will be display.this link is use for show all the installment perticuler member wise.



40.Disbursement Successfully

Above screen display all the data.and when we click on check boxes then after we need to click on submit button.when we click submit button then disbursement is successfully this type of message will be display on the screen.



View link display below screen. Here we check above check box for disbursement . Then click on the submit button and make the disbursement.

Above screen display the meeting date, loan product name as well as installment details with amount for the particular member’s loan application. Basically admin give this list to the member. So, member easily remembers his/her meeting date and installment amount with details.



41.Disbursement Approval Master

Click on the submit button get loan approval data for the disbursement.

42.Disbursement Approval with data



Disbursement approval process done by the organization after the 2 or 3 day when disbursement was over. Because approval time organization give the fund. Here we select the all check box and then after click on the submit button for making status done of disbursement then after member get it’s loan application money. View link also display above screen for details purpose.

43.Loan Collection Master

Now we go for the loan collection. Loan collection is a one process for get the money backs from the member which ever take the loan. There are two type of loan collection (1) particular member wise (2) SHG Group Wise.

1) Particular Member Wise:-

Branch manager or FCO may be collect the loan installment individual member wise

2) SHG Group Wise:-

Branch manager or FCO collect the loan installment as a SHG Group wise. He/she is only able for group wise collection



when all SHG member collection installments number is same. Otherwise get the message collection does not proper.

Above screen is for the loan collection first select the proper SHG name then select the collection type. Here if he/she selects the particular member wise then he/she gets member list in combo box. Now, we see below screen.

44.Particular Member Wise Loan Collection

In above screen when he/she select the particular member then he/she gets details like loan type, loan amount, demand principle, demand interest, demand insurance, overdue amount, demand total, due date, installment amount, balance amount also display the previous collection in table with the title of “Loan Collection Details”.

When he/she collect the loan installment particular member wise at that time collection amount and repayment date automatically comes after the member select.



45.Group Wise Loan Collection

A branch manager and FCO (Field Credit Officer) collect the loan installment as a group wise. But here we require same installment no for group wise collection. Here view button display the details of current loan position. Save button is for to save the collection information. For details information see the following screen.



46.Scheduler, Loan Product, collection and Installment Details Display in Gray Box.



47.Loan Collection Approval

After collection is over, a branch manager give the collected amount to organization with information like how many member present, amount of collection, an admin check the weather the collection is proper or not .so we provide the facility of loan collection approval.

An admin can approve loan collection as SHG wise.



48.Loan Collection Approval with Data

In above screen we provide the single check box for to check the all data. Also provide the absent check box for filling the absent details if absent is check it’s indicated member is absent. If check box unchecks its indicated member is present. Here we select the all check box then after click on submit button.



49.Manage Loan Collection

Every system performs its task perfectly. A mistake may be done by admin, or by branch manager so proper management is require. So here we provide the Loan Collection Management for updating and deleting purpose. Here we only provide last loan collection management not all. In Above screen, system only displays last loan collection data. If admin want to update the data then he should click on the edit button.



50.Manage Loan Collection with Edit Mode

In above screen when admin click on the edit button then related information will be display above like member name, collection amount, receipt no, and repayment date. Here we update the collection amount. Then after click on the update button.



51.Manage Loan Collection Updated Successfully

Here we get the updating message after the update as well as also get the new data in table.



52.Preclosure Master

Now we explain the details of preclosuer. Preclosuer is process to close the current loan application of the member in advance. Here we provide the two type of preclosuer 1) Member Wise and 2) SHG Wise.

A member can’t close the loan until at least installment not collected. If at least installment collected then member close the loan if he/she want. We already define the preclosure installment as well as preclosure installment charges in loan product.



53.Member Cancel-Registration Master

If member want to deregistration from the system after the loan collection is over. Member should be pay loan amount before the de registration.

In above screen, first we select the SHG then after all member list come in the combo box, if we select any member so it’s related details automatically comes at page right side.



54.Member Cancel-Registration Master with Member Data

Then after we click on de registration button it means this member is de register successfully and this member will not display in member drop down.



Reports

55.Disbursement Report

Above screen display for disbursement report purpose.



56.Disbursement Report Generated Successfully



57.Collection Demand Report



58.Demand Collection Sheet Generated Successfully



59.Demand Collection Position with Data



60.Demand Collection Position Report Generated Successfully



TESTING



Testing Strategy:

White Box Testing

White box testing assumes that the specific logic is important and must be tested to guarantee the system’s proper functioning. The main use of the white box is in error based testing, when you already have tested all object of an application and all external or public methods of an object that you believe to be of greater importance. Here we are looking for bugs that have a low probability of execution, have been carelessly implemented or were overlooked previously.

o Statement Testing

The main idea of statement testing is to test every statement in the object’s method by executing it at least once.

o Branch Testing

The main idea behind branch testing is to perform enough tests to ensure that every branch alternative has been executed at least once under some test.

We have done statement testing under white box testing as well as branch testing because we do not have much complex condition. So there is no need to take special care about it. But we have tried to cover that in black box testing.

Black box Testing

The concept of the black box is used to represent a system in which inside working are not available for inspection. Here the test item is treated as “black”, since its logic is unknown; all that is known is what goes in and what comes out, or the input and output.

Here try various inputs and examine the resulting output.



Common Test Cases:

Test Case Back ground Process Status

Numeric Components Validation, Format Done

String Validation Done

Date Validation, Format Done

Check Box Multiple Selection Done

Select(Combo Box) Validation Done



FUTURE ENHANCEMENT

If in future there is a need to add new things, then it can be added by some changes only. So the system is flexible, because system is made using MVC architecture.

The system is using compiled class files, so if there is any change in any of the code file; it can be updated to previously installed application by making a small patch called update.

Right now we provide facility only for Micro Finance Activity. In future we may include other services like Accounting for organization, Youth Counseling and Rural Marketing.



GLOSSARY

SHG :- Self Help Group.

MFI:- Micro Finance Institution

FCO :- Field Credit Officer.

UnAssign :- revoke the role from the user.

Re-Assign :- gives the role again to user after revoke.



CONCLUTION



BIBLIOGRAPHY

Complete Reference JAVA 2

By Herbet Schildt

Head First Servlets and JSP (E-book)By Katherine Sierra, Bert Bates, Bryan Basham

The Definitive Guide to iReport (E-book)

By Giulio Toffoli

Websites referred

www.google.com

www.jquery.com

www.w3schools.com

www.java2s.com

http://jasperforge.org

http://www.opportunity.org.au

http://www.supath.org


http://www.supath.org/

http://www.opportunity.org.au/

http://jasperforge.org/

http://www.java2s.com/

http://www.w3schools.com/

http://www.jquery.com/

http://www.google.com/

new microfinance web portal(kdp)

Documents

microfinance web portalfield

microfinance web portal30

microfinance web portal16

microfinance web portal

mem regb ean

unique identification id

shg fd details id foreign key

field credit officer