JIMMA UNIVERSITY

INSTITUTE OF TECHNOLOGOY
FACUALTY OF COMPUTING AND INFORMATICS
PROGRAM: INFORMATION TECHNOLOGY

Final Year Project Group 6

Title: Web Based Tax information management system for Jimma Town

Name ID
Samuel Duguna……………………………….RU1997/12
Beruk Moges……………………………. RU0063/12
Ephrem Desalegn…………………… RU2142/12
Endris Assefa……………………… RU1007/12
Abubeker Tofik…………………… RU0268/12

Advisor
________
___
 Abstract
The aim of this project is to develop Web based Tax information Management system for Jimma
Town Tax revenue Authority Office. The main objective of the system is to prepare a tax summary
of a tax payer fairly based on the taxpayer income and property information in secured manner.
We are doing this Project by using Software development methodology and Hypertext
Preprocessor as a programming tool with MySQL as a database tool. After all the procedures are
completed Tax summary is prepared for the entire tax payer by tax preparer and the prepared tax
summary are announced for the tax payer. If there is complaint about prepared tax summary the
taxpayer submits complaints for the admin using submit complaint form. Once he/she agree by the
calculated tax summary the tax payer can pay the tax and can download or print the Portable
Document format of his Tax Summary receipt. This system will help the administrators to manage
tax payer file such as update tax payer information, registering tax payer, announcing tax payment
period for the taxpayer and generating reports done easily.
CHAPTER ONE

1. Introduction
Since internet controls the whole world, it is essential to develop web-based systems that have
direct integration to the internet. Web based systems are systems that create deep integration
between the client (the user) and the server in order to create better communication in computing
area. In our case Tax administration is the department of the government responsible for the
management of tax obligations specified by the tax law. Its primary task is to ensure that the right
taxpayer pays the right amount of tax at the right time, providing the government with the needed
revenue to deliver goods and services as planned. Tax is the best way of collecting money from
the citizens for the sake of their Welfare, Because the tax or money collected from the people or
company are distribute again for the citizens in case of infrastructure such as school, health care
and others. Every citizen need to pay tax of the property for the particular authorities. If taxpayers want to
pay his tax, he/she should go to office and take bank account of office then go to bank pay bill and come to
office in order to take receipt. This is not an easy job to get all this tax information in different authorities
now days. For that purpose, we are going to develop web based Tax Information Management System,
which can help Organization in order to collect the tax information from different authorities based on the
house no’s, owner name, and TIN by using Web Services and stores the data in our own database and also
it enables us calculating the tax summary accurately. For getting the information, regarding taxes citizens
need to register first. The bills are calculating on different modes like annual, half-yearly, quarterly etc.
According to Ethiopian revenues and custom authority, proclamation there are three categories of taxpayer
depends on their annual income capital. Those are:

Category “A” their capital is >=1,000,000

Category “B” their capital is >=500,000 and less than or equal to 1,000,000 and
Category “C” their capital is<=500,000
Tax is the main source of income or money, which is collect from the peoples and organizations, based on
the rule and regulations for the sake of responding people’s service question. There are two kinds of taxes
in Ethiopia direct and indirect. A direct tax is a tax that a person or organization pays directly to the
entity that imposed it. Indirect taxes are basically taxes that can be passed on to another entity or
individual.
1.1 Background
1.1.1 Background of the organization
The Jimma Town tax revenue office found in Jimma city administration compound is included
under finance it formulated independently with its staff members. Its primary objective is to collect
tax from the taxpayer fairly based on the rule and regulation. Now the organization has members
within Six group which are data collector or interviewer group collect data that are necessary for
calculating the tax summary and they guess the daily income based on the property that the tax
payers have and tax payers working location, data auditor or tax preparer group the task of these
groups are calculate the tax summary for the tax payer based on the collected information, learning
and trainer group they try to give information for the people to pay tax and give training if new
proclamation occur, and cash register machine this is used to collect tax indirectly from the people,
Admin who control all activities that proceed in organization, Casher who collect tax paid by
taxpayer, Record officer Who collect all document related with tax.

1.1.1.1 Vision
Jimma Town tax revenue authority aspires to bring new technology and that has fairness in
collecting tax process in coming few years.

1.1.1.2 Mission
Jimma Town tax revenue office is devoted to provide relevant and quality tax payer process to
produce one of the best ways to collect tax from tax payers and bring fairness that has great
promotion for the development of our country.

1.1.2 Background of the Project

Various Publications have addressed how the Web based tax information is processed and collect
tax from client but their main disadvantage is not give a TIN (Tax Identification Number)
automatically by System. The one that we will develop in future give TIN (Tax Identification
Number) automatically to each tax payer while he/she want to register.

Web based tax information management system is a system that helps the revenue and custom
authority by making their work easy and effective in case of time, cost, manpower, and soon by
changing the manually based system to computerized system integrated to the internet.
The major goals of this project are registering taxpayers to the database, give a unique TIN (Tax
Identification Number), and calculate the tax summary of each taxpayer based on the information
uploaded by the interviewer and observed by the interviewer group.

1.2 Statement of Problem

Since the current system is manual based so the current system is faced with the following
problems Such as:-

Storage problem: due to large amount of tax payer files the physical file or paper
occupy too much space to store tax payer file.
Difficulty in locating tax payer file: due to large amount of tax payer file in the
record officer if we want to locate, search, update tax payer file it is very difficult
to manage.
Poorly generated records: to generate and exchange reports from department to
department it is not effective and efficient.
Human and computational error: Many errors may enable by the employee due
to tedious computation required for managing and calculating the tax summary of
each tax payer because of there is no validation mechanism exists in manual system.
More complaints from tax payer: due to poor management of tax payer
documents the calculation of tax summary may lead to more complaints from tax
payer during payment.
Man power: the manual system requires more manpower to perform operation
like: - manage tax payer file, calculate tax summary, interview and upload tax payer
income file, and to proceed the payment process.
Time: The most important thing in organization and today world is time the system
takes more time to do simple jobs like mentioned above.
Security problem: unauthorized user may access and modify the tax payer file and
other actions due to no security mechanisms exist in manual based system
File may lose easily: tax payer and other files may be lost by fire and natural
disaster.
 1.3 Objectives
