Trade License First Draft

FACULTY OF ENGINEERING AND TECHNOLOGY
DEPARTEMENT OF COMPUTER SCIENCE
DESIGNING AND IMPLIMENTATION OF ONLINE TRADE REGISTRATION AND

LICENSE MANAGEMENT SYSTEM FOR ADDIS ABABA CITY
A PROJECT SUBMITTED TO DEPARTEMENT OF COMPUTER SCIENCE OF GAGE

UNIVERSITY COLLEGE IN PARTIAL FULFILLMENT OF THE REQUIREMENTS
FOR THE DEGREE OF BACHELOR SCIENCE IN COMPUTER SCIENCE
SUBMITTED BY:
No Name ID
1. Mekonnen Kebede Secll 2559

2. Dawit Teshome Sec ll 2389
3. Nigussie Worku Sec ll 2358
4. Yonas Moges Sec ll 2241
5. Getachew Worku Sec ll 2429
ADVISOR YADETA G.
JUNE, 2020
ADDIS ABABA, ETHIOPIA
Declaration
This is to declare that the project work is done under the supervision of Mr. Yadeta Gonfa and
having the title Online Trade Registration and License Management System for Addis
Ababa City by the contribution of:
1. Mekonnen Kebede
2. Dawit Teshome
3. Nigussie Worku
4. Yonas Moges
5. Getachew Worku
No part of the project work has been reproduced illegally which can be considered as Plagiarism.
All referenced parts have been referenced properly. We will be responsible and liable for any
consequence if violation of this declaration occurs.
____________________________________________
Date
Full Name Signature
1. Mekonnen Kebede __________________________________
2. Dawit Teshome __________________________________
3. Nigussie Worku __________________________________
4. Yonas Moges __________________________________
5. Getachew Worku __________________________________
The project has been submitted for examination with my approval as University advisor.
______________________________ ____________________________
Advisor’s Name Signature
Online Trade Registration and Licensing Management System for Addis Ababa City I
ACKNOWLEDGEMENT
At first we would like to extend our unshared thanks to the almighty God fir his help. We
indebted to and gratefully acknowledge our advisor Mr. Yadeta Gonfa who put us in the right
track of the project. Successful and timely accomplishment of this project would have been very
difficult without his generous time devotion from the early title selection till the final write up of
the project through adding her constructive and ever teaching comments. Thus, we very much in
debt to him for his willingness to advise us and day-to-day efforts that enabled us to finalize the
project. We have also grateful thanks for our instructors who are thought as at GAGE College.
Lastly, but not the least, we like to thanks Addis Ababa City trade and Industry office for their
assistance.
Online Trade Registration and Licensing Management System for Addis Ababa City II
COMMITMENT-BONIFAFIDE CERTAFICATE
__________________________ _______________________
Chairman/ Dep’t head Chairman’s signature
__________________________ ________________________
Advisor’s name Advisor’s signature
__________________________ ________________________
Examiner’s name Examiner’s signature
EXAMINORS AND ADVISORS FORM
__________________________ ________________________
Advisor’s name Advisor’s signature
__________________________ ________________________
Examiner’s name Examiner’s signature
Online Trade Registration and Licensing Management System for Addis Ababa City III
ACRONYMS
BR…………………………………………………………….Business Rule
CD………………………………………………………………Compact Disk
DB……………………………………………………………….Database
ER……………………………………………………………….Entity Relationship
ETB………………………………………………………………Ethiopian Birr
HTTP……………………………………………………………Hyper Text Transfer Protocol
MYSQL…………………………………………………………MY Structural Query Language
PHP……………………………………………………………..Pre Hyper Processor
RAM…………………………………………………………….Random access Memory
SD……………………………………………………………….Sequence Diagram
SSL………………………………………………………………Server Socket Line
TCP………………………………………………………………Transfer Control Protocol
TIN………………………………………………………………Tax Identity Number
TLMS…………………………………………………………..Trade license management system
UC……………………………………………………………….Use Case
UI………………………………………………………………..User Interface
UML……………………………………………………………Unified Modeling Language
Online Trade Registration and Licensing Management System for Addis Ababa City IV
Table of Contents
ACKNOWLEDGEMENT ............................................................................................................................ ii
COMMITMENT-BONIFAFIDE CERTAFICATE ..................................................................................... iii
EXAMINORS AND ADVISORS FORM ................................................................................................... iii
ACRONYMS ............................................................................................................................................... iv
ABSTRACT................................................................................................................................................. xi
CHAPTER ONE ....................................................................................................................................... - 1 -
INTRODUCTION .................................................................................................................................... - 1 -
1.1. Overview ........................................................................................................................................ - 1 -
1.2. Background Information of the office and the system ................................................................. - 1 -
1.2.1. Organizational Background .................................................................................................... - 1 -
1.2.2. Background of the System ...................................................................................................... - 2 -
1.3. Statement of Problem ..................................................................................................................... - 3 -
1.4. Objective of the project .................................................................................................................. - 4 -
1.4.1. General objective .................................................................................................................. - 4 -
1.4.2. Specific objectives ................................................................................................................ - 4 -
Some of the Specific Objects are the following: - .................................................................................... - 4 -
1.5 Scope and Limitation of the project .............................................................................................. - 4 -
1. 5.1. Scope ...................................................................................................................................... - 4 -
1.5.2. Limitation ................................................................................................................................ - 5 -
1.6. Risk, Constraints and Assumption ................................................................................................. - 5 -
1.6.1. Risk ......................................................................................................................................... - 5 -
1.6.2. Constraints .............................................................................................................................. - 5 -
1.6.3. Assumptions ............................................................................................................................ - 6 -
1.7. Significance of the Project ............................................................................................................. - 6 -
Online Trade Registration and Licensing Management System for Addis Ababa City V
1.8. Beneficiaries of the project ............................................................................................................ - 7 -
1.8.1. Traders .................................................................................................................................... - 7 -
1.8.2. Organization ............................................................................................................................ - 7 -
1.9. Team composition, budget and schedule ....................................................................................... - 7 -
1.9.1. Team composition ................................................................................................................... - 7 -
1.9.2. Budget ..................................................................................................................................... - 8 -
Software Requirements Cost ........................................................................................................... - 9 -
1.9.3. Schedule .................................................................................................................................. - 9 -
CHAPTER TWO .................................................................................................................................... - 11 -
SYSTEM REQUIREMENTS SPECIFICATION (SRS) ........................................................................ - 11 -
1. Existing System Description ........................................................................................................... - 11 -
2. Major Functions of the Existing System ........................................................................................ - 11 -
2.1. Business process of the existing system................................................................................... - 11 -
2.2. Players in the Existing System ................................................................................................. - 13 -
2.3. Business Rules in the Existing System .................................................................................... - 14 -
2.4. Report generation, forms, documents etc. in the existing system ............................................ - 14 -
2.5. SWOT analysis of the existing system. ................................................................................... - 15 -
3. Problems of the Existing System ................................................................................................... - 16 -
4. Proposed System ............................................................................................................................ - 17 -
5. Methodology and tools ................................................................................................................... - 17 -
5.1. Data Collection methods .......................................................................................................... - 17 -
5.2. Hardware and Software Tools.................................................................................................. - 17 -
5.3. Minimum hardware and software requirements ...................................................................... - 18 -
5.3.1. Hardware Tools ..................................................................................................................... - 18 -
5.3.2. Software Tools ...................................................................................................................... - 18 -
6. System analysis tools and techniques employed (DFD, OOSAD tools etc.) .................................. - 19 -
7. Feasibility Analysis......................................................................................................................... - 20 -
7.1. Technical feasibility ................................................................................................................. - 20 -
7.2. Operational feasibility .............................................................................................................. - 21 -
7.3. Economic feasibility ................................................................................................................ - 21 -
7.3.1 Tangible feasibility ................................................................................................................ - 21 -
Online Trade Registration and Licensing Management System for Addis Ababa City VI
7.3.2 Intangible feasibility .............................................................................................................. - 21 -
7.4. Schedule feasibility .................................................................................................................. - 21 -
8. System Requirements of the new system ........................................................................................ - 22 -
8.1. Functional requirements ........................................................................................................... - 22 -
8 .2. Non-functional requirements .................................................................................................. - 23 -
CHAPTER THREE ................................................................................................................................ - 24 -
SYSTEM DESIGN ................................................................................................................................. - 24 -
1. Overview ......................................................................................................................................... - 24 -
2. System Architecture ........................................................................................................................ - 24 -
3. UML of the proposed system .......................................................................................................... - 25 -
3.1. Use case diagram and use case description .............................................................................. - 25 -
Use Case Documentation ............................................................................................................................ 27
3.2. Sequence diagram ........................................................................................................................ 37
Figure 11. Sequence diagram for cancel ..................................................................................................... 43
3.3. Collaboration diagram.................................................................................................................. 45
3.4. State chart diagram....................................................................................................................... 47
3.5. Class diagram ............................................................................................................................... 49
3.6. Component diagram ..................................................................................................................... 53
3.7. Deployment diagram .................................................................................................................... 54
4. Data persistence modeling .................................................................................................................. 55
4.1. Entity, attribute and schema ......................................................................................................... 55
4.2. ER –Diagram ............................................................................................................................... 56
4.3. Referential integrity constraints ................................................................................................... 60
4.4. Database table schema ................................................................................................................. 63
4.5. Normalization (1NF, 2NF, 3NF, BCNF) ..................................................................................... 69
CHAPTER FOUR....................................................................................................................................... 72
IMPLEMENTATION AND TESTING.................................................................................................. 72
4.1. Introduction ...................................................................................................................................... 72
4.2. Algorithm Design and Code ............................................................................................................ 72
4.2.1 Algorithm Design........................................................................................................................... 72
4.2.2 Coding ............................................................................................................................................ 73
Online Trade Registration and Licensing Management System for Addis Ababa City VII
4.3. User interface of the prototype –mock up screen............................................................................ 80
Figure 28. Employee’s page ....................................................................................................................... 83
4.4. Startup Strategies ........................................................................................................................ 83
CHAPTER FIVE .................................................................................................................................... 84
SYSTEM TESTING ............................................................................................................................... 84
5.1 System Testing Overview ................................................................................................................. 84
5.2 Testing Strategies Employed ............................................................................................................ 84
Table 25. black box testing example .......................................................................................................... 85
5.1.1 Unit testing ......................................................................................................................................... 86
Table 24. Unit testing................................................................................................................................. 86
5.2.2 System Testing ............................................................................................................................... 86
5.2.3 Integration testing .......................................................................................................................... 87
5.2.4 Acceptance Testing ............................................................................................................. 87
5.3 System Description and Process Flow ........................................................................................... 88
5.4. Training ....................................................................................................................................... 88
5.5. Installation................................................................................................................................... 89
CHAPTER SIX ........................................................................................................................................... 90
CONCLUSION AND RECOMMENDATIONS ........................................................................................ 90
6.1 Conclusion ...................................................................................................................................... 90
6.2 Recommendation .............................................................................................................................. 90
6.3 Future work ....................................................................................................................................... 91
6.4. References ....................................................................................................................................... 92
Online Trade Registration and Licensing Management System for Addis Ababa City VIII
List of table
List of table ................................................................................................................................... ix
Table 1. Hardware Requirement Cost ......................................................................................... - 9 -
Table 2. Software requirement cost ............................................................................................ - 9 -
Table 4. Trader’s application and license giving ...................................................................... - 12 -
Table 5.Renewal of license ....................................................................................................... - 12 -
Table 6: Update license ............................................................................................................. - 12 -
Table 7 : Cancel trade license ................................................................................................... - 13 -
Table 8. Entity and attribute.......................................................................................................... 56
Table 9. Entity and attributes ........................................................................................................ 56
Table 10. License .......................................................................................................................... 63
Table 11. License request ............................................................................................................. 63
Table 12. Message ........................................................................................................................ 64
Table 13. Renew ........................................................................................................................... 64
Table 14. Renew request ............................................................................................................... 65
Table 15. Notification ................................................................................................................... 65
Table 16. Rejected ........................................................................................................................ 65
Table 17. Account ......................................................................................................................... 66
Table 18. Applicant ....................................................................................................................... 66
Table 19. Employee ...................................................................................................................... 67
Table 20. Cancel ........................................................................................................................... 67
Table 21. Cancel request ............................................................................................................... 68
Table 22. Update request .............................................................................................................. 68
Table 23. Update ........................................................................................................................... 68
Online Trade Registration and Licensing Management System for Addis Ababa City IX
List of figure
List of figure .................................................................................................................................. x
Figure 1: Team Composition. ..................................................................................................... - 8 -
Figure 2. Form of the current system ........................................................................................ - 14 -
Figure 3. DFD diagram ............................................................................................................. - 20 -
Figure 4. System architecture ................................................................................................... - 25 -
Figure 6.Sequence diagram for login ............................................................................................ 38
Figure 7.Sequence diagram for registration .................................................................................. 39
Figure 9. Sequence diagram for given license .............................................................................. 41
Figure 13. Collaboration diagram for login .................................................................................. 45
Figure 14. Collaboration diagram for renewal .............................................................................. 46
Figure 15. Collaboration diagram for cancel license .................................................................... 46
Figure 16. Collaboration diagram for report ................................................................................. 47
Figure 17. Collaboration diagram for update ................................................................................ 47
Figure 18. State chart diagram for view report ............................................................................. 47
Figure 19. State chart diagram for update ..................................................................................... 48
Figure 22. State chart diagram for cancel ..................................................................................... 49
Figure 23. Class diagram of all system ........................................................................................ 49
Figure 24. Component diagram ................................................................................................... 54
Figure 25. Deployment diagram ................................................................................................... 55
Figure 23. Home page ................................................................................................................... 80
Figure 24. Login Form .................................................................................................................. 81
Figure 26. Trader Page .................................................................................................................. 82
Figure 27. Manager page .............................................................................................................. 82
Online Trade Registration and Licensing Management System for Addis Ababa City X
ABSTRACT
Trade Registration and Licensing Management System in Addis Ababa City was performed
manually in the existing system. So the existing system has many problems. Such as: it is cost
respect to time and human resources as well as there is work overload on the employers. For this
reason we have proposed an online trade registration and licensing management system which
solve the above mentioned problems. The proposed new trade registration and licensing
management system for Addis Ababa City is cost effective respect to human resource,
expenditure to take the license and time both for office employees and traders. Since the
proposed system is online some who want for every service can access what he/she wants access
everywhere and every time without coming to the office. The functional requirements of the
system are easy to understand and there is efficient information to how to use the system.
Generally, at the completion of the proposed system both traders and employees of the office
were benefited from it. In addition, the project team was also benefited from this project;
because, the project was done for academic purpose.
Online Trade Registration and Licensing Management System for Addis Ababa City XI
CHAPTER ONE
INTRODUCTION
1.1. Overview
Trade involves the transfer of the ownership of goods or services from one person or entity to
another in exchange for other goods or services or for money. Possible synonyms of "trade"
include "commerce" and "financial transaction". A network that allows trade is called a market.
Modern traders generally negotiate through a medium of exchange, such as money. As a
result, buying can be separated from selling, or earning. The invention of money (and
later credit, paper money and non-physical money) greatly simplified and promoted trade. Trade
between two traders is called bilateral trade, while trade between more than two traders is called
multilateral trade.
Trade license is the papers provided by the particular countries government for starting the
business. It ensure that the newly business or started business legality.
1.2. Background Information of the office and the system

