Report On Credit Society

A Project Report
On
Online Credit Society
Submitted By
Chokkar Sandeep 13084221014
Nitish Xavier Tirkey 13084221158
M.Sc.(Information Technology)
Semester-IV
Guided By
Mrs. Sonal J. Patel
Submitted to
Department of Computer Science-IIC
Ganpat University, Ganpat Vidyanagar-384012
May- 2015

Department of Computer
Science-IIC
Ganpat University,
Ganpat Vidyanagar-384012
14 /5 /2015
C E R T I F I C A T E
T O W H O M S O E V E R I T M A Y C O N C E R N
This is to certify that the following students of Master of
Science in Information Technology Semester-IV have
completed their project work titled “Online Credit Society”
satisfactorily.
Name Exam No
Chokkar Sandeep 13084221014
Nitish Xavier Tirkey 13084221158
Internal Guide Project Co-ordinator Principal/HOD
Mrs. Sonal J. Patel Mrs. Anjali Gokhale Prof. Dr. Satyen Parikh

A C K N O W L E D G E M E N T
 With immenseness pleasure, we would like to presence the project assignment.
The nature of the project on the development of “Online Credit Society ” has
given us a wide
 opportunity to think We would like to acknowledge all the people who have
helped us at one stage or another by providing the much needed support and
groundwork, to complete it on the specific schedule.
 The Project on Online Credit Society would not have been possible to
complete without support of staff members of Aspiration. We are very thankful
to all of them for making us friendly and comfortable in the organization.
 The Project on Fruit Store Management System would not have been possible
Without support and encouragement of Mrs. Sonal J. Patel Assistant professor
of Department of Computer Science, who have provide their precious time and
knowledge and facilities for completion of Project.
 We are thankful to our honorable H.O.D. of Department of Computer Science,
and whole staff members through whom we are able to do this work and make
ourselves very confident about the Software Development
Yours Sincerely,
Chokkar Sandeep
Nitish Xavier Tirkey

PREFACE
In many respects, Development of any system is very difficult at first time. But
our own experience is a good starting point in ASP.NET MVC.
Working on ASP.NET project is our best experience, because it was a Mini
Project. So it was a great opportunity to work with having many difficulties.
We have practically worked in ASP.NET Programming and completed the
project- “Online Credit Society” in ASP.NET MVC. The main purpose of our
project was to maintain loan, customer accounts and Banking work.
When we have started our final year project in ASP.NET MVC, it seems very
hard at first time. But, as time passed, we worked in it and get the right direction
in project.
Developing a system with new challenges helps us a lot to improve our skills
and knowledge and introduce us the real IT environment.
The Person cannot learn anything by only reading hundreds of books, but they
require the practice of this practical project.
Thus, Bookish Knowledge is not the sequence of computer knowledge but
practical knowledge and practices held an important status.

CONTENTS FOR PROJECT REPORT
Sr. No Title Page
No
1 Project Profile
1.1 Project Title
1.2 Objective
1
2 Requirement specification
About Existing System & Need for new system/ Features of the new system
2
3 Minimum Hardware & Software Requirement 3
4 Function Specification (Only List) 4
5 System Flow Chart 5
6 UML Diagrams
1. Use Case Diagram
2. Sequence Diagram
6
7 Data Dictionary 9
8 Class Diagram 24
9 Process Description
9.1 Description of Process 25
9.2 Process Algorithm 26
10 Input Design 31
11 Output Design 41
12 Testing 62
13 Post Implementation Review 63
14 Future Enhancement 66
15 Conclusion 67
16 Bibliography / References 68

1
Project Title
1.0 Project profile
1.1 Project Title : Online Credit Society
 FRONT-END:-Asp.net
 BACK-END: - My SQL Server
 Web Services: - Asp.net
 Web Back End: - MySQL Server
 Scripting Language:-MVC
1.2 Objective:
 Online Credit Society is “public prosperity” by offering financial services to all groups of
people and offering equal opportunity to all.
 Online Banking Society is an online banking through which the customer can know about
different schemes for the welfare of the self and family.

2
2.0 Requirement specification
Existing System
 Semi Computerized.(MS-Excel, tally, registers)
 Record Generation of various areas is done manually using great amount of
manpower and time.
 The existing system is that the service to the customers is limited to the bank
hours only.
Need For New System
 Fully Computerized.
 Record generation of various areas is done simultaneously at the same time,