1.3.1 General Objective
The main objective of this project is developing web-based Tax information management system
for Jimma Town tax revenue office.

1.3.2 Specific Objective

In order to achieve the general objectives of this project the specific objectives of the project are:-

To Gathering requirements for the system.

Designing user friendly interface.
To implement the system.
Testing the new system and make it available for function.
Finally to develop secured system.

1.4 Methodology
1.4.1 Data Collection methods
We gather necessary information or data that helps us in order to do this project using the following
ways:-

Interviewing: The Project Team has interviewed the tax revenue office workers and
managers to get necessary information about how the current system is going on and what
problems occur.
Observation: The Project Team has observed the current system and identifies the
problems regarding to the tax information system. Therefore, it helps us as easy way to
understand the system and to develop the project.
Document analysis: Using this method of gathering requirements, our team try to analyse
an existing written document that helps us in order to identify the problem and to design
solution.

1.4.2 System Development Methodology

The software development methodology is a framework that is used to structure, plan, and
control the process development of system. The basic purpose of these methodologies is to
provide smooth software development according to the project requirements.
The Waterfall methodology also known as the Waterfall Model is a sequential software
development process, where progress flows steadily toward the conclusion like a waterfall through
the phases of a project that is, requirements, design, development, testing etc.

The waterfall method is a rigid linear model that consists of sequential phase’s requirements,
design, implementation, verification, maintenance focusing on distinct goals. Each phase must be
100% complete before the next phase can start. There’s usually no process for going back to
modify the project or direction.

The reason why we use These System Development Methodology is that:

❖ The linear nature of the waterfall development method makes it easy to understand and
manage Projects with clear objectives and stable requirements can best use the waterfall
method. Less experienced project managers and project teams, as well as teams whose
composition changes frequently, may benefit the most from using the waterfall
development methodology

Figure 1 Waterfall Model

Object Oriented Methodology
Object Oriented Methodology (OOM) is a system development approach encouraging and
facilitating re-use of software components.
Object Oriented Approach: this approach is helpful for us to represent the different phases of
the project through many diagrammatic representations such as activity diagrams, use cases,
sequence diagrams, class diagrams etc. Generally we choose object oriented development design
because of:-

These techniques have a reusability feature.

These techniques provide greater opportunities for users to participate in the development
process.

This increases flexibility.

This also improved quality.

These techniques are latest, powerful, easy and highly usable.

1.4.3 Development Tools

1.4.3.1 Hard Ware Tools
Our project uses the hardware tools like in the bellow table:-

Hard Ware Tools Their Function

Laptop/Computer Used to develop the system in general.

Pen Used to write the drafting of the idea on the paper.

A4 Sized Paper Used to organize the idea before writing to computer.

Flash Disk Will be used to store and secure and transfer data.

Printer Will be used to print document.

Table 1 Hard Ware Tools

1.4.3.2 Soft Ware Tools
Our project uses the software tools like in the below table:-

Software tools Their function

MS Windows Microsoft Windows provides users with a graphical

environment
Web server to store, process and deliver web pages to the users

Mozilla Firefox, let’s you visit websites and do activities within them
Google chrome, like login etc.
Internet explorer
Notepad++,Macromed enable the user to create and edit text
ia visual studio
MS Office Used for Documentation
Microsoft Visio 2013. Used for drawing of different UML Diagrams
E draw Max

Table 2 Software tools

1.5 Project Scope and Limitation

1.5.1 Scope
This system mainly focuses on the tax that needs to be pay by the people who are working in
Jimma Town. The scope of the system is restricted to Jimma Town.

The proposed system will be applicable on:

Announce the amount of bill that the person must be pay along with specified day.
The system tries to calculate the tax summary.
Develop security mechanism for users.
Manage Tax Payer file.
View schedule.
Upload user files.
Assign interviewer.
Manage complaint.
Generate report.
1.5.2 Limitation
Limitation indicates that the activities that cannot support while we replace the existing system
with new system. So, our system has limitations like.

It doesn’t support online interview between Admin, tax interviewer, tax payers, and tax
preparer.
The system is only for literate people.
Online payment system is not going to implement in our project. Instead, we designed
simulation for the online payment systems.

1.6 Significance and Beneficiary

1.6.1 Significance of the Project
Significance of the project deals with why our project is important for the people who use after
project deployment. So our project has significance for client, Tax revenue office department, in
the following way:-

Easy to calculate tax summary.

Decreases work load of the office.
Increased efficiency & effectiveness the tax payment process.
There will not be error in tax summary preparation and calculation.
Improved user satisfaction.
Time saving.
Motivate employees.
Security problem in manual system will be fixed.
Easy Way to submit complaints

1.6.2 Target Beneficiary of the System

There are different bodies that can get benefit from this system such as:-

Mainly the organization Jimma tax revenue office will be highly benefited from
this system.
Tax payers or clients: the user can satisfy by the system because system easy to use.
Employees of Jimma Tax Revenue office organization: It can save resources like time and
money from extra cost.
1.7 Feasibility Study
1.7.1 Economic Feasibility
Economic feasibility is study about the cost feasibility of our project from beginning up to the
completion. Our system is economically feasible, because it reduces the cost needed to perform
certain activities as printing papers for announcing tax pay period and tax summary for the
taxpayers, we see economics feasibility by dividing in two. Those are Tangible and Intangible
benefits

