WOMEN SELF HELP GROUP MANAGEMENT SYSTEM

A project report submitted in partial fulfillment for the award of the requirements of

BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE

Submitted by
P. LAVANYA (Reg. No. 17CS0523)
J. DHANALAKSHMI (Reg. No. 17CS0517)

Under The Guidance of

Dr. D. THAMIZH SELVAM, M.Sc., M.Phil., Ph.D.,

Assistant Professor, Department of Computer Science,
Rajiv Gandhi Arts & Science College,
Thavalakuppam, Puducherry-605 007.

DEPARTMENT OF COMPUTER SCIENCE

RAJIV GANDHI ARTS AND SCIENCE COLLEGE
(Accredited by NAAC with ‘B’ Grade)
(Run by the Pondicherry Society for Higher Education)
GOVERNMENT OF PUDUCHERRY
THAVALAKUPPAM, PUDUCHERRY-605 007.

OCTOBER 2020
 BONAFIDE CERTIFICATE

This is to certify that the project work entitled “WOMEN SELF HELP GROUP
MANAGEMENT SYSTEM” is a Bonafide record of work being jointly submitted by
P. LAVANYA (Reg. No. 17CS0523) and J. DHANALAKSHMI (Reg. No. 17CS0517) in
partial fulfillment for the degree of Bachelor of Science in Computer Science of Pondicherry
University.

This project work has not been submitted elsewhere for the award of any other degree.

INTERNAL GUIDE

Dr. D. THAMIZH SELVAM, M.Sc., M.Phil., Ph.D.,

Assistant Professor,
Department of Computer Science,
Rajiv Gandhi Arts and Science College,
Puducherry-605 007.

HEAD OF THE DEPARTMENT

Dr. N. GNANAMBIGAI, M.Sc., M.Phil., Ph.D.,
Assistant Professor & Head,
Department of Computer Science,
Rajiv Gandhi Arts and Science College,
Puducherry-605 007.

Submitted for the University Examination held on …………………….

EXTERNAL EXAMINER INTERNAL EXAMINER

ACKNOWLEDGEMENT
 ACKNOWLEDGEMENT

We extend our sincere thanks and praise to the almighty, who have been showering his
grace all through our ways in completing the project.

We would like to express our deep sense of gratitude to our respected

Dr. V. ARJUNAN, M.Sc., M.Phil., M.Ed., PGDCA., Ph.D., Principal, RAJIV GANTHI
ARTS AND SCIENCE COLLEGE,who has given us the opportunity to take up this project
work.

We feel glad to thank Dr. N. GNANAMBIGAI M.Sc., M.Phil., Ph.D., Department

In Charge, Department of Computer Science, RAJIV GANTHI ARTS AND SCIENCE
COLLEGE, for her kind co-operation to complete this project.

We express our deep sense of gratitude to Dr. D. THAMIZH SELVAM, M.Sc.,

M.Phil., Ph.D., Assistant Professor, Department of Computer Science, RAJIV GANTHI ARTS
AND SCIENCE COLLEGE, our project guide for the guidance and help he has given to
throughout our course and the project work.

We would thank everyone at the THIRUMAHAL MAHALIR SHG for their kind
cooperation and support.

We extend our most heartfelt thanks to our Parents, our Lecturers and our Classmates for
their never-ending support and encouragement, which enable to complete this project.

By

P.LAVANYA,
J.DHANALAKSHMI.
SYNOPSIS
 SYNOPSIS

The process of identifying the different loan schemes and of breaking them down and
relating them to the various activities of the organization is referred as “WOMEN WELFARE
SCHEME”.

It is a management tool used to computerize and estimate the overall Schemes of SHG,
assuming normal operations.

The project deal with calculating the principle and interest of the different loans. The
SHG mainly involves different operations like: new registration, member details, loan details,
insurance details, and installment.

The system will also facilitate reduction of man power and paper work in WOMEN
WELWARE SCHEME. Once this system is introduced, computers can mimic every manual
operation of the shortage and can store and retrieve data whenever required without loss of time.

WOMEN WELWARE SCHEME is a software package developed in HTML, CSS and

PHP as the Front-End and My SQL as the Back-End for the SHG, Pondicherry.
 TABLE OF CONTENT
CHAPTE
TITLE PAGE NO
R
ACKNOLEDGEMENT

SYNOPSIS

1 INTRODUCTION

1.1 About the Organization

1.2 About the Project

1.3 Plan of the Project

2 PROBLEM DEFINITION AND FEASIBILITY

ANALYSIS

2.1 Introduction

2.2 Problem Definition

2.3 Feasibility Analysis