1.2.1. Organizational Background
The Ministry of Trade was re-established in August 1995 under -- proclamation No 4/1995
issued to provide for the definition of powers and duties of the executive organs of the Federal
Democratic Republic of Ethiopia (FDRE). The Ministry was again reorganized with a
proclamation No 619/2003 issued to amend the reorganization of
the executive organs of the Federal Democratic Republic Ethiopia Proclamation No 256/2001.
With this proclamation and by other laws, the Ministry has been given the power to supervise
and coordinate five government institutions that are involved in the promotion & development of
trade, industry and investment activities. The Ministry is organized under one minister,
implementing departments, five support services, one Civil Service Reform office and trade
branch office that enable the ministry to effectively perform its duties and responsibilities vested
with it.
Online Trade Registration and Licensing Management System for Addis Ababa City -1-
Addis Ababa City Trade and Industry office is found in Addis and the office has reached the
current position and gets its current name after three changes. The organization is functionally
structured in to the following five (5) sub office and there is one supporting group for materials
and any other activities. Those are
1. Trade registration, license giving and modernization of trade and market office.
2. Trade legality and trade system controlling office.
3. Service and infrastructure provider office .
4. Product quality assurance and marketing place building office.
5. Customers and traders rights protecting office.
Mission:
The organization is mainly aimed to make sure that the people are benefitedby providing modern
and fast trading system with trade legality and fast Industry.
Vision
automated information system of Addis Ababa City Trade and Industry office and improve the
lives for the peoples within the City to stand them on behalf of medium income countries.
1.2.2. Background of the System

All trade and Industry offices have a wide range of long-term registration of new coming traders
and licensing system as well as payments for the services and annual tax. The registration may
be for getting TIN (Tax Identity Number) number or for getting trade license. The licenses
system incorporates giving, renewal, updating and cancelation of the license. According to our
new system the application for registration to get license and TIN number reduces paper work,
the need of many man power and costs. The proposed online registration for trade license and the
payment system for the services will eliminate all the manual invention and increase the speed of
whole process of licensing and payment system.
Generally the system is web application especially it will allow applicants to fill their personal
information online and submit to the system. A trader will have a unique name and login
password. In this work we are going to design and implement the online registration system for
trade license and the payment system for the services used for Addis Ababa City Trade and
Industry Office.
1.3. Statement of Problem

The office of Addis Ababa City Trade and Industry works in manual system for trade registration
and licensing. All the activities of license giving, updating license, cancelling license and others
are done through manual process.
For an applicant to be a trader or to have a trade license, he/she must come with a Kebele or
Woreda identification card given from the Kebele administrator and the tax identity
number(TIN) which is given by the revenues authority by verifying his/her fingerprint if the
applicant is an individual or who is willing to work alone. Genetic fingerprint is not mandatory
for those who apply for trade license as a group. An applicant should have a house for built for
trading purpose, if the house is rented he/she has to show the legal agreement made in between
the house owner and the trader. Applicants must provide the documents that are originals or
copies certified by the issuer for his/her identity, age and citizenship. Applicants should have
valid bank account. After having registered he/she has to select one of the trade codes and the
manager checks the requirements. An applicant should pay for the registration, for the license
when he/she wants to have, or in updating and cancellation. If all are ok the trader take trade
license which allows him/her to do any trade activity based on that trade code.
Currently faced problems
 Applicants have to come to the office for every service, this lead more cost and time wastage.
 Trader waits much time to get services.
 Since the current system is manual, it consuming time when registering new applicants,
Giving license, Renewal the license, cancelling the license.
 Need of many employees.
 Time loss to give information about trade for each applicant.
 Accessing information is difficult.
1.4. Objective of the project
1.4.1. General objective
The main objective of this project is to develop online trade registration and license management
system for Addis Ababa City Trade and Industry office.
1.4.2. Specific objectives

Some of the Specific Objects are the following: -
 Understand the current systems and its efficiency.

 Identifying the problem of the current system.
 Identify functional and non-functional requirements.
 Propose new systems which solve the problem of the current system.
 Model the new system using object-oriented methodologies.
 Finally implement and test the new system.
1.5 Scope and Limitation of the project

1. 5.1. Scope
The system includes functionalities of registering applicants for license, give the license for those
who fulfill the requirements, renew the license annually, update the license whenever it is
necessary and cancel the license.
An applicant to be a trader performs the registration process through online application by