A) Tangible benefits According to our determination the project we are going develop
will provide the next benefits as tangible benefits. Those are:
Reduce the costs used for resources.
Reduce energy consumption which is wasted for file exchange.
Error reduction.
Increase speed of activity.
B) Intangible benefits According to our determination Project That we are going to
develop has intangible benefits like:
Increase security.
Increase employee morale.
Increase management flexibility.
Provide more timely information.

1.7.2 Technical Feasibility

The system is technically feasible; this means the project team has the ability to develop this system
since the team has studied the required methodologies and tools. So the system will be technically
feasible.

1.7.3 Operational feasibility

The System that we are going to develop is operational feasible because the deployment the system
will be test effectively using some of testing mechanisms. This system is free from error because
we will do unit testing for each individual codes in the system if there is error we will fix it and
also we will perform module and system testing to assure the system will be free from error.
Because of this the system will be operational feasible.
1.7.4 Time Feasibility
The new system does not take much time to access every data and information of the organization
because most of the activities done by human power will be changed to computerized way, Since
the computer can do these activities in a short period of time our project can be feasible in terms
of time. Time feasibility concerned with the amount of that takes the project to Complete.

1.8 Risk Assessment

Risk assessment for a web-based tax information management system involves identifying
potential risks and analyzing the likelihood and impact of those risks. Below are some of the key
risks and their potential impact:

Cybersecurity: A web-based tax information management system is vulnerable to

cybersecurity threats such as hacking, malware, and phishing attacks. The impact of a
cybersecurity breach could be severe, resulting in data theft or loss, financial losses, and
damage to the reputation of the organization.
Data Privacy: Tax information is highly sensitive, and a breach of privacy could lead to
legal or regulatory consequences. The impact of data privacy breaches could result in
lawsuits, penalties, and damage to the reputation of the organization.
Technical Issues: Technical issues such as software bugs, compatibility issues, and
hardware failures can impact the effectiveness of the system, leading to errors or loss of
data. The impact of technical issues could result in loss of productivity and financial losses.
Human Error: Users of the system may make errors when inputting data or processing tax
information. The impact of human error could result in financial losses, penalties, and
damage to the reputation of the organization.
To mitigate these risks, it is essential to implement robust security measures, including firewalls,
encryption, and access controls. Regular backups and system maintenance can help prevent
technical issues and system downtime. Employee training can reduce the risk of human error, and
regular compliance audits can ensure regulatory compliance. It is also critical to have a plan in
place to respond to cybersecurity incidents, data breaches, and other emergencies.
1.9 Work Breakdown
Work breakdown refers to the process of breaking down a project or a task into smaller, more
manageable components. It involves identifying the individual tasks and activities required to
complete a project and organizing them into a structured hierarchy.

Breaking down work into smaller components helps to make a project more manageable, identify
potential risks and issues early on, and enables better tracking of progress and resource
allocation. The work breakdown structure serves as a useful tool for project managers to plan,
execute, and monitor their projects. Here are individual tasks and group members roles are
identified below:-

NO NAME ID NO ROLE IN TEAM

SAMUEL DUGUNA Ru1997/12 In all activities

1.
BERUK MOGES RU0063/12 In all activities
2.
Endris Assefa RU1007/12 In data collection and coding
3.
ABUBEKER TOFIK RU0268/12 In data collection and coding
4.
EPHREM DESALEGN RU2142/12 In documentation and coding
5.

Table 3 Work Break down

CHAPTER TWO

Requirement Analysis
Introduction
Requirement Analysis, also known as Requirement engineering, is the process of defining user
expectations for new software being built. From What to How: It involves all the tasks that are
conducted to identify the needs of different stakeholders. therefore requirements analysis means
to analyze, document, validate and manage software or system requirements.

The software requirements analysis process involves the following steps/phases:

1. Eliciting requirements
2. Analysing requirements
3. Requirements modelling
4. Review and retrospective
1- Eliciting requirements

The process of gathering requirements by communicating with the customers is known as eliciting
requirements.

2- Analyzing requirements

This step helps to determine the quality of the requirements. It involves identifying whether the
requirements are unclear, incomplete, ambiguous, and contradictory. These issues resolved before
moving to the next step.

3- Requirements modeling

In Requirements modeling, the requirements are usually documented in different formats such as
use cases, user stories, natural-language documents, or process specification.

4- Review and retrospective

This step is conducted to reflect on the previous iterations of requirements gathering in a bid to
make improvements in the process going forward.
2.1 Current System
2.1.1 Overview of existing System

Currently the system in Jimma Town Tax Revenue Office is using SIGTAS (Standard Integrated
Government Tax Administration System) is an integrated the administration of all taxes using a
single comprehensive information system for storing taxpayer file and uses manual system that
contains different sub functional activities like: calculating the tax summary of each tax payer and
tax payment system and so on. Most of these activities are performed manually by using paper
work. The clients pay their tax through got the tax revenue office physically and take bank account
from tax revenue office then go to bank to pay bill in three categories these are Category ‘A’,
category ‘B’, and category ‘C’ according to their source of income. It is necessary to know how
the current manual system performs different activities and the problems behind it to develop a
better solution. As mentioned above the existing system currently performs different activities
includes managing tax payer information, make payment, schedule the tax payment period, Update
the tax payer information if it is necessary, calculating the tax summary and also Generate report
and submitting complaints in manual way. Performing those activities manually leads to the
following problems:

Security problem
Wastage of time
Wastage of resources
Require huge man power
Calculating tax summary problem.
The target area of the proposed system is to develop a better solution which is called web-based
Tax Information Management system for Jimma Town tax revenue office (i.e. change manual
system in to computerized system) to overcome the above problems.