2.3.1 Operational Feasibility

2.3.2 Technical Feasibility

2.3.2.1 Hardware Resource

2.3.2.2 Software Resource

3 2.3.3 Economic Feasibility

SOFTWARE REQUIREMENT

SPECIFICATION

3.1 Introduction
 3.1.1 purpose

3.1.2 Scope

3.1.3 Definition ,Acronyms and Abbreviations

3.1.4 References

3.1.5 Overview

3.2 General Description

3.2.1 Product Perspective

3.2.2 Product Function

3.2.3 User Characteristics

3.2.4 General Constraints

3.2.5 Assumptions and Dependencies

3.3 Special Requirements

3.3.1 Behavioral Requirements

3.3.2 Software Requirements

3.3.3 Hardware Requirements

3.3.4 External Interface Requirements

3.3.4.1 System Interface

3.3.4.2 User Interface

3.3.5 Performance Requirements

3.3.6 Design Constraints

3.3.7 Attributes

3.3.8 Other Requirements

3.3.8.1 Database
 3.3.8.2 Help Text

3.3.8.3 Code Reuse

4 SYSTEM DESIGNS-PRELIMARY

4.1 Introduction

4.2 Basic Design Approach

4.3 Design Concept

4.3.1 Modularity

4.3.2 Coupling

4.3.3 Cohesion

4.4 User Interface Designs

4.5 Database Designs

4.6 System Environment

5
SYSTEM DESIGN-DETAILS

5.1 Introduction

5.2 Modules-Purpose and Description

5.2.1 Administration

5.2.2 New Registration

5.2.3 Group Management

5.2.4 Member Maintenance

5.2.5 Account Details

5.2.6 Insurance Maintenance

5.3 Exception Handling

5.4 Security
6
 CODING, TESTING AND IMPLEMENTATION

6.1 Coding

6.1.1 Naming Convention

6.1.1.1 General

6.1.1.2 Variables

6.1.1.3 Constants

6.1.1.4 Methods

6.1.2 Comments

6.2 Testing

6.3 Implementation

7 CONCLUSION AND FUTURE

ENHANCEMENTS

7.1 Conclusion

7.2 Future Enhancement

APPENDIX
BIBLIOGRAPHY
APPENDIX
A - Data Flow Diagram
APPENDIX
B - Data Dictionary
APPENDIX
C - Reports

D - Sample Screens
INTRODUCTION
 CHAPTER-1

INTRODUCTION

1.1 ABOUT THE ORGANISATION

The Women Welfare scheme (SHG) was established in 1993 by Government of

Pondicherry under the bank, 1953 to serve as a Nodal institution for financing the development
schemes for Women Welfare Community and work for their Social Economic Development.

Funds being on the basis of all these welfare activities, SHG get funds from the
Government of India, Government of Pondicherry and the Financial Institution like HDFC,SBI
and Indian Bank etc., Women Welfare Scheme is an apex funding body and SHG is the
Channelizing Agency for the schemes. The various loan schemes of Women Welfare Scheme ,
the repayment of which Ranges 1 to 2 years, are the best attraction and popular among the
beneficiaries. SHG undertakes to identify the beneficiaries and collect the loan and interest from
the beneficiaries.

SPECIALIZED INSTITUTIONAL SCHEMES

This Corporation has been implementing the following schemes for the Women Welfare
Scheme:

 The Women Welfare Scheme was developed for women development. It

allows for positive discrimination in favor of women. The article, under right
to equality and the women who are credit lower income women in India.

MAIN FEATURE OF THE CORPORATION

 Identification of various business and profession and financing such income

generating schemes for the benefit of the Women Welfare Scheme with a
view to improve their living standards.
  Imparting skills and entrepreneurial development training to the unemployed
women for gainful employment or to enable to setup their own business.

1.2 ABOUT THE PROJECT

This project deals with definition and fundamental function of SHG. It can store large
amount of information data’s about the SHG for future use. Accuracy and automatic data’s are
stored in the project. The project is a tool and it is as extension services of SHG. All the details
of each scheme is given below:

 NEW REGISTRATION

New registration may help to add the people to the Women Welfare Scheme.
Through this registration people may get the benefits which are available under the scheme.
After this registration the details are verified by the manager and then the will approved.

 MEMBER DETAILS

In the member details, we can verify a member in a group and we can see the details
of a member.

 LOAN DETAILS

SHG provides loan to at the rate of Rs.25000/- to the Women Welfare community
people living below the poverty line in the UT of Pondicherry for starting petty business in order
to improve the economic condition of their families. The recovery of loans will be made by the
Corporation directly through the field Staffs of the Recovery wing.

 INSURANCE DETAILS