accessing the organizations website. Applicant has to submit or fill his/her bank details and the
tax identity number (TIN) taken from the revenue’s authority. Having the TIN number an
applicant performs registering for license. The license can be prepared and given for an applicant
if the following conditions are met.
 An applicant should have renewed Kebele identification card.
 The coming trader should have a house for the trading purpose, whether it is rented and
his own
 He/she must have a bank account.
 He/she has to have TIN.
 Pay for the Service.
 When such license wants to verification, he can from verification body (sector).
1.5.2. Limitation
 Trading system has much functionality. But we are limited only to trade license giving,
renewal, updating and its legal cancelation. The annual tax payment system is not
included because of the authority to collect tax is not a power of this office.
 The trade controlling system is not included in the system, since it need further
supervision rather than performing it online.
 The system is not mobile based and cannot send SMS message
 The user interface is only support English language i.e. another language is not supported
1.6. Risk, Constraints and Assumption

1.6.1. Risk
Computer Viruses
While we encounter this problem, we take full scanning of our computer and documents
using the latest antivirus available, also keep our antivirus updated and make random scans
on our computer before this risk encounter.
Power failure and data loss
The action to be taken if there is a power loss. We use laptops, and to prevent a loss of data
we save the copy of our whole project on different computers (Lab computers, Personal
computers) and keep updated copy of the project on flash disk and CD-RW.
1.6.2. Constraints
 Project schedule/time limit
 Lack of experience of working with different program.
 Problem of getting the companies information as needed that means on time.
 Lack of enough internet access
 Shortage of equipment
1.6.3. Assumptions
We have some methods that we assume for the problems. Some of them are:
 All the team members have positive thinking to develop or work cooperatively for
success.
 We will have also some resource that we are using in the system .we will have back up
CDs .so that there will be not be loss of data.
 Trader and the office share ideas online using this system by instant messages.
 The system must have an interface which is simple enough to understand.
 The code should be free from errors.
1.7. Significance of the Project

 Unauthorized person will be out of service
 Each task is performed easily
 Can perform many tasks in short period of time
 Change the manual system of the organization to computerized system
 Reduce unnecessary resource wastage.
 Reduce employee overload work.
 System gives fast service to the customer
 Information accessing is easy and fast.
1.8. Beneficiaries of the project
1.8.1. Traders
 Can apply the registration for trade license, license renewal, canceling license, and
payments for services from anywhere at a given time.
 Allow traders get information online where they are and can be easily awarded.
 Decreasing cost and time wastage, when they are taking, updating, and cancelling the
license.
1.8.2. Organization
Addis Ababa City Trade and Industry office will be benefited after the completion of the project
in many ways including:
 To be competitive, profitable, and manage all traders’ affairs easily.
 The access to information will be easier, faster, safer, and also in a neat and well-
organized way.
 Employee cost will be reduced with respect to both time and money.
1.9. Team composition, budget and schedule

1.9.1. Team composition
Team Composition means the way the project developer or system developers communicate each
other in case to exchange or share information. And also, this is known by the name of the team
organization. This method of communication can be categorized into three. Those are
 Centralized.
 Decentralized.
 Mixed control team organization.

Among the three team organization types we selected the decentralized team organization to
develop our project. Because:
 Our team member found on the same level of knowledge stage.
 We have equal professions on our project (knowledge, programming skill, experience).
 We believe this method is strongly important to work our project.
 In general, we believe that this method makes us to communicate each other
Figure 1: Team Composition.

1.9.2. Budget
The developers tried to minimize the cost of the project the minimum price concerning all
economic problems of the group. The items used to formalize the project and the price they cost
is listed below in table.
Hardware Requirements cost
No Materials Required Amount Price Per Unit (birr) Total Cost (birr)
1 Dell laptop computer 1 15000.00 15000.00
2 Pen 5 5.00 25.00
3 A4 Size Paper 1 Destin 100.00 100.00
4 Print 100 pages 1.00 100.00
5 Flash Disk 1(8G) 120.00 120.00
6 CD-RW 2 25.00 50.00
Total 15395.00
Table 1. Hardware Requirement Cost
Software Requirements Cost
No Materials Required Price Per Unit

1 Microsoft Word 2010 Free
2 Notepad++ Free
3 Microsoft Office Visio 2007 Free
5 Mozilla Firefox Free
6 WAMP/XAMP Free
Table 2. Software requirement cost
1.9.3. Schedule
Concerning the project scheduling, it will be bound by strict timing so it must be delivered
within the time bound given over the table. The intention of the project team is to finalize this
project according to the time table given to finish this project.
I Task Startin End Dur February - June, 2020
D Name g Date date atio
February March April May June
n in
Day
s
1 Problem Februa Februa 10
Selection ry01,2 ry
and 020 10,202
Proposal 0
2 Requirem Februa Februa 14
ent ry13,2 ry
Analysis 020
27,202
0
3 System March March 15
Design 01,202 15,202
0 0
Object March April 15

4 Design 17,202 1,2020
0
5 Impleme April May 27
ntation 5,2020
and 2,2020
Testing
6 Documen May May 16

tation and 07, 23,202
Reporting 2020 0
Table 3. Schedule
- 10
Online Trade Registration and Licensing Management System for Addis Ababa City -
CHAPTER TWO
SYSTEM REQUIREMENTS SPECIFICATION (SRS)
1. Existing System Description

The current system of trade license management system is manual.The existing systems working
process has no speed and not gives timely information for traders. In order to gives the license,
update license, renewal license, and cancel license along with collecting the service fee. For an
applicant to be a trader or to have a trade license, he/she must come with a Kebele identification
card given from the Kebele administrator and the tax identity number(TIN) which is given by the
revenues authority by verifying his/her fingerprint if the applicant is an individual or who is
willing to work alone. An applicant should have a house for built for trading purpose, if the
house is rented he/she has to show the legal agreement made in between them. Applicants must
provide the documents that are originals or copies certified by the issuer for his/her identity, age
and citizenship. Applicants should have valid bank account. After having registered he/she has
to select one of the trade codes and the manager checks the requirements. An applicant should
pay for the registration, for the license when he/she wants to have, or in updating and
cancellation. If all are ok the trader take trade license which allows him/her to do any trade
activity based on that trade code.
2. Major Functions of the Existing System

2.1. Business process of the existing system
The major functions of the existing system are the following:
 Trader’s application and license giving
 Renewal of license
 Update license
 Cancel trade license
- 11
Table 4. Trader’s application and license giving
Input Trader’s application and license giving
Process The applicant he/she must come with the following. The TIN number is
given by revenues authority by taking the applicant fingerprint if
applicant is coming alone. Fingerprint is not needed for group
applicants. If the house is rented, he/she has to show the common
agreement approved by the legal body. After this all the requirement
can be checked by the office. The coming trader selects one trade code
and applies to the office after filling the written form.
Output Then the office giving license to the applicant after checking the above
requirements.
Table 5.Renewal of license

Renewal of license
Input Renewal of license
Process The license holder has to go to the office having a clearance from the
revenue’s authority showing details of annual tax payment
Output License is renewed annually.
Table 6: Update license

Update license
Input Update license
Process License holder can request the office to update his/her license when
 There is loss in capital (means when budget or capital crisis
- 12
happen).
 There is upgrade in capital.
Output If the requirements meet update for the license is completed and the
manager makes changes to the trader’s profile in the cabinet.
Table 7 : Cancel trade license

Cancel trade license
Input Cancel trade license form
Process Trade license can be cancelled if the one of the following situations
happen and get acceptance.
 Where there is less competence.
 Where there is falling of the risk in business.
 During death of holder.
 During leaving the country.
 When holder does not pay annual tax payment.
 When holder performs illegally
Output Cancel trade license
2.2. Players in the Existing System

The main players in the existing system includes the following: -
 Traders: - Trader will go to the Office to register, update, and renew the license when
existing criteria is fulfilled
 Trade and Industry Office: - To register, update, renew and cancel the license.
 Revenue Authority: - Give TIN and give receipt the trader paid annual tax
 Bank: Accept the fees deposit on the account and open account for trader
- 13
 Kebele: Give kebele Identity Card (ID).
2.3. Business Rules in the Existing System

 A business rule is effectively an operating principle or polices that we try to specify for
both the existing system and the new system must satisfy. The organization has the
following principles in the existing system which includes:
 #BR1: Applicant must have Keble Identification Card.
 #BR2: Applicant must come with TIN number given from the revenue’s authority.
 #BR3: Applicant must have a built house for trading purpose. If rented he/she has to
show the legal agreement made between them.
 #BR4: Applicant must have valid bank account.
 #BR6: Trader must pay 210 ETB to take trade license.
 #BR7: Trader must pay 105 ETB to update trade license.
 #BR8: Trader must pay 105 ETB to renewal trade license.
2.4. Report generation, forms, documents etc. in the existing system

In an existing system different reports are generated for different purposes. Those reports include
about giving of license and renewal of license, about the update and cancel licenses.
The manager generates report monthly and annually what activities are performed, the report is
manual and it takes time.
Putting required form filled during the registration
Figure 2. Form of the current system
- 14
2.5. SWOT analysis of the existing system.
Strengths of the Current System
 The payment of service was added on the organization account; this reduces the
extravagance of birr.
 Any task could not be done without permission of the office.
 The license can be prepared and given for an applicant if the criteria are met.
Weakness of the Current System
 Activities performed in the Trade license management system is done manually.
 License giving can take much time, much manpower and many losses of trader
information
 Getting necessary report about the license management is difficult and takes long
time.
Opportunities of the existing system
 There is man power who perform every activity diligently
 Traders have awareness when the license is renewed and in what situation the
cancellation of license is takes place
Thread of the existing system
 No enough computer in the office to do every activity easily and on time
 Even though diligent worker in the office there is no sufficient man power to perform
every activity efficiently & effectively and on time
 Since this system is manual may be serving the trader on time according the trader wish
