Professional Documents
Culture Documents
Saving and Credit
Saving and Credit
COLLAGE OF TECHNOLOGY
DBRE MARKOS
January, 2010 E.
Abstract
The purpose of this project is to develop a Web Based employee’s saving and credit association
information management System for Debre markos University, the system reduces the time and
labor required to provide services, Reduce the error that made by the employees, change the
manual storage mechanisms into computerized system (database), provide fast, efficient,
flexible, reliable and secured services for better satisfaction of customers and improves the
motivation of the employees. The existing system of the organization is facing different
problems such as data redundancy, lack of data security and lots of paper work. To solve this
problem the project team used different data collection methods such as Interview, Document
analysis and Practical observation. In order to analyze and design the system we used Object
oriented approach for both analyzing and designing the new system.
To change the current manual system to a web based, needed different software and hardware
tools such as PHP, MYSQLI and others
i
Acknowledgment
First of all we would like to thank GOD for making us able to perform our tasks well, without
the will of GOD everything is impossible. We have a great thanks and appreciation to our
advisor Teshome F for his excellent advice and supervision.
Next we’d like to thank our classmates and friends for their wellness to give important
information and ideas for us. And also we would like to thank association employees for their
good approach at interview time and wellness at giving important information for us.
Generally we will extend our thanks and appreciation to all individuals that give important
information to us.
ii
Table of Contents
Abstract .......................................................................................................................................................... i
Acknowledgment .......................................................................................................................................... ii
Acronym ....................................................................................................................................................... v
List of tables................................................................................................................................................. vi
List of figures .............................................................................................................................................. vii
CHAPTER ONE ........................................................................................................................................... 1
1. INTRODUCTION ................................................................................................................................... 1
1.1 Introduction ....................................................................................................................................... 1
1.2 Background of the project ................................................................................................................. 1
1.3 Problem statement ............................................................................................................................. 1
1.4 Objective of the project ..................................................................................................................... 2
1.4.1 General objective ......................................................................................................................... 2
1.4.2Specific objective .......................................................................................................................... 2
1.5 Scope of the project .......................................................................................................................... 3
1.6 Significance of the project ................................................................................................................ 3
1.7 System requirement .......................................................................................................................... 4
1.7.1 Hardware requirement.................................................................................................................. 4
1.7.2 Software requirement ................................................................................................................... 4
1.7.3 Programing language ................................................................................................................... 4
1.8 Data collection methodology ............................................................................................................ 5
1.8.1 Design Methodology ............................................................................................................. 5
1.8.2 Data gathering technique ............................................................................................................ 5
1.9 Feasibility study ................................................................................................................................ 6
1.9.1 Operational feasibility .................................................................................................................. 6
1.9.2 Economic feasibility .................................................................................................................... 6
1.9.3 Technical feasibility ..................................................................................................................... 6
1.9.4 Legal feasibility............................................................................................................................ 6
CHAPTER TWO .......................................................................................................................................... 7
2. SYSTEM ANALYSIS ............................................................................................................................ 7
2.1 Overview of the existing system ......................................................................................................... 7
2.2 System requirement specification ....................................................................................................... 8
iii
2.2.1 Functional requirement ................................................................................................................ 8
2.2.2 Nonfunctional requirement .......................................................................................................... 9
2.2.3 Business rule ................................................................................................................................ 9
2.3 System requirement analysis ............................................................................................................. 10
2.3.1 Actor and use case identification ............................................................................................... 10
2.3.2 Use case diagram ....................................................................................................................... 15
2.3.3 Use case description ................................................................................................................... 17
2.3.4 Sequence diagram .......................................................................................................................... 23
2.3.5 Activity diagram ............................................................................................................................ 29
2.3.6 Analysis class diagram ............................................................................................................... 33
CHAPTER THREE .................................................................................................................................... 35
3. SYSTEM DESIGN ................................................................................................................................. 35
3.1 Design class diagram ........................................................................................................................ 35
3.2. Class diagram description ................................................................................................................ 37
3.3 Database design ................................................................................................................................ 39
3.3.1Physical data model .................................................................................................................... 40
3.4 User interface design......................................................................................................................... 42
3.5 System architecture (deployment design) ......................................................................................... 47
CHAPTER FOUR....................................................................................................................................... 48
4 IMPLEMENTATION ................................................................................ Error! Bookmark not defined.
4.1. Over view of the programming language used ................................................................................ 48
4.2 Algorithm used.................................................................................................................................. 48
4.3 sample code....................................................................................................................................... 49
CHAPTER FIVE ........................................................................................................................................ 55
5 CONCLUSION AND RECOMMENDATION .................................................................................... 55
5.1 Conclusion ........................................................................................................................................ 55
5.2 Recommendation and future enhancement ....................................................................................... 55
Reference .................................................................................................................................................... 57
iv
Acronym
CPU central processing unit
CSS cascade style sheet
DMU Debre Marko’s University
GB giga byte
GHZ giga hertiz
GUI graphical user interface
HRM human resource management
HTML hypertext markup language
PHP Hyper Text Pre processor
RAM random access memory
UC Use Case
UML unified model language
v
List of tables
Table 1 use case identification .................................................................................................................... 12
Table 2 use case description for login ......................................................................................................... 17
Table 3 use case description for register customer ..................................................................................... 18
Table 4 use case description for create user account .................................................................................. 19
Table 5 use case description for send loan request ..................................................................................... 20
Table 6 use case description for approve loan request ................................................................................ 21
Table 10 description of customer class ...................................................................................................... 37
Table 11 description of admin class ............................................................................................................ 38
Table 12 description of manager class ........................................................................................................ 38
Table 13 description of loan table .............................................................................................................. 39
Table 14 description of request table .......................................................................................................... 39
Table 15 employee table ............................................................................................................................. 40
Table 16 customer table .............................................................................................................................. 41
Table 17 response table ............................................................................................................................... 41
Table 18 meeting table ................................................................................................................................ 42
Table 19 feedback table .............................................................................................................................. 42
vi
List of figures
Figure 1 use case diagram ........................................................................................................................... 16
Figure 2 sequence diagram for login........................................................................................................... 24
Figure 3 sequence diagram for register customer ....................................................................................... 25
Figure 4 sequence diagram for create account ............................................................................................ 26
Figure 5 sequence diagram for send loan request ....................................................................................... 27
Figure 6 sequence diagram for view balance .............................................................................................. 28
Figure 7 Activity diagram for login ............................................................................................................ 29
Figure 8 Activity diagram for create account ............................................................................................. 30
Figure 9 Activity diagram for send loan request......................................................................................... 31
Figure 10 Activity diagram for view balance ............................................................................................. 32
Figure 11 Analysis class diagram ............................................................................................................... 34
Figure 12 design class diagram ................................................................................................................... 36
Figure 13 login page ................................................................................................................................... 43
Figure 14 admin page create account .......................................................................................................... 44
Figure 15 register customer ........................................................................................................................ 45
Figure 16 send request ................................................................................................................................ 46
Figure 17 deployment design ...................................................................................................................... 47
vii
CHAPTER ONE
1. INTRODUCTION
1.1 Introduction
As we know today, the world is in technological area so the world is being coming to one
village. As a result, we should to develop an automated system for Debre Marko’s university
credit association management system.
Debremarkos university employee’s saving and credit association is an organization under the
control of Debremarkos university employees that provides saving and credit services for
employees in the university that wants to use the services. The association manages different
employees like accountants, cashers, and other members
This system provided service to employees of Debre Marko’s university for saving and loan
money. In once credit association the using of money must be performed properly.
1
Some of the problems are:
The customer can’t easily view his/her balance:- since the system is paper based it
is difficult to view balance easily
Post meeting date is difficult and time consuming:- because the meeting date must
be uploaded on different areas of the campus in order to late the members it
Transaction report is presented two times within a year :- since it is paper based it
is difficult to present report monthly
Calculating loan and deposit interest is difficult and not free from errors:-because
all the calculation processes are performed by the accountant so errors may be
occurred
Giving response for loan request takes long time:-since there are many processes to
response for loan request it is time consuming by the current system
The customer must be registered on three papers:-used to protect data from lost
1.4.2Specific objective
The specific objectives of the proposed system is list of objectives that are useful to achieve the
general objectives
2
To develop a system that makes members to view response easily.
3
The system makes the association database accurate and secured.
Modification of the object implementation is easy because objects are loosely coupled.
Understanding of the structure is easy because object oriented modeling and tools used to
represent real world entities.
1.8.2.1 Interview
We made an interview questions with the employees of debre markos university employee’s
saving and credit association to get information that are useful for developing our system.
1.8.2.2 Observation
We observed the working mechanism of the existing system
1.8.2.3 Document analysis
We read the document which is prepared by the association that explains about the association
feature.
5
1.9 Feasibility study
It is an analysis of the ability to complete a project successfully, taking into account legal,
economical, technological, operational and other factors.
6
CHAPTER TWO
2. SYSTEM ANALYSIS
In the existing system generating the overall report of the organization is done manually and also
the association accepts feedback from customer only on the meeting date because of manual
working.
The accountant in the association registers customer and their information such as customer
name, phone number, occupation, address. The customer saves money monthly according to
his/her income by agreement with the association. There are forms available for customer to be
filled by their information such as their name, address, and account number and so on, when they
want to save or take loan money.
To request for loan the customer must go to the HRM enters applicant, and then go to the
association and asks for loan, the accountant in the association register the request and forwards
it to the loan committee, according to the customer capacity to loan the loan committee approve
or deny the request and forwards the response to the main committee, the main committee
forwards it to the manager and the manager forward to accountant, the accountant gives loan
money for the customer if the request is approved. The accountant calculates the saving and loan
interest rate for the customer of the association.
To request for withdraw the customer must go to the association, the accountant in the
association register the request and forwards it to the manager and send back to accountant.
In general, the existing system of DMU employee’s saving and credit association is difficult to
access and manage customer’s account because all the activities are done manually.
Users of the existing system
Manager: a person who manages and coordinates the system activities.
Loan committee: to approve or deny loan request
Accountant: a person who calculate saving and loan interest rate, generate report, register
customer
7
Customer: The people who get service like loan money, deposit money and withdrawal
money from the association.
HRM officer: To check the customer is the member of university and free from loan at
the time of loan request
Finance officer: Snip from salary for deposit and loan.
8
Customer send loan request
Manager view withdraw request
Manager view approve loan request
Accountant view approve loan request checked by manager
Loan committee view loan request
Security- this system has user name and password to login to the system for perform the tasks
and also the data base uses the encryption methods in order to protect the data.
Effectiveness- can user’s complete task, achieve goals with the product
Error handling: - This system allows minimize error by displaying the message box or the system warns
the users who make errors.
9
RB1: the customer before send loan request applicant in human resource management
BR3: the minimum amount of money to loan is 50 birr
BR4: In order to get loan the loan request must be approved by the loan committee
BR5: the customer must be an employee of this university
BR6: the customer can’t take loan more than ones until it repays 1/3 of the loan
BR7: the maximum amount of loan money the member can take is 5times of the
deposited money.
An actor represents anything or anyone that interacts with your system. This may include people,
external systems, and other organizations.
List of actor:
System Administrator: controls the overall system
Manager
Loan committee
HRM officer
Finance officer
Accountant
Customer
10
Use case identification
A use case describes a sequence of actions that provide something of measurable value to an
actor
11
UC26 Login
View reported response
UC27 Login
View loan request
UC28 Login
Approve loan request
Reject loan request UC29 Login
12
Actor: system Administrator:
Register employee
View employee
Manage account
View new customer
Back up DB
Restore DB
View log file
view feedback
view meeting date
Change password
Actor: manager:
post meeting date
View withdraw request
View loan close request
View approve loan
Approve withdraw request
Reject withdraw request
Revise meeting date
View monthly report
View feedback
View employee
Change password
Actor: accountant:
register customer
register repay money
register issue money
send report for deposit
view monthly report
update customer information
13
view customer
view approved request
view notification
view receipt
view reported response
view meeting date
view feedback
change password
Actor: customer
send request
cancel request
view response
view balance
send feedback
view meeting date
change password
Actor: loan committee
view loan request
approve loan request
reject loan request
view meeting date
change password
Actor: HRM officer
register debtor
register representative
view debtor
view representative
change representative
change password
14
Actor: finance officer
view deposit report
view loan report
transfer money
view feedback
change password
15
Figure 1 use case diagram
16
2.3.3 Use case description
Table 2 use case description for login
17
Table 3 use case description for register customer
3. Open customer
registration page. 4. Display customer registration
page.
5. Enter the appropriate
information on the form.
18
Table 4 use case description for create user account
19
Table 5 use case description for send loan request
20
Table 6 use case description for approve loan request
Alternative course of action A: If the request information is not fulfilling the criteria
A1: the system reject the request
21
Table 7 use case description for view report
22
Table 8 use case description for view balance
23
user login form login controller user page database
2 enter um and pw
3 validate
4 invalid
5 refill form
6 valid
7 validate
8 invalid
9 refill form
10 valid
11 display
24
login form Register form
accountant login controller accountant page register link register form database
controller
2: enter un and pw
3 ckeck validate
6 ckeck
7 invalid
8 refill form
25
Create account Create account Create account
Admin login form login controller admin page database
link form Form controller
2: enter un and pw
3 ckeck validate
valid 6 ckeck
7 invalid
8 refill form
18 invalid
19 refill form
26
Send loan Send loan Send loan
customer login form login controller customer page database
link form Form controller
2: enter un and pw
3 ckeck validate
valid 6 ckeck
7 invalid
8 refill form
17 store in DB
27
View balance
customer login form login controller Customer page database
link
valid 6 ckeck
7 invalid
8 refill form
10 valid
11 display page
13 display balance
28
2.3.5 Activity diagram
Activity diagram is UML behavior diagram which shows flow of control or object flow with
emphasis on the sequence and conditions of the flow. An activity diagram visually presents a
series of actions or flow of control in a system similar to a flowchart or a data flow diagram. (5)
Activity diagrams are often used in business process modeling
Some of the activity diagrams of the project known as DMU employee’s saving and credit
association information management system are:
valid invalid
display actor page check display error message
29
admin open home page
invalid
check system display error message
valid
system display create account form admin fill form and click create account
invalid fill
check system display error message
valid
30
Customer open home page
invalid
check the system display invalid message
valid
31
Customeropen home page
check invalid
the system display error message
valid
32
2.3.6 Analysis class diagram
The class diagram in the unified modeling language is a type of static structure diagram that
describes the structure of a system by showing the system's class, their attributes, operations (or
methods), and the relationships among objects.
The class diagram is the main building block of object oriented modeling. Classes in a class
diagram represent both the main elements, interactions in the application, and the classes to be
programmed (5)
33
Figure 11 Analysis class diagram
34
CHAPTER THREE
3. SYSTEM DESIGN
System design is the first part to get into the solution domain in a software development.
The purpose of designing is to show the direction how the system is built and to obtain clear and
enough information needed to drive the actual implementation of the system. It is based on
understanding of the model that the software built on. The objectives of design are to model the
system with high quality. Implementing of high quality system depend on the nature of design
created by the designer.
35
Figure 12 design class diagram
36
3.2. Class diagram description
Table 7 description of customer class
Method Description
Send Used to send request and send feedback
view Used to view response and balance
37
Table 8 description of admin class
Admin attribute
Method Description
Add Used to vote and register user
Block Used to block users from access
View Used to view employee
Create Used to create account to users
Manager attribute
38
Manager method
Method Description
Post Used to post meeting date to users of association
View Used to view customer request and others
39
Unique identifiers are not allowed to have NULL values. These referred to as primary
keys in the physical database. Consider creating a unique index on the identifiers to
enforce uniqueness.
Relationships are module as foreign keys
40
Table 13 customer table
41
Table 15 meeting table
42
Figure 13 login page
43
Figure 14 admin page create account
44
Figure 15 register customer
45
Figure 16 send request
46
3.5 System architecture (deployment design)
A UML deployment diagram depicts a static view of the run time configuration of hardware
nodes and the software components that run on those nodes. UML deployment diagrams show
the hardware for your system, the software that is installed on that hardware, and the middleware
used to connect the disparate machines to one another (5)
47
CHAPTER FOUR
4 IMPLEMENTATION
4.1. Over view of the programming language used
This project used php server side programming technology integrated mysqli database with a
programming language. Because:
The code and its syntax is simple to understand
There is a wealth of online information regarding PHP
It's quick to develop in PHP
PHP is flexible.
It's available for free
It runs on many different operating system easy to access other web based tools through PHP
(i.e. Google)
In general PHP is a widely used open source general purpose scripting language that is especially
suited for web development and can be embedded into HTML.
Register customer
Click on register customer link
Registration form is displayed
Fill user profile data
Click on register button
If (valid)
Display successful message.
Else display invalid input message
create account
Click on create account link
Form is displayed
Fill information for the user
Click on create button
48
If (valid)
Display successful message.
Else display invalid input message
<html>
<head>
<script>
function show_password() {
var x = document.getElementById("password");
if (x.type === "password") {
x.type = "text";
}
else {
x.type = "password";
}
}
</script>
</head>
<body>
<?php
session_start();
include("connection.php");
?>
<?php
49
if(isset($_POST["login"]))
{
if($con)
{
$un=$_POST["username"];
$password=$_POST["Password"];
$pw=md5($_POST["Password"]);
$sql="select * from account where username='$un' and
password='$pw' and status='Active'";
$matchfound=mysqli_query($con,$sql);
if($row=mysqli_fetch_assoc($matchfound))
{
$id=$row['userid'];
$username=$row['username'];
$password=$row['password'];
$role=$row["role"];
50
{
$user=$row11['userid'];
$fn=$row11['fname'];
$coll=$row11['collage'];
$photo=$row11['photo'];
$sql=mysqli_query($con,"delete
from attempt");
$_SESSION['$acc']=$acc;
$_SESSION['$user']=$user;
$_SESSION['$id']=$id;
$_SESSION['$fn']=$fn;
$_SESSION['$fnn']=$fnn;
$_SESSION['$coll']=$coll;
$_SESSION['$photo']=$photo;
$_SESSION['$photoo']=$photoo;
$_SESSION['Username']=$username;
$_SESSION['Password']=$password;
$_SESSION['Role']=$role;
$start_time = date("d M Y @ h:i:s");
$_SESSION['$start_time']=$start_time;
if($role=="administor")
header("location:adminpage.php");
else if($role=="accountant")
header("location:accountantpage.php");
else if($role=="loancommittee")
header("location:loancommitteepage.php");
51
else if($role=="manager")
header("location:managerpage.php");
else if($role=="finance")
header("location:financepage.php");
else if($role=="hrm")
header("location:hrmpage.php");
else if($role=="customer")
header("location:customerpage.php");
}
}
}
else
{
$count="insert";
$sql=mysqli_query($con,"select*from attempt");
$total=mysqli_num_rows($sql);
$total++;
if($total>3)
{
header("location:index1.php");
}
else
{
echo "<FONT color='red'>Please enter correct username and password</FONT>";
echo "<br>you are tries $total times,but allowed 4 times<h1>";
$insert=mysqli_query($con,"insert into attempt values('$count')");
52
}
}
}
else
echo "Connection Failed";
}
?>
<table width="100%">
<tr>
<td>
<table border="" width="100%">
<tr><td bgcolor="#808080" style="font-size: 20px">
<h2 align="center">User Login</h2></td></tr><tr
style="width:100%"><td bgcolor="#1f618d">
<form action="" method="POST" enctype="multipart/form-data">
<h3 style="background:#1f618d;height:30px "align="center">User Name:</h3> <input
type="text" name="username" placeholder="Enter User Name" required="user name is
required" style="height: 35px;width: 100%"><br>
<h3 style="background:#1f618d;height:30px "align="center">Password:</h3> <input
type="password" name="Password"id="password" placeholder="Enter Password"
required="password is required" style="height: 35px;width: 100%"><br><br>
<label >
<input type="checkbox" name="checkbox"
id="chekbox" onClick="show_password();">Show Password
</label>
</td>
</tr>
</table>
</body>
</html>
54
CHAPTER FIVE
This project is developed for DMU employee’s saving and credit association to web based
system in order to give efficient, reliable, timely, secure system, easily accessed, availability
of service throughout Debre markos university .The main propose of this system is not only for
the user but also for the association.
By challenges money problems we develop this new system, this system is very important for
developing Debremarkos university saving and credit association. In this project we tried to
solving complex and manual system to web based mechanism by using this new system such as:
substitute manual to web based system.
The proposed system made computerized to reduce human errors and to increase the efficiency.
Any user who wants to interact with DMU employee saving and credit association should
have some knowledge. In order to clarify who required what knowledge the team
Recommended:-
Related with customer
User must have a basic firsthand experience with systems or other related
experiences.
User must have a basic knowledge of computer.
Training user should be considering for best performance and efficiency of IT
technology.
Related with association
55
Organization should have adequate computer facilities to the activities of student
information system.
Budget should be allocated to take specific measure: -
To change the manual system into new system.
To maintain the system in a timely and speedy manner.
Future enhancement
Online payment
Profit distribution for share
Procurement
56
Reference
(1) (Unpublished) Debre markos university employee's saving and credit association rule and
regulation, 2007
57