Insurance is means of protection from financial loss. It is a form of risk

management, primarily used to hedge against the risk of a contingent or uncertain loss… the
amount of money charged by the insurer to the policy holder for the coverage set forth in the
insurance policy is called the premium.
1.3 PLAN OF THE REPORT

The report is intended to capture the complete life cycle of the project, starting from
the development of the idea to build the system till exploring never dimensions to enhance the
system.

CHAPTER 2: Problem Definition and Feasibility Analysis

This chapter lays down the objectives of the system and the feasibility analysis of the
project on operational, technical and economic terms, which helps to determine whether the
project is feasible from the above aspects.

CHAPTER 3: Software Requirements Specification

This chapter contains all that the developer needs to know about the system and also
serves as an agreement between the developer and the client regarding the functionality of the
system. It gives various requirements for the system and describes the general factors such as the
type of environment and other constraints that affect the system.

CHAPTER 4: System Design - Preliminary

This chapter discusses the preliminary level design of the system as such depending on
various design needs of the SHG. It discusses the basic design approach followed and the design
concepts followed in the preliminary design. It also deals with the design of the user interface
providing good interaction, which is the main goal of the Application. The Database design
description is designed in the preliminary level terming the various tables available for
facilitating the application. Finally, the System environment is discussed in the chapter.

CHAPTER 5: System Design - Detailed

This transforms the preliminary designed model to actual design model that serves as
a blueprint for software developer.
CHAPTER 6: Coding, Testing and Implementation

This chapter explains in detail about the various coding conventions followed during
the coding phase. The various kinds of tests that were performed on the system are discussed. It
also discusses the various methods used to develop the system.

CHAPTER 7: Conclusion and Future Enhancements

The conclusion of the report is presented in this chapter. It also specifies the
enhancements that could be done in the days yet to come.

BIBLIOGRAPHY

This is also an important section of the report, which shows the various support and
ideas for the development of the system.

APPENDICES

APPENDIX A: Data Flow Diagrams

Appendix A provides Data Flow Diagrams designed.

APPENDIX B: Data Dictionary

Appendix B provides the Detailed Database Design.

APPENDIX C: Reports

Appendix C provides the Reports available in the system.

APPENDIX D: Sample Screens

Appendix D provides the Sample Screen Shots.

PROBLEM DEFINITION
AND
FEASIBILITY ANALYSIS
 CHAPTER 2

PROBLEM DEFINITION ANDFEASIBILITY ANALYSIS

2.1 INTRODUCTION

This section deals with the definition and description of the basic functionalities of the
system. It specifies the information to be processed and the performance of the components.
Problem definition is the first step in software development life cycle. It specifies the design
constraints and validation criteria to define a successful system.

2.2. PROBLEM DEFINITION

Women Welfare Scheme- A management tool used to estimate the overall loan
repayment, assuming normal operations. The total money, time and resources associated with a
loan or activity.

The problem is to design a tool to manipulate the loan of a Scheme for the SHG ,
Pondicherry. Maintaining a database to store the information about the loan.

2.3. FEASIBILITY ANALYSIS

The purpose of feasibility study is not to solve the problem but to determine if the
problem is worth solving. The following feasibility studies have been performed to assess the
feasibility of the system.

 Operational feasibility
 Technical feasibility
 Economic feasibility

2.3.1 OPERATIONAL FEASIBIITY

This describes the ease with which the user can use the system. It verifies whether the
proposed system can yield the expected results under the specified environment. It is observed
that the design and implementation of the system makes the placement cell more users friendly.
2.3.2 TECHNICAL FEASIBILITY

Technical feasibility checks the technical possibilities of the system to be developed.

Necessary hardware and software resources to develop the system are readily available. No new
technology is used for the design of application. Thereby it can be more feasible. Other sources
of information like books and Internet are also available.

2.3.2.1 HARDWARE RESOURCE

As the proposed system needs to be developed over the Windows platform and it
requires machines with Pentium processors or equivalent and 64 MB RAM or more.

2.3.2.2 SOFTWARE RESOURCE

Software’s required are Windows 10, HTML, CSS, PHP and My SQL These
software’s are readily available in the SHG.

2.3.3 ECONOMICAL FEASIBILITY

The economic feasibility is estimated in terms of

 Time
 Cost
 Manpower

The Time given for this project was three months. This includes the system study,
design, implementation and testing of the system.

The Cost includes the expenditure on the hardware, software requisites of the system
and the manpower. It also includes the cost of learning the language.

The Manpower is the number of people involved in the development of the system. In
this case, three people are involved in designing of the application.