Problem of Existing System

After we’ve studied how the existing system work flow the current tax revenue office has facing
many problems due to the use of manual based system in day to day activities. In the current
manual based tax information management system problems occurred in the following situations.
Input
An input problem indicates the problems occurred while the employees perform input
activities to the system. Like the following: -
Tax payer registration: -in the existing system tax payers are register on
papers manually then store in SIGTAS so, there is data redundancy, and
incorrectly registered because the manual based system has no validation.
Gathering income detail information from tax payer to calculate tax summary
is also done manually.
Process
Process problems are also problems occurred during processing of tax payer information and
other documents in the existing system
Incorrect tax summary calculation: the main problem in tax revenue office is
calculating tax summary for each individual tax payer incorrectly because,
while calculating it, incorrect and unfair tax summary return delivered to the
tax payer.
Duplication of clients file while registering
Output
Output problems are problems occurred when the employee display, print out and deliver
information from the system.
No fast retrieval of data and some time cause lose data because it store on
local system on SIGTAS.
As we observed and also interview the tax information management system
office the report generating mechanism is paper based, that is any kind of
report is delivered by worker and then it will be transformed to whom it may
concerns. There is also wastage of materials for posting the tax payers list and
information.
There is also wastage of materials for posting the tax payers list and
information.
2.1.2 Description of Actors
Players in the Existing System
The players indicate that the main actors of the existing system. The main actors in tax revenue
authority are the following.
Admin: the manager has the following duties: - register tax payer, update tax payer, delete
tax payer, view annual finance report, view message and comment which is sent from tax
payers and reply for complaint.
Tax preparer/ tax auditor: the auditor calculates the tax summary of each individual tax
payer based on the information gets from the data encoder and generates report.
Interviewer: The responsibilities of this actor are gather information about the income
details of the tax payer by interviewing and observation and generate report.
Tax payer: the tax payer is the core actor in tax information management system that is
responsible for paying tax.
Record officer: a person who is responsible for to record tax payer file and store it.
Cashier: the responsibility is to receive tax bill receipt of bank from the tax payer and give
receipt of office.

2.1.3 Function of Existing System

Tax revenue office performs most of the activities manually. In this organization the data encoder
group collects information about the income level of the tax payers, then generate report for the
manager or administrator after that according to the tax proclamation their level is approved. There
are three levels of tax payer according to the Ethiopian tax payer proclamation rule.
Those are:
1. Category ‘A’, their capital is greater than or equal to one million birr.
2. Category ‘B’, their capital is greater than or equal to five hundred thousand birr.
3. Category ‘C’, their capital is less than or equal to five hundred thousand birr.
In the existing system the tax revenue office performs different activities according to the
following situations.
Input
Tax payer registration: - In the existing system clients are register on papers then store
on SIGTAS and gives TIN (tax payer identification number).
Gathering information about the income details of each tax payer is done by manually.
Process
Calculating tax summary: - In the current system calculating the tax summary for each
individual tax payer is done on paper, calculator and SIGTAS database.
Give receipt for the tax payer after tax payment successfully paid.
Managing tax payer information like deleting, updating and editing.
Schedule interview date and interviewer for the tax payer also done manually.
Output
Generating report: In the existing system the report generating mechanism is paper
based, that is any kind of report is delivered by worker.
Posting the tax payment period for the tax payer.
Announcing the amount of tax bill paid by the tax payer.
Give training for the employees if there is new rule approved and give information why
the government collects tax from the client.
2.2 Business Rules
Tax revenue office, is an organization used for collecting tax from the citizens and it is the back
bone of one’s country economy. Tax revenue office perform operation by proving functions like
making tax summary preparation for the tax payer according to its income details, generating
reports, keeping and tracking tax payers’ information. Thus, to authenticate this all information
the following business rules are specified in the system:

The system couldn’t accept all actors without user name and password

Identifier: BR01
Description: All actors can access the system when they enter valid user name and
password. Else access will be denied.
BR1: All actors cannot do anything without logging into website by using their user
name and password.

BR2: after the system validates all necessary information then it will be accessed.

Only the administrator has the responsibility to manage taxpayer file.

Identifier: BR02

Description: Except the administrator no one can add, delete, and update taxpayer file of system.

BR1.Administrator should log into administrator own page with valid user name & password.

BR2.System must verify whether he/she is the authorized administrator.

BR3.The administrator can add, update and delete taxpayer file information.

The taxpayer can register their property information.

Identifier: BR03
Description: The admin also register taxpayer’s property information as optional and
assigned interviewer to the registered taxpayer.
BR1: The taxpayer should have to log-in to taxpayer own page with valid user name & password.

BR2: System must verify whether he/she is the authorized taxpayer.

BR3: The taxpayer can register theirs owns property.
Identifier: BR04

Each taxpayers has a unique TIN and a profile

Description: The profile includes First name, Last name, sex, Age, salary, and also other necessary
information in general it contains detail personal information.
BR1: taxpayers should have registered in registration page.
BR2: The system gives unique TIN for each taxpayer.
BR3: taxpayers can view their TIN by login to their own page with valid user name & password.
Identifier: BR05
Only Interviewers can upload taxpayer file.
Description: Interviewers can upload taxpayer file those are assigned to her/him.
BR1: Interviewers should have to log-in to the system with their own valid user name and
password.
BR2: The system verifies whether access trial is an authorized user name and password for
Interviewers.
BR3: Interviewers view the schedule and assigned taxpayers then upload their file after
interviewed them.
Identifier: BR06
Tax preparer can calculate the tax.
Description: Tax preparer can calculate the tax based on the file received from interviewer.
BR1: Tax preparer should have to log-in to the system with their valid user name and password.
BR2: The system verifies whether access trial is an authorized user name and password for tax
preparer.
BR3: Tax preparer view the file and calculate tax.
Identifier: BR07
Taxpayer can view their calculated tax summary.
Description: Taxpayer can view the calculated tax summary about his/her income capital and if
there is complaint, he/she submit complaint.
BR1: Taxpayer should have to log-in to the system with their valid user name and password.
BR2: The system verifies whether access trial is an authorized user name and password for
taxpayer.
BR3: Taxpayer their own calculated tax summary using their own TIN.
2.3 Proposed System
2.3.1 Overview of Proposed System
After We studying the current tax information Management system problems, we decide to
develop a computerized system to remove these problems. so the proposed system is a web based
tax information management system the system has web server, database and client browser. The
server is used to fetch data from the database and store data in to the database according to the
instruction of the user.