is too difficult
- 15
3. Problems of the Existing System
The problems that are going to be addressed under this section are generalized using the
PIECES framework. It is an acronym to indicate Performance, Information, Economics,
Control, Efficiency and Service.
Performance: of any system is required to show to meet the needs of users of that system. The
current system’s performance is weak. This is due to the following reasons: - first the time
required from initiation to completion of a particular task is relatively high. Second is the
acceptable response time for a particular task is large. It is difficult to predict the response time
of each process based on the detailed description of the major functions of the existing system.
Information: Information related problems can be measured with respect to input, output and
stored data information of the existing system.
Input: Invalid input of data –Record values can be put to the wrong fields resulting in wrong
information about trader’s records which are kept in the record office. Also inaccurate capture of
data – Data is handled in a way that is not efficient for retrieval or processing purpose.
Output: To provide information, no easily method to Search due to manual existing system (in
this case waste time as well as human power).
Stored data: Data is not secured. Due to this, secret information is opened for unauthorized
persons.
Economics: Manual handling of data is expensive as compared to automated system. In general,

cost in terms of time is very high. As the number of employee’s increases, the existing system
will incur cost to handle.
Controlling: Since all the records associated with the manual system are recorded and stored
manually the security that the system provides for the privacy of this records is not good. The
system shouldn’t provide sufficient protection for access and manipulation of the records
associated with the system.
- 16
Efficiency: Due to the manual operation most of the activities are prone to wastage of resources
like man power, time etc. to produce the corresponding outputs. This makes the existing system
inefficient while utilizing resources.
Services: The main users of the current system are traders and the office staff itself. The services
given to users are not flexible, reliable and expandable i.e. the users must there in the office to
get the services given by the system. Those services given by the system are limited to a
particular area.
4. Proposed System
After careful observing the current manual system and identifying all the problems occurred
during over all activities of the existing system, the project team has decided to design automated
system for them. Since the automated system is fully flagged online at any time, it will solve the
problem and limitation of the current manual system of Addis Ababa City Trade and Industry
office. This means the proposed system is cost and time effective during performing every task.
The proposed system will use the major functionality of the existing system and able to advance
in accordance with speed, performance and efficiency with respect to current system.
5. Methodology and tools

5.1. Data Collection methods
Observation: The project team has conduct observation around the office of Addis Ababa City
Trade and Industry Office to know the overall activities performed and studied the working
environment and also we have observed how the trader document or file is stored.
Interview: The team has prepared interviwe to gather information for the overall functionalities,
activities, and processes of the trading system.
Document analysis: We have analysed documents like the regestration form which helps to
build the contents of the registration form.
5.2. Hardware and Software Tools

To develop the system different software, hardware tools and programming language are very
important. Hardware tools such as computer (laptop), Network cable, flash disk and CD-RW,
- 17
software tool such as Microsoft office word, Notepad and PowerPoint, Microsoft Office Visio
2007, WAMP/XAMP and programming language such as HTML and JavaScript and PHP are
used.
5.3. Minimum hardware and software requirements

5.3.1. Hardware Tools
1. Computer: - computer is a machine capable of doing many things. We use it to type on it and
install all software and programming language. All tasks are done on computer.
2. Network Cable: - used to get the internet access by connecting internet line from internet hub
to computer for further read and search information from internet.
3. Flash Disk and CD-RW: - used for the movement of data from one machine to another.
5.3.2. Software Tools

1. Microsoft Office Word: -It is very useful because it takes less time to write and format
the text, communicative effectively smart diagram and chart tools, quickly assemble
document. By looking its useful properties, we use Microsoft office word to type our
project work to get all the above benefits of it.
2. Power Point: - use to present the document in abstract forms. We use it to present our
presentation in short and brief way.
3. HTML: - The html language was designed to an effective way of achieving this
transferring of data and was designed to be evolving as new media format was created.
We use html to develop our statically parts of our code. We use because of html is
compact and effective language.
4. JavaScript: - JavaScript is very interesting language used to validate data and develop
different messages. We use it to validate our data which we use in html code.
5. PHP: -for sever side scripting
6. Notepad: -To write programs and different codes
- 18
7. WAMP/XAMP: - To run our code
8. Microsoft Visio 2007: - To draw Gantt chart
6. System analysis tools and techniques employed (DFD, OOSAD tools etc.)
Data flow diagram is used to shows how data flows in a system.
- 19
Figure 3. DFD diagram of Trade Registration and License Management of Addis Ababa
7. Feasibility Analysis
In this phase we have seen different feasibility measures such as, operational feasibility,
technical feasibility, and economical feasibility and schedule feasibility of the new system.
7.1. Technical feasibility
The new system does not require new professional person that process the implemented Web
based because the system does not need many employees which need special computer skill.
The system help human power should not be much loose. As much as possible the system is
easily understandable. So, each and every customer in the organization can access without any
confusion.
- 20
7.2. Operational feasibility
The new system is operationally feasible because:-
 The new system fits with the existing system.

 Satisfy the user needs or requirements
 It might not be possible to see full operational system within the given limit of time for
software development.
7.3. Economic feasibility

When the system is automated it does not be require much more cost beyond the capacity of the
organization by automating the system. This is one advantage of solving problems with Addis
Ababa City Trade and Industry office.
7.3.1 Tangible feasibility
This Trade license management system is expected that it will be economically feasible because
it will save the budget of organization. That is spending on papers and employees.
7.3.2 Intangible feasibility

The intangible benefits we suggest from the developing system are:
 Increase reliability, portability, and efficiency

 Faster processing
 Organized file management
 Reduce cost for manual data management
 Easy update & retrieval on stored records
 Less errors occur
7.4. Schedule feasibility

Projects are always given deadlines. Every project is completed in specific duration. We had to
complete the project in time and if it is not possible to complete on time then we should try to
fulfill requirements.
- 21
8. System Requirements of the new system
The services and tasks that the system required to perform can be categorized into Functional
and Non-Functional requirement to develop the new system.
8.1. Functional requirements
Functional requirement describe what the system should do. It also describe behavior of the
system relates to the system functionality. And it also the main things that the user expect from
the system.
In general functional requirement describe between the system and the user independent from its
implementation.
Functional requirement of the proposed system are:-
 The system enables users to login by entering correct username and password.
 The system enables system administrator to manage user
 The system enables license office to manage trader information such as trader first name,
last name, sex, age, etc.
 System enables manager and employee to view trader information.
 The system shall be able to deliver messages for the directed person through his/her
account.
 The system enables the user to send their complaint and receive feedback
 The system enables registering applicants for trade license,
 The system enables trader to register online.
 The system handling give license, renewal of the license, update the license, and cancel
the license.
 System allow trader to payment system for services fee.
 System is able to send online registration confirmation for trader
 The system enable Generate reports
 The system enable send notification to traders to renounce them that they have to renewal
their license through mailing system.
 Validate data and store it without error, giving information for future traders
 Giving information to how to fill trade license forms

 Providing information for traders who want to their trading activity
- 22
8 .2. Non-functional requirements
Non-functional requirements describe user-invisible aspects of the system that are not directly
related with the functional behavior of the system.
Non-functional requirements include Quantitative constraints, such as response time (i.e., how
fast the system reacts to user Commands) or accuracy (i.e., how precise are the system’s
numerical answers).
Security: Since information about the traders is secret the system should be able to give account
for each trader. The system should allow traders to login to the system. If the trader has failed to
enter a valid username and password, the system should again prompt to enter valid username
and password after displaying a message that tells him/her to enter correct username and
password. If the username and password are correct the system should allow them to get the
services.
Response Time: This is the time that needed to get any required service from the website after
applying a request. The system should be able to serve as quickly as possible.
User Interface: The application should have a user interface which is simple to use and
negotiable through each page. The system is user friendly.
Efficiency: The system must respond to applicant’s request as fast as possible and should be
fully response at time.
Performance: The system should have a quick response time for a single request made. It is
expected that the software would perform functionally all the requirements that are specified by
the organization.
Ease of use: The general and organizational views should be easy to use and innate. Online help
out and certification should be provided.
Reliability: System is reliable respect to error occurrence and Validate user input on Forms
information or data.
Maintainability: After the deployment of the project if any error occurs then it should be easily
maintained by the software developer.
- 23
CHAPTER THREE
SYSTEM DESIGN
1. Overview
System design is the process of defining the elements of a system such as: the architecture,
modules and components, the different interface of those components and the data that goes
through that system. Therefore, this chapter depicts the system architecture or the architectural
design for the system.
2. System Architecture
We have used three level architecture with three layers. These three layers are the client
Application layer, server Application layer and the data access layer. These are:-
Client layer: is present data to the user and take data from the user in the form of user interface.
Server layer: is act as interaction between client and data access layer and also validate any data
that flow to and from client and data base.
Data access layer: It contains data base and perform any modification that accessed in database.
- 24
Client tier
Middle
tier
Send request through HTTP
Web server
Client 1
select
Get response through HTML

My sql
Data
tier
database
Client n
Figure 4. System architecture
3. UML of the proposed system

3.1. Use case diagram and use case description
Use case diagram is a UML diagram that is used for describing user scenarios and capturing user
needs. It is used during the analysis phase to represent the external behaviors (actors, the
boundary and use cases including the association in between them).
- 25
Figure 5 use case diagram
Online Trade Registration and Licensing Management System for Addis Ababa City 26
Use cases are:
 UC-01:- Login
 UC-02:- Apply Registration
 UC-03:-Pay service fee
 UC-04:- Transfer money
 UC-05:-add tradecode
 UC-06:- Give License
 UC-07:- Renew License
 UC-08:-Update License
 UC-09:- Cancel License
 UC-10:- Generate Report
 UC-11:- View Report
 UC-12:-Manage Account
 UC-13:-Manage Tradecode
Actors
 Admin
 Manager
 Trader
 Employee
 Bank
Use Case Documentation

