Tax management system for Debre Markos city Revenue

and Custom office

Project Report

Submitted by:-

Name ID

1. Belete Dagnaw TER/1449/08

2. Tewabech Degarege TER/1481/08
3. Getaneh Awoke TER/1458/08
4. Medina Fetu TER/4674/07
5. Alene Girmaw TER/4643/07
In partial fulfillment for the award of the degree of

BACHLER OF SCIENCE IN INFORMATION TECHNOLOGY

Under the guidance of

Ins. Baye A.-------------

Advisor signature

Information Technology Academic Program

School of Computing

Institute of Technology

DEBRE MARKOS UNIVERSITY

DEBRE MARKOS
January/2011/E.
 Tax management for merchants

Acknowledgment
First and foremost we would like to thank God and his mother Saint Mary for giving us the
necessary guidance, energy and drive to complete the project. We owe a great deal of gratitude to
our advisor MSC Baye A. for his unfailing patience, unreserved and valuable advises during the
course of writing this paper. He gave us support to each of the difficulties encountered starting
from writing the project proposal to the finalization of this portion of the project, filled with
sharp intelligence and understanding. Thanks to those who gave us information for the
completion of our project, to tax management system for their valuable comment and helpful
information sharing.
Our Thanks is also forwarded to individuals who directly or indirectly supported us during our
project work.
Last but not least, we would like thank our families and friends for providing us priceless support
and encouragement during our study.

Information Technology Academic Program 2011 E.C Page i

 Tax management for merchants

Abstract
The manual system of calculating tax for each merchant is very time consuming
and prone to error. In order to get different service, the merchant would the
revenue and custom office. Even if the merchant goes to the office that takes other
time and energy or other resource. The officer also prone to error when calculate
tax for each merchant using paper. To overcome all these problems, we propose to
make an automated system. The system will take various inputs like daily income
for each merchant and calculate easily by reducing error. The merchant make any
request and view any necessary information about their tax. Depending upon these
inputs, it will generate a possible agreement, making optimal utilization of all
resources in a way that will best suit any of constraints or rules.
So our aim is to develop a general-purpose automated system which can
effectively generate automatic tax management system when given with several
input constraints.

CONTENTS

Information Technology Academic Program 2011 E.C Page ii

 Tax management for merchants

List of figure...............................................................................................................................................vi
List of table................................................................................................................................................vii
List of acronym and abbreviation..............................................................................................................viii
CHAPTER ONE..........................................................................................................................................1
1. Introduction.........................................................................................................................................1
1.1. Background of the study..................................................................................................................1
1.2. Problem statement...........................................................................................................................2
1.3. Objective of the project...................................................................................................................3
1.3.1. General objective.........................................................................................................................3
1.3.2. Specific objective........................................................................................................................3
1.4. Scope of the project.........................................................................................................................3
1.5. Limitation of the study.....................................................................................................................4
1.6. Significance of the project...............................................................................................................4
1.7. Tools and Methodology...................................................................................................................5
1.7.1. Data collection.............................................................................................................................5
1.8. Programming language used............................................................................................................5
1.9. System requirement.........................................................................................................................6
1.10. System modeling tools.................................................................................................................7
1.11. Feasibility of the study.................................................................................................................7
1.11.1. Technical feasibility.....................................................................................................................7
1.11.2. Operational feasibility..................................................................................................................8
1.11.3. Economic feasibility....................................................................................................................8
1.11.4. Legal feasibility...........................................................................................................................8
CHAPTER TWO.........................................................................................................................................9
2. System analysis...................................................................................................................................9
2.1. Overview of the existing system......................................................................................................9
2.1.1. Users of the existing system........................................................................................................9
2.2. System requirement specification..................................................................................................10
2.2.1. Functional requirement..............................................................................................................11
2.2.2. Non-functional requirement.......................................................................................................12
2.2.3. Business rule..............................................................................................................................13
2.3.1. Actor and use case identification...............................................................................................14
2.3.1.1. Actor identification:...............................................................................................................14
2.3.1.2. Use case identification:..........................................................................................................15

Information Technology Academic Program 2011 E.C Page iii

 Tax management for merchants

2.3.2. Sequence Diagram.....................................................................................................................27

2.3.3. Activity Diagram.......................................................................................................................30
2.3.4. Analysis class diagram...............................................................................................................32
CHAPTER THREE...................................................................................................................................34
3. System design....................................................................................................................................34
3.1. Design Class Diagram...................................................................................................................34
3.2. Database Design............................................................................................................................36
3.2.1. Physical Data model..................................................................................................................36
3.3. User interface design.....................................................................................................................39
3.4. System Architecture (Deployment diagram)..................................................................................41
chapter four...............................................................................................................................................43
4. Implementation..................................................................................................................................43
4.1. Over View of Programming language used...............................................................................43
4.2. Algorithms Used........................................................................................................................43
4.3. Sample code...............................................................................................................................44
4.3.1. For login...............................................................................................................................44
4.3.2 For view tax amount..............................................................................................................47
chapter five................................................................................................................................................49
5. testing................................................................................................................................................49
5.1. Unit testing................................................................................................................................49
5.2. Integration testing......................................................................................................................49
5.3. System testing............................................................................................................................49
5.3.1. Sample test............................................................................................................................49
chapter six.................................................................................................................................................51
6. Conclusion and recommendation.......................................................................................................51
6.1. future enhancement........................................................................................................................51
Reference...................................................................................................................................................53

Information Technology Academic Program 2011 E.C Page iv

 Tax management for merchants

List of figure
Figure 1 use case diagram..........................................................................................................................18
Figure 2 sequence diagram for login.........................................................................................................29
Figure 3 sequence diagram of merchant registration.................................................................................30
Figure 4 send registration request..............................................................................................................30
Figure 5 sequence diagram for tax announcement.....................................................................................31
Figure 6 sequence diagram for create account...........................................................................................31
Figure 7 sequence diagram for view profile..............................................................................................32
Figure 8 Activity diagram for login...........................................................................................................33
Figure 9 Activity diagram for tax announcement......................................................................................33
Figure 10 Activity diagram for view profile..............................................................................................34
Figure 11 Activity diagram for view payment file.....................................................................................34
Figure 12 Analysis class diagram..............................................................................................................35
Figure 13 design class diagram..................................................................................................................37
Figure 14 account table..............................................................................................................................38
Figure 15 license table...............................................................................................................................39
Figure 16 Displeasure table.......................................................................................................................39
Figure 17displeasure decision table...........................................................................................................40
Figure 18 notification table........................................................................................................................40
Figure 19 Notice_user table.......................................................................................................................40
Figure 20 user interface design..................................................................................................................41
Figure 21 web based user interface............................................................................................................42
Figure 22 sample forms on web based user interface................................................................................43
Figure 24 System deployment diagram.....................................................................................................45
Figure 25 data interaction in deployment diagram.....................................................................................46
Figure 26 thin registration sample test…………………………………………………………51