The Program section SHG is providing all the resources in terms of hardware, software
and skilled staff without incurring any extra cost. Thus, the system is highly available.

Hence the entire system is feasible.

 SOFTWARE
REQUIREMENTS
SPECIFICATION
 CHAPTER 3
SOFTWARE REQUIREMENTS SPECIFICATION
3.1 INTRODUCTION

The following text had been submitted to the SHG, Pondicherry by the developer as a
separate SRS document. The document has been reproduced here for easy reference of readers.
The SRS is developed as a consequence of analysis for identifying the requirements and
understanding the system more clearly.

3.1.1 PURPOSE

The purpose of this document is to provide an insight into the requirements for the
development of application for SHG, Pondicherry. The content of this document shall serve as a
mutual binding agreement between the client and the designer/developer concerning the
functionality that the application should exhibit.

3.1.2 SCOPE

The scope of the product is a tool for the SHG for providing the Schemes.

The document is made available through the life cycle and can be produced on demand.
All the functionalities specified in the document will be made available in the tool..

3.1.3 DEFINITION, ACRONYMS AND ABBREVITIONS

DEFINITION

 “Women Welfare Scheme” is a tool developed for SHG, Pondicherry. This tool is
used to manipulate the loan of schemes.

 “Basic Authentication” – This authentication mechanism is the widely used industry

standard method for getting user name and password. The application interface displays
a dialog box where users can enter their account usernames and passwords. The
application attempts to establish a connection using this information.
 ACRONYMS AND ABBREVIATIONS:

SHG - Self Help Group

SRS - Software Resource Specification

PHP - PHP: Hypertext Preprocessor

SQL - Structured Query Language

CSS - Cascading Style Sheets

HTML - Hypertext Markup Language

3.1.4 REFERENCE

Software Design Document -

“Software Engineering” by Roger Pressman.

“Software Engineering Concepts”

by Richard Fairly,

3.1.5 Overview

Section 3.2 General Description - This section provides a general description of the
product “Women Welfare Scheme”. It describes the product perspective, product functions, user
characteristics, general constraints, assumptions and dependencies.

Section 3.3.1 Behavioral requirements - This section describes the functional behavior
and responses of “Women Welfare Scheme”.

Section 3.3.2 Software requirements - This section specifies the software needed to
implement “Women Welfare Scheme”.

Section 3.3.3 Hardware requirements - This section describes the hardware

configuration to implement “Women Welfare Scheme”.

Section 3.3.4 External Interface requirements – This section describes the external
interfaces that “Women Welfare Scheme” interacts with internally and externally.
 Section 3.3.5 Performance requirements - This section describes the performance
requirements of “Women Welfare Scheme” such as error handling, operational response time
and testing requirement.

Section 3.3.6 Design constraints - This section describes the restriction constraints
pertaining to the design of “Women Welfare Scheme”.

Section 3.3.7 Attributes - This section describes the security, reliability, availability,
maintainability, portability, reusability and efficiency issues of “Women Welfare Scheme”.

3.2 GENERAL DESCRIPTION

3.2.1 PRODUCT PERSPECTIVE
 Users Perspective
The System makes the user more effectively and efficiently manipulates the loan of
schemes.
 Developers Perspective

The system provides big challenge to the developer, as the tedious calculations has to
be understood, manipulated and then computerized.

3.2.2 PRODUCT FUNCTIONS

The functionalities to be provided by “Women Welfare Scheme” are as follows.

 Manipulate the Schemes of SHG.

 Record all the information in the database.
 Project them in a well-designed Report.
3.2.3 USER CHARACTERISTICS

The users are categorized under two privilege groups. First, the Manager, who will
check the results. Second, the Staffs available in Program section who are going to use the tool.
3.2.4 GENERAL CONSTRAINTS

“Women Welfare Scheme” needs HTML, CSS and PHP with My SQL.

3.2.5 ASSUMPTIONS AND DEPENDENCIES

“Women Welfare Scheme” is deployed based on the assumption that all the users
systems have Windows 10 and My SQL installed.

3.3 SPECIFIC REQUIREMENTS

3.3.1 BEHAVIOURAL REQUIREMENTS

 The system should be able to provide means for efficient searching.

 The system should provide appropriate error messages or warning through
which flexibility increases.
 The system should enable reliability and correctness of the user interface
should be standard.
 Data at any point of time.
 The system should incorporate all the validations and verifications at any point
of time.
 The system should provide a very good response time.

3.3.2 SOFTWARE REQUIREMENTS

Database Server : My SQL

Tools & Languages : HTML

3.3.3 HARDWARE REQUIREMENTS