Use case description for login
Name: Login
Use case ID: UC-01
Primary actor: Administrator, Manager, Trader, Employee
Description: To interact with the system.
Precondition: Trader, Employee and Manager must have username and password.
Post condition: System should transfer control to the user main home page to proceed to the
desired further actions.
Basic Course of Action:
1. User select login menu.

2. System display login page.
3. User inputs username and password and also selects their status whether they are trader
or manager, administrator.
4. System validates username and password.
5. System displays main home page.
6. Use case ends.
Alternate Course 4A: user is not eligible to login
4A.1. the system determines the user name or password is incorrect.

4A.2. Display wrong username or password entered.
4A.3. Use case continues at step 3 in main course of action.
Use case description for apply registration
Name: apply registration
Use case ID: UC-02
Primary actor: Applicant
Description: applicant wants to be a trader for this he/she has to have a registration.
Precondition: applicant wants to have license.
Post condition: applicant can have license.
Use case description for pay service fee
Name: pay service fee
Include: Login
Basic course of action:
1. Applicant browses the website of Addis Ababa City Trade and Industry office.
2. Applicant select register menu.
3. System displays the registration form.
4. Applicant fills all detail information.
5. Applicant click on register button.
6. System display conformation message.
7. Use case end.
Alternative course of action: 1A. The requested page does not found.
1A.1. applicant get page not found message.
1A.2. applicant refresh browser and click on try again.
1A.3. applicant leaves the page.
Alternative course of action: 4B. Applicant fills wrong information.
4B.1. System displays error message.
4B.2. use case continues at step 4 of basic course of action.
Use case ID: UC-03
Primary actor: Applicant
Description: applicant pays for the service he/she has used.
Precondition: applicant has registered for license and has account.
Post condition: bank successfully transfers money to the account of the trade and Industry office
from the applicants account.
Includes: login, Transfer Money.
1. Applicant dials to the bank.

2. Applicant fills the login pin code.
3. System displays list of services.
4. Applicant chooses transfer money menu.
5. System displays the money transfer form.
6. Applicant fills required information.
7. System validates information (account validity).
8. Applicants click on ok button.
9. System requests an applicant to confirm the transfer.
10. Applicant click ok button/confirms.
11. System finishes transaction.
12. System changes applicants account.
13. System generates confirmation number for successful transfer.
14. System sends the number to the sender and receiver.
15. Use case end.
Alternative course of action: 2A applicant fills wrong pin code.
2A.1. bank displays please enter correct pin code message.
2A.2. use case start at step 2 of basic course of action.
Alternative course of action: 7B applicant fills invalid account.
7B.1. bank displays account you fill does not exist. Please fill the correct one.
7B.2. use case goes to step 6 of basic course of action.
Alternative course of action: 7C applicant account does not have enough balance.
7C.1. bank displays account has insufficient balance message.
7C.2. Applicant exits.
Use case description for the give license
Use case name: give license
Use case ID: UC-06
Primary actor: Employee
Description: after an applicant request to have license and has paid for taking license the
manager prepare the license and give to him/her.
Precondition: applicant must be registered for license.
Post condition: manager allows an applicant to take the license.
Includes: login
Basic course of the action:
1. Employee browses the website.

2. Employee selects license request menu.
3. System displays applicant’s request.
4. Employee check the code the applicant has send.
5. Employee click on prepare license menu.
6. System display license form.
7. Employee fills information on the form.
8. Employee click on print button.
9. Employee put the seal on license.
10. Employee scans the license.
11. Employee sends the license through mail.
12. Use case end.
Alternative course of action: 4A code not match.
4A. 1 Employee send mail saying you are not allowed.
Use case descriptions for renewal license
Use case name: renewal license
Use case ID: UC-07
Description: after an applicant request to renew license and has paid the fee for license renewal
the Employee can renew the license.
Precondition: applicant need to renew license. Employee must login to system
Post condition: applicant’s license renewed for the year.
Includes: login
1. Employee browses the website.k

2. Employee selects renew license menu.
3. System displays applicants request to renew license.
4. Employee renews the license.
5. Use case ends.
Alternative course of the action: 3A. There are no new requests.
3A.1 Employee leaves the page.
Use case descriptions for update license
Use case name: update license
Use case ID: UC-08
Description: after an applicant request to update license and has paid the fee for license updating
the manager can update the license.
Precondition: applicant need to update license. Employee must login to system
Post condition: applicant’s license updated for the year.
Includes: login

2. Employee selects update license menu.
3. System displays applicants request to update the license.
4. Employee updates the license.
5. Use case ends
Alternative course of the action: 3A. There are no new requests.
Use case description for the cancel license
Use case name: cancel license
Use case ID: UC-09
Description: Employee cancels trader’s license when there is illegal action or when trader has
encountered business crash.
Precondition: applicant needs to cancel license or by the manager himself. Applicants have to
send their reason to cancel along with an approved document from Keble administrator.
Employee must login to system.
Post condition: applicants can’t do with their license.
Includes: login

2. Employee selects license cancelation request menu.
3. System displays applicants request to cancel the license.
4. Employee cancels the license.
5. Use case ends.
Alternative course of action: 3A. There are no new requests.
Use case description for generate report
Use case name: generate report
Use case ID: UC-10
Primary actor: Manager
Description: manager needs to prepare a report over he works in daily or weekly. Manager
checks works done within the same day for daily report and within the week for weekly reports
similarly for monthly and annually.
Precondition: manager needs to have report Manager must login to system
Post condition: reports effectively generated.
Includes: login
1. Manager browses the home page.

2. Manager select generate report menu.
3. System displays report form.
4. Manager select report type (daily, weekly, monthly, and annually).
5. System display selected report form.
6. Manager writes the report and click on save button.
7. Use case ends.
Alternative course of action: 1A. Browser fails to open the website.
1A.1 System display page not found message.
1A.2 Manager refreshes the browser.
1A.3 Manager leaves.
Use case description for view report
Use case name: View report
Use case ID: UC-11
Description: Manager needs to see a report over he works in daily or weekly done in office.
Precondition: Manager must login to system
Post condition: Manager can see reports of office.
Includes: login

2. Manager select view report menu.
3. System displays reports.
4. Manager view reports.
5. Use case ends.
1A.3 Manager leaves
Use case description for manage account
Use case name: manage account
Use case ID: UC-12
Primary actor: Administrator
Description: Administrator it manage the account of the actors whom participants on the system
Precondition: Administrator must login to system
Post condition: account effectively manageable.
Includes: login
1. Administrator browses the home page.

2. Administrator select manage account menu.
3. System displays form.
4. Administrator select account types (create, delete, update, and change password).
5. System display selected account form.
6. Use case ends.
1A.2 Administrator refreshes the browser.
1A.3Administrator leaves.
Use case description for manage trade code
Use case name: manage trade code
Use case ID: UC-13
Description: Manager needs to see a report over he works in daily or weekly done in office.
Precondition: Manager must login to system
Post condition: Manager can manage trade code.
Includes: login

2. Manager select manage trade code menu.
3. System displays form.
4. Manager select account types (add, delete, update).
5. System display selected account form.
6. Use case ends.
1A.3 Manager leaves
3.2. Sequence diagram

It shows interaction of objects and classes involved in the scenario and the sequence of messages
exchanged between the objects needed to carry out the functionality of use case scenarios.
Figure 6.Sequence diagram for login
Figure 7.Sequence diagram for registration
Figure 8. Sequence diagram for renewal
Figure 9. Sequence diagram for given license
Figure 10. Sequence diagram for view report
Figure 11. Sequence diagram for cancel
Figure 12. Sequence diagram for pay service fee
3.3. Collaboration diagram
Collaboration diagram of license management system shows the objects and their association
with other objects of license management system apart from how they interact with each other.
Figure 13. Collaboration diagram for login
Figure 14. Collaboration diagram for renewal
Figure 15. Collaboration diagram for cancel license
Figure 16. Collaboration diagram for report
Figure 17. Collaboration diagram for update

3.4. State chart diagram
In our system we used state chart diagram to describe operational work flow of any component
in a system.
Figure 18. State chart diagram for view report
Figure 19. State chart diagram for update
Figure 20. State chart diagram for login
Figure
21. State chart diagram for renewal
Figure 22. State chart diagram for cancel
3.5. Class diagram
The following class diagram depicts the license system’s object structure. It shows object classes
that the license system is composed of as well as the relationships between those object classes.
Figure 23. Class diagram of all system
1. Login
login
-user name : String
-password : String
+login()
+Cancel()
 Attribute Description for Login

User name: This attribute used to hold the name of a specific user that is trying to
log in to the system and its data type is string.
Password: This attribute used to hold the password or the validation key of the user
that has been used as the first criteria to log in to the system.
 Operation
Log in (): This method used to check the user validity in the system.
Cancel (): This method used to exit from this class.
 Constraints
Invariant: Both username and password must be valid and must not be null.
Precondition: The username and password should be correct.
Post condition: The login object is created and successfully login to the system if
authorize.
2. Trader
 Attribute Description for Trader
First name: this is type of string and used to store the first name of the traders.
Middle name: this is type of string and used to store middle name of the traders.
Last name: this is type of string and used to store last name of the traders.
Keble id: this is type of integer of and used to store the Kebele number of the
traders.
Sex: this is type of char and used to store the gender type of that trader.
Age: this is type of integer and used to store the age of that trader.
Date: this is type of date and used to store the date at which the traders register.
 Operation
Pay service Fee ( ): This operation when invoked the trader pay for service fee.
Register for License ( ): This operation when invoked creates a new trader.
Take License ():This operation when invoked the trader he/she take the license
 Constraints
Invariant- the registration form not be empty.
Precondition: The trader must have fill the information in the form.
Post condition: The trader successfully Register.
4. Employee
 Attribute Description for Employee

First name: this is type of string and used to store the first name of the employee.
Middle name: this is type of string and used to store middle name of the
employee.
Last name: this is type of string and used to store last name of the employee.
Sex: this is type of char and used to store the gender type of that employee..
Age: this is type of integer and used to store the age of that employee.
 Operation