Database server

Figure 2 Overview of Proposed System

Actors in the proposed system are the following

Manager or admin
Tax payer
Interviewer
Tax preparer/ tax auditor
The proposed system has the following advantages:
Reduce resources consumptions that are wasted in the manual system. For
example, if the information stored in the database then the paper and pen
consumption will be resolved.
The proposed system enhances the performance. For instance, if we want to access
tax payer information simply write the TIN to the text field then search it after that
the tax payer information will be displayed with in microsecond. This indicates that
there will be fast response time in proposed system.
Security problem will be resolved because to access any information the system
needs authentication for that purpose.
Enable easy way of generating report and payment period announce easily.
Tax summary will be calculated easily and efficiently.
2.3.1 Functional Requirement
The functional requirements are functions the system must include to satisfy the user need and to
be acceptable by the user.
The Proposed system provides the following functionalities with respect to each actor:
Admin
❖ The system allows the admin to register and login.
❖ The system allows the admin to view and give response for the complaint of the tax payer.
❖ The system allows the admin to schedule interviewer.
❖ The system allows the admin to post the tax payment period and amount of tax paid by
each individual tax payer.
❖ The system allows the admin to view and generate report.
❖ The system allows the admin to view comment.
❖ The system allows the admin to change password and sign out.

Interviewer
❖ The system allows the interviewer to write comment
❖ The system allows the interviewer to login by using password and username has taken from
admin manually.
❖ The system allows the interviewer to attach files and fill the form about income details of
the tax payer that is necessary for calculating tax summary
❖ The system allows the interviewer to generate report
❖ The system allows the interviewer to change password and sign out
Tax preparer/ Tax Auditor
❖ The system allows the Tax preparer to login by using password and username has taken
from admin manually.
❖ The system allows the Tax preparer to view the files and information’s attached or
submitted by the data encoder.
❖ The system allows the Tax preparer to calculate the tax summary for each tax payer based
on the TIN (tax payer identification number)
❖ The system allows the Tax preparer to generate report
❖ The system allows the Tax preparer to change password and sign out
Tax payer
❖ The system allows the tax payer to register and request for TIN.
❖ The system allows the tax payer to view the tax payment period and the tax summary
prepared.
❖ The system allows the tax payer to make payment.
❖ The system allows the tax payer to submit complaint.
❖ The system allows the tax payer to give comment.
❖ The system allows the tax payer to attach file and fill the form that used to calculate the tax
summary.
❖ The system allows the tax payer to change password and sign out.

2.3.2 Non-Functional Requirements

A non-functional requirement of our project defines the overall qualities or attribute of them
system also referred to as technical requirement pertains to the technical aspects the system must
fulfill such as performance related issues, reliability issues, and availability issues, Non-Functional
Requirements are those requirements that determine the performance of the whole system.
Generally Non-functional requirement are essential to ensure the usability and effectiveness of the
entire software system.
Performance requirements
The user can login to the system easily and can access information on a computer from database.
The server is large which is to accept the request from the users and give responses after processing
the request in a short period of time. The system serves all users simultaneously. The performance
of the system has short response time for a piece of work, high rate.

Security and Access permissions

The new system provides security to prevent and protect unauthorized modification of data, the
new database must have a security to control the activities that can be performed by the users and
determine which information can be viewed and modified. The system generates warning
messages for every invalid input and secures every document in database.
 Backup and Recovery
The proposed system can store any data inserted in to the system in appropriate manner. The stored
data can be kept in database permanently and can be retrieving easily when the user accesses it
from database.
Usability: This system will provide well-structured user manuals
Availability: The system is available for users and there is must be a connection if users
want to access social media of Organization.
Interoperability: The system has the same interface with in different browser.
Flexibility: The system can be easily changed if we need to add new features.
Reliability: Our system can perform its functions without any failure.

2.3.4 System Analysis

System analysis is an essential activity that must be taken in any project in order to have a clear
idea of a proposed system. The analysis phase defines the requirement of the system independent
of how this requirement will be accomplished. This phase defines the problem that the customer
is trying to solve. As mentioned above, in this project, the team used an object oriented system
development methodology which incorporates two principal phases. In this topic, what the team
will do is the object oriented analysis. During object oriented analysis the major activities are
modeling the functions of the system (Use Case Modeling) which includes identifying if there are
any additional actors and use cases, constructing a use case model, and documenting the use case
course of events.

2.3.4.1 Use Case Diagram

The proposed system has four major actors. These are:-

1. Tax payer: a person who is responsible for paying tax according to their income level.
2. Tax preparer/ tax auditor: a person who is responsible to prepare tax summary of the tax
payer using the document uploaded by tax payer and interviewer.
3. Interviewer: a person who is responsible to interview the tax payer about their income
details and upload file that contains the income details of the tax payer.
4. Admin: a person who is responsible to manage the work flow of the office and manage tax
payer and follow the payment process.
Figure 3 Use case Diagram
 2.3.4.2 Use Case Description