Windows 10 running with My SQL with a minimum of 128 MB of RAM and

500 MHz speed.
3.3.4 EXTERNAL INTERFACE REQUIREMENTS

3.3.4.1 SYSTEM INTERFACE

“Women Welfare Scheme” interacts with the underlying OS through system calls,
which are abstracted.

3.3.4.2 USER INTERFACE

A standard user interface with the company logo in the main page is to be provided.
Appropriate help and error messages are to be generated to guide the user.

3.3.5 PERFORMANCE REQUIREMENTS

 The response should be fairly fast.

 The prime requirement is that no error condition shall cause the system to exit
abnormally. That is, the user should not be confused at any point of time about the action
that is happening.
 Errors occurring in a page should return an explanatory error message about the nature of
the error that is comprehensible to the user.
 Since the system incorporates vast features, regression testing has to be performed.
3.3.6 DESIGN CONSTRAINTS

Database has to be designed in such a way so that the search time is very much
reduced. The calculations are to be correct.

3.3.7 ATTRIBUTES

3.3.7.1 SECURITY

Security has to be enforced at two levels. At level 1, no user should be able to modify
the contents of the system and at level 2, only administrator should be able to manipulate the
database.

3.3.7.2 RELIABILITY

The system is guaranteed to provide reliable results. However the reliability depends
on the hardware reliability.
3.3.7.3 AVAILABILITY

The system is available to all the users with restricted privilege within the SHG.

3.3.7.4 MAINTAINABILITY

“Women Welfare Scheme ” is to be developed with ease of maintenance in mind. The

modules are to be clearly documented and possess the least degree of coupling so that they can
be independently modified.

3.3.7.5 PORTABILITY

“Women Welfare Scheme” is to be developed using software that are compatible with
different browsers. Hence, it can be ported across any environment that has a compatible
browser.

3.3.7.6 REUSABILITY

Code pertaining to the general functionalities can be reused since they are generic.

3.3.7.7 EFFICIANCY

The system should be highly efficient in providing the intended functionalities

through efficient code that utilizes less time and storage.

Attribute High Medium Low

Security X
Reliability X
Availability X
Maintainability X
Portability X
Reusability X
Efficiency X

3.3.8 OTHER REQUIREMENTS

3.3.8.1 DATABASE

An RDBMS, which provides efficient storage for huge number of records, is needed.
Details of the tables used are discusses in CHAPTER 4.

3.3.8.2 HELP TEXT

The system is very much self-explanatory. In case of errors and violations sufficient
messages are provided to help the user.

3.3.8.3 CODE REUSE

The functionalities of “Women Welfare Scheme” are generic thus allowing for
expansion and reuse.
SYSTEM DESIGN –
PRELIMINARY
 CHAPTER 4
SYSTEM DESIGN – PRELIMINARY
4.1 INTRODUCTION

The system is designed in two phases:

 Preliminary Design
 Detailed Design
In the preliminary design, design of Schemes is made with the standards design issues.

4.2. BASIC DESIGN APPROACH

The basic design of the “Women Welfare Scheme” is made as per “WATER FALL
Module” (also referred as “Classic Life Cycle Module”)

The Methodology for the project follows the sequence of

 ANALYSIS
 DESIGN
 CODE
 TEST

4.3. DESIGN CONCEPTS

For an efficient and effective system, modular design approach was followed.

4.3.1. MODULARITY

The Women Welfare Scheme is divided into three functional modules, which are
independent among themselves. And they are as follows:

 Schemes
 Beneficiaries Enquiry
 Installments
4.3.2. COUPLING

“Coupling is one of the qualitative criteria for measuring the relative interdependence
among modules”.

Strong Coupling mechanism is followed by the system and module interdependency

is provided.

4.3.3. COHESION

“Cohesion is another qualitative criteria for measuring the relative functional strength
of a module”.

The modules in “ Women Welfare Scheme” are provided in such a way that, the order
of cohesion among modules is in Mid-range, which is a good design aspect.

4.4. USER INTERFACE DESIGN

The user interface follows the following design:

Schemes Details

Registration Insurance details

Scheme benefits D less of Beneficiaries

SHG

Member Details
Loan Details

Installment
4.5 DATABASE DESIGN

Proper database design makes a system efficient and effective. The database must be
normalized to receive the goal of efficiency.

The “First Normal Form” (Each field in Table must convey unique information) is
followed in the design of the System.

The “Second Normal Form” (No field must derive from another field) is also
followed in the design of the System.

In addition to the above, “Third Normal Form” (No Duplicate information through
out database) is also followed.

As a whole the system follows the normalization process for complete Database
design.