Give license ( ): This operation when invoked the manager gives license for trader.
Renew license ( ): This operation when invoked the manager renew the license for trader.
Update license ( ): This operation when invoked the manager update the license for trader.
Cancel license ( ): This operation when invoked the manager cancels the license from trader.
Generate report (): This operation when invoked the employee. Generate the report to the
manager.
 Constraints
Invariant- all the attributes should not be null...
Precondition: The trader must have an application for license.
Post condition: The license successfully.
5. User account
USER ACCOUNT
-User name : string
-Password : string
-Account type : string
+Create account()
+Delete account()
+Update account()
+Change password()
 Attributes Description for User account
Username-this is type of string and used to enter user name.
Password-this is type of string and used to enter password.
Account Type-this is type of string and used to select account type.
 Operation
Create account- is used to add user to the database.

Delete account -is used to delete or remove user.
Update account- is used to update account.
Change password-is used to change password
 Constraints
Invariants: The username and password must not be null.
Precondition: The user must have username and password.
Post condition: The user successfully entered to the system if it’s authorized.
6. License
LICENSE
-Code : int
-Name : string
-Level : int
-Category : string
+getGiveDate()
+getRenewalDate()
+getCancelDate()
+getUpdateDate()
 Attributes Description for License
Code: this is type of integer and used to store a license trade code.
Name: this is type of string and used to store traders name.
Level: this is type of integer and used to store the level of the license.
Category: this is type of integer and used to store category of license
 Operation
Get give date (): this method is used to hold the date of given license.
Get renewal date (): this method is used to hold the date of renewal license.
Get cancel date (): this method is used to hold the date of cancel license.
Get update date (): this method is used to hold the date of update license.
 Constraints
Invariants: All the attributes should not be null.
Precondition: The trader must have fulfill the criteria to get license.
Post condition: The manager manages license
3.6. Component diagram
Component diagram is used to model the physical aspects of the system. These physical aspects
are the elements in the system like executable, libraries, documents, files, forms, etc. which
resides in the nodes, so that we used component diagrams to visualize the organization and
relationships among components in our system.
Database server
Application
Browser Manage account

TCP/IP
ODBC
Generate report
Administrator -End2
add trade code
*
-End1
Give License
1
Manager
Persistance
Update License
employee Cancel License
Renew License
Trader View report
Bank TLMS
Apply registration
Pay service Fee
Transfer Money
Figure 24. Component diagram
3.7. Deployment diagram

Deployment represents the nodes that form the systems hardware topology on which the system
executes. It shows the configuration of nodes at run time and the component hosted on them;
model the installation of the parts that make up the physical system.
Figure 25. Deployment diagram
4. Data persistence modeling

4.1. Entity, attribute and schema
An entity represents a real-world object or concept, such as an employee or a project that is
described in the database. An attribute represents some property of interest that further describes
an entity, such as the employee's name or salary.
No Entity Attribute Data type Size Primary key
1 Trader f_name varchar 32
m_name varchar 32
l_name varchar 32
Bank_account_no varchar 200
Birth_date date
Trade_code int 50
Trade_name varchar 550
User_name varchar 32 Yes
Password varchar 20
tin_no varchar 200 Yes
City varchar 40
Sub-City varchar 40
Kebele/Woreda varchar 40
Kebele_id varchar 12 Yes
Phone int 15 Yes
Photo varchar 544
Gender varchar 10
2 License License_no int 11 Yes
Given_date date
Renew_date date
Update_date date
Cancel_date date
Table 8. Entity and attribute
No Entity Attribute Data type Size Primary key
3 Employee f_name varchar 32
m_name varchar 32
l_name varchar 32
Photo varchar 544
employee_id varchar 12 Yes
Gender varchar 10
Nationality varchar 32
Birth_date date
Salary int 11
Phone int 15 Yes
Position varchar 50
Education_level varchar 50
Date_hired date
Password varchar 20
Email Varchar 20
4 Admin f_name varchar 32
m_name varchar 32
l_name varchar 32
Password varchar 20
Email Varchar 20
Table 9. Entity and attributes
4.2. ER –Diagram
Entity relationship is the graphical representation of an information system that depict the
relationship among people, objects, places, concepts or events with in that system.
figure 26 ER-diagram
license-no
Given for
zone
Update for
Given-date
M
Trader
M
Renew for Address
Renew-date Transfer
M M M
money for
M
License
M M M
Update-date
M Open
Update by account
M M 1
Given by Get account
by
Bank 1
Renew Registered
by by
M 1
M M M 1
Admin name
Get
M account by
Employee
M 1
Registered by
email
4.3. Referential integrity constraints
Referential integrity is a relational database concept in which multiple tables share a relationship
based on the data stored in the tables, and that relationship must remain consistent. These
constraints include Primary Key, Foreign Key, Unique Constraints and other constraints.
Account
list_no f_name m_name l_name gender phone user_name Password
Employee
list_n phot Employee f_na m_na l_na gend phon Nationali ema User_na education_le salar birth_da hired_da Stat
o o _id me me me er e ty il me vel y te te e
Applicant
list_no Kebele_id photo f_name m_name l_name gender phone capital Email trade_code trade_name tin_no zone City birth_date regist_d
License
license_no Kebele_id photo f_name m_name l_name gender phone User_name email trade_code trade_name tin_no Zone City kebele bir
License request
license_no Phone User_name Bank_account_no State regist_date Receipt
Renew
license_no Kebele_id photo f_name m_name l_name gender phone User_name email trade_code trade_name tin_no Zone City kebele bir
Renew requestk
request_no License_no User_name Email clearance receipt date seen
Update
update_no Kebele_id license_no Photo f_name m_name l_name Gender Phone User_name email trade_code trade_name tin_no zone City
Update request
Update_request_no license_no User_name Cause trade_code trade_name receipt Date seen
Cancel
list_no license_no Photo f_name m_name l_name gender phone user_name trade_code trade_name tin_no Zone kebele City h
Cancel request
list_no license_no user_name date Seen
Rejected
list_ Kebele Pho f_na m_na l_na gend pho User_na Em Bank_accou trade_c tin_ zo Cit kebe house_ regist_d
no _id to me me me er ne me ail nt_no ode no ne y le no ate
Notification
Notification_no user_name Notify for Description From seen
Message
message_no From To detail Date Seen
4.4. Database table schema
The overall design of the database is called the database schema. Schemas are changed
frequently, if at all.
Table 10. License
Table 11. License request
Table 12. Message
Table 13. Renew
Table 14. Renew request
Table 15. Notification
Table 16. Rejected
Table 17. Account
Table 18. Applicant
Table 19. Employee
Table 20. Cancel
Table 21. Cancel request
Table 22. Update request
Table 23. Update
4.5. Normalization (1NF, 2NF, 3NF, BCNF)
In our registrar system we use normalization mechanism to organize the data of registrar system and
to keep its consistency.
1st NF
Any row must not have a column in which more than one value is saved.
2nd NF
Every column in the table must fully dependent on primary key
Applicant table
1ST NF applicant
list Kebel photo f_na m_na l_na Gen Pho capita ema trade trade tin Cit sci birth re
no e_id me me me der ne l il _cod _nam _n y ty _dat t_
1 2333 Dawit kebede nege mal 09 1100 gg 1110 coffe 33 A Ye - -

ra e 00 22 A ka
2nd NF
list_no Kebele_id phone email tin_no House_no
1 234 0993 bb@gmai 33221 0112334

l.com 12212
3rd NF
Kebele Phot f_na m_na l_na gen Pho Capit trade trade sci to birth regis Bank_accou
o ty
_id me me me der Ne Al _cod _nam ne wn _dat t_dat nt_no

e e e e
License table
1st NF
license_no Kebele Phot f_na m_na l_na Gend Phon User_ ema trade trade tin sci City ke
_id o me me me er e name il _cod _nam _n ty ele
2nd NF
license_no Kebele_id phone User_name Email tin_no
3rd NF
licens Phot f_na m_na l_na Gend trade trade zo City keb birth given Given State
e_no o me me me er code _nam ne ele _dat _date _by
Renew table
1st NF
2nd NF
licens Kebel phon User_n ema tin_

e_no e_id e ame il no
3rd NF
Pho f_na m_n l_na gen ema zo City Keb birth give Renew expiry
to me ame me der il ne ele _dat n_da _date _date
e te
Update table
1st NF
updat Kebel license phot f_n m_n l_na Gend Pho User_n emai trade trade tin zo City Keb
e_no e_id _no o ame ame me er ne ame l _cod _na _n ne ele
e me o
2nd NF
updat Kebel license pho User_n Ema tin

e_no e_id _no ne ame il _n
3rd NF
updat Phot f_n m_n l_na gende trade trade zo City keb updat update expiry
e_no o ame ame me r _cod _na ne ele e_dat _by _date
E Me e
CHAPTER FOUR
IMPLEMENTATION AND TESTING
4.1. Introduction
Implementation is the phase where objectives of physical operations of the system turned into reality
i.e. real working model. This includes implementing the attributes and methods of each object and
kintegrating all the objects in the system, to function as a single system. The crucial phase in the
system development life cycle is the successful implementation of the new system design. The
process of converting as new system into an operational one is known as system implementation. The
implementation activity spans the gap between the detailed object design model and a complete set of
source code files that can be compiled together. This chapter presents Algorithm design & coding.
4.2. Algorithm Design and Code
4.2.1 Algorithm Design

 Algorithm for log in to the trader home page
Display main homepage form
Fill user name and password in the appropriate interface
If the filled input is valid
Display trader main page
Else
Display Error Message and return to home page
End if
 Algorithm for System Administration
Display Main homepage
Display trader main page
Else
Display Error Message and return to home page
End if
 Algorithm for authentication