saves manpower and time.
 The New System is that the service to the customer is available for 24 X 7.

3
3.0 Minimum Hardware & Software Requirement
SERVER SIDE
Hardware
• Processor : Dual Core
• Hard disk capacity : 500 GB
• RAM capacity : 4GB
Software
• Front End : ASP.NET C# MVC 4
• Back End : SQL SERVER 2012
• Tools : Visual Studio 2012
CLIENT SIDE
Hardware
• Processor : Dual Core
• Hard disk capacity : 50 GB
• RAM capacity : 1GB
•
Software
Web Browser : Google Chrome, Mozilla Firefox
,Internet Explorer etc.

4
4.0 Function Specification
Accounting :-
• Includes financial details.
Members :-
 Includes Customer, Staff details
Schemes :-
• Includes Loan Schemes details.
Agency :-
• Includes Agent details.
Locations :-
• Includes branch details
Commissions :-
• Includes Commission and Interest details.
Rates :-
 Includes Rates of the Schemes details
Transactions :-
• Includes all the Transactions details.

9
7.0 Data Dictionary
• Table Name :- Login
• Description :- Contains username and password for login process
Sr
No
Field DataType Size Constraint Description
1 LoginID integer Primary
Key
It contains Login ID
2 Email Varchar 40 Not Null It Contains Email Address
3 Password Varchar 10 Not Null It contains Password
4 SecQuestion Varchar 50 Not Null It contains Security
question
5 Answer Varchar 20 Not Null It contains Answer
6 UserType Varchar 10 Not Null It contains the type of user

10
• Table Name :- Agent
• Description :- It contains the details of the Agent.
Sr
No
1 AgentID integer Primary
Key
It contains Agent ID
2 BranchID integer Foreign Key It Contains Branch
ID
3 LoginID integer Foreign Key It contains Login ID
4 FirstName Varchar 30 Not Null It contains the first
name
5 MiddleName Varchar 30 Not Null It contains the Middle
Name
6 LastName Varchar 30 Not Null It contains the Last
Name
7 MobileNo Varchar 13 Not Null It contains the Mobile
Number
8 PhotoPath Varchar 20 Not Null It contains the photo
path
9 AddressLine1 Varchar 50 Not Null It contains the
address
address
11 PinCode Integer Not Null It contains the
Pincode
12 CityID Integer Foreign Key It contains the city id
13 JoinDate Date Not Null It contains the
Joining Date

11
• Table Name :- Branch
• Description :- It contains the details of the Branch.
Sr
No
1 BranchID Integer Primary
Key
It contains the
Branch ID
2 CityID Integer Foreign Key It contains the City
ID
3 PhoneNo Varchar 15 Not Null It contains the
Phone Number
4 Address Varchar 50 Not Null It contains the
Address

12
Table Name :- City
Description :- It contains the details of the City.
Sr
No
1 CityID integer Primary
Key
It contains the City
ID
2 CityName Varchar 20 Not Null It contains the City
Name

13
Table Name :- Commission
Description :- It contains the details of the Commissions.
Sr
No
1 CommissionID Integer Primary
Key
It contains the
Commission ID
2 SchemeID Integer Foreign Key It contains the
Scheme ID
3 Month Integer Not Null It contains the
month
4 CommissionRate Decimal (2,2) Not Null It contains the rate
of the commission

14
Table Name :- Customer
Description :- It contains the details of the Customer
Sr
No
1 CustomerID Integer Primary
Key
It contains the
Customer ID
2 FirstName Varchar 30 Not Null It contains the first
name
3 MiddleName Varchar 30 Not Null It contains the Middle
Name
4 LastName Varchar 30 Not Null It contains the Last
Name
address
address
7 PinCode Integer Not Null It contains the
Pincode
8 CityID Integer Foreign
Key
It contains the City
ID

15
9 BirthDate Date Not Null It Contains the
BirthDate
10 Signature Varchar 20 Not Null It Contains the
signature path
11 Photo Varchar 20 Not Null It Contains the photo
path
12 NomineeName Varchar 35 Not Null It Contains the
Nominee Name
13 PANCardNo Varchar 10 Not Null It contains the
pancard number
14 CurrentBalance Decimal (10,2) Not Null It contains the current
balance
16 LedgerID Integer Foreign Key It contains the Ledger
ID
17 BranchID Integer Foreign Key It contains the Branch
ID