Information Technology Academic Program 2011 E.C Page vi

 Tax management for merchants

List of table
Table 1 Use case identification..................................................................................................................17
Table 2 approve profile use case description.............................................................................................19
Table 3 close license use case description.................................................................................................20
Table 4 login use case description.............................................................................................................21
Table 5 view profile use case description..................................................................................................22
Table 6 upload bank use case description..................................................................................................23
Table 7 create account use case description...............................................................................................24
Table 8 announce tax amount use case description....................................................................................25
Table 9 send displeasure decision use case description.............................................................................26
Table 10 view payment file use case description.......................................................................................27
Table 11 give renewed license permission use case description................................................................29

Information Technology Academic Program 2011 E.C Page vii

 Tax management for merchants

List of acronym and abbreviation

UI ………………………………………………………...…. user interface

HTML….....................................................................................Hypertext markup language

CSS ………………………………………………….………...cascading style sheet

MYSQL………………………………………………………..my structured query language

BR…..........................................................................................business rule

ID…………………………………………………………….…Uniquely identifier

UC……………………………………………………………....use case

UML…………………………………………………………….Unified manipulating language

Information Technology Academic Program 2011 E.C Page viii

 Tax management for merchants

CHAPTER ONE

1. Introduction
The Ethiopian government collects different tax from many bodies in order to administer the
country. The economic plan of the country is proposed by collecting tax revenue from different
bodies. Tax is charged or imposed by the government on persons, entities or properties and
organizations to generate revenue in order to administration. Tax is a major source of income
generation for financing government activities. The individual and organizations are expected to
fulfill their obligations on tax payment as required by law that sated to give financial
administrative power. The Ethiopian government collects taxes from different parts of the
country on many tasks. The country has nine regional states with two city administration. Each
region and city administration collects and manages taxes for better country administration. The
region and city administration also branched to zone, woreda, and kebele tax management
system. The federal government allocates the annual budget of the country as federal, regional
and the each region also include zone, woreda and kebele level from the collected taxes. Those
parts of the country should collect taxes from merchants, employee, organization, farmer and
other entities. The way of tax collection and management in all parts of the country is manual,
but some parts are starting to use the bank to revenue office bank account interaction system for
especially employee and merchant. Then goes to the revenue office to announce the recipient and
then the officer seen and give paid announcement. The current manual way of collecting tax is so
difficult and prone to error. In order to avoid these and the like problem or limitation by
developing web based tax management system for revenue and custom office.

1.1. Background of the study

The project that going to develop will be web based tax management system for revenue and
custom office of merchant in case of Debre Markos city. The purpose of the study will transform
the manual process of collecting tax by web based. The project manages the way of collecting
tax to make fair, transparent assessment and valuation of items, effective or efficient billing or
collection mechanism. The system will not only resolve unfairness, corruption but also it will
provide fast processing and accurate calculation of tax that due on merchants. It also provides

Information Technology Academic Program 2011 E.C Page 1

 Tax management for merchants

secure data of the merchant that stored on a specific data base. The merchant will get everything
regarding with their tax easily and fast. The project will resolve many problems that faced on
current tax management. The project will ensure the obligation of merchants with efficient way
tax collection and management. The project will improve many problems that arise from manual
management system by web based tax management system.

1.2. Problem statement

The existing system has the number of problems in the working procedures of tax management
system.

Form this problem:-

 Time consuming problem

 It takes more time to calculate the payment.
 To search file or any data of one merchant it takes so much time.
 The merchant takes so much time to do any tasks.
 Too much paper work
 The tax calculation or summery is done using manually, so it takes so much
paper work.
 To register each merchant.
 To prepare any request for the problem.
 Loss of data or registered merchant file
 It is so manual if one document is lost, many merchant file or data is lost. It is
difficult to recover the data or file.
 Loss of tax revenue
 Due to the manual process of calculation of tax and not properly recording of
data, the government fails to collect the appropriate tax from merchants.
 Loss data security
 Unauthorized user or merchant easily access and update data or file.
 Improper tax use by the tax collector.
 Prone to corruption.
 High queuing: Customers must wait in long queues to get their turn for registration.

Information Technology Academic Program 2011 E.C Page 2

 Tax management for merchants

 Redundancy: Manual records tend to contain data which are redundant. This is because
Normalization followed is consistent data base is missing feature in manual records.
 High labor cost: additional human force is needed to serve the customers (for instance
to register a traders/customers).
 Low availability of information: When there is some announcements, some customers
may hear others may not, because somebody can damage the paper post on post board
or totally remove it.

1.3. Objective of the project

The aim of the project can be seen using generally or specifically.

1.3.1. General objective

The general objective of the study or project is to develop web based tax management
system for revenue and custom office of merchants in case of the Debre Markose City.

1.3.2. Specific objective

To achieve the general objective of the system, the proposed system consists of the following
specific objectives. These are sub tasks which can be do in order to achieve the general objective.

 To know the way of tax collection and management system

 To create organized database to record merchants’ detail.
 To design a user-friendly registration, payment processing system of merchant.
 To design and build the particular model of the web based tax management system.
 To collect data from different source about the merchant tax payment duties and rules.
 To identify the tasks that the current tax management system uses.

1.4. Scope of the project

The project mainly focuses on web based tax calculation and management system for revenue
and custom of merchant in Debre Markos city including their license management. The activities
that do in the project are:-

 Manage registration merchant’s history.

Information Technology Academic Program 2011 E.C Page 3

 Tax management for merchants

 Calculate the tax amount for each merchant.

 Manage trade license like closing and renewed.
 Manage payment system by sending bank receipt to revenue office.
 Investigate or search document for each merchant.
 Upload different file for merchant or officer.
 Announce tax payment amount for each merchant.
 Create clear announcement about rule and regulation of tax.
 Manage displeasure of merchant.

1.5. Limitation of the study

The project has some limitation or shortage like time and resource that needed to support by any
user. Some of these limitations are:-

 It needs large memory or RAM.

 It needs laptop to use.

1.6. Significance of the project

The new proposed system web based tax management system will more reliable, easy, fast, and
consistent that plays an important role for the system worker and the merchants. The main
significant of the system are:-

 Reduce resource to calculate the payment.

 Minimize the number document that store on the record office about merchant files.
 Avoid tax avoidance and evasion.
 Improve efficiency, effectiveness and security for the tax management.
 Reduce merchant data loss.
 Making an efficient and accurate computation of tax payment due.
 Calculate tax payment without error easily.
 Improve information sharing between the merchant and the revenue officer.
 Reduce corruption that conducted by tax management officer in the system.
 Easily calculate the tax payment system in short period of time without error.
 Control unauthorized data change, registration and view of the merchant file.

Information Technology Academic Program 2011 E.C Page 4

 Tax management for merchants

1.7. Tools and Methodology