The Database structure of Women Welfare Scheme consists of the following tables:

 New Registration
 Member Details
 Loan Details
 Insurance Details
 Installment
For detailed database designs refer APPENDIX. B.

4.6 SYSTEM ENVIRONMENT

The system works in HTML environment. Only Visual Basic supported OS can My sql
the tool.

The environment is made user friendly by providing various SWISHmax which doesn’t
distract the environment.
SYSTEM DESIGN –
DETAILED
 CHAPTER 5

SYSTEM DESIGN – DETAILED

5.1. INTRODUCTION

Detailed design is needed to know the working of the “Women Welfare Scheme”. The
design issues made in preliminary design are more elaborately worked out here.

5.2. MODULE –PURPOSE AND DESCRIPTION

The system follows the modular design concept and the system is partitioned into
various modules. Thereby, designing and managing of them is made easier and efficient. The
various modules of “Women Welfare Scheme” are discusses in this Chapter.

5.2.1 MODULE 1: LOAN DETAILS

This module manipulates the loan of schemes. It gives the loan to the eligible
candidates. It first checks the eligible criteria‘s Eg: family annual income, voter id, caste
certificate etc.
5.2.2 MODULE 2: INSTALLMENTS

In this module, the beneficiaries monthly installment details are updated. This module
calculates the last payment and current payment and recovery within the installment periods.

The module calculates scheme and low investment scheme, by using the following
formulae:
Installment:
a = Val (BAmt.Text)/2

b = a * 1 * 6 / 100

c=a+b

d = c / 36

where a is initial amount, b, c, d are constants

 Low Investment scheme:

a= Val (BAmt.Text)/2

b = a * 1 * 4 / 100

c=a+b

d = c / 25

where a is initial amount, b, c, d are constants

5.2.3 MODULE 3: INSURANCE DETAILS

The SHG have its dealings with the beneficiaries. In this module, the beneficiaries
loan collection details are show easily by its name, id and scheme.

5.3 EXCEPTION HANDLING

Exception Handling is a process, in which if something goes wrong the operations of

the system withstands without disturbance.

The SHG system is moderate in exception handling.

5.4. SECURITY

Security is the main goal to be achieved when go for designing an application. And in
the SHG system a medium level of security is provided with basic authentication mechanism.
CODING, TESTING AND
IMPLEMENTATION
 CHAPTER 6
CODING, TESTING AND IMPLEMENTATION
6.1. CODING
The goal of the coding phase is to convert the design of the system into code in a given
language. Insufficient effort in the coding phase will affect both the testing and maintenance
heavily. The aim is always to implement the design in the best possible manner.

“A program should be constructed in a way so that they are easy to write, read and
understand”. One of the most important criteria for judging a program is its readability. The
developers, hence, adopted a standard to ensure readability and maintainability of their
programs. Standards for programming were designed and strictly followed throughout the whole
coding phase.

6.1.1 NAMING CONVENTION

6.1.1.1. GENERAL

 The names should be chosen in a fashion that reflects the purpose.

 The name may be abbreviated if it is so long.
 Underscores should be avoided in the names

6.1.1.2. VARIABLES

Variable names may be composed of a number of Words. The first character of the
name should be in upper case while the first character of the subsequent words in the name
should be in lower case. E.g: Abbbbb.

6.1.1.3 CONSTANTS

Upper case letters should be used for constants.

E.g.: AMOUNT.
6.1.1.4. METHODS

The naming convention for methods is the same as that for variables. The first word of
the name should preferably be a verb.

6.1.2. COMMENTS

Comments are included to increase the clarity of the source code. Documentation of
programs using comments is an important tool that helps to make the code more readable.
Readability in turn ensures maintainability of the code and hence reduction in total development
cost. Comments should, hence, be placed throughout the code. They should be meaningful and
not trivial.

E.g.: ‘ this function validates the date’.

6.2. TESTING

Testing is the process of executing a program with the intent of finding errors. If
testing is conducted successfully it will uncover errors in the software. The objective of testing is
to find the greatest possible number of errors with a manageable amount of effort applied over a
realistic time span. The different verification and validation techniques are part of testing.

Test cases are designed and their outcome is found out manually. Each test case
tells what to do, what data to use and what result to expect. The output of the program with these
test cases as input is noted and compared with the corresponding manual results.

6.2.1 UNIT TESTING

All the modules in this project namely Schemes, Installments and Enquiry have
been individually tested. This test detects errors in coding and logic with each module. The
module were tested and checked for its consistency.

After the code has been developed, reviewed and verified for correspondence to
component level design, unit test case was designed. Each test case was coupled with a set of
expected results.
6.2.2 STRESS TESTING