16
Table Name :- LedgerGroup
Description :- It contains the details of the ledger Group
Sr
No
1 GroupID Integer Primary
Key
It contains the
Group ID
2 GroupName Varchar 30 Not Null It contains the name
of the group
3 GroupSide Varchar 8 Not Null It contains the
Groupside

17
Table Name :- Ledger
Description :- Contains the details of the ledger.
Sr
No
1 LedgerID Integer Primary
Key
It contains Ledger ID
2 GroupID Integer Foreign
Key
It Contains the Group ID
3 LedgerName Varchar 20 Not Null It contains Ledger Name
4 Balance Decimal (10,2) Not Null It contains Ledger
Balance
•

18
• Table Name :- Scheme
• Description :- Contains the details of the Schemes.
Sr
No
1 SchemeID Integer Primary
Key
It contains Ledger ID
2 SchemeName Varchar 30 Not Null It Contains the name of the
scheme
3 SchemeImage Varchar 20 Not Null It contains Image of the
scheme
4 SchemeDetails Varchar 300 Not Null It contains Scheme Details
5 SchemeAmount Decimal (10,2) Not Null It contains scheme amount

19
Table Name :- Rates
Description :- Contains the details of Rates.
Sr
No
1 RateID Integer Primary
Key
It contains Rate ID
2 SchemeID Integer Foreign
Key
It Contains the Scheme ID
3 Months Integer Not Null It contains number of months
4 Rate Decimal (8,0) Not Null It contains Rate

20
Table Name :- Interest
Description :- Contains the details of Interest.
Sr
No
1 InterestID Integer Primary
Key
It contains Interest ID
2 CustomerID Integer Foreign
Key
It Contains the Customer
ID
3 Duration Integer Not Null It contains number of
months
4 Year Varchar 10 Not Null It contains Rate
5 SchemeID Integer Foreign
Key
6 Amount Decimal (5,2) Not Null It Contains the amount

21
Table Name :- AgentCommission
Description :- Contains the details of agent commission.
Sr
No
1 AgentCommissionID Integer Primary
Key
It contains Rate ID
2 AgentID Integer Foreign
Key
3 Amount Decimal (5,2) Not Null It contains number of months
4 Date Date Not Null It contains Rate
5 Details Varchar 30 Not Null It Contains details

22
Table Name :- Staff
Description :- Contains the details of the Staff.
Sr
No
1 StaffID Integer Primary
Key
It contains Staff ID
2 LoginID Integer Foreign
Key
It Contains the LoginID
3 BranchID Integer Foreign
Key
It contains Branch ID
4 FirstName Varchar 30 Not Null It contains First name
5 MiddleName Varchar 30 Not Null It contains Middle name
6 LastName Varchar 30 Not Null It contains Last Name
7 Qualification Varchar 10 Not Null It contains the Qualification detail
8 Photo Varchar 20 Not Null It contains the Photo
9 MobileNo Varchar 10 Not Null It contains Mobile No detail

23
Table Name :- Transaction
Description :- Contains the details of the Transaction.
Sr
No
1 TransactionID Integer Primary
Key
It contains Transaction
ID
2 LedgerID Integer Foreign
Key
It Contains the Ledger
ID
3 Amount Decimal Not Null It contains Amount
4 TransactionType Varchar 10 Not Null It contains Transaction
Type
6 TransactionDate Date Not Null It contains the
Transaction Date
7 StaffID Integer Foreign
Key
It Contains the Staff ID
8 Details Varchar 50 Not Null It contains the
transaction details

25
9.0 Process Description
9.1 ADMIN
1) Admin Login:-
Admin login the system ,if username and password is correct then it will show the main
form which shows different modules.
2) User Accounts:-
if admin wants to change/edit the user account, or even can create a new account.
3) Schemes:-
Admin can add different schemes for customers.
4) Rates:-
Admin add rates of the schemes.
STAFF
5) Staff Login:-
Admin login the system ,if username and password is correct then it will show the main
form which shows different modules.
6) Account :-
Related to customer account, their details and all.
7) Transactions:-
All transactions related with the customers which are withdraw and deposit.
8) Commissions:-
All transactions related with the agents of their commissions.
9) Interests:-
Interest calculates on every three months and added to the customer balance.