This section describes the methods that were used to gather the requirements or information for
the system. There are many things that used to full accomplish the project. Methodology is the
way of gathering information or organized data to accomplish or finish proper works. Among the
different methodologies available we are using object oriented methodology for the analysis and
design of the system. Object oriented methodology enables us to represent complex relations
among different objects and represent data and process with consistent notation throughout the
system.

1.7.1. Data collection

Data collection is the major activity to analyze the current system or to get information about
existing system and to develop the new or proposed system. Data for developing the new system
obtained from different sources. Such as from system users, from documents used in the agency
office and from manuals. In our project use data collection methodology those are interviews,
document analysis and observation.

The methods we used for data collection are:

 Interviewing: to find which problems are available in the current system, important
questions raised while interviewing.
 Document analysis: we have read the document available in Debre Markos city revenue
and custom office.
 Observation: we used in order to analyze the conditions to which the current system is
acting. It is useful to observe how jobs are done, how information flows.
 We use different reference web site.

1.8. Programming language used

Programming language is important to complete the system in the best way and to make it good,
easy and interactive with the customer.

The programming language is:

 Java/jsp: It is simple programming language.

Information Technology Academic Program 2011 E.C Page 5

 Tax management for merchants

 JavaScript: for animation purpose and to display prompt boxes.

 HTML: that used to create web content so it can be displayed by a browser.
 CSS: for the formatting of the system. That is it defines the style of a website’s content.
MYSQL
 MySQL: Open –source, Security, Easy to develop and for database management

1.9. System requirement

In order to develop a web base system, it is very important to select the correct hardware,
software and programming language. Some explanations of the hardware, software to
development tools to the system.

 Hardware requirement

Hardware requirements are the touchable and visible components that are necessary to develop a
system.

 Computers or personal computer: To do different activity or applications. Used to

write documentation and implementation.
 Flash disk (16GB): To store data. The data in the computer may be lost because of
different cases and to take available data from different sources.
 Pen and Paper:-To design the system before typing on the computer.
 Mobile:-for idea exchanging,
 Software requirement
The software requirements are the instructional components used to develop a system. Software
requirement to develop system are as follows:

 Wamp server:-includes MYSQL, apache, PHP.

 Netbean: to do the actual code or work.
 Edraw Max and Visual paradigm editor and AuxerAP:-For drawing different UML
diagrams.
 Browser: -chrome, Firefox, opera, UC browser, Internet explorer used to run the
program.
 Microsoft office word 2010:-For writing documentation

Information Technology Academic Program 2011 E.C Page 6

 Tax management for merchants

 Microsoft PowerPoint 2010:-For presentation

 Window 7 or window 10:-An operating system.

1.10. System modeling tools

Object oriented system analysis and design: -The team plan to use the Object oriented system
analysis and design development methodology for the development of the system among the
different methodologies. Because it is better way to construct, manage and assemble objects that
are implemented in the system. Typically Object oriented system analysis and design uses
Unified Modeling Language to represent and visualize the interacting objects and models in the
system. We use iterative system development approach when doing the project. This may
include the following:

 Use Cases and actors

 Use case diagram
 Class Diagrams
 Activity Diagrams
 Sequence Diagrams and the like.

1.11. Feasibility of the study

The feasibility study aims to provide answers to a number of issues such as Is it easy to
operate? Does the return on investment justify the project and running costs? Is the system
easier for maintenance? Is the system compatible with the legal, political and social
requirements of society in general in Debre Markos city for merchants and the country in
particular?

1.11.1. Technical feasibility

Web based tax management system is technically feasible. In order to ensure whether the
system is technically feasible or not, the system should specify the following cases:

 The software currently possess the necessary technology: Because it achieves the
required goal, as much as possible we tried to encounter all hardware and software
requirements and also the technology is easily available and deployed everywhere.

Information Technology Academic Program 2011 E.C Page 7

 Tax management for merchants

 The new system posses’ necessarily technical experts: In this project the team uses
languages such as HTML, java/jsp, java script and CSS to develop the new system.
All these are the technology side and once the module is developed it can be easily
held by non-technical person, so it doesn’t require any technical expertise.

1.11.2. Operational feasibility

This project is operationally feasible because the proposed system is a good solution maker
of the problem or specific solution will work in the existing system and create a good
environment towards the user of the system. The project wills implement using both
Amharic and English language. So, the proposed system is operationally feasible because:

 We have all the resource needed for its implementation.

 The system is accepted and supported by the users and site viewers.
 The system will minimize the time and man power needed to give fast and hospitable
service to the users.

1.11.3. Economic feasibility

The current system used by the tax revenue officer has enormous expenditure on paper, pen,
time and other costs due to improper mechanism to deal with the customer information. The
project resolves these additional requirements and expenditures by using a computerized
system. Making the new system is economically feasible.

1.11.4. Legal feasibility

The proposed system’s role is to automate tax collection and management system processes of
Debre Markos city revenue and custom office of merchants, it do not interfere or contract with
any of the rules and regulations Debre Marko’s branch or the country tax regulation. Hence, the
system is legally feasible. The system has no conflict with any government directives, because
it gives services for the merchants effectively and efficiently.

Information Technology Academic Program 2011 E.C Page 8

 Tax management for merchants

CHAPTER TWO

2. System analysis
It is a process of collecting and interpreting facts, identifying the problems, and decomposition of
a system into its components. System analysis is conducted for the purpose of studying a system
or its parts in order to identify its objectives.

2.1. Overview of the existing system

The current system is doing the tax management system manually. The system is also complex
and prone to error. Each tax collection and management is do using manual calculation or
recording system. The initial merchant goes to the revenue office to announce his or her trade
licenses to work on the licenses. After goes to the office it is so difficult to get the customer
service office. Even after that the merchants is tired to get service like registered, to announce
and the like activity. But the number of user is difficult to get the service takes so much time or
go back for the other day. After the merchant is registered by the recorder he or she get teaching
or information about tax from the tax information and teaching officer based on the rule and
regulation of the country tax management system. Every information that arise from the system
to merchants or internal system workers are announce on board. Every merchant can get his or
her tax decision after the tax administer officer the merchant day to day incomes that studied by
pursuit officer. The current approved system works on when the merchant tax due five hundred
birr or above he or she pay the tax with the bank account number of the revenue office. Every
data of the merchant are recorded in the record officer and auditor officer for different purpose
like auditing.

2.1.1. Users of the existing system

There are many users for the current tax management system. In order to do the tax management
system the task is allocated to so many users in the system. These users are:-

Customer service officer: give clearance for paid merchant, give tax working document for
merchant, , and give permission to renewed trade license of the merchant, give permission to
close trade license, and give permission to open trade license.

Information Technology Academic Program 2011 E.C Page 9

 Tax management for merchants

Displeasure hearing: view displeasure, send displeasure decision for the merchant, view related
work and view payment file.