Entering unexpected value as data is given to the module an error message will appear.
For example if we give negative values for installment amount then the error message should
appear “loan amount should not be negative”. So that the user will be made aware of these
mistakes and enter the correct data.

6.2.3 SYSTEM TESTING

System Testing is a verification of the system with its initial objectives. The entire
system is tested. The testing is done to see if the system developed meets all the requirements of
the users. The outputs of the system were found to be correct. System testing involves two kinds
of activities: Integration Testing and Acceptance Testing.

6.2.3.1 INTEGRATION TESTING

Any software system is complete only if all the sub-systems are integrated and work
in harmony. This testing is a systematic technique for constructing the program structure while at
the same time conducting tests to uncover errors associated with interfacing. The unit-tested
components are taken to build a program structure that has been dictated by the design.

All modules such as Schemes, installments and enquiry are integrated by giving
input to each module to check for the correctness of the output. The integration system is carried
out for the results to be proved as accurate.

All the modules are linked in the single MDI form by calling the particular file in
the corresponding menu.

6.2.3.2 ACCEPTANCE TESTING

Acceptance Testing is carried out to determine how for the user’s system,
requirements and needs are satisfied. The actual users are made to test the integrated system. We
tested our applications by giving it to the user and the user needs are satisfied.
6.2.3 REGRESSION TESTING

Regression testing is the re- execution of some subset of tests that have already been
conducted to ensure that changes have not propagated unintended side effects. This testing is
applied to ensure that no side effects occur.

6.2.4 CLUSTER TESTING

Cluster testing integrates a set of collaborating pages. Test cases are derived to
uncover errors in the collaborations.

6.2.5 VALIDATION TESTING

Validation succeeds when software functions in the manner that can be reasonably
expected by the customer. Software validation is achieved through a series of black box tests that
demonstrate conformity with requirements. The validation of this system focused on user-visible
actions and user recognizable output from the system. Test cases were developed for this purpose
and each validation test case has been conducted and found that the function and performance
characteristics conform to specification.

The system is implemented in a variety of different environmental configurations and

is tested for compatibility with each configuration.

6.2.6 White Box Testing

 By using this technique it was tested that all the individual logical paths were executed at
least once.
 All the logical decision was tested on both their true or false sides.
 All the loops were tested with data in between the ranges and especially at the boundary
values.
6.2.6 BLACK BOX TESTING
 By the uses of this technique the missing functions were identified and placed their
positions.
 The errors in the interfaces were identified and corrected.
 This technique was also used to identify the initialization and termination errors and
correct them.
6.3 IMPLEMENTATION

The implementation phase is one of the important phases in the evolution of the
software product. Enough importance is ought to be given to it. If the implementation is not
smooth, it gives rise to some problems; the user can doubt the usefulness of the system and be
reluctant to use it.

After the system has been thoroughly tested, it was implemented by deploying it on
the SHG for the users to use it. No special training is needed for using of this system, since it is
trouble-free to access.

All the Staff members found it more efficient and user friendly. Clear and concise
documentation has been provided for the whole system so as to aid the maintainers.

The code in every function, event and procedure has been duly commented with full
description giving the purpose and other details. This enables the maintainers to easily carry out
any modifications.

For further implementation details, check the APPENDIX.A, where the “DATA
FLOW DIAGARMS” are given.
 CONCLUSION
AND
FUTURE ENHANCEMENTS
 CHAPTER 7
CONCLUSION AND FUTURE ENHANCEMENTS
7.1. CONCLUSION

By providing “Women Welfare Scheme” system, the SHG is made more powerful
and functional. And with the proper use of the “Women Welfare Scheme” system, the SHG
may break all its previous records.

Careful verification procedures with real time data were performed and confirmed to
justify the user requirements in both performance and security aspects.

Thus, the system has been found to be working efficiently and error free. The
possibility of data loss has been reduced to a greater extent.

7.2. FUTURE ENHANCEMENTS

There is always a room for improvement in any software package, however good and
efficient it may be. But the improvement requires that the system should be flexible enough for
further modification. Considering this important factor, the system is designed in such a way
that further enhancement without affecting the system presently development.

This package can be enhanced to include features for connecting various branches and
allowing information sharing using public or private network. The information produced by this
system can be used to maintain many other details.

The system manipulates Women Welfare Scheme for loan of schemes.

The report can be represented in other file format system for the organization for easy
verification of the item and easy calculation.
 BIBLIOGRAPHY

Books:

 Roger S. Pressman,
“Software Engineering”: A Practitioner's Approach”.
The McGraw-Hill Companies, Inc., 1997.

 Jeffery C.Jackson,