26
9.2 Process Algorithm
Admin:
Step 1: Start
Step 2:Login Details(Email ID, Password)
Step 3:If(Email and Password) is true Then
3.1 Move to Step 4
Else
3.2 Move to Step 2
Step 4: Manage staff, Agents, Schemes, Commissions, Rates and reports
Step 5:Logout
Step 6:End
Staff:
Step 1: Start
Step 2:Login Details(Email ID, Password)
Step 3:If(Email and Password) is true Then
3.1 Move to Step 4
Else
3.2 Move to Step 2
Step 4: Create and Manage staff, Agents, Customer, ledger groups, schemes,
Commissions, Rates and reports
Step 5:Logout
Step 6:End

27
10.0 ScreenShot
1) Login:-Create , Edits , Deletes and can view the page.

31
1)Agent:-Create , Edits , Deletes, view the page and calculate
commission.

36
2) Branch:-Create , Edits , Deletes and can view the page.

37
3) City:-Create , Edits , Deletes and can view the page.

39
4) Commission:-Create , Edits , Deletes and can view the page.

41
5) Customer :- Create , Edits , Deletes and can view the page.

45
6) LedgerGroups:- Create , Edits , Deletes and can view the page.

47
7) Ledgers:- Create , Edits , Deletes and can view the page.

49
8) Schemes :- Create , Edits , Deletes and can view the page.

51
9) Rates :- Create , Edits , Deletes and can view the page.

53
10) Staff :- Create , Edits , Deletes and can view the page.

55
10) Transactions :- Create , withdraw,deposit and interest
calculation.

59
Rports:
1) Branch wise Customers

63
12.0 Testing
1.System Testing:
System testing is the testing of behavior of a complete and fully integrated software product based on the
software requirements specification (SRS) document. In main focus of this testing is to evaluate Business /
Functional / End-user requirements.
This is black box type of testing where external working of the software is evaluated with the help of
requirement documents & it is totally based on Users point of view. For this type of testing do not required
knowledge of internal design or structure or code.
This testing is to be carried out only after System Integration Testing is completed where both Functional &
Non-Functional requirements are verified.
In the integration testing testers are concentrated on finding bugs/defects on integrated modules. But in
the Software System Testing testers are concentrated on finding bugs/defects based on software application
behavior, software design and expectation of end user.
Why system testing is important:
a) In Software Development Life Cycle the System Testing is perform as the first level of testing where the
System is tested as a whole.
b) In this step of testing check if system meets functional requirement or not.
c) System Testing enables you to test, validate and verify both the Application Architecture and Business
requirements.
d) The application/System is tested in an environment that particularly resembles the effective production
environment where the application/software will be lastly deployed.
Generally, a separate and dedicated team is responsible for system testing. And,System Testing is
performed on staging server which is similar to production server. So this means you are testing software
application as good as production environment.

64
13.0 Post Implementation Review
A Post-Implementation Review (PIR) is an assessment and review of the completed working
solution. It will be performed after a period of live running, some time after the project is
completed.
There are three purposes for a Post-Implementation Review:
 To ascertain the degree of success from the project, in particular, the extent to which it met its objectives,
delivered planned levels of benefit, and addressed the specific requirements as originally defined.
 To examine the efficacy of all elements of the working business solution to see if further improvements can
be made to optimise the benefit delivered.
 To learn lessons from this project, lessons which can be used by the team members and by the organisation to
improve future project work and solutions.
In some cases, the first of these objectives can be a contractual issue. Where that is the case, it may
be safer to run separate reviews - one focused on contractual compliance and the other seeking to
derive further benefit from a no-blame review.
A Post-Implementation Review should be scheduled some time after the solution has been deployed. Typical periods
range from 6 weeks to 6 months, depending on the type of solution and its environment.
The PIR is intended to be an assessment and review of the final working solution. There should
have been at least one full processing and reporting cycle completed.
It should not be performed while the initial snags are still being dealt with or while users are still
being trained, coached and generally getting used to its operation.
The PIR should be timed to allow the final improvements to be made in order to generate optimum benefit from the
solution. There is no point in waiting too long as the results are intended to generate that final benefit for the
organisation and team.