Audit officer: Study merchant Personal book, and study merchant payment file from financial
officer then distribute to merchant and Tax decision officer.
Record officer: register merchant history, organize tax payer profile.

Tax education and communication officer: announce rule and regulation of tax for merchant,
create clearness or importance of tax for each merchant by prepare tax leaflets, and initiate
merchants using media about tax.

Pursuit officer detects daily revenues of each merchant, guess daily income of the merchant
then give to decision officer, study debt of merchant, and announce debt of merchant to decision
officer.

Merchant: register license, pay tax, make displeasure, and announce daily income.

Cashier officer: record daily paid tax income from accountant, summarize tax and give payment
receipt publishing.

Tax decision officer: record daily income of merchant from pursuit officer, determine tax
amount for each merchant, and determine level of merchant taxes.

Accountant officer: record daily income from merchant, send payment for cashier officer, if not
payment send to tax decision officer, give payment receipt.

Business licensing officer: renewed license, open license, close license, and view license
permission.

2.2. System requirement specification

System Requirements Specification is requirement by the system to achieve its goal. In this
section we have kept the basic understanding of the requirements and dependencies of the
current system prior to any actual design or development work. We deal the functional and non-
functional requirements of the proposed systems.

Information Technology Academic Program 2011 E.C Page 10

 Tax management for merchants

2.2.1. Functional requirement

A functional requirement defines the capabilities of a system that must be able to perform
successfully. The functional requirement is the study of what a system should be able to do, the
functions it should perform and describes the interactions between the system and its
environment. And also explain what has to be done by identifying the necessary task, action or
activity that must be accomplished. It is a statement of exactly what the system must do. The
new proposed system will able to do the following activities easily:-

Store merchant file: the new proposed system will able to store merchant files for easily data
management.

Register merchant file: the user easily register the merchant file to specified database.

View merchant profile: the system able to user easily accessing the merchant file from the data
base.

Upload bank receipt: the user easily sending receipt that get from the bank to revenue office by
merchant.

Send displeasure: the user easily makes question on different issue that arises from the
merchant.

View displeasure: the system able to seeing the question that make from merchant.

Renewed/close/open license: the business officer can modify or close the merchant trade license

Send decision: the user easily announce the final decision that make on the tax.

View merchant file: the user easily finding the store merchant files for different purpose.

Register daily income: the user easily announce the day to day works in order to know the tax
amount.

Announce tax amount: the merchant easily known the tax amount for merchant by calculating
appropriate or correct tax amount from the system.

Record daily paid tax: the user easily announces the total amount of tax that pays every day.

Information Technology Academic Program 2011 E.C Page 11

 Tax management for merchants

Announce tax rule and regulation to merchant: create clear awareness about the rule and
regulation or the obligation and right of merchant to pay taxes.

2.2.2. Non-functional requirement

Non-functional requirements define how a system is supposed to be. Non-functional
requirements specify the system’s quality characteristics or quality attributes. These
requirements are additional features.

The following are the non-functional or Technical requirement related with the system:

Authentication: Correct implementation of the system will be avoiding unauthorized person to

access. The security service provided by the system will maintain the security of the system.
Users will have their own encrypted password and username by using encryption algorithm to
access the system.

Performance: The system uses an algorithm that should perform all tasks in a short response
time and high rate of processing with valid tax management system and required information. To
enhance system performance should develop power full server.

Usability: The system will be designed to have user-friendly interfaces and easy navigate to one
link to other, which enhances users’ efficiency. It is also designed in such a way that users can
easily learn how to interact with the system.

Authorization: The proposed system should be authenticating the user of the system by asking
username and password and determine which users are authorized to access or perform specific
activities or operations.

Modifiability: the system should be modifiable by authorized users of the system whenever it
needed and easily added new functionality.

Reliability: The system is expected to be used smoothly without being corrupted and frequently
failure. When failures occur the system should be tolerates failure, troubleshoot in short period of
time and return related error message.

Availability: The system will be functional 24 hours/7 day and whenever the service is available
by using redundant server.

Information Technology Academic Program 2011 E.C Page 12

 Tax management for merchants

2.2.3. Business rule

A business rule defines or constrains one aspect of business that is intended to assert business
structure or influence the behavior of the business. A statement that describes a business policy
or procedure must be fulfilled. Business rule often focus on access control issues.

BR1: annual income of the merchant is greater than one million the level should be A, between
five hundred thousand and one million the level should be B and less than five hundred thousand
the level should be C.

BR2: merchant should announce the displeasure of his or her up to 21 days when knows his or
her tax decision to customer officer but after the day the displeasure is rejected.

BR3: every merchant should pay tax with sated date, if not punish with 20% from the announced
tax amount.

BR4: the annual income of the merchant is less than 7200 he or she is no pay the tax.

BR5: a merchant should renewed license after completing tax payment date up to 1 month with
102 birr.

BR6: for every level a merchant should not announce daily income 5% of the daily income
punished.

BR7: in order to close the license the merchant should not have debt, if not cannot close the
license.

BR8: In order to open the license every merchant should first register thin number.

BR9: the annual income of the merchant is the average of merchant announced income and
pursuit officer income.

2.3. System requirement analysis

In systems requirements analysis encompasses those tasks that go into determining the needs or
conditions to meet for a new or altered product or project, taking account of the possibly
conflicting requirements of the various stakeholders, analyzing, documenting, validating and
managing software or system requirements.

Information Technology Academic Program 2011 E.C Page 13

 Tax management for merchants

2.3.1. Actor and use case identification

2.3.1.1. Actor identification:

An actor represents a type of users of the system or external system that plays a role in one or
more interactions with our system.

Merchant: register file, view profile, send bank receipt, send displeasure, announce daily
income, view displeasure decision, view approve income, register receipt, view tax amount, send
license permission and view license permission.

Customer service officer: approve merchant file, approve displeasure decision, register thin,
send open license permission, send renewed license permission, send close license permission,
and view merchant profile.

Audit officer: generate report, view relate work document, and view payment file.

Finance officer: approve daily income, post announce date, view merchant profile, announce tax
amount, report total tax, register daily paid tax, view payment file, and register debt of merchant.

Administer: create account, update account, block account, view log event, take backup Restore
backup, and post notice.

Business licensing officer: renewed license, close license, open license, view license
permission, and view profile.

Pursuit officer: view receipt, register daily income.

Displeasure Hearing Committee፡ view displeasure sends displeasure decision, view payment
file.

Information Technology Academic Program 2011 E.C Page 14

 Tax management for merchants

2.3.1.2. Use case identification:

A use case describes a sequence of actions that provide a measurable value to an actor. A use
case is drawn as a horizontal ellipse on unified modeling language use case diagram.

Use case identification

Use case name Use case ID Interact with