Use case description explains in detail the general flow of use case diagrams. Each table
contains the use case name, use case ID, the actor that initiates and interacts with the use case,
and flow of event that show the interaction between the actor and the use case which enable
the user to easily understand the functions of the proposed system.

Use case: Register

Uc1 Register

Participating Actor tax payer

Description System allows users to register for member ship

Pre-condition Actors open website and wants to register

Post condition The actors registered successfully

1. Users are on the homepage and wants register to the system

Event flow.
and press register link.
2. The system displays the registration form
3. Users fills the form and click register button
4. The system checks the validity and if it is valid registered
successfully
5. Use case ends

Alternative event 4.1 If the form is not filled correctly the system displays error try
flow again message and display the form again.

Table 4 Register Use case

 Use case: Login

Uc2 Login

Participating Actor Tax payer, tax preparer, interviewer and admin

Description System allows users to login using user name and Password

Pre-condition Actors open website homepage

The actors should have an account for login

Post condition The actors login to their privileged page

1. Actors click on login button from the website homepage

Event flow
2. The system displays the login form.
3. Users enter user name and password and click login button.
4. The system checks the validity (if error alternative event flow)else
5. The system displays the actors main page
6. Use case ends

Alternative event flow 4.1 If the user name and password is not valid go to event flow 3.

Table 5 Login Use case

 Use case: Register tax payer

Uc3 Register tax payer

Participating Admin , tax payer

Actor

Description System allows users to register the tax payer information

Pre-condition Actors login to the system means should have username and password

Post condition The tax payer registered successfully and TIN assigned

1. The user activates the tax payer registration page from the
Event flow.
admin or tax payer main page
2. The system displays the tax payer registration form
3. User fill the form and click register button
4. The system updates tax payer list (if the user not enter Invalid
Input ; alternative flow of event) else
5. The system displays successfully registered message
6. The use case ends

Alternative flow 4.1. The system displays error message

event
4.2. The system displays tax payer Registration form

4.3. The use case ends

Table 6 Register tax payer Use case

 Use case: Update tax payer

Uc4 Update tax payer

Participating Actor Admin, tax payer

Description System allows users to update the tax payer information or file

Pre-condition Actors login to the system and first tax payer should be available
on the database

Post condition The tax payer information updated successfully

1. The actor activates the update tax payer information page

Event flow.
2. The system displays the text field and search button
3. The actor enters the TIN of tax payer or name that will be
updated and click search button
4. The system displays the tax payer information in the form
5. The actor edit the form and click update button(if the user
not insert Invalid Input ; alternative flow of event ) else
6. The system displays successfully updated message
7. The use case ends
5.1.The system displays error
Alternative flow event
5.2.The system displays the text field and search button
5.3.The use case ends

Table 7 Update tax payer Use cases

 Use case: View tax payer

Uc5 View tax payer file

Participating Manager, tax preparer, interviewer

Actor

Description System allows users to view the tax payer file

Pre-condition Actors login to the system and registered tax payer file should be available
first

Post condition The whole tax payer file list displayed

1. The actor activates the view tax payer file link

Event flow.
2. The system checks the availability of client(alternative flow event)
else
3. displays the tax payer file list
4. The use case ends
2.1.The system displays error
Alternative
2.2.The system displays the manager home page
flow event
2.3.The use case ends

Table 8 View tax payer Use case

 Use case: Delete tax payer

Uc6 Delete tax payer file

Participating Admin
Actor

Description System allows users to delete the tax payer file

Pre-condition Actors login to the system and registered tax payer file should be available first

Post condition The tax payer file removed from the database

1. The actor activates the delete tax payer file link

Event flow.
2. The system displays the tax payer file list
3. Admin selects the tax payer file going to be deleted and press delete
button
4. The system displays are you sure to delete this tax payer file
(alternative flow event)
5. The admin clicks yes button
6. The system deletes the tax payer file and display successfully deleted
message
7. The use case ends
4.1. The system displays the alert message
Alternative flow
4.2. The admin selects no button
event
4.3. The use case ends

Table 9 Delete tax payer Use case

 Use case: Manage news

Uc7 Manage news

Participating Actor Manager

Description System allows users to manage news

Pre-condition Actors login to the system

Post condition The news managed successfully such us posting, deleting and updating news

1. The actor activates the mange new page from the actor home page
Event flow.
2. The system displays the manage news pages link list like post, delete
and update news link
3. The actor clicks the link for example posting news
4. The system displays the post new form
5. The actor fill the form and click post button(if the user not insert Invalid
Input ; alternative flow of event ) else
6. The system displays successfully posted message
7. The use case ends
5.1 The system displays error
Alternative flow
5.2 The system displays the text field and search button
event
5.3 The use case ends

Table 10 Manage news Use case

 Use case: submit complaint

Uc8 Submit complaint

Participating Tax payer

Actor

Description System allows tax payer to submit complaint

Pre- Actors login to the system

condition

Post The complaint submitted successfully

condition

1. The actor activates the submit complaint page from the actor home
Event flow.
page
2. The system displays the complaints form
3. The actor fill the form and click submit button
4. The system checks the validity of the form
5. If the form is valid the system display successfully submitted else
(alternate flow event)
6. The use case ends
5.1 The system displays form is not filled correctly please fill again
Alternative
5.2 The system displays the form
flow event
5.3 The use case ends

Table 11 Submit complaint Use case

 Use case: View complaint

Uc9 view complaints

Participating Manager
Actor

Description System allows users to view complaints

Pre-condition Actors login to the system and complaint first should be submitted by client

Post condition The complaints displayed successfully and can able to give response

1. The actor activates the view complaint page from the actor home page
Event flow.
2. The system displays the complaints submitted by tax payer(alternative
flow event)
3. The use case ends