65
2.User Acceptance Testing:
User Acceptance testing is the software testing process where system tested for acceptability & validates
the end to end business flow. Such type of testing executed by client in separate environment (similar to
production environment) & confirm whether system meets the requirements as per requirement
specification or not.
UAT is performed after System Testing is done and all or most of the major defects have been fixed. This
testing is to be conducted in the final stage of Software Development Life Cycle (SDLC) prior to system
being delivered to a live environment. UAT users or end users are concentrating on end to end scenarios &
typically involves running a suite of tests on the completed system.
The Acceptance testing is “black box” tests, means UAT users doesn’t aware of internal structure of the
code, they just specify the input to the system & check whether systems respond with correct result.
User Acceptance testing also known as Customer Acceptance testing (CAT), if the system is being built or
developed by an external supplier. The CAT or UAT are the final confirmation from the client before the
system is ready for production. The business customers are the primary owners of these UAT tests. These
tests are created by business customers and articulated in business domain languages. So ideally it is
collaboration between business customers, business analysts, testers and developers. It consists of test suites
which involve multiple test cases & each test case contains input data (if required) as well as the expected
output. The result of test case is either a pass or fail.
Acceptance Testing Definition:
Acceptance Testing is a level of the software testing process where a system is tested for acceptability

66
3.Usability Testing:
Usability Testing is a Black Box Testing Technique. Usability testing is done with users point of view. It is
a technique implemented in user-centred interaction design to evaluate a product or service by testing it
with representative users. On the Web page the usability is a most important and required condition for
survival. If the website is difficult to use then peoples will not stay on the page. If the page content or
details are hard to read or understand then also peoples will leave the page. So Usability testing plays an
important role which assesses how easy user interfaces is to use.
The testing aim is to recognize any usability problems, gather qualitative and quantitative data and establish
the participant’s fulfillment with the product.
Usability testing is an essential element of quality assurance. It is the measure of a product’s potential to
accomplish the goals of the user. Usability testing is a method by which users of a product are asked to
perform certain tasks in an effort to measure the product’s ease-of-use, task time, and the user’s perception
of the experience. This look as a unique usability practice because it provides direct input on how real users
use the system. Usability testing measures human-usable products to fulfill the users purpose. The item
which takes benefit from usability testing are web sites or web applications, documents, computer
interfaces, consumer products, and devices. Usability testing processes the usability of a particular object or
group of objects, where common human-computer interaction studies try to formulate universal principles.
Usability features like “Look and feel” cannot be measured at all time because they are subjective in nature.
In usability testing mostly testers test the ease with use of user interface. Tester can test user-friendly or
non- friendly applications or the products too. Usability testing is a true test of how people actually use a
web site & determines that whether user is feeling comfortable with other applications or Web sites
according to different parameters like; the flow, browsing and layout, speed and content.

67
14.0 Future enhancement
As we have discussed in previous section, software is continuously changing entity. Software
should be reflected with new features wherever new requirements emerge. Software evolution is
one of the big phases in any software’s lifecycle. We have to project towards some newly emerged
and previously ignored functionality in way to enhance the system.
Once the software is implemented and installed into its essential environment, we have to examine
newly emerging requirements, misinterpretation of older requirements, impact due to omission of
some important requirements, and failure of some features.
For this developed system we are willing to provide some new features, they are as quoted below:
1) Enhance Customer Services.
2)We will inform about schemes via sms service..
3) we will keep track of bug found while testing.

68
15.0 Conclusion
Every project work, doesn’t matter software project or any other project, could not be the result of
sole effort, even though developer team consists of a single member. We think that the success of
any project doesn’t depend only on better software development skills, but also, zeal to listen and
help the users. Only user interaction at development phase can give you an idea to fulfill their
requirements.
Because, software is that of developer, up to the development or installation phase, but then after it
is of the users. We experienced that we make the software for users not for fame of being better
programmer or a software developer. Ultimately, users appraise your efforts not your peers.
We have completed our project work using software engineering and system analysis and design
approach. We have done work with preplanned scheduling related with time constraints and result
oriented progress in project development.
We have done this work by regularly being in contact with the persons who are dealing with end
user’s request to know about their requirement and their working strategy and user responsibilities
and regularities. We also discussed problems, which they have to face in the current system.

69
16.0 Bibliography
1)www.asp.net/mvc
2)www.w3schools.com
3)www.Lokhitbharti.com
Book Name Author Publisher Year of Publish
Beginning
ASP.NET MVC 4
Jose Rolando Mcgraw Hill
Private limited
2014

Report On Credit Society

More Related Content

Viewers also liked

Similar to Report On Credit Society

More from Nitish Xavier Tirkey

Recently uploaded

Report On Credit Society