“Web Technologies: A Computer Science Perspective”,

Pearson Education, 2007.

 Julie C.Meloni,

“Sams Teach Yourself; HTML,CSS and JavaScript All in One”

SAMS, 2014.

 Richard Fairly,
“Software Engineering Concepts”

The Macmillan Computer Publishing.

DATA FLOW DIAGRAM
 APPENDIX – A

DATA FLOW DIAGRAM

Data flow diagram is a structured analysis for showing the movement of data
through the different transformation or processes in the system. A rectangle represents a source
or sinks and is a net originator or consumer of data. A source or sink is typically outside the main
system study. DFD can be hierarchically organized which helps in partitioning and analyzing the
large system such system are called leveled DFD’s. For the hierarchy to be consistence it is
important that net input or output of a DFD for a process are the same input and output of the
higher level DFD.

OVERALL SYSTEM DIAGRAM

 Schemes Details

Registration Insurance details

SHG

Member Details
Loan Details

Installment

REPORT
 LOAN COMPLETED DETAILS

LOAN PENDING DETAILS

SCHEME LIST

Reports

YEARLY LOAN COLLECTION DETAILS

ALL BENEFICIARIES LIST

MONTHLY LOAN COLLECTION DETAILS

ADD & PENDING

 ADD
ENTRY

SCHEME

PENDING

FINANCE SCHEME
 Monthly36 Installments

6% INTEREST
Payment BALANCE

INSTALLMEMT
Monthly 25 Installments

4%
Installment INTEREST BALANCE

SHG SCHEMES
 Recovery scheme Bank based scheme

LOAN DETAILS
FINANCE
SCHEME

Recovery sc SCHEMES

Payment Scheme Rise management scheme

INSTALLMENT
INSURANCE
DATA DICTIONARY

APPENDEX-B

DATA DICTIONARY
 TABLE DESIGN

TABLE NAME : Login

PURPOSE : Maintain user name and password for authentication
PRIMARY KEY : User id

FIELD NAME DATA TYPE CONSTRAINT DESCRIPTION

User id Varchar Primary key User id

password Varchar Not null password

Secret question Varchar Not null Secret question

Secret answer Varchar Not null Secret answer

TABLE NAME : Registration

PURPOSE : Maintain member details
PRIMARY KEY : Member id

FIELD NAME DATA TYPE CONSTRAINT DESCRIPTION

Member id Integer Primary key Member id

Member name Varchar Not null Member name

Address Varchar Not null Address

DOB Integer Not null DOB

Aadhar number Integer Not null Aadhar number

TABLE NAME : Self_Group

PURPOSE : Maintain group details
PRIMARY KEY :Group id

FIELD NAME DATA TYPE CONSTRAINT DESCRIPTION

Group id Integer Primary key Group id

Member id Integer Foreign key Member id

Group name Varchar Not null Group name

Total number of Total number of

Integer Not null
member member

Loan amount Integer Not null Loan amount

Loan type Varchar Not null Loan type

TABLE NAME : Loan_details

PURPOSE : Maintain loan details
PRIMARY KEY : Loan number

FIELD NAME DATA TYPE CONSTRAINT DESCRIPTION

 Loan number Integer Primary key Loan number

Member id Integer Foreign key Member id

Loan issue date Integer Not null Loan issue date

Installment loan Installment loan

Integer Not null
amount amount

TABLE NAME : Loan_installment

PURPOSE : Maintain loan installment details
FOREIGN KEY : Member id

FIELD NAME DATA TYPE CONSTRAINT DESCRIPTION

Loan id Character Foreign key Loan id

Member id Character Not null Member id

Installment date Installment date

Character Not null
amount amount

Remittance date Character Not null Remittance date

TABLE NAME : Insurance

PURPOSE : Maintain insurance details
PRIMARY KEY : Insurance number

FIELD NAME DATA TYPE CONSTRAINT DESCRIPTION

 Insurance number Integer Primary key Insurance number

Member id Integer Foreign key Member id

Insurance date Integer Not null Insurance date

Insurance amount Integer Not null Insurance amount

Premium amount Integer Not null Premium amount

Duration Integer Not null Duration

TABLE NAME : Premium_remittance

PURPOSE : Maintain insurance remittance details
PRIMARY KEY : Insurance number

FIELD NAME DATA TYPE CONSTRAINT DESCRIPTION

Policy number Integer Primary key Policy number

Remit amount Integer Not null Remit amount

Remit date Integer Not null Remit date

APPENDEX-C

REPORTS
 APPENDEX-D

SAMPLE SCREENSHOTS