2.1 The system displays error

Alternative
2.2 The system displays manger homepage
flow event
2.3 The use case ends

Table 12 View complaint Use case

 Use case: Make payment

Uc10 Make payment

Participating Actor Tax payer

Description System allows users to make payment

Pre-condition Actors login to the system, tax summary return should be prepared first

Post condition The payment performed successfully

1. The actor activates the view tax return page from the actor home page
Event flow.
2. The system displays the form that contains tax return and tax payer
details with pay now button
3. The actor view the tax return calculated by the tax preparer if there is
no complaint click pay now button
4. The system displays fill billing information form
5. The user fill the billing information like bank account no, user name,
TIN and click proceed button(alternative event flow )
6. The system checks the amount to be pa with the tax payer balance
6.1 if the balance >= the total tax summary the system add to the
tax organization account the total tax summary in birr
6.2 else you have not enough balance to pay come again later
7. The use case ends

5.1 The system displays your tax return is not calculated

Alternative flow event
5.2 The system displays user homepage
5.3 The use case ends

Table 13 Make payment Use case

 Use case: Calculate tax summary

Uc11 Calculate tax summary

Participating Actor Tax preparer

Description System allows the tax preparer to calculate tax summary of the client

Pre-condition Actors login to the system

The income information must be uploaded or submitted first

Post condition The tax summary of the tax payer calculated successfully

1. The actor activates the calculate tax summary from the tax preparer home
Event flow.
page
2. The system displays the whole tax payer table with prepare tax summary
button
3. The tax preparer click the prepare tax payer button from the table
displayed
4. The form displayed that contains the User name, TIN, Keble, daily
income, annual income, photo, category and location with calculate tax
return button
5. The tax preparer fill the form and click calculate now button (Alternative
flow event)
6. The system displays the tax summary return document
7. The use case ends
5.1 The system displays error
Alternative flow event
5.2 The system displays tax preparer homepage
5.3 The use case ends

Table 14 Calculate tax summary Use case

 Use case: View interviewer

Uc12 View interviewer

Participating Actor Interviewer, tax payer

Description System allows tax payer to view who is assigned for him

Pre-condition Actors login to the system and interviewer must first allocated

Post condition The interviewer displayed successfully

1. The tax payer clicks view interviewer button

Event flow.
2. The system checks is the interviewer assigned(alternate flow
event)
3. displays the interviewer assigned for him
4. Use case ends

Alternative flow 2.1 The system displays the interviewer is not assigned yet
event 2.2 The system displays the tax payer home page
2.3 The use case ends

Table 15 View interviewer Use case

 Use case: Generate report

Uc13 Generate report

Participating Actor Tax preparer, interviewer, tax payer and admin

Description System allows users to generate report

1. The user must have valid username and password

Pre-condition
2. There must be record in the database to be generated
3. The user first login to the system

Post condition The report generated successfully

1. The user clicks “generate report” button

Event flow event
2. Then, the system displays the form
3. The user fills the necessary attribute and click the “generate”
button(alternate flow of event)
4. The System generates the report
5. Use case ends

3.1 The system displays error not filled correctly

Alternative flow event
3.2 The system displays error message that the user entered invalid
data and allows them to enter valid data.
3.3 The use case ends

Table 16 Generate report Use case

 2.3.4.3 Sequence Diagram
Sequence diagram shows the sequence activities performed and their interactions among objects
and used to represent or model the flow of messages, events and actions between the objects or
components of a system. Sequence diagrams are also used primarily to design, document and
validate the architecture and interfaces of the system by describing the sequence of actions that
need to be performed to complete a task

Sequence diagram for Login

Figure 4 Sequence Diagram for login

Sequence diagram for actors’ registration

actors
All Actors registerati registeration registeration acknowldg
registerati
on link form form control ement
on table

Press()
Fill all required
form()

Click submit()
x

Validate()
If valid register()
x
x Check()
If exist you registered before x

If not exist you registered

x
successfully

Figure 5 Sequence Diagram for actor registration

 Sequence diagram for view tax summary

view tax tax tax

actor
homepage summary summary summary
<<tax payer>>
button control form

Login()
Press tax summary btn()
If not prepared()
Check()

If prepared display()
Tax summary not prepared()

Tax summary displayed for the user()

x x x x
x

Figure 6 Sequence diagram for view tax summary

 Sequence diagram for calculate tax summary

actor calculate tax tax summary

home page main page control database
<<tax preparer>> summary link preparetion form

Open()
Login()

Click link()
Open tax form()

Display tax summary form()

Fill form and click preparer Check() Invalid()
btn()

Fill again there is an error()

x Valid()
x x Store()
x

Tax summary prepared succesfully()

x
x

Figure 7 Sequence Diagram for Calculate tax summary

 Sequence Diagram for Submit complaint

submit
actor home
main page complaint control database
<<tax payer>> page
page

Open()
Login()
Activate complaint
page()

Complaint form
displayed()

Fill complaint form and submit() Check()

x Invalid()
x
x
Fill again please()
Valid()
Submit()
Complaint submitted successfully()

Figure 8 Sequence Diagram for Submit complaint

 Sequence Diagram for Payment Process

actor home main view tax bank

billing form control
<<tax payer>> page page summary link account

Open()
Login to
man page() Click tax
summary link()
Form
displayed
Click pay now
button()
Billing form displayed
Fill the form and click
proceed()
Check()
x
x
Invalid()
x Please fill again()
If valid check
x balance()
x
If(balance<Total tax summary) your payment process failed please try again

If(balance>=Total tax summary) you paid successfully take receipt x x

Figure 9 Sequence Diagram for Payment Process

 Sequence Diagram for Upload File

actor upload file income file

