Professional Documents
Culture Documents
Ambo University: Institute of Technology Department of Computer Science
Ambo University: Institute of Technology Department of Computer Science
Institute of Technology
Department of Computer Science
Final Project
Online saving and credit association management system for Ambo Town
Group members
Name Id
1. Abdi Fikru BRT/2104/08
2. Bontu Gemachu BRT/2268/08
3.Gena Wonbera BRT/2209/08
4. Kumsa Etana BRT/2296/08
5. Nuhamin Adugna BRT/2310/08
6. Obsa Biftu BRT/2236/08
7. Tashita Mama BRT/2244/08
AMBO, ETHIOPIA
[January 08, 2019]
Ambo University Academic Education Evaluation System
Declaration
This is to declare that this project which is produced under the supervision of Dr. Pramod title
“online saving and credit association management system for Ambo Town” is the sole
contribution of the authors and no part here of has been produced illegally which can be
considered as plagiarism. We will be responsible and liable for any consequences if violation of
this declaration is proven.
Date: ________________
Project members:
Name: Abdi Fikru signature_______________________
Name: Bontu Gemachu signature_______________________
Name: Gena Wonbera signature_______________________
Name: Kumsa Etana signature_______________________
Name: Nuhamin Adugna signature______________________
Name: Obsa Biftu signature_______________________
Name: Tashita Mama signature______________________
The project has been submitted for examination with my approval as university advisor.
Advisor name: ____________________signature______________date_____________________
Approval for the examining board:
_____________________________ _________________
Project coordinator signature
______________________________ _________________
Advisor signature
_______________________________ _________________
Examiner signature
Title Page
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 Ambo Town credit
association management system.
Ambo Town employee’s saving and credit association is an organization under the control of
Ambo Town employees that provides saving and credit services for employees in the Town that
wants to use the services. The association manages different employees like accountants,
cashers, and other members
This system provided service to employees of Ambo Town for saving and loan money. In once
credit association the using of money must be performed properly.
The customer can’t easily view his/her balance: - since the system is paper based it is
difficult to view balance easily
Difficult to shares information easily in the association: - information sharing among
parents is time consuming.
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 .
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
Specific Objective
The specific objectives of the proposed system is list of objectives that are useful to achieve the
general objectives
Simplicity:- software objects model real world objects, so the complexity of our project is
reduced and the program structure is very clear.
Increased Quality:- Increases the quality of our project by-product of this program reuse.
Maintainable:- Object oriented methodology makes code more maintainable. Objects can be
maintained separately, making locating and fixing problems easier.
Data Sources
The data source for this study was primary data sources and secondary data sources. The primary
data collection have been done through questionnaires, group discussion and interview and the
secondary data sources was from Magazines, books, reports, woreda sectors, journals, articles,
Design Methodology
To design the system, the project team has chosen Object Oriented Modeling techniques and
unified modeling language tools. Reason for choosing:
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
To develop this system we prefer OOSAD (Object Oriented System Analysis and
Design) methodology.
This is because an OOSAD provides the following advantages Promotes better
understanding of user requirements.
Leads to clear design by using use case, activity diagrams and sequence diagrams.
Allows to breakdown complicated systems into smaller, clearly defined and more
manageable parts.
Enables the standardization of objects which increases design understanding and
decreases the risk associated with project development.
Development tools
We can see development tools in to ways hardware part and software part.
Hardware requirements
Hardware parts are the physical part that can be touchable and visible components that are
necessary to develop a system. The hardware required to develop the proposed system are:
Table 1 hardware requirements
Tools Activities
Personal computer (PC) Almost all tasks of our project are performed on computer.
RAM 4GB To store the file temporarily
Software requirements
The software parts are the instructional components used to develop a system. Software parts to
develop system are as follows:
Table 2 software requirements
Tools Activities Why?
Sublime, Code writing. Easy to use.
notepad++
MYSQLI For designing the database. Database server for PHP.
server
MS word 2019 Documentation. Easy to use.
E-draw max, to design Unified Modeling Easy to design diagram.
Visio Language (UML) diagrams.
HTML Client side coding. It works with PHP.
XAMP Server to test the system by running. Easy to use.
CSS Style/beautify the content. It works with HTML and PHP
Web For browsing and running the system Better for displaying webpage
browser(Google
chrome)
apache Web server Web server for PHP
Snipping tool Capturing images Easy to use
First we will tests each unit at each system. So, if a problem is encountered it will immediately
maintain at which the problem is occurred.
Integration Testing
After we test each unit of the proposed system we will perform an integration test to check
whether the system meets all the functional requirements. When a number of components are
complete; it will test to ensure that they integrate well with each other, the operating system, and
other components.
System Testing
For verifying as the whole system is functioning in integrated manner and helping in striving
planned goal. System testing is comparing Function of the system developed in relation with
expected function of the system.
1.8 Limitation
The system have a link with bank manually.
The system does not include any financial transaction.
Virus attack: It is difficult to control data from virus but try to scan the data, installing and
updating antivirus software.
Time management problem: this problem by working cooperatively, divide our time by
schedule for each phase of the project and we try to use the schedule effectively. Two of our
group members go to their original homeland while in the process of project development as
result of cold war exist in our campus to solve this problem the remaining group member
together covers this member work. Therefore whatever situation happen or occurred that hinder
during the progression of the project the team try to select the best option to do what expected
and reform it. Risk analyses are to solve the above problems that have used different techniques
for protecting the data from infection. The methods include:-
Computers.
Internet.
Electric power.
Because the proposed system is depending on the above constraints. We assume that there is
internet access and electric power and also needs computers. So electric power and Internet
connection must need to the system to work as intended.
Assumptions
Scheduling
The department gave us calendar for our phase one (documentation part) of project according to
the following chart.
Business rules
A business rule is an operating principle or policies that must be fulfilled in order to the system
function properly and effectively. It often pertain to access control issues, business calculations,
or operating polices and principles of the organization.
BR1: when customers want to get service they must be registered first to the association.
BR2: the customer before send loan request applicant in human resource management.
BR3: the minimum amount of money to loan is 50birr.
BR4: In order to get loan the loan request must be approved by loan committee.
BR5: the customer must be in this town(Ambo).
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.
Efficiency
Operational feasibility
It is the measure of how well the solutions for problems will work in the association.
The project will be beneficial because it satisfies the objectives when developed and used. And
as well the new system brings an easy and user friendly working environment that helps the
employees get services from anywhere as well as the association workers to handle tasks easily.
Technical feasibility
It’s a measure of whether the proposed system is user friendly and enables users to maintain
when problems occur or not.
Our system is technically feasible due to the following reason:-
Member can adapt the system easily.
No need of much more skill
Developed with in the latest technology.
Users can maintain problems easily.
Economic feasibility
Economic feasibility is the analysis of a project's cost benefit analysis in an effort to determine
whether or not it is logical and possible to complete. Our proposed project is economically
feasible because it has less expensive when compared to the existing system, so the project helps
in reducing the cost.
Behavioral/Political feasibility
Behaviorally/politically this project will meet all legal and ethical requirements of the project are
applied. The system we are going to developed is not conflict with any government directives or
cannot interfere with any political issue and with any cultural aspects. So our project is
Behaviorally/politically feasible.
Functional requirement
Functional requirement is described as what the system is done by identifying the necessary task,
action or activity that must be accomplished. User requirement that are all about the functionality
of the system.
These kinds of requirement are directly related to the system, to user, and stockholders.
The proposed system has the following functional requirements:-
Manager register new customer
Manager view loan request.
Manager updates customer information up on it required.
System calculate interest rate for loan and deposit money
Customer view their balance
Manager announces meeting date.
Manager view report such as amount of deposit money, amount of loan money, amount
of customer.
Manager view report such as amount of deposit money, amount of loan money, amount
of customer.
Customer send feedback
Nonfunctional requirement
Non-Functional requirement explains and describes requirements that support the system but
they are not part of the system functionalities. Generally nonfunctional requirements describe the
quality of the system.
Performance: Since the system is web based the deliver response time of the system should be
very fast. It perform its activity that are relating to the vote is accurately.
Security and access permissions: 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.
Backup and Recovery: This system allows backup and recovery by displaying the message box or the
system warns the users who want backup and recovery.
Resources, usability, availability: the customer to access the system at any time 24/7 hour.
Because the Object system development approach gives easier and natural way to break down
problems into simple, small and manageable components so that it reduces the vague appearance
of the big problem. Moreover, it is predominately used and popular method in present software
development trend. The major activities described in this chapter are system requirement
specification, constructing a use case diagram; use case description, constructing sequence and
activity diagram analysis level class diagram and user interface prototype about the proposed
system.
Based on this designing our target is providing the online saving and credit management system
to the Ambo town. Under this system requirement specification we can describe the use case
identification and use case diagram.
UC24 Login
Approve loan request
Reject loan request UC25 Login
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
ID UC1
6. If the username,
password and role is
correct login in the
system.
ID UC2
Actor manager
8. If the filled
information is correct
the system registers the
new customer in the
system database and
display successful
message.
ID UC4
Actor manager
8. If the filled
information is correct
the system saves on the
system database.
ID UC22
Actor customer
8. If the filled
information is valid the
system displays
successful message.
Alternative course of action A: If the customer did not fulfill the requirement
ID UC24
Actor manager
Id UC28
4. display
report button
6. display
monthly report
Id UC32
Actor customer
Scenarios
Table 14 Scenarios
Construct Description Syntax
Use case A sequence of action including the 聽
function that system can perform to
Use case
interact with actor of the system
name聽
聽 Actor name
聽
System boundary Represents boundary between physical
system and the actor who interact with
the physical system
Some of the activity diagrams of the project known as Ambo town online saving and credit
association information management system are:
User interfaces describes how the user interacts with the new system interfaces. User interface
guides the user with user friendly commands how to operate the system. Most of the time user
interfaces does not need training of users, because users expected only now commands. User
interface is a complex task that focuses all the applying common UI design principles and
techniques, applying the station chosen interface design standards and involving our UI design.
4 System Design
4.1 Introduction
System design is the transformation of the analysis model into a system design model. System
design is the first part to get into the solution domain in a software development. Design focus on
transforming the analysis model into the design model that takes into the nonfunctional
requirements and constraints described in the problem statement and requirement analysis.
The purpose of design is to determine how to build the system and to obtain information needed
to drive the actual implementation of the system. The focus is particularly on the solution domain
rather than on the problem domain.
User friendly
Our system should be designed in easy way. It is not difficult to learn or to understand.
The system interface will be well-organized, easy to locate different tools and options.
Simplify
The system should be designed with a primary focus of simplicity for users. Users should
be able to use the system intuitively and with minimum training.
Reliability
The system is able to perform required function under stated conditions for a specified
period of time.
Performance
The system will be designed by considering performs tasks with in a time frame that is
acceptable for the user, and does not require too much memory.
The data Layer maintains the applications data such as customer data , employee data and saving
and deposit data. The middle layer (web/application server) implements the business logic,
controller logic and presentation logic to control the interaction between the application’s clients
and data. The controller logic processes client requests such as requests to view customer result,
to retrieve data from the database. The business logic dictates how clients can and cannot access
application data and how applications process data.
A web server is a program that runs on a network server (computer) to respond to HTTP
requests. HTTP is the standard protocol for transfer data across the internet. The client layer is
the applications user interface containing data entry forms and client side applications. It displays
data to the user.
The client layer interacts with the web/application server to make requests and to retrieve data
from the database. It then displays to the user the data retrieved from the server.
Subsystem Decomposition
From the functional requirements we identified in the system analysis section, the
Fictional/imagine system consists of the following subsystems:
Customer gates service–user or Customer can take service after manager accept them. They send
request and view answer on system immediately after the system display information of
customer.
Login _ enables the system to be accessed by system users. Users in order to interact with the
system must first interact with the login interface. It authenticate the user
Manage user account-enables the manager of the system to interact with the system in order to
administrate it. Admin can create user account, block user account and reactive user account.
<<Application server>>
Multiple levels of security protect sensitive documents and files from unauthorized viewers.
Each user has a security access level and each document has a sensitivity level.
The admin initiates the UI Subsystem by logging into the system and can perform several
sub operations.
The customer, employer and association subsystem is initiated after login into the system
and can perform several sub operations.
The Database Subsystem can be initiated at any point by all Subsystems except the UI
Subsystem. Any request (send request/cancel) to the repository initiates the Database
Subsystem. The system stores its contents in the database between executions. When the
application is run again, it retrieves the contents from the previous execution. Any
change in the contents during this execution updates the database.
Boundary Conditions
Startup goes to system URL and login.
Shout Down. Click logout and close browser.
Error Conditions:
Logging in
Username or password field cannot be blank.
Password and Username don’t match.
Username is wrong does not exist.
Users setting.
User is unable to change certain setting.
Data Entry.
The system fails the customer are entering information.
Log In Module User name and If the user name and Authenticates and
password to enter in the password matches authorizes the user
to the system the main form will be
displayed if not
correct notify the user
Service access What request to get Generate result after Reports the customer
Module service. they complete service services access
information from the
database
5.1 Introduction
In this chapter we mainly focuses on the implementation part, implementation concerned with
the type of material (Hardware and software required), techniques to develop the systems,
samples codes of the system, data preparation, how to install the system, some testing
techniques, start up strategy for the new installed system are briefly described in this part of
documentation.
System testing is the stage of implementation, which is aimed at ensuring that the system works
accurately and efficiently before live operation commences.
Testing is one validation technique of the system with acceptable standard inputs from the
Different testing types. Such as:
Unit testing: by which the team tested components individually. Every module of the System
is separately tested. I.e. the team tests every module by applying some selection mechanism.
Integration and system testing: In this testing part, all the modules will be combined
together and tested it for its fitness with each other and with the systems functionality .we have
tried to test the system for its integration that justifies that major components of the system are
working as per the requirements gathered.
System Testing
Here we compile the whole system stating from initial and proceed testing the whole system to
check out for the errors and flow control of the system.
Server:
for connection to the client computer (to host the system).
Computers.
Network connection (cables).
Printer to print soft copy.
Flash
Software
As Customer:
The customer log into the system using username and password for:
Send Request.
View balance.
Send feedback.
View meeting date.
Change password.
As Admin:
As Finance:
After installing both notepad++/sublime and XAMP/WAMP server software do the following
steps ONLINE SAVING AND CREDIT ASSOCIATION MANAGEMENT SYSTEM FOR
AMBO TOWN(WALQO).
Step1
Step 2
In Xamp Copy the folder to WWW folder in the c:/programfiles/wamp After doing these
steps again, copy the folder “Register” from the Developing Team then.
Step3
Step4
6.2 Recommendation
The system recommends the following
Since our project is effective and efficiency in saving resources we recommended that
this project is only for Ambo town. If the project inclusive all fresh man is Good but to
do this, it must have integrated with customer placement systems
We recommended for another developer of online saving and credit management system
to add other local language.
We recommended West show zone Ambo town to apply our system starting from 2012
because it save time.
We also recommended this system have some limitation this occurs because of lack of
time and connection in our university so we strictly recommended that university must
fulfill material in learning and teaching process.