Display login form
If user name=Administrator
Display Administrator Main Page
Else type=Employee
Display Employee Main Page
Else type= Trader
Display trader Main Page
Else
Display Error Message “please insert correct username and password”
End if
4.2.2 Coding
Coding is the process whereby the physical design specification created by the designers is turned in
to working computer code by the programmer. The code is made simple in such a way that another
programmer can easily understand and work on that in future. It is a phase where all the work during
analysis and design will be turn off to a functional system prototype. We use object oriented
programming Language with android throughout the code.
Sample of coding is as follows:
CODE FOR LOGIN:
<?php
session_start();
error_reporting(E_ALL^E_NOTICE);
$username=$_POST["username"];
$password=$_POST["password"];
$password = $_POST["password"];
$crypt_pass = md5($_POST['password']);
include('db.php');
k$qry="select * from account where user_name='".$username."' and password='".$crypt_pass ."'";
$results = mysqli_query($con,$qry) or die(mysqli_error($con));
$count=mysqli_num_rows($results);
if($count<='0'){
?>
<font color="white">
<?php
$error='please insert the correct user name and password';
include("index.php");
}
else
{
while ($row = mysqli_fetch_array($results)) {
$user1=$row['privilege'];
$id=$row['list_no'];
$state=$row['state'];
$username=$row['user_name'];
if($state=="active")
{
if($user1=="manager"){
$_SESSION['id']=$id;
$_SESSION['username']=$username;
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<center><img src="images/32.gif"></center>';
echo'<h1 align="center" class="err"><b>.....Loading.......<br>Please Wait....</b></h1>';
echo'<meta http-equiv="refresh" content="3;url=manager/managehome.php">';
//header('location:manager/managehome.php');
}
if($user1=="admin"){
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<h1 align="center" class="err"><b>.....Loading.......<br>Please Wait....</b></h1>';
echo'<meta http-equiv="refresh" content="3;url=admin/adminhome.php">';
//header('location:admin/adminhome.php');
}
if($user1=="employee"){
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<h1 align="center" class="err"><b>.....Loading........<br>Please Wait...</b></h1>';
echo'<meta http-equiv="refresh" content="3;url=employe/employe_page.php">';
//header('location:employe/employe_page.php');
}
else if($user1=="trader"){
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<br>';
echo'<h1 align="center" class="err"><b>.....Loading........<br>Please Wait...</b></h1>';
echo'<meta http-equiv="refresh" content="3;url=trader/home.php">';
//header('location:trader/home.php');
}
else if($user1==""||$user1==null)
$error= "You have no privilege";
}
else
{
$error="this Account is deactivated or inactive";
//header('location:home.php');
inkclude("index.php");
?>
</font>
<?php
}
}
}
?>
CODE FOR ADMINPAGE:
<?php
mysql_connect("localhost","trade", "trade");
mysql_select_db("license");
session_start();
if(isset($_SESSION['username']))
{
$name=$_SESSION['username'];
}
else
{
header('location:../home.php');
}
?>
<html>
<head>
<title>Administrator Page</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="viewport" content="initial-scale=1.0">
<link rel="stylesheet" href="../ate_files/css3menu1/style.css" type="text/css" />
<style type="text/css">
._css3m{display:none}
</style>
<style type="text/css">+
</style>
</head>
<body background="../images/mback.jpg">
<table bgcolor="#gold" border="0" align="center" width="935" height="alternate">
<tr><td> <img src="../images/logo.JPG" height="150" width="630"/><img
src="../images/er.gif" height="150" width="300"/>
</td></tr>
<tr><td>
<input type="checkbox" id="css3menu-switcher" class="c3m-switch-input">
<ul id="css3menu1" class="topmenu">
<li class="switch"><label onclick="" for="css3menu-switcher"></label></li>
<li class="topfirst"><a class="pressed"href="adminhome.php"
style="width:130px;height:17px;line-height:17px;"><center>Home</center></a></li>
<li class="topmenu"><a href="pass.php" style="width:130px;height:17px;line-
height:17px;"><center>change password</center></a></li>
<li class="topmenu"><a href="#" style="width:260px;height:17px;line-
height:17px;"><center>user account</center></a>
<ul>
height:17px;"><center>For Trader</center></a>
<ul>
<li><a href="trader.php">Create Account</a></li>
<li><a href="view_acc.php">delete Account</a></li>
</ul>
height:17px;"><center>For employee</center></a>
<ul>
<li><a href="add_emp.php">Create Account</a></li>
<li><a href="view_acc.php">delete Account</a></li>
</ul>
</li>
</ul>
height:17px;"><center>feedback </center></a>
<ul>
<li><a href=" feedback.php">send comment </a></li>
<li><a href="feedbackview.php ">view comment </a></li>
</ul>
</li>
<li class="toplast"><a href="../Logout.php"style="width:150px;height:17px;line-

height:17px;"><center>log out</center></a></li>
</ul>
</td></tr>
</table>
<table bgcolor="#green" border="0" align="center" width="937" height="600">
<tr>
<td width="922">
<td>
<iframe src="preadminhome.php" width="920" height="600"></iframe>
</td>
</td>
</tr>
</tr>
<tr align="center">
<td colspan="3" color="white">Copyright©2020 Gage College!!</td>
</tr>
</table>
</body>
</html>
CODE FOR TRADER PAGE:
<?php
include('db.php');
session_start();
if(isset($_SESSION['username']))
{
$name=$_SESSION['username'];
}
else
{
header('location:../home.php');
}
?>
<!DOCTYPE html>
<html dir="ltr">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta name="viewport" content="initial-scale=1.0">
<title>Trade License</title>
<link rel="stylesheet" href="../userhomeate_files/css3menu1/style.css" type="text/css" />
<style type="text/css">
</style>
</head>
<body background="../images/mback.jpg">
<table bgcolor="#ffffff" border="0" align="center" width="935" height="alternate">
<tr><td align="right">
<tr><td> <img src="../images/ER.GIF" height="100" width="450"/><img
src="../images/logo.jpg" height="100" width="450"/></td></tr>
<tr><td>
<input type="checkbox" id="css3menu-switcher" class="c3m-switch-input">
<ul id="css3menu1" class="topmenu">
<li class="switch"><label onclick="" for="css3menu-switcher"></label></li>
<li class="topfirst"><a class="pressed" href="home.php"
style="width:130px;height:17px;line-height:17px;"><font size="2"
color="#191970">Home</font></a></li>
<li class="topfirst"><a class="pressed" href="home1.php"
style="width:130px;height:17px;line-height:17px;"><font size="2"
color="#191970">payment</font></a></li>
<li class="topfirst"><a href="about.php" style="width:120px;height:17px;line-
height:17px;"><font size="2" color="#191970">About</font></a></li>
<li class="topmenu"><a href="license.php" style="width:120px;height:17px;line-
height:17px;"><span><font size="2" color="#191970">change password</font></span></a>
<ul>
<li><a href="profile.php">Profile</a></li>
<li><a href="pass.php">Change Password</a></li>
</ul>
</li>
<li class="topmenu"><a href="notification.php" style="width:120px;height:17px;line-
height:17px;"><span><font size="2" color="#191970">Notifications</font></span></a>
<li class="topmenu"><a
href="../Logout.php"style="width:130px;height:17px;line-height:17px;">Log Out</a></td></tr>
</li>
</td></tr>
</table>
<table bgcolor="#ffffff" border="0" align="center" width="935" height="alternate">
<tr>
<td>
<td>
<iframe src="inner_home.php" width="920" height="500"></iframe>
</td>
</td>
</tr>
</tr>
<tr align="center">
<table align="center"width="936">
<tr><td colspan="3" height="40" align="center" text="white"><font size="5" color="white">
Copyright©2020 Gage College!!!</td></tr>
<hr>
</table></tr></table></body>
</html>
4.3. User interface of the prototype –mock up screen
It is how the user would interact and access the system. That means how information would flow
between the user and the software. The user interface requirements for the system are: -
System will provide graphic user interface for all functionality.
The user interface should provide processing message to users to indicate the status of an
action.
The system would prompt for a password to secure it from unauthorized persons.
The system would provide error for invalid inputs.
Figure 23. Home page
Figure 24. Login Form
Fig.25 ADMIN PAGE
Figure 26. Trader Page
Figure 27. Manager page
Figure 28. Employee’s page
4.4. Startup Strategies

Startup means the process to make the new system begin to operate. It is the process of how to start
our system. There is different approach for startup.
1. Open XAMPP control panel

2. Click on start Appache and start MySQL
3. Open any browser which and type http://localhost/addistrade/home.php
CHAPTER FIVE
SYSTEM TESTING
5.1 System Testing Overview

Final phase of implementation is testing. Testing is a process to show the correctness of the program.
This is checking of the system workability in an attempt to discover errors and avoiding such errors
from the system.
System testing is the process of evolution of system or its parts by manual or automatic means to
detect the differences between existing and expected output. Under this chapter we will test our
system by applying different types of testing to eliminate any fault existing in our system. This task is
very important because it is life saver of old system and it allows us to answer the questions, which
helps us to identify the area where we need additional knowledge about the system as system
developer. Accordingly, the following questions should be answered during this phase.
1. Does our system really work as expected?

2. Does our system meet the users’ requirements?
3. Is it what the users expect? Do the users like it?
4. Is it compatible with our other systems?
5. How does it perform?
6. How does it scale when more users are added?
7. Which areas need more work?
Generally, no system is perfect due to communication problems between user and developer, time
constraints, or conceptual mistakes by developer. . In this the team members tested the entire system
as a whole with all forms, code, modules. In this we tested all the functionalities in the System. All
errors in the forms, functions, modules have been tested. The following are different testing
strategies.
5.2 Testing Strategies Employed

While we are testing the system we have been used both white box testing and black box testing.
 White Box testing system: White-box testing is the detailed investigation of internal logic and
structure of the code. Since we are developer of the system, we have used white box testing
strategy to verify and validate our project. By this testing strategy we have a look inside the
source code and find out which unit/chunk of the code is behaving inappropriately.
 Black box testing system: The technique of testing in which the tester has no any knowledge of