register merchant profile UC01 Login
view profile UC02 Login
upload bank receipt UC04 Login
send displeasure UC05 Login
send license permission UC06 Login
announce daily income UC07 Login
approve merchant file UC08 Login
view displeasure UC09 Login
send open license permission UC10 Login
Send renewed license permission UC11 Login
Send close license permission UC12 Login
Generate report UC13 Login
send displeasure decision UC14 Login
view work document UC15 Login
view payment file UC16 Login
approve daily income UC17 Login
announce tax amount UC18 Login
report total tax UC19 Login
register daily paid tax UC20 Login
register debt of merchant UC21 Login
create account UC22 Login
block account UC23 Login
renewed license UC24 Login

Information Technology Academic Program 2011 E.C Page 15

 Tax management for merchants

close license UC25 Login

open license UC26 Login
view license permission UC27 Login
View log event UC28 Login
Take backup UC29 Login
Restore backup UC30 Login
Login UC31

Table 1 Use case identification

Use case diagram

A use case diagram is a graphic depiction of the interactions among the elements of a system. A
use case is a methodology used in system analysis to identify, clarify, and organize system
requirements. Use Case diagrams show the various activities the users can perform on the
system. The system is something that performs a function. A use case diagram illustrates a set of
use cases for a system, the actors of these use cases, the relations between the actors and these
use cases, and the relations among the use cases.

Information Technology Academic Program 2011 E.C Page 16

 Tax management for merchants

Figure 1 use case diagram

Information Technology Academic Program 2011 E.C Page 17

 Tax management for merchants

Use case description

Use case name Approve profile

ID UC10
Actor Customer service officer
Description Customer service officer should able to register merchant profile
Precondition Customer service officer should login to his or her page to
approve merchant by valid account.
Post condition Customer service officer should approve merchant profile
Basic course of action 1. Customer service officer open the system
2. The system display login page
3. Customer service officer should enter valid username and
password.
4. The system direct to Customer service officer page
5. Customer service officer click approve register profile link.
6. The system display merchant data with approve and reject
link
7. Customer service officer click approve or reject link to
register
8. The system display registers successfully.
9. Use case end
Alternative course of action Al1: if the customer service officer enters invalid user name and
password on login form the system display error message,
continue from step 3.
Al2: if the customer service officer approve invalid data the
system display invalid registration, continue step 7.

Table 2 approve profile use case description

Use case name close license

ID UC29

Information Technology Academic Program 2011 E.C Page 18

 Tax management for merchants

Actor Business licensing officer

Description Business licensing officer should able to close trade license of the
merchant
Precondition Business licensing officer should login to his or her page to register
merchant by valid account.
Post condition Business licensing officer should close trade license
Basic course of action 1. Business licensing officer open the system
2. The system display login page
3. Business licensing officer should enter valid username and
password.
4. The system direct to Business licensing officer page
5. Business licensing officer click on close license link
6. Business licensing officer check the merchant free from debt
from view license permission page
7. Business licensing officer set any necessary information to close.
8. Business licensing officer click the close button
9. The system display successfully close license
10. Use case end
Alternative course of action Al1: if the Business licensing officer enters invalid user name and
password on login form the system display error message, continue
from step 3.
Al2: if the Business licensing officer close license with debt the
system display cannot close license, continue step 7.
Table 3 close license use case description

Use case name Login

ID UC32
Actor Customer service officer, audit officer, merchant, finance officer
administrator, Business licensing officer.

Information Technology Academic Program 2011 E.C Page 19

 Tax management for merchants

Description The user should able to log into the system

Precondition The user must get valid user account from administrator
Post condition The user should log into the system
Basic course of action 1. The user open the system
2. System display login form
3. User fill login data (user name and password) and then click login button
4. System display user page based on the entered account
5. Use case end

Alternative course of Al1: if the user enters invalid user name and password on login form the
action system display error message, continue from step 3.

Use case name View profile

ID UC02
Actor Merchant, customer service officer, audit officer, finance officer
Description The user should able to view merchant profile data
Precondition The user should login to his or her page to be view merchant
profile data with valid account.

Table 4 login use case description

Information Technology Academic Program 2011 E.C Page 20

 Tax management for merchants

Post condition The user should be view merchant profile data

Basic course of action 1. The user open the system
2. The system display login page
3. The user should enter valid username and password.
4. The system direct to user page
5. The user click on view merchant profile link
6. The system display view profile form
7. The user fill data on search field and click search button
8. The system display merchant data with table
9. Use case end
Alternative course of action Al1: if the user enters invalid user name and password on login
form the system display error message, continue from step 3.

Table 5 view profile use case description

Table 6upload bank use case description

send bank receipt
Use case name
ID UC04
Actor Merchant
Description The Merchant should able to upload receipt
Precondition The merchant should login to his or her page to be upload payment
receipt with valid account.
Post condition The merchant should be upload payment receipt
Basic course of action 1. The merchant open the system

Information Technology Academic Program 2011 E.C Page 21

 Tax management for merchants

2. The system display login page

3. The merchant should enter valid username and password.
4. The system direct to Merchant page
5. The merchant choose upload receipt link
6. The system display upload file and choose form file from
stored place
7. The merchant click on upload receipt button
8. The system display successfully upload
9. Use case end
Alternative course of action Al1: if the merchant enters invalid user name and password on login
form the system display error message, continue from step 3.
Use case name Create account
ID UC25
Actor Administrator
Description The Administrator should able to create user account
Precondition The Administrator should login to his or her page to be creating
user account with valid account.
Post condition The Administrator should be create valid user account
Basic course of action 1. The Administrator open the system
2. The system display login page
3. The Administrator should enter valid username and
password on login form.
4. The system direct to administrator page
5. The admin click on create account link
6. The system display create account form
7. The admin fill appropriate data and then click on create
button.
8. The system display successfully create account
9. Use case end
Alternative course of action Al1: if the user enters invalid user name and password on login
form the system display error message, continue from step 3.

Information Technology Academic Program 2011 E.C Page 22

 Tax management for merchants

Use case name Announce tax amount

ID UC20
Actor Finance officer
Description The Finance officer should able to announce tax amount
Precondition The Finance officer should login to his or her page to be
announcing tax amount with valid account.
Post condition The Finance officer should be announce tax amount
Basic course of action 1. The finance officer open the system
2. The system display login page
3. The finance officer should enter valid username and
password on login form.

Table 7 create account use case description

Information Technology Academic Program 2011 E.C Page 23

 Tax management for merchants

4. The system direct to finance officer page

5. Finance officer click tax announce link
6. The system display merchant tax announce form
7. The finance officer search the merchant data by thin
number
8. System display data filled form with tax
9. Finance officer click send button
10. The system display send successfully
11. Use case end
Alternative course of action Al1: if the user enters invalid user name and password on login
form the system display error message, continue from step 3.
Table 8 announce tax amount use case description

Use case name Send displeasure decision