homepage main page control
<<interviewer>> link table

Open()
Login()
Click on upload
file page()
Upload file form
displayed

Fill the form and click

upload button
Check()

Invalid()

x Fill the form again()

Valid save()
x
x
x
File uploaded successfully
x

Figure 10 Sequence Diagram for Upload File

 Sequence Diagram for View Tax payer

actor tax payer

home page main page view tax payer
<<manager>> table

Open()

Login()
Click view tax payer
link() Check is
empty()

If empty no tax payer is exist

If no
empty()
Tax payer table is displayed

x x x x

Figure 11 Sequence Diagram for View tax payers

2.3.4.4 State Chart Modeling
A State chart diagram describes a state machine. State machine can be defined as a machine
which defines different states of an object and these states are controlled by external or
internal events. State chart diagram describes the flow of control from one state to another
state. The main purposes of using State chart diagrams are to model the dynamic aspect of
a system, to model the Life time of reactive system, to describe different state of an
object during life time and define state machine to model the state of an object.

State chart diagrams for register and login

activate
initial state login page
Start state activate Start state
fill
registration form
login page form
display
click
registration form
login button
press
incorre
Validate
register button ct
invali ?
d User main page displayed
validate correct
Registered successfully
valid

Figure 12 State chart diagrams for register and login

State Chart diagrams for tax payer registration

admin and tax

payer login first
activates

register tax payer link

Display()
tax payer registeration form
Fill and click If registered
register() before
register button
invalid
send
register button control

Validates?
check
valid check the data base s
If not registered
before
insert in to data base
display

Registered successfully message

Figure 13 State chart diagrams for tax payer registration

 State Chart diagrams for upload tax payer file

actor login yto the system

Start state activate

upload tax payer file page

fill

upload file form

click

upload file button

inva lid validate

valid tax payer file uploaded
successfully

Figure 14 State chart diagrams for upload tax payer file

State Chart diagrams for report generates

Idle state

Activat
e
D is play evaluation page

press
Show result Button

click
select f inancial or technical r eport
click

D is play evaluation result

press
G ener ate r esult button tur ned -on

inva
lid Display e rror message

valid

Repor t Generated

Figure 15 State chart diagrams for report generates

 2.3.4.5 Activity Diagram
Activity diagram is another important diagram in UML to describe the dynamic aspects of the
system. Activity diagram is basically a flowchart to represent the flow from one activity to
another activity. The activity can be described as an operation of the system. The control flow is
drawn from one operation to another. This flow can be sequential, branched, or concurrent.
Activity diagrams deal with all type of flow control by using different elements such as fork, join,
and etc. activity diagram is used to show message flow from one activity to another.

Activity diagram for login

login screen

enter user name

and password

check input

false error message

true

actors main page

Figure 16 Activity diagram for login

Activity diagram for tax payer registration

login to actor main

page

open tax payer

registeration form

fill the from

send

check input

invalid show error message

valid

successfuly
registered

Figure 17 Activity diagram for tax payer registration

Activity diagram for update tax payer information

login

manger and tax payer main

page displayed

click on update tax payer

existing tax payer info

displayed in the form

the manager edit the form

click update button

check

invalid show error message

valid

updated successfully

Figure 18 Activity diagram for Update tax payer file

Activity diagram for make payment and view tax summary

tax payer login to the main page

Th e tax summary is n
activate view tax summary page ot prepared right now please wait

system checks is the tax summary

calculated?

false error message

true
system display the tax summary calculated
in a form

click make payment button

system display the fill billing info form

the tax payer fill the form

Fill again the form
system checks validty

error while filling

invalid
the form
valid
check balance >=tax
summary

you can not make the

fal se
payment process
true

take the tax summary amount in birr from the account

balance of the tax payer and add to the tax
organization account

payed successfully
message you can
take the reciet

Figure 19 Activity diagram for make payment and view tax summary
 2.3.4.6 Class Diagram
The Class diagram for the proposed tax information management system of Jimma Town tax
revenue office shows an object oriented analysis and design in brief. A class diagram shows the
classes of the system, their interrelationships and the operations and attributes of the classes

Users
authenticator
+uname:string
+firstname:sting
+ lastname:string +validateuser(username,paasword
+ password:string ()
+ gender:char +changepassword()
+user type:string
+reister()
+login()
+logout()

*
tax payer 1
manager interviewer tax preparer
+TIN:string +id:string
+id:string -memberName
+salary:float 1 ma +id:string +id:string() +salary:float
1 nag +viewtax return()
+manage taxpayer() 1 * +salary:float +view tax payer()
e +manage account()
+assigninterviewer() +interviewer date() +prepare tax summary()
* +view interviewer() +generate report()
+generatereport() 1 +upload file()
+download rceipt()
+managenews() +view tax payer()
+uploadfile()
+managecomplaint() 1 +generate report() 1 *
1
1
1
manage subm
Pay 1
* it
complaint bill
1 income file
news +TIN:string 1
+daily income:float
+start date:date
upload +income source:string
+date:date +send date:date 1
1 +submit()
+post() +complaint:string +view()
+settaxprice() +sent()
+view() +view()
+response()
billing form

+TIN:string
+payer
tax return name:string
+billing
+tax return id:string amount:double
+tax return date:date
+generate bill()
TIN:string
+lvel:string *
+tax payer name:string 1
+income:float
+download() Prepare tax summary
+calculate()
+print()

Figure 20 Class Diagram

2.3.4.7 User interface prototyping

The reason to do UI prototyping is to quickly and effectively communicate design ideas to

stakeholders and team members. the following are diagrams that show what will design in the
future.

prototypes for home page

Figure 21 Prototypes for home page

Prototype for registration page

Figure 22 registration page prototype

Prototypes for login

Figure 23 login page prototype