the interior workings of the application. Also the tester does not have access to the source code
typically, while performing a black-box test; a tester will interact with the system's user interface
by providing inputs and examining outputs without knowing how and where the inputs are
worked upon. For this reason, we can identify whether the system is easy to use or not by using
black box testing strategy.
 Black box testing example
o Test type: - Black box testing

o Test number: - test 1
o Test Case Name: - Login
o Test case description: - To test login screen
o Precondition: - User has username and password
o Post condition: - User is authenticated and successfully login to the system
o Test priority: - Medium
Table 25. black box testing example
Specification
Input Expected output Output result Pass or fail

Valid User name and Invalid Error message Display error Fail
Password message
Invalid User name and Error message Display error Fail
valid password message
Valid User name and valid User page is Login Pass

displayed
5.1.1 Unit testing
Verification (A set of operations that the software correctly implemented a particular function) on the
smallest element of the program i.e. the modules are tested alone in order to discover any error in the
code. Every module of the System is separately tested i.e. we have tested every module by applying
some selection mechanism. Several errors were occurred during testing and we removed all the bugs
as per the specification of testing standards.
Expected Result Error Handling
Data Type Validation Accepts only valid data Displays the corresponding
message box
Password Checking Allows only authorized Display Password or user
person to login into the name error massage
system
No Inputs Allows the new application Displays an error message
to accept the needed data box
rather than null.
Date Allows the new system to
recognize the current date ------------
of the pc.
Table 24. Unit testing
5.2.2 System Testing
It is the final step of testing. In this the team members tests the entire system as a whole with all
forms, code, modules. This form of testing is popularly known as Black Box testing or System tests.
In this the team members tests all the functionalities in the System. All errors in the forms, functions,
modules are tested. The specification will be described according to the test types that will be done on
the system.
5.2.3 Integration testing
Integration testing is the activity of software testing in which individual software modules are
combined and tested as a group. A type of testing used to conform that all code modules function as
specified and whether the system as a whole performs perfectly on the plat form it will be deployed.
It occurs after unit testing and before acceptance testing. Thus, Integration testing is a logical
extension of unit testing. In its simplest form, two units that have already been tested are combined
into a component and the interface between them is tested. Here a component refers to an integrated
aggregate of more than one unit. In a realistic scenario, many units are combined into components,
which are in turn aggregated into even larger parts of the program. The idea is to test combinations of
pieces and eventually expand the process to test your modules with those of other groups.
Integration testing can be done in a variety of ways but the following are three common strategies:
 The top-down approach to integration testing requires the highest-level modules be test and
integrated first.
 The third approach, sometimes referred to as the umbrella approach, requires testing along
functional data and control-flow paths.
 The bottom-up approach requires the lowest-level units be tested and integrated first
5.2.4 Acceptance Testing
Acceptance testing is the process of testing system (e.g. software, lots of manufactured mechanical
parts, or batches of chemical products) prior to its delivery. A system is mainly developed for an end
user normally a customer of the organization. A system is said to be accepted if and only if the user of
the system is satisfied. In this perspective acceptance testing is widely used to prove that system
performs as per the requirements.
In acceptance testing the customers provides the input data to validate the system operation. It is also
known as functional testing, black-box testing, release acceptance, QA testing, application testing,
confidence testing, final testing, validation testing, or factory acceptance testing.
5.3 System Description and Process Flow
After the system is hosted on the server, it will have to enter to the system: this system is best system
which is used for the security of our customer information. All customer of this system must have
password to enter to the system that means user of this system is needs to enter password and
username that is for trader, manager and administrator of the system. To access those parts one has to
have password and user name so that he/she can enter into it and use it. This accessibility has also
two parts, one which is restricted for administrator and the other for the rest actor.
The trader of this system he wants to create his own account from the system. In order to this all
person who is authorized is possible to use this system. For the entire actor this system is using the
same step, those are:-
1. Enter the username

2. Enter password of this username
3. In the last click on LOGIN.
After login you have to process whatever you want with validation of same thing.
5.4. Training
Training is the process of teaching or learning a skill or job. Training is needed for two reasons:
 If users are not adequately trained they will not operate the system correctly or efficiently.
 If users fill that they are being asked to perform tasks that are outside their capabilities, they
may become demoralized and separated.
User training must be providing to user of the system in order to help them become equated with the
system. Users are vital part of any system. The introduction of new system must mean changes in
roles and relationship, if system being introduced is proposed by Trade and development Office. It is
less likely to be successful.
5.5. Installation
After installing the xampp server software do the following steps.
Step1
 Get the folder “addistrade “from the Developing Team.
Step 2
 Copy the folder in the C:\xampp\htdocs\addistrade
Step3
 Run XAMPP server and create a database with a name of license
Step4
 After doing these steps import the SQL file which named as license.sql
Step5
 Paste the folder into the folder ”trader “in the C:\wamp\www
Step6
 Installation of the system is finished
CHAPTER SIX
CONCLUSION AND RECOMMENDATIONS
6.1 Conclusion
The project is partitioned into six chapters and each chapter has a specific deliverable which is
essential and base for the next chapter.
Considering the drawbacks of the existing system and importance of new technologies the developed
system, the system includes functionalities of registering applicants for license, give the license for
those who fulfill the requirements, update license annually, and cancel license.
The system performs works better than existing system (usability, speed, efficiency and
effectiveness). Security also included in this system developed and authorized user can access the
required services. The system is also very useful in minimizing time and other utilities wastage.
This project document deals all about Trade License management system for Addis Ababa City Trade
and Industry Office.
Generally, project team would like to remark that the project has given us a great deal of experience
not only in the technical aspect but also in writing together as a team to accomplish a certain goal,
which is a much desired quality.
6.2 Recommendation
Nowadays, the world is highly becoming a competitive world. Organizations have to divert their
attention on using the recent technology to be on the first line and competitive. This can be real if
they are able to use information communication technology (ICT) to successfully achieve their
objective.
 Trading system has much functionality. But we are limited only to trade license giving,
renewal, and its legal cancelation. The annual tax payment system is not included because of
the authority to collect tax is not a power of our office. For that reason on the coming system
development should be done in the future.
 The trade controlling system is not included in the system should be done in the future.
 The Tin number is not included in this system should be done in the future
6.3 Future work
As a developer of this online trade system, we write the following to be done and executed in the
future
 Expand the system to support all organization of the trade and development market .
 When the addition of new feature is needed the trade administrator should invite those
persons having excellent programming knowledge described in the system development
tools.
 Use finger print password system for authentication mechanism.
 Expand the system to have direct contact between trader and trade administrator to talk
about the trader and other areas which is not covered.
6.4.References
 WWW.tutorialspoint.com
 STRUCTURED QUERY LANGUAGE (SQL) Practical introduction
AKEEL I DIN
Appendix
Interview questions
We interview the manager and employee of Addis Ababa City Trade and Industry office the
following questions
1. When the office was established?
2. How many Process owners the office has?
2.1. List the process owners:-
3. How many trade levels are they? Specify with their capital:-
4. What is the problem of current system?
5. If something is left from the above question specify it:-

Trade License First Draft

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Trade License First Draft

Uploaded by

Copyright:

Available Formats

FACULTY OF ENGINEERING AND TECHNOLOGY

DEPARTEMENT OF COMPUTER SCIENCE

DESIGNING AND IMPLIMENTATION OF ONLINE TRADE REGISTRATION AND

A PROJECT SUBMITTED TO DEPARTEMENT OF COMPUTER SCIENCE OF GAGE

1. Mekonnen Kebede Secll 2559

Advisor’s name Advisor’s signature

Examiner’s name Examiner’s signature

EXAMINORS AND ADVISORS FORM

HTTP……………………………………………………………Hyper Text Transfer Protocol

MYSQL…………………………………………………………MY Structural Query Language

PHP……………………………………………………………..Pre Hyper Processor

RAM…………………………………………………………….Random access Memory

SSL………………………………………………………………Server Socket Line

TCP………………………………………………………………Transfer Control Protocol

TIN………………………………………………………………Tax Identity Number

TLMS…………………………………………………………..Trade license management system

UML……………………………………………………………Unified Modeling Language

because, the project was done for academic purpose.

1.2. Background Information of the office and the system

1.2.2. Background of the System

1.3. Statement of Problem

Currently faced problems

 Trader waits much time to get services.

 Need of many employees.

 Time loss to give information about trade for each applicant.

 Accessing information is difficult.

1.4.2. Specific objectives

 Understand the current systems and its efficiency.

1.5 Scope and Limitation of the project

An applicant to be a trader performs the registration process through online application by

 An applicant should have renewed Kebele identification card.

 He/she must have a bank account.

 Pay for the Service.

1.6. Risk, Constraints and Assumption

Power failure and data loss

 The system must have an interface which is simple enough to understand.

 The code should be free from errors.

1.7. Significance of the Project

 Each task is performed easily

 Can perform many tasks in short period of time

 Change the manual system of the organization to computerized system

 Reduce unnecessary resource wastage.

 Reduce employee overload work.

 System gives fast service to the customer

 Information accessing is easy and fast.

 To be competitive, profitable, and manage all traders’ affairs easily.

1.9. Team composition, budget and schedule

 Mixed control team organization.

 We believe this method is strongly important to work our project.

 In general, we believe that this method makes us to communicate each other

Figure 1: Team Composition.

Hardware Requirements cost

1 Dell laptop computer 1 15000.00 15000.00

2 Pen 5 5.00 25.00

4 Print 100 pages 1.00 100.00

5 Flash Disk 1(8G) 120.00 120.00

6 CD-RW 2 25.00 50.00

Table 1. Hardware Requirement Cost

Software Requirements Cost

No Materials Required Price Per Unit

Object March April 15

6 Documen May May 16

SYSTEM REQUIREMENTS SPECIFICATION (SRS)

1. Existing System Description