ID UC16
Actor Displeasure hearing officer
Description The Displeasure hearing officer should able to send investigate
result
Precondition The Displeasure hearing officer should login to his or her page to
be send investigates result with valid account.
Post condition The Displeasure hearing officer should be send view decision
Basic course of action 1. The Displeasure hearing officer open the system
2. The system display login page
3. The Displeasure hearing officer should enter valid username
and password on login form.
4. The system direct to Audit officer page

Information Technology Academic Program 2011 E.C Page 24

 Tax management for merchants

5. The system display view work document link, view payment

file link
6. The Displeasure hearing officer click view work document
link and view payment file link and investigate those file and
click send investigate link
7. The system display form of send displeasure decision link
8. The Displeasure hearing officer fill valid data and click send
button
9. The system display successfully send
10. Use case end
Alternative course of action Al1: if the Audit officer enters invalid user name and password on
login form the system display error message, continue from step 3.
Al2: if the Audit officer enters invalid data on form the system
display error message, continue from step 9.

Use case name View payment file

ID UC18
Actor Audit officer, Finance officer, customer service officer
Description The user should able to view pay tax amount
Precondition The user should login to his or her page to be seeing the amount of tax
pay with valid account.
Post condition The user should be view tax pay amount
Basic course of action 1. The user open the system
2. The system display login page
3. The user should enter valid username and password on login form.
4. The system direct to user page
5. The user click view payment link

Information Technology Academic Program 2011 E.C Page 25

Table 9 send displeasure decision use case description

 Tax management for merchants

6. System display tax payment data

7. The user click use thin number and click search button
8. The system display tax payment data
9. Use case end
Alternative course of action Al1: if the user enters invalid user name and password on login form the
system display error message, continue from step 3.

Use case name send renewed license permission

ID UC13
Actor Customer service officer
Description The Customer service officer should able to give license renewed
permission to merchant.

Table 10 view payment file use case description

Information Technology Academic Program 2011 E.C Page 26

 Tax management for merchants

Precondition The Customer service officer should login to his or her page to give
license renewed permission to merchant with valid account.
Post condition The Customer service officer should be give license renewed
permission to merchant
Basic course of action 1. The Customer service officer open the system
2. The system display login page
3. The Customer service officer should enter valid username and
password on login form.
4. The system direct to Customer service officer page
5. The Customer service officer click give permission link
6. System display notification page form
7. The customer service officer select view permission link click
on renewed permission
8. The system direct permission request.
9. The customer service officer click send notification link
10. The system direct to send notification form
11. The customer service officer announces to pay 102 birr to
renewed license.
12. Customer service officer see payment successfully for
renewed license payment.
13. The customer service officer send notice to merchant to
permission to renewed license on send notice button.
14. The system display send successfully
15. Use case end
Alternative course of action Al1: if the customer service officer enters invalid user name and
password on login form the system display error message, continue
from step 3.
Al2: if the customer service officer fill invalid data on send
notification form the system display error message and go to step 9

Information Technology Academic Program 2011 E.C Page 27

Table 11 give renewed license permission use case description

 Tax management for merchants

2.3.2. Sequence Diagram

A UML Sequence diagram shows the sequence of interactions among objects and used to
represent or model the flow of messages, events and actions between the objects or components
web based tax management system for merchant in case of Debre Markose City. Generally, a
sequence diagram shows object interactions arranged in time sequence.

Figure 2 sequence diagram for login

Information Technology Academic Program 2011 E.C Page 28

 Tax management for merchants

Figure 3 sequence diagram of merchant registration

Figure 4 send registration request

Information Technology Academic Program 2011 E.C Page 29

 Tax management for merchants

Figure 5 sequence diagram for tax announcement

Figure 6 sequence diagram for create account

Information Technology Academic Program 2011 E.C Page 30

 Tax management for merchants

Figure 7 sequence diagram for view profile

2.3.3. Activity Diagram

Activity diagrams are graphical representations of workflows of stepwise activities and actions
with support for choice, iteration and concurrency .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.

Figure 8 Activity diagram for login

Information Technology Academic Program 2011 E.C Page 31

 Tax management for merchants

Figure 9 Activity diagram for tax announcement

Figure 10 Activity diagram for view profile

Information Technology Academic Program 2011 E.C Page 32

 Tax management for merchants

Figure 11 Activity diagram for view payment file

2.3.4. Analysis class diagram

A class diagram is a static model that shows the classes and the relationships among classes that
remain constant over the time. Class is the main building block of class diagrams, which stores
and manages information in the system. In the phase of conceptual class modeling we just create
or classes and their interrelationship.

Information Technology Academic Program 2011 E.C Page 33

 Tax management for merchants

Figure 12 Analysis class diagram

Information Technology Academic Program 2011 E.C Page 34

 Tax management for merchants

CHAPTER THREE

3. System design
Systems design is the process of defining elements of a system like modules, architecture,
components and their interfaces and data for a system based on the specified requirements. It is
the process of defining, developing and designing systems which satisfies the specific needs and
requirements of a business or organization. The purpose of design is to determine how the
system is going to build and to obtain the information needed to drive the actual implementation
of the system. It focuses on understanding the model how the software will be built.

3.1. Design Class Diagram

Class diagram is not only used for visualizing, describing and documenting different aspects of a
system but also for constructing executable code of the software application. The class diagram
describes the attributes and operations of a class and also the constraints imposed on the system.
A 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 classes, their attributes, operations
(or methods), and the relationships among objects. Design class diagram differ from analysis
class diagram in that design class have data type for each attribute and their focus solution
domain.

Information Technology Academic Program 2011 E.C Page 35

 Tax management for merchants

Figure 13 design class diagram

Information Technology Academic Program 2011 E.C Page 36

 Tax management for merchants

3.2. Database Design

Database design is the process of producing a detailed data model of a database. Database design
is a collection of processes that facilitate the design, develop, implementation and maintenance
of enterprise data management systems.

3.2.1. Physical Data Model

Physical data modeling is conceptually similar to design class modeling, the goal being to design
the internal schema of a database, depicting the data tables, the data columns of those tables, and
the relationships between the tables. A physical database model shows all table structures,
including column name, column data type, column constraints, primary key, foreign key, and
relationships between tables.
Features of a physical data model include:
 Entities become tables in the physical database.
 Attributes become columns in the physical database. Select an appropriate data type for
each of the columns and size.
 Unique identifiers become columns that are not allowed to have NULL values.
 Specification all tables and columns.
 Foreign keys are used to identify relationships between tables.

Figure 14 account table

Information Technology Academic Program 2011 E.C Page 37

 Tax management for merchants

Figure 15 license table

Figure 16 Displeasure table

Information Technology Academic Program 2011 E.C Page 38

 Tax management for merchants

Figure 17.displeasure decision table

Figure 18 request table

Figure 19Notice_user table

Information Technology Academic Program 2011 E.C Page 39

 Tax management for merchants

3.3. User interface design

A user interface, also called a "UI" or simply an "interface," is the means in which a person
controls a software application or hardware device. A good user interface provides a "user-
friendly" experience, allowing the user to interact with a computer.

Figure 20 user interface design

Information Technology Academic Program 2011 E.C Page 40

 Tax management for merchants

Web based user interface

Figure 21web based user interface

Information Technology Academic Program 2011 E.C Page 41

 Tax management for merchants

Figure 22 sample forms on web based user interface

3.4. System Architecture (Deployment diagram)

Deployment diagrams shows how they are deployed in hardware. Deployment diagram will
show the hardware configuration Data base Server / Web Server / Client Machine and Utility
component will be placed into the client machine node. Deployment diagrams are made to focus
on hardware topology of a system. The communicate relationship defines how an actor
participates in a use case. You can add an arrow to the relationship to indicate the direction the
information flows.

Information Technology Academic Program 2011 E.C Page 42

 Tax management for merchants

Figure 23 System deployment diagram

Figure 24 data accessing interaction in deployment diagram

Information Technology Academic Program 2011 E.C Page 43

 Tax management for merchants

CHAPTER FOUR

4. Implementation
Implementation in the system includes implementing the attributes and methods of each
object and integrating all the objects in the system, to function as a single system the
implementation activity spans the gap between the detailed objects designed model and a
complete set of source code file that can be compiled together.

4.1.Over View of Programming language used

Programming language is important to complete the system in the best way and to make it
good, easy and interactive with the customer.

The programming language is:

 Java/jsp: It is simple programming language.
 JavaScript: for animation purpose and to display prompt boxes.
 HTML: that used to create web content so it can be displayed by a browser.
 CSS: for the formatting of the system. That is it defines the style of a website’s
content. MYSQL
 MySQL: Open –source, Security, Easy to develop and for database management

4.2.Algorithms Used
We us pseudo code. Pseudo code is a detailed readable description of what a computer program
or algorithm must do, expressed in a formally-styled natural language rather than in a
programming language. Pseudo code is sometimes used as a detailed step in the process of
developing a program. It allows designers or lead programmers to express the design in great
detail and provides programmers a detailed template for the next step of writing code in a
specific programming language. The purpose of using pseudo code is that it is easier for people
to understand than conventional programming language code, and that it is an efficient and
environment independent description of the key principles of an algorithm

Information Technology Academic Program 2011 E.C Page 44

 Tax management for merchants

Algorithm for Login

Logged page
Click on login link
Login form displayed
Enter
Username and password
Click login button
Connect to database If (valid)
The privileged page displayed
Else Display error message /return value

4.3.Sample code
4.3.1. For login
<%--
Document : login
Created on : Mar 6, 2019, 1:04:04 PM
Author : user
--%>

<%@page import="org.apache.tomcat.util.codec.binary.Base64"%>
<%@page import="javax.crypto.spec.SecretKeySpec"%>
<%@page import="javax.crypto.Cipher"%>
<%@ page import="java.sql.*,java.io.*" %>
<%@page contentType="text/html" pageEncoding="UTF-8"%>

<link rel="stylesheet" type="text/css" href="form1.css">

<!DOCTYPE html>
<div id="login">
<form action="" method="POST" >
<table><tr>
<th id="font"> Login</th>
</tr>
<tr>
<td>User_name:</td>
</tr>
<tr><td><input type="text" name="username" placeholder="Username" required=""
style="height: 15px; margin-left: 15px; width: 100px; padding: 5px; border: 3px double
rgb(204, 204, 204);"/></td>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;

Information Technology Academic Program 2011 E.C Page 45

 Tax management for merchants

</tr>
<tr>
<td>Password:</td>
</tr>
<tr><td><input type="password" name="password" placeholder="Password"
required="" style="height: 15px; margin-left: 15px; width: 100px; padding: 5px; border: 3px
double rgb(204, 204, 204);"/></td>
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</tr>
<tr>
<td><input type="submit" name="log" value="login" style="height: 34px;
margin-left: 15px; width: 60px; padding: 5px; border: 3px double rgb(204, 204, 204);" >
<input type="reset" name="can" value="cancel" style="height: 34px;
margin-left: 15px; width: 60px; padding: 5px; border: 3px double rgb(204, 204,
204);"></td>
</tr>
<tr><td><font size="4px" color="white">Forgot you password?</font><a
href="ff">click</a></td></tr>
</table>
</form>
</div>
<%

String user = request.getParameter("username");

String pw = request.getParameter("password");
try {
Connection con = null;
ResultSet rs = null;
Statement stmt = null;
PreparedStatement pstmt = null;
int inserted = 0;
String url = "jdbc:mysql://localhost:3306/tax";
Class.forName("com.mysql.jdbc.Driver").newInstance();
con = DriverManager.getConnection(url, "root", "");
stmt = con.createStatement();
if (user != null && pw != null) {
final byte[] key = {
0x4, 0x68, 0x69, 0x79, 0x49, 0x73, 0x66, 0x53, 0x65, 0x63, 0x72, 0x65,
0x14, 0x4f, 0x65, 0x60
}; Cipher cipher = Cipher.getInstance("AES/ECB/PKCS5Padding");
final SecretKeySpec secretKey = new SecretKeySpec(key, "AES");
cipher.init(Cipher.ENCRYPT_MODE, secretKey);
final String pass = Base64.encodeBase64String(cipher.doFinal(pw.getBytes()));

Information Technology Academic Program 2011 E.C Page 46

 Tax management for merchants

String sql = "select*from account where username='" + user + "'and

password='" + pass + "' and status='" + 1 + "'";
rs = stmt.executeQuery(sql);
while (rs.next()) {
String un = rs.getString("username");
String pas = rs.getString("password");
String role = rs.getString("role");
if (user.equals(un) && pass.equals(pas)) {

session.setAttribute("suname", user);
session.setAttribute("spass", pass);
if (session.getAttribute("suname") != null &&
session.getAttribute("spass") != null) {
if (rs.getString("role").equals("admin")) {
response.sendRedirect("admin.jsp");
} else if (rs.getString("role").equals("merchant")) {
response.sendRedirect("merchant.jsp");
}
else if (rs.getString("role").equals("customer")) {
response.sendRedirect("customerofficer.jsp");
}
else if (rs.getString("role").equals("finance")) {
response.sendRedirect("finance.jsp");
}
else if (rs.getString("role").equals("auditor")) {
response.sendRedirect("auditor.jsp");
} else if (rs.getString("role").equals("business")) {
response.sendRedirect("business.jsp");
}
else if (rs.getString("role").equals("pursuit")) {
response.sendRedirect("pursuit.jsp");
}
else if (rs.getString("role").equals("dishear")) {
response.sendRedirect("dishear.jsp");
}
else if (rs.getString("role").equals("administrator")) {
response.sendRedirect("admin.jsp");
}

} else if (session.getAttribute("suname") == null &&

session.getAttribute("spass") == null) {
response.sendRedirect("log.jsp");
}
}

Information Technology Academic Program 2011 E.C Page 47

 Tax management for merchants

}
}
if (user != null && pw != null) {
String sql = "select*from account where username !='" + user + "'and password !
='" + pw + "' and status='" + 1 + "'";
out.print("<div id='re'> Incorect username and password</div>");%>
<script>
alert("Fail to login please enter correct account???????");
</script>

<%
}

}
catch (Exception ex) {
//out.println("Unable to connect to database.");
out.println(ex.getMessage());

%>

4.3.2 For view tax amount

<form action="" method="POST">
<h2>Enter thin<input type="text" name="thin"><input type="submit"
name="sea" value="view"></h2>
</form>

<%
try{
Connection con=null;
ResultSet rs = null;
Statement stmt = null;
PreparedStatement pstmt = null;
PreparedStatement pstm = null;
String url = "jdbc:mysql://localhost:3306/tax";
Class.forName("com.mysql.jdbc.Driver").newInstance();
con = DriverManager.getConnection(url, "root", "");
stmt=con.createStatement();
String acti=request.getParameter("thin");
String act=request.getParameter("sea");

Information Technology Academic Program 2011 E.C Page 48

 Tax management for merchants

String ss="select * from license, announcetax where thinnum='"+ acti +"' and
stat='approve' and lnnum=anlnnum";
rs=stmt.executeQuery(ss);
if(act!=null){
%>
<form action="" method="Post">
<table border='1'><tr><th>Thin number</th><th>Your name</th><th>Father
name</th><th> Grand father name </th>
<th>Trade name</th><th> Tax amount </th>
</tr>
<%

while(rs.next())
{

String a=rs.getString("thinnum");
String b=rs.getString("lnnum");
String c=rs.getString("fname");
String d=rs.getString("mname");
String e=rs.getString("lname");
String f=rs.getString("tname");
float h=rs.getFloat("tax");

%>

<tr><td><%=a%></td>
<td><%=c %></td>
<td><%=d%></td>
<td><%=e%></td>
<td><%=f%></td>
<td><%=h%></td>

</tr>
<% }
} %>

</table></form>
<%}catch(Exception e){
out.print(e);
}
%>

Information Technology Academic Program 2011 E.C Page 49

 Tax management for merchants

CHAPTER FIVE

5. TESTING

5.1.Unit testing
Unit testing is a software verification and validation method in which a programmer tests if
individual units of source code are fit for use. The web based tax management system units are
tested one by one.

5.2.Integration testing
Combining modules and testing them is called integration testing. Integration testing is gradual.
First we test the highest level, or coordinating module, and only one of its subordinate modules.
After unit testing, the automated web based tax management system is also tested whether every
unit is integrated to each other.

5.3.System testing
System testing of software or hardware is testing conducted on a complete, integrated system to
evaluate the system's compliance with its specified requirements. It is a testing process in which
the aim is to ensure that the overall system works as defined by the requirements.

Web based tax management system is functionally tested based on the use case model developed
during the analysis phase.

5.3.1. Sample test

Figure 25 thin registration sample test

Information Technology Academic Program 2011 E.C Page 50

 Tax management for merchants

Figure 26 income registration sample test

Information Technology Academic Program 2011 E.C Page 51

 Tax management for merchants

CHAPTER SIX

6. Conclusion and recommendation

This project is developed for Debre Markos city revenue and custom office for tax
management of merchant only to web based system in order to give efficient, reliable,
timely, secure system, easily accessed, availability of service throughout Debre markos city .The
main propose of this system is not only for the officer but also for the merchant itself.

By challenges money problems we develop this new system, this system is very important for
developing Debre Markos city revenue and custom office of merchant tax management system.
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.

The main aim of our project is:

 Reduce the number of employee

 Minimize the time required to perform task
 Minimize the work load of employees
 Remove redundancy of data
 Update the record easily
 Easy retrieval of data
 Provide sufficient security
 Increase employee satisfaction etc.

6.1. Future enhancement

In the future the one that can do this project will included the following features to develop best
tax management system for revenue and custom office. They cannot include some features
because of the shortage of time and other resource. Some of the features are:-

 Including camera at the merchant place to get accurate daily income as input for pursuit
officer.
 Include VAT and TOT of the merchant in day to day buying and selling.

Information Technology Academic Program 2011 E.C Page 52

 Tax management for merchants

 Use appropriate payment system like online payment or bank transaction.

Appendix I

Declaration
We, undersigned, declare that thesis our original work, has not been presented for a degree in this or
any other university, and all the source of martial used for the thesis/project have been
acknowledged.

No_ Name ID No Signature

1. Getaneh Awoke TER/1458/08 ---------------------------

2. Belete Dagnew TER/1449/08 ---------------------------

3. Alene Girmaw TER/4643/07 ---------------------------

4. Tewabech Degarege TER/1481/08 ---------------------------

5. Medina Fetu TER/4674/07 ……………………….

Information Technology Academic Program 2011 E.C Page 53

 Tax management for merchants

APPENDIX II

Approval of advisors and examiners

This thesis/project has been submitted for examination with my approval as a thesis/project
advisor.
Advisor’s Name: --------------------------------
Signature: ----------------------------------
This thesis/project has been examined with our approval as thesis/project examiners.
Examiners Name:-
1. --------------------------- Signature: ----------------------------------
2. ---------------------------- Signature: ----------------------------------
3. ---------------------------- Signature: ----------------------------------

Information Technology Academic Program 2011 E.C Page 54

 Tax management for merchants

Reference
[1]The Federal Democratic Republic of Ethiopia, Ethiopian Revenue and Customs Authority
http://www.erca.gov.et/images/Documents/Directives/Amharic_Format/139.pdf accessed at
12/05/2011 e.c.

[2]Online Tax Information System ASP.NET Project https://www.codewithc.com/online-tax-

information-system-asp-net-project/accessed at 16/05/2011e.c

[3]Sanyu Students Project Center http://sanyuprojects.com/tax-management-system-project-vb-

msaccess.php accessed at 28/04/2011 e.c

[4] Computer science last year students IGNOU, SMU University final year project
http://ignousupport.blogspot.com/p/online-tax-management-system-project.html accessed at
08/05/2011 e.c

[5]Ethiopian Ministry of Revenue http://www.erca.gov.et/index.php/news/international-news

accessed at 20/02/2011 e.c

[6]Ethiopian Ministry of Revenue http://www.erca.gov.et/index.php/news/international-

news/ accessed 26/05/2011 e.c

[7]The Ethiopian Revenues and Customs Authority (ERCA) proclamation No.587/2008 on

14July2018, https://businessguide.ezega.com/Default.aspx?
action=BussinessDetail&pid=766690&bid=1214105&page=5accessed at 21/05/2011 e.c

[8] Ethiopian Ministry of Revenue (http://www.erca.gov.et/index.php/about-us) accessed at

20/04/2011 e.c

Information Technology Academic Program 2011 E.C Page 55