Final Project Web Based Ethiopian Postal Service

Mizan-Tepi University
School of computing and informatics
Department of Information systems
Industrial project on Web Based Ethiopian Postal Service Management System
Submitted to the department of Information Systems in partial fulfillment of the

requirements for the Degree of Bachelor of Science in Information Systems
By Group 10:
NAME ID
Nuraddis Jemal SCIR/273/10
Henok Getachew SCIR/195/10
Korma Nure SCIR/211/10
Mulualem Yohannis SCIR/254/10
Abraham Tamirat SCIR/020/10
Zewditu Ebabu SCIR/367/10
Advisor (s) Tepi, Ethiopia Month, Yea
Advisors: Mr.Tibebu & Ms.Alemitu
Tepi, Ethiopia 25th Aug 2021 GC

It is approved that this project has been written in compliance with the formatting rules laid down
by the faculty.
Name and signature of Members of the Examining Board
Name Signature Date
1. ______________________ __________ __________

2. ______________________ __________ __________
3. ______________________ __________ __________
4. ______________________ __________ __________
5. ______________________ __________ __________
6. ______________________ __________ __________
7. ______________________ __________ __________
Chairman
Name Signature Date
__________________________ __________ __________
i|Page
To: Department of Information Systems
Subject: Industrial Project Submission
This is to certify that the industrial project entitled as “Web Based Ethiopian Postal Service
Management System” submitted in partial fulfillment of the requirements for the degree of
Bachelor of Science in Information systems has been carried out by the group members under my
supervision. Therefore, I recommend that the students has fulfilled the requirement and hence
hereby they can submit the project to the department.
Name of advisor Signature Date
______________ ___________ __________
ii | P a g e
Anti-Plagiarism Declaration
This is to declare that this final project which was developed under the supervision of Mr.Tibebu
and Ms. Alemitu having title “Web Based Ethiopian Postal Service Management System” is the
only contribution of the authors and no part here has been reproduce illegally (cut and paste) which
can be considered as plagiarism .We will be responsible and liable for any consequence if violate
on of this declaration is proven.
GROUP MEMBERS SIGNATURE DATE
1) NURADDIS JEMAL ____________ ____________

2) HENOK GETACHEW ____________ ____________
3) MULUALEM YOHANNI ____________ ____________
4) KORMA NURE ____________ ____________
5) ABRAHAM TAMIRATN ____________ ____________
6) ZEWDITU EBABU ____________ ____________
iii | P a g e
ACKNOWLEDGMENT
First of all, thanks to God for the completion of this project and for our group members that have
been actively participating without any tired.
Secondly, we would like to say thank you our adviser Mr.Tibebu for his nice contribution in our
project by giving constructive comment and advice. We also say thank you to our co-adviser Ms.
Alemitu she played her role in helping us in our project by commenting and giving us advices. We
would like to give thanks to our department head Ms. Marta for her great contribution to give us
computer laboratory as well as Internet service.
The success and final outcome of this project required a lot of guidance and assistance from many
people specially teachers who provide us with information on the current problem of examination
system. All that we have done is only due to such supervision and assistance and we would not
forget to thank them.
iv | P a g e
Contents
ACKNOWLEDGMENT ........................................................................................................................ iv
CHAPTER ONE ..................................................................................................................................... 1
1. INTRODUCTION ........................................................................................................................... 1
1.1 Background of the organization ..................................................................................................... 1
1.2 Background of the project .............................................................................................................. 2
1.3 Motivation ..................................................................................................................................... 3
1.4 Statement of the problem ............................................................................................................... 3
1.5 Proposed System............................................................................................................................ 4
1.6 Objective of the project .................................................................................................................. 4
1.6.1 General objective .................................................................................................................... 4
1.6.2 Specific objective .................................................................................................................... 5
1.7 Scope and limitation of the project ................................................................................................. 5
1.7.1 Scope ...................................................................................................................................... 5
The scope of the project implemented in Ethiopia, for all branches of Ethiopian post office and it
does not cover all activities performed by the post office and also not include foreign countries. ...... 5
1.7.2 Limitation ............................................................................................................................... 5
1.8 Methodology and tools................................................................................................................... 6
1.8.1 Methodologies ........................................................................................................................ 6
1.8.1.1 Data gathering methodologies .............................................................................................. 6
1.8.1.2 Design methodology............................................................................................................. 7
1.8.1.3 Implementation Methodology ............................................................................................... 8
1.8.1.4 Testing methodology ............................................................................................................ 9
1.8.2 Tools....................................................................................................................................... 9
1.8.2.1 Hardware Tools .................................................................................................................. 10
1.8.2.2 Software Tools ................................................................................................................... 10
1.9 Feasibility analysis....................................................................................................................... 11
v|Page
1.9.1 Economic feasibility.............................................................................................................. 11
1.9.2 Technical feasibility .............................................................................................................. 11
1.9.3 Operational feasibility ........................................................................................................... 11
Schedule feasibility........................................................................................................................ 12
1.10 Benefits and Beneficiaries of the project .................................................................................... 12
1.11 Risk and constraints ................................................................................................................... 13
CHAPTER TWO................................................................................................................................... 15
2. OVERVIEW OF EXISTING SYSTE............................................................................................. 15
2.1 Introduction ........................................................................................................................... 15
2.2 Literature Study ..................................................................................................................... 15
2.3 Weakness and strength of the existing system ......................................................................... 17
2.3.1 Weakness of the existing system ..................................................................................... 17
2.3.2 Strength of the existing system ....................................................................................... 17
2.4 Business rules ........................................................................................................................ 17
CHAPTER THREE ............................................................................................................................... 19
3 REQUIREMENT ANALYSIS ....................................................................................................... 19
3.1 Introduction ........................................................................................................................... 19
3.2 System Requirement Specification ......................................................................................... 19
3.3 Functional requirements ......................................................................................................... 19
3.3.1 Actors Specification ....................................................................................................... 20
3.3.2 System Use-case Identification ....................................................................................... 20
3.3.3 Use Case Description and Scenario ................................................................................. 22
1.3.4 Use case diagrams .......................................................................................................... 29
1.4 Non Functional requirements.................................................................................................. 31
1.5 Dynamic Modeling................................................................................................................. 31
1.5.1 Sequence Diagram.......................................................................................................... 31
1.5.2 Activity Diagrams .......................................................................................................... 35
vi | P a g e
CHAPTER FOUR ................................................................................................................................. 38
4 SYSTEM DESIGN ........................................................................................................................ 38
4.1 Design goals ................................................................................................................................ 38
4.2 Proposed System Architecture...................................................................................................... 39
4.2.1 Proposed software architecture .............................................................................................. 40
4.2.2 Subsystem Decomposition..................................................................................................... 41
4.1 Hardware/Software Mapping.................................................................................................. 42
4.2 Persistent Mapping................................................................................................................. 43
4.3 Class/Package Diagram .......................................................................................................... 44
4.4 State Modeling ....................................................................................................................... 45
4.5 Component Modeling............................................................................................................. 50
4.6 Deployment Modelling........................................................................................................... 51
CHAPTER FIVE ................................................................................................................................... 52
5 IMPLEMENTATION......................................................................................................................... 52
5.1 Introduction ................................................................................................................................. 52
5.2 Environmental Setup.................................................................................................................... 52
5.3 Algorithm Design and Coding...................................................................................................... 53
5.3.1 Algorithm ............................................................................................................................. 53
5.3.2 Sample code.......................................................................................................................... 54
5.4 User Interface(GUI)design ....................................................................................................... 63
CHAPTER SIX ..................................................................................................................................... 67
6 Conclusion and Recommendation ....................................................................................................... 67
6.1 Conclusion................................................................................................................................... 67
6.2 Recommendation ......................................................................................................................... 68
Reference .............................................................................................................................................. 69
vii | P a g e
List of Tables
Table 1 :- project schedule ..................................................................................................................... 12
Table 2: Risk and constraints ................................................................................................................. 13
Table 3. The scenario or use case description of the Login use case ....................................................... 22
Table 4. The scenario or use case description of the user registration use case ........................................ 23
Table 5. The scenario or use case description of the rent post box use case ............................................. 24
Table 6. The scenario or use case description of the sent airmails registration use case. .......................... 24
Table 8. The scenario or use case description of the Check_Track use case ........................................... 25
Table 9. Use case description for Create account.................................................................................... 26
Table 10. Use case description for deliver airmail .................................................................................. 27
Table 11. Use case description for deliver material ................................................................................ 28
Table 12. Use case description for Logout ............................................................................................. 29
viii | P a g e
List of Figures
Figure 1: waterfall model......................................................................................................................... 8
Figure 2 Use Case Diagram ................................................................................................................... 30
Figure 3 sequence diagram for login to the system ................................................................................. 32
Figure 4 sequence diagram for user registration ................................................................................... 33
Figure 5 sequence diagram for renting post box ..................................................................................... 33
Figure 6 Sequence diagram for sent airmail registration ......................................................................... 34
Figure 7 Sequence diagram for logout.................................................................................................... 34
Figure 8 Activity diagram for administrator ........................................................................................... 35
Figure 9 Activity diagram for Counter ................................................................................................... 36
Figure 10 Activity diagram for Post Man ............................................................................................... 36
Figure 11 Activity diagram for Post Man ............................................................................................... 37
Figure 12 Proposed system architecture ................................................................................................ 40
Figure 13 Proposed software architecture............................................................................................... 41
Figure 14 Subsystem decomposition diagram ........................................................................................ 42
Figure 15 Diagram for persistence mapping ........................................................................................... 44
Figure 16 Class diagram of the system ................................................................................................... 45
Figure 17 State diagram for user login ................................................................................................... 46
Figure 18 State diagram for create user account ..................................................................................... 47
Figure 19 State diagram for tracking material ........................................................................................ 47
Figure 20 State diagram for give feedback ............................................................................................. 48
Figure 21 State diagram for sending material ......................................................................................... 49
Figure 22 Component diagram............................................................................................................... 50
Figure 23 Deployment diagram.............................................................................................................. 51
Figure 24 Ethiopian postal services Home Page ..................................................................................... 63
Figure 25 Ethiopian postal services Admin Page .................................................................................... 64
Figure 26 Ethiopian postal services Postman Page ................................................................................. 65
Figure 27 Ethiopian postal services Counter Page .................................................................................. 66
ix | P a g e
List of Acronyms
BPR Business Process Reengineering
OPOMS Online Post Office Management System
EMS Express Mail Service
UPU Universal Postal Union
RAD Requirement Analysis Documentation
HTTP Hyper Text Transfer Protocol
TPO Tepi Post Office
UI User Interface
UML Unified Modeling Language
GUI Graphical User Interface
DBMS Data Base Management System
DV Diversity Visa
RAM Random Access Memory
PHP PHP Hypertext Preprocessor
MYSQL My Structure Query Language
MTU Mizan Tepi University
CSS cascading style sheet
HTML Hypertext Markup Language
ID Identification
x|Page
CHAPTER ONE
1. INTRODUCTION
1.1 Background of the organization
The origin of postal service dates back to the middle Ages and was developed from the medieval
system of royal messengers whom employed to carry government documents from one place to
another. In most countries, the postal service developed in the 18th century when different means
of transport such as mules, horses, camels and stage-caches were used to carry mail. In some
Middle-Eastern countries even falcons were specially trained to carry written messages from one
place to another. The first railway mails were carried in Europe in 1830. The establishment of the
Universal Postal Union (UPU) in 1875 is what greatly promoted international mail services.
Prior to the establishment of the postal service in Ethiopia on March 9, 1894 following an imperial
edict, correspondence was conducted through messengers known as ‘melektegnas or postegnas’.
These tough individuals travelled great distances, often on foot, overcoming rough landscape and
weathering hostile climate. They endured the pangs of hunger and thirst and carried their letters
over their heads, on cleft sticks (which later became the symbol of the post office still today) until
they reached their destination. Ethiopian Postal Service was established nearly two decades after
the birth of UPU. The second half of the 19th century in Ethiopia was characterized by the
establishment and consolidation of the empire state under the protection of Emperor Menelik.
Menelik found in the postal service, like the telephone and the telegraph, a vital means of
exchanging information, first for political and administrative purposes and later on for public
correspondence.
The construction of the Djibouti - Addis Ababa train made it possible for letters, parcels and
merchandise, which were previously transported on camel back. This was a crucial factor that
greatly improved the pace and efficiency of the postal service while it laid the basis for the
international exchange of mail. Then Ethiopia became a member of the Universal Postal Union in
1908.
With an area of 1.1 million sq.km and a population of 95 million, Ethiopia has at present over
1,200 post offices. Out of this 1016 Permanent post offices, and over 170,000 post boxes. It is
1|Page
estimated that one post office is serving 79,116 inhabitants while one private box serves 558
people.
In the result of opportunities and challenges, Ethiopian postal service establishes EMS (express
mail service) in 1989. The introduction of EMS has made the Ethiopian Postal Service competitive
in the express delivery market. Today Ethiopian postal service is under the implementation of
business process reengineering (BPR), which had been study for 18 months. Due to this the
structure become process and customer oriented. The managers and the employees are doing their
best to accomplish the needs of their customers.
1.2 Background of the project
The impact of technology in modern life is immeasurable, we use technology in different ways
and sometimes the way we implement various technologies ends up changing our lives or the
society we leave in. Technology is applied to the roles each individual fulfills during life. We use
technology on a daily basis to accomplish specific tasks or interests. It means the source of the
radical changes that are happening in all phases of life.
So our System is plays its Owen role to implement and provide technological system to the society
by developing automated Postal. As we know; now a day everything is done with the help of
computer so as to achieve the Samara Postal Office Mission and vision our system plays its Owen
roll.
Our automated Online Ethiopian Postal office system used to improve the organizations drawback
and to support automated system and also to simplify employees work load, to speed up or to do
the organizations service in short time and to achieve the customers went. So the aim of our
proposed system is mainly to avoid the drawback of the current existing system and adding some
new features that do not exist before and also changes the activity of the organization to
computerized or automated System and reduce the extravagancy of resource.
2|Page
1.3 Motivation
The main morally idea to develop the system that Ethiopian postal service Management System is
as the whole processes of the world activity is based on the electronics part to reduce the time,
cost, human labor we take part in developing this system in our country. When develop this system
we forced to exist special use of service for postal service in our country based on technological
perspectives. And hence, developing the system using technology has a tremendous effect for
organizations and offices; which is in our case our country currently, the system is manual based;
due to this customers and employees have so worked ineffective manner. Because of this some
problems, we are initiated to develop our system Web based Ethiopian postal service Management
System in order to minimize the problem by using computerized system.
1.4 Statement of the problem
In fact, postal service is one of the most crucial as well as backbone of the people by giving postal
related services as well as any other services which can be transfer through postal system. Our
project team considers Online Ethiopian Postal Service Management System, still the system
generally does follow or perform the manual system or paper based system and somewhat
automated to provide service to its customers. So that using manual system has a lot of problems
in many cases.
Moreover, the following are problems that are present in the current system of postal service
system in general. Because of this reason the organization faced to many problems. The problems
are:-
 Work load of the Employers.
 It needs much time due to record, to search ones specific customer file if it is necessary.
 Wastage of resources.
 Loss of data, poor organized and unsecured data.
 Instability of the country.
 Lack of different transport bus.
3|Page
 Time limitation in which the system doesn’t keep track of sending and receiving different
materials deliver in the customers’ expected time and date. Example, postponing customer
expected time.
 N.B: The problems that raised in the above limit the organization not to give reliable and
fast service to its customers.
1.5 Proposed System
Since our project is Web Based Ethiopian Postal service and it is the most crucial service for the
people, it has a basic purpose that communicating the customers throughout the world giving
service by considering the following things.
 Through real and customers expected time.

 Using less amount of resource.
 Using less amount of human power.
 Through customers information based.
 By using fast and efficient technology.
 By providing how customers check their materials or any messages they have sent and they
do a truck where it reaches.
 By communicating customers with the organizations' employee through online.
 And all branch organizations are communicating each other through online network.
Online Ethiopian Postal office system used to improve the organizations drawback and to support
automated system and also to simplify employees work load, to speed up or to do the organizations
service in short time and to achieve the customers went. So the aim of our proposed system is
mainly to avoid the drawback of the current existing system and adding some new features that do
not exist before and also changes the activity of the organization to computerized or automated
System and reduce the extravagancy of resource.
1.6 Objective of the project
1.6.1 General objective

The general objectives of this project is to develop and implement Online postal service for
Ethiopia .That is to develop and provide a full internet application or web based application, then
4|Page
can be accessed by any customers throughout the world as well as branch organizations are
communicate each other through online network application. It helps customers to use their time
and other resources effectively and efficiently whenever they use postal service. It also viewed as
how to create a system as problem solver to the customers and employers of the organizations.
1.6.2 Specific objective

To achieve or accomplish the general objectives of our proposed system, the following specific
objectives are set.
 Collect the necessary information or data and identify problems of the existing system by using
different data gathering methodology
 Analyze the system requirements by using analyzing methodology
 Design the artifacts of the proposed system for the overall view of the structure.
 Implementing the proposed system.
 Testing the system by using different tasting methodology
 Finally Deploy the proposed system
 Reduce workload of employees and provide simple and efficient service for customers
1.7 Scope and limitation of the project
1.7.1 Scope
The scope of the project implemented in Ethiopia, for all branches of Ethiopian post office and it
does not cover all activities performed by the post office and also not include foreign countries.
1.7.2 Limitation
There are many factors that limited us to minimize our scope, such as time limitation, resource,
place, and complexity of the system. In general our proposed system will not include:-
 performing the tasks of Western Union Services,

 Forming DV Lottery,
 Distributing SIM Cards and Mobile Card.
 Income tax Collection
 Not supports international postal system. Mostly SPO provides a service in a commission
or Agency works such as blood trace,
5|Page
 Selling different organization products are out of scope of this project.
1.8 Methodology and tools
1.8.1 Methodologies
Methodology is a method or approach or a technique that we are uses to develop this system and
it describes how the work to be done to achieve the objectives using system requirements. To
develop this system we use data gathering, development, testing and other methodology’s used.
1.8.1.1 Data gathering methodologies

Gathering Requirements from existing system is important tasks to develop the System. To fulfill this
requirement our project development team may obtains from:
 Primary
 Secondary source.
Primary Source
This is a data that we collected the original data by different techniques from different source.
The techniques are we used to collect this data:
Observation: This technique is used to gather accurate information about how the system actually
operates, particularly about the processes. Observing how the tasks are actually is the good way of
understanding the existing system. By observing the current working environment of OPSMS our
team collects data which necessary for automating of postal service system. Our team tried to
observe things mentioned below
 The general system of providing service in the current system

 How the system handles and store material’s information
 Types of document format is there printed or non-printed
Interview: The reason why the team select interview is: it permits clarification of questions, it has
high response rate than written questionnaires, and the interview is flexible and adaptable way of
finding information. So to know how the postal service system is work prepare questions
concerning on postal service and interview the counter TOPOMS. The counter is person who
performs managing the all transactions inside the post office, as well as the manager is a person
6|Page
who controls and manages the overall system. He also called postmaster. So from the manager will
gain the overall description of the system.
Secondary Source
Our team collect this type of data is by reading different references books and by analysis of
different internet address.
Document Analysis: In order to gate more detailed and reliable information about services
provided by the post office and to understand the way those services are delivered to customers
our team analyzes the Ethiopian Postal Service Enterprise Service Charter book which is prepared
by Ethiopian Post Office.
1.8.1.2 Design methodology

Among the available different methodologies our team plan to use the object oriented analysis,
object oriented design and object oriented implementation methodology for the development of
our system. Because it is best way to construct, manage and assemble objects that are implemented
in our system, and the composition of objects and collaboration between objects on the system.
The team prefers to use object oriented system analysis because of the system is a collection of
integrated data and method is called object so this model focuses on the object, provides less
transition among different phases of software development, after implementing the system is easy
to maintain and modify and also this model promotes reusability to improve consistency, reduce
time and cost for system development, easy to maintain or modify and increase reliability.
For developing our system, we will use Waterfall model linear framework type.Waterfall model
is a sequence development process where development flows steadily downwards through the
various phases of analysis, design, implementation, testing, integration and maintenance.
7|Page
Figure 1: waterfall model
We preferred waterfall model approach for the following advantages:
 Progress of system development is measurable.
 Simple and easy to understand in use.
 Easy to manage due to rigidity of the model. Each phase has specific deliverables and a
review process.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.
 The orderly sequence of development steps and strict controls for ensuring the adequacy
of documentation.
1.8.1.3 Implementation Methodology

Implementation is a realization of a technical specification or algorithm as a program, software
component through programming. there are different types of tools available to implement the
system from those tools we select php to develop front end of the system, Xampp2.5 server to
develop back end of the system ,UML editor to sketch different UML diagrams and Microsoft
word 2010 to prepare the documentation part of the project .
8|Page
1.8.1.4 Testing methodology
Testing methodologies are approaches to testing, from unit testing through system testing and
beyond. There is no formally recognized body of testing methodologies, and very rarely will you
ever find a unified set of definitions. But here are some common methodologies:
Unit testing: The act of testing software at the most basic (object) level. Generally performed by
developers, run in "friend classes" with code-level access to read and manipulate objects.
Acceptance testing: Also known as acceptance tests, build verification tests, basic verification
tests, these are rudimentary tests which prove whether or not a given build is worth deeper testing.
The term "smoke test" is a colloquial term -- when machines are built, engineers will power them
up and just let them run, looking for smoke as a sign of serious problems.
Functional testing: Functional testing takes a user story or a product feature and tests all of the
functionality contained within that feature. For example, in a photo application like Photoshop,
functional testing would cover all the functionality contained within a feature like opening files
(resolving file paths, determining appropriate format filters, passing the file path off to the filter)
as well as handling errors within that functionality.
System testing: Testing the project as a collective system. System testing generally combines
multiple features into an end-to-end process or scenario.
Performance testing: Tests an application's performance characteristics, be it file size, concurrent

users, or mean-time-to-failure.
Security testing: A collection of tests focused on probing an application's security, or its ability to
protect user assets.
1.8.2 Tools
Implementation is a realization of a technical specification or algorithm as a program, software
component through programming.
9|Page
1.8.2.1 Hardware Tools
Hard ware tools are primary requirement to develop the new system. Although the team of the
project takes different kinds of hard ware tools, to develop this project we take the following HW
tools requirements:
Processer: this is the basic hard ware component to develop our system so in the client side we
needs 3.30MHZ and in the server side also 6MHZ is needs.
RAM Size: also another type of hard ware component to develop our system and it is a storage
device and we need 4GB and 8GB in client and server side respectively.
Internal Hard Disc Space: this is another type of hard ware component to develop our system so
in the client side we need 500GB and in the server side also 1TB is needs.
1.8.2.2 Software Tools

The different kind of software we used for developing the project is:-
 Xampp Server 2.5(MYSQL) or xampp-win32-1.7.3: to develop database application

 PHP, HTML, Java Script –Programming Languages,
 Microsoft office word 2016 for documentation.
 Windows 10 Operating system- will be used for the system since it is readily available in
our laboratories
 Microsoft Visio 2016- to design Sequence Diagram, Class Diagram, and Use case
Diagram.
 Browsers-since our system is web based, it is very necessary requirement.
 Sublime text 3-for writing the code
10 | P a g e
1.9 Feasibility analysis
1.9.1 Economic feasibility

Our system is economically feasible, because it reduces the time needed to perform certain a ctions
such as customer registration, generate report, paper and pen, which they are using for manual
work. The system that we are going to develop will have economic benefit. That economic benefit
may be tangible or intangible.
o Tangible benefit: This means the concrete benefit that can be expressed in terms of
dollars or birr. Therefore, the proposed system will decrease many birr that was
expensive to buy the hard copy document material such as paper, pencil, rubber, and
so on. Also, reduce the loss of data that means if it reduces the loss of data, it also
reduces the cost of replacing the lost data.
 The system requires very less human power.
 The system will provide fast and efficient automated environment.
 The system will have GUI and very less user-training is required to learn it.
o Intangible benefit: Those benefits cannot express in terms of birr or dollar. Intangible
benefit that the system will give is the following:
 Give more readable
 Reliable and
 Manage easily.
1.9.2 Technical feasibility

The system will be develop by using technologically system development techniques such as PHP,
Java Script, CSS and MySQL database without any problems and the group members have enough
capability to develop the project. When we evaluate the hardware’s and software’s requirement
and how they meet the need of the proposed system, our proposed system is technically feasible
because we are using currently available and affordable technologies to develop the proposed
system.
1.9.3 Operational feasibility

Operational feasibility is a measure of how well a proposed system solves the problems, and takes
advantage of the opportunities identified during scope definition and how it satisfies the
11 | P a g e
requirements identified in the requirements analysis phase of system development. It shows the
success and achievement of the objectives of the proposed system to the organization. The
proposed system will minimize the time and the workers required to give service for the customer.
Schedule feasibility
The proposed system i.e. web based Ethiopian postal service will be developed totally and begin
to give services according to the time given. Therefore, it is feasible in schedule.
Table 1 :- project schedule

Activity April April April May June
20/2021 21/2021- 26/2021- 01/2021- 01/2021-
25/2021 27/2021 30/2021 14/2021
Title
Submitted
Requirement
gathering
Prepare
Proposal
System analysis
System design
1.10 Benefits and Beneficiaries of the project
Since our project is the Postal service and it is the most crucial service for the people, it has a basic
purpose that communicating the customers throughout the world giving service by considering
using fast, efficient technology to improve the above mentioned problem, Through real and
customers expected time, Using fewer amounts of resource and human power, providing how
customers check their materials or any messages they have sent and they do a truck where it
reaches, and communicating all branch organizations each other, customers with the organizations'
employee through online.
12 | P a g e
From our proposed system three main bodies Employees they are working in the organization,
Customers they are sends and receives messages and also the organization are benefited but we
are also benefited from this project because as a developer we increases our knowledge. Those
body are benefit like register or record, search, add, remove customers information and prepare or
provide report on a prepared form simply in less time, see and manage customers information and
minimize employees work overload, able to reach messages to destination in expected time,
1.11 Risk and constraints
Table 2: Risk and constraints

Project Risks:
Risk Probability Effects Risk planning strategy
The experience staff in the Low Serious Use more than one staff for each
team leave the project before it section, which might minimize this
is finish, or someone was ill risk. Also, manager tries to increase
salary for him.
The methodology to solve the High Serious Must be study more than one
problem can't work in a proper methodology to minimize this risk.
manner.
Budget does not enough or Low catastrophic Put a condition in the contract if there
there is no budget. any more expenses, the funded side
must be pay it. To avoid this risk.
HW requirement can't come in moderate Serious See if there is any more time to delay
the time. the project or not. If there is no more
time work by the team computers, to
minimize this risk.
Product Risks:
13 | P a g e
Packages and Development High Serious Put a condition in the contract to

tools does not enough. increase the time of project delivery
depends on the problem occur.
Business Risks:
Can't found the suitable place moderate tolerable Monitoring the work by E-mail every
for meeting the team. day. To avoid this risk.
Damage the electricity high serious There is a spare generator to avoid this
generator. risk.
Marketing the product system. low catastrophic Distribution of advertisements, which
minimize this risk.
14 | P a g e
CHAPTER TWO
2. OVERVIEW OF EXISTING SYSTEM

2.1Introduction
The role of postal administration in providing the excellence services and enjoying the trust and
loyalty in customers by diversifying themselves through innovative products and services and the
changing role of post offices by entering new areas such as telephony and financial services.
Several innovative products are implemented for letters and delivery of parcels. It’s a critically
window for the rural people to avail sophisticated products and financial products. Its core
competencies are its credibility, brand strength and outreach to millions of people.
Generally postal services are related to delivery of parcels, letters, documents and packages. Also
postal transportation process consists following activities, (collection, input sorting, transportation,
output sorting & distribution). Postal industry used of physical communication in the past or
transportation process. Postal services face many challenges in the past decade, specifically:
Customer satisfaction is a business term, which identify that the product or service which supplied
to customers how much satisfying them. Different authors use different criteria, elements,
characteristics when discussing about customer satisfaction. Moreover customer satisfaction is an
important factor in future tendency to make a purchase, also sometimes satisfied customers talks
probably enthusiastically about their positive experience, or their buying, or use of a particular
service with other people. High quality product or service ensure customer satisfaction,
furthermore customer’s feelings and beliefs affect their satisfaction level.
2.2Literature Study
Currently the Postal Service System mostly follows manual based system and somewhat
automated to provide service to its customers. The services provided by the system are mainly
categorized in to two which are direct and commission. The direct one is the service which provide
by SPO sending and receiving different type of Airmail and the commission services are provided
by the SPO for other governmental or non-governmental organizations for collective benefits. The
services provided by the system are sending and receiving airmail, renting post box, giving
15 | P a g e
western union service, forming of Dv lottery, selling SIM, CDMA/WCDMA, mobile cards,
income tax collection, blood tramp and tale agency license tax collection.
Sending airmail
On the process of sending airmail if a customer want to send an airmail, first she/he contact the
counter, then he/she must select the types of airmail, the counter receives the airmail to check
whether the address of both sender and receiver are valid or not. Second, the counter measures the
weight of the airmail, attach postage stamp and record the information available on airmail (date
of sending, registration no, sender address, receiver address, weight, barcode number (for EMS air
mail), cost and price) in three copies on the form. Finally the customer pays the price and receives
the receipt. Then the counter starts to collect daily received airmails and group together according
to their destination, then packed and gives to the messenger/postman. The messenger/postman
takes the packed airmails to the bus station and distribute to different expected sites of the
customers.
Receiving airmail
Every day the messenger/postman brings the packed airmails from the bus station and gives to the
counter. The counter registers all received airmails. Then, if the airmail is ordinary or first order
airmail the counter distribute it to the post box of a customer. But type of airmail is either registered
or parcel, the counter distribute registered letter 1 st advice form (if the customer received a single
airmail) or collective 1st advice form (if the customer has more than one received letter). For EMS
the messenger/postman directly contact the customer and gives the airmail.
Renting post box
The customer fills contract renting post box form and pay 48 birr for a single post box and 20 birr
for key. Then the counter records the information of the customer.
Giving western union money transfer service
The counter receive a Fax message about the receiver information, sender address ,amount of
money and date of sending .Then ,by recording the above information she/he pay the money sent
to the receiver.
16 | P a g e
Forming of DV lottery
The customers who want to apply DV lottery of a year through postal system fill the form by
fulfilling all requirements. The counter collects and registers all DV lottery forms.
Selling SIM, CDMA/WCDMA, mobile cards
The counter sells SIM card to different customers by registering their personal information such
as name, id. Number, address, phone number, PIN code and PUK code of the sold SIM card.
2.3Weakness and strength of the existing system
2.3.1 Weakness of the existing system

The current system has weakness of use more human power since the system is not some more
computerized it use more human power to give service, there is duplication of data because of the
data are not well organized and structured, there is also disorder of data because the data are not
stored sequentially and the user information is may be accessed by unauthorized person because
of the information is stored manually there is the disadvantage for employees it is difficult to
perform any activity that performed in this organization so high work bourdons for employees.
2.3.2 Strength of the existing system

The current system has strength to develop the new system it is used as a secondary source
to gather system requirements, the employee working overtime, punctual to the society, honesty
to the users, responsible and transparent for their action and also used for the following action.
 The employees have their own privilege (freedom).

 A Distribution of work for the employee.
2.4Business rules
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 business rule is a principle or a policy in
which the proposed system operates accordingly. It deals with access control issues. It often
pertains to access control issues, operating policies and principles of the organization. The
organization has the following principles in the existing system which includes:
17 | P a g e
 The organization does not functional on Sunday.
 It does not reach books to customers to their address.
 The organization prepares reports to the higher officials monthly.
 The organization is functional only restricted time (from 2:00-6:00 morning and from 8:30-11:00
afternoon).
 The organization does not functional on holiday. Our proposed system includes the following
operating principles or rules:
o Business Rule1: the customer uses the application properly.
o Business Rule2: the customer fills the form properly.
o Business Rule3: the system gives fast responses to the customer.
o Business rule4: the system helps to arrive the books to the customer place.
o Business rule5: it provides more options to customers.
18 | P a g e
CHAPTER THREE
3 REQUIREMENT ANALYSIS
3.1Introduction
System Requirements Analysis gives the professional systems engineer the tools to set up a proper
and effective analysis of the resources, schedules and parts needed to successfully undertake and
complete any large, complex project. Requirement specification can be viewed in terms of
functional and non-functional requirements.
3.2System Requirement Specification
The system model of Ethiopian postal service system is composed of the functional model
represented by Use cases, the dynamic model represented by the sequence diagram and object
model represented by class diagram.
3.3Functional requirements
Functional requirements describe the interactions between the system and its Environment
independent of its implementation. The environment includes the user and any other external
system with which the system interacts. The system should provide how the system should react
to particular inputs and how the systems behave in particular situations. The following are the
functional requirements of the system:-
 User management.
 The system verifies user account to login in to the system by checking their information.
 The system handles user information.
 The system enables Users/Customers to change their password.
 Mail management.
 The system registers different types of airmails and materials information.
19 | P a g e
 The system provides data manipulation service such as insertion, updating and deletion.
 The system enables users to search data.
 The system should enable Users/Customers to change their password.
 Customers can write comments, suggestions, questions, and thanks on the online service of the
system.
 Box rent management
 The system enables user to rent boxes.
 The system enables user to return boxes.
 Tracking: the system enables users to track their mails.
3.3.1 Actors Specification

Administrator: is a person who registers user, update and delete information about the user.
Counter: is a person who register, update and delete sent and received airmails and rent post box
information.
Postman: is a person who sends and receives airmails as well as materials to and from customers
respectively. Also who can register, update, search and delete materials in the system.
Customers: are people or any users who can send and receive whatever their materials using the
Ethiopian postal service system throughout the world.
3.3.2 System Use-case Identification

Use-case model consists of the collection of all actors and all use case, a use case is a scenario that
describes the use of the system by an actor to accomplish a specific goals, an actor is a user playing
a role with respect to the system. Scenario is a sequence of step that describes the interaction
between an actor and the system.
 Use cases
 Login
20 | P a g e
 Register user
 Register rent post box
 Register material
 Register sent airmail
 Register received airmail
 Search user
 Update user
 Delete user
 Search airmail
 Update airmail
 Delete airmail
 Search material
 Update material
 Delete material
 Search post box
 Update post box
 Delete post box
 Check track
 Create account
 Generate report
 Deliver Airmail
21 | P a g e
 Deliver Material
 Assign Sent Mail Cost
 View feedback
 Manage rent post box
 Logout
 Actors
 Administrator
 Counter
 Postman
 Customers
3.3.3 Use Case Description and Scenario

Table 3. The scenario or use case description of the Login use case
UC Name Login
UC Description Enables all users of the system to login.

Actor Administrator, Counter, Postman
Precondition The users should have an account.
Flow of event 1. The user activates the system.
2. The system display login window
3. The user type user name and password and click login
button.
4. The system checks and validates the entered user id and
password. [A1:A2].
5. The system displays the main window.
6. The system displays access page for the respective user.
UC-01
7. Use case ends.
22 | P a g e
Post condition The user entered to the system and can access the system.
Alternative course A1: Information Not Fulfilled
of action 1. The system displays “Please enter your user name and
password!” message.
2. The system resumes at step 3.
A2: Invalid Entry Message
1. The system displays “Incorrect User Name or Password!”
massage.
Table 4. The scenario or use case description of the user registration use case
UC Name User registration
UC Description Allows administrator to register user information.
Actor Administrator
Precondition The administrator should successfully login into the
system.
Flow of event 1. The administrator selects the “Add user” menu.
2. The system displays the user registration form.
3. The administrator fills the form and submits it by
clicking “Add” button
4. The system checks and validates the entered data.
[A1].
5. The system display “user is registered successfully ”
message
6. The system saves the registered user account of the
Users.
7. Use case ends.
Post condition The account of the users registered (created).
Alternative course A1: Missing of Required Information Message
UC-02
of action
23 | P a g e
1. The system displays “Fill all information!”
massage.
Table 5. The scenario or use case description of the rent post box use case
UC Name Renting post box
UC Description Allows rent post box..

Actor Counter
Precondition The counter should have logged into the system
Flow of event 1. The counter selects “Rent post box’ menu.
2. The counter completes and submits the rent post box
form by clicking “Rent” button.
3. The system checks and validates the entered
data.[A1:A2]
4. The system display “Renting is successfully completed”
message.
5. Use case ends.
Post condition The account of the users registered (created).
Alternative course of A1: The post box was rented by other user.
action 1. The system displays “The post box was rented by another
user!” message.
A1: Missing of Required Information Message
1 The system displays “Fill all information!” massage.
UC-03
The system resumes at step 2.
Table 6. The scenario or use case description of the sent airmails registration use case.
UC Name Sent airmail register
UC-
UC Description Allows counter to register sent airmails.

05
24 | P a g e
Actor Counter
Precondition The counter should have logged into the system
Flow of event 1. They selects “Register Sent Airmail” menu.
2. They should complete and submits airmail’s
registration form by clicking “Send” button.
3. The system checks and validates the entered data.
[A1].
4. The system displays “airmail information recorded”
message
5. Use case ends
Post condition Sent airmail information is registered
Alternative course A1: Missing of Required Information Message
of action 1. The system displays “Fill all information!”
massage.
The system resumes at step 2.
Table 8. The scenario or use case description of the Check_Track use case
UC Name Check_Track
UC Description Enables all customers check their materials and airmails through
tracking with which where it reach.
Actor Customers
Precondition Customers have to know the track number
Flow of event 1. The user activates the system.
2. The system displays the main window.
3. The user enters the track number and click on check button.
4. The system checks and validates the entered information.
[A1:A2].
5. The system displays access page for the respective user and
shows information.
UC-19
6. Use case ends.
25 | P a g e
Post condition The user entered to the system and can check the material where
it reaches through tracking the system.
Alternative course A1: Information Not Filled Message
of action 3. The system displays “You Interred Invalid Track Id Please
Tray Again!!” message.
A2: Invalid trucking number
3. The system displays “You Interred Invalid Track Id Please
Tray Again!” massage.
Table 9. Use case description for Create account

UC Name Create Account
UC Description Describes how an administrator creates account

Actor Administrator
Precondition The administrator should successfully login into the system
Flow of event 1.The Administrator click create account link
UC-21
2. The system displays create account page.
3.The Administrator fills full information about users
4.The Administrator clicks on submit button
5 .The system validates the information interred by an Admin,

Customer [A1
6 .The systems register and create new account.
7 .The use case ends

Post condition Admin successfully generates Account and approve it
Alternative course A1: Invalid information
of action The system display “Please enter correctly” message display
26 | P a g e
Table 10. Use case description for deliver airmail

UC Name Deliver Airmail
UC Description Allow postman to Deliver Airmail and To describe how a post

man Deliver Airmail
Actor Post man

Precondition The post man should have logged in to the system successfully
Flow of event • 1. The post man selects the “Deliver Airmail” link.
• 2.The system display Deliver Airmail form and also all

records
• 3.The post man inters the Airmail identification or other

attributes or directly press Deliver Airmail button from
UC-23
displayed records
• 4.The system checks and validates the entered value
• [A1].
• 5.The system displays the Deliver Airmail is successfully

Deliver message
6.Use case ends

Post condition Post man successfully deliver airmail
Alternative course A1: Check identification number
of action The system display “identification number is invalid” message
display
27 | P a g e
Table 11. Use case description for deliver material
UC Name Deliver material
UC Description Describe how a post man control Delivered Material
Actor Post man

Precondition The post man should have logged in to the system successfully
Flow of event • 1. The post man selects the “Deliver Material” link.
• 2.The system display Deliver Material form and also all

records
• 3.The post man inters the Material identification or other

attributes or directly press Deliver Material button from
displayed records
• 4.The system checks and validates the entered value
• [A1,A2].
• 5.The system displays the Deliver material is successfully

UC-24
Deliver message
6.Use case ends

Post condition Post man successfully deliver material
Alternative course A1: Check identification number
of action The system display “identification number is invalid” message
display

A2: Check the entered value
The system display “please enter the correct value” message
display
28 | P a g e
Table 12. Use case description for Logout
UC Name Logout
UC Description Describes how users Logout to the system in order to leave out
from the system
Actor Administrator, Counter, Post man

Precondition The Administrator, Counter, Post man should have an account
UC-28
Flow of event • 1. The Administrator, Counter, Post man activates the system.
• 2.Users clicks on Logout button
• 3.The system return successfully to the home page
4.Use case ends

Post condition An authorized user can leave out of the system and the end of
the actions
1.3.4 Use case diagrams

Use case diagrams for the proposed system are used to represent the basic functionalities of the
system as Use cases focus on the behavior of the system from an external point of view. It also
represents user requirements gathered during requirement elicitation, contains use case, actors,
system boundary and their relationships. Use Case diagram of our system is shown as follows
with respective description.
29 | P a g e
Create user USE CASE DIAGRAM FOR ETHIOPIAN View material
account
POST OFFICE cost
Manage user
Manage user registerrecived
Register
account
account material
material
Assignsentsent
Assign mail Register recived
mailcostcost airmail
ADMIN <<Include>>
<<Include>>
Register recived
view feedback airmail
<<Include>> <<Include>>
Generate View delivery
report <<Include>>
<<Include>> <<Include>> material
POSTMAN
<<Include>>
<<Include>>
Vie delivered View sent
material <<Include>> <<Include>> material
<<Include>>
Login
Register sent <<Include>>
Airmail <<Include>>
Include View sent matrial
<<Include>>
View delivery
airmail <<Include>> <<Extend>>
<<Include>> Manage
<<Include>> Material
Manage
COUNTER Airmail <<Include>> Deliver
Material
Manage Rent
post box
<<Include>>
Logout Deliver
airmail
Post notice
Check_truck
View airmail
cost
Give
Feedback
RegisterRent CUSTOMER
postbox
Figure 2 Use Case Diagram
30 | P a g e
1.4 Non Functional requirements
Nonfunctional requirements describe user-visible aspects of the system that are not directly related
with the functional behavior of the system. Nonfunctional 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).
The nonfunctional requirements of our system will address are discussed as follows:-
 Robustness: - the system should be robust while validating data during data entry.
It also ability to survive invalid user input
 Security: - the system should be secured and protected from unauthorized user. It should have
a user’s database and should authenticate each user on login and should grant user specific
services.
 User interface:-the system should have friendly user interface
 Performance: - System will have good performance as much as possible this will be attained
via easily loadable interface components and optimal algorithms which make searching,
updating, deleting, inserting and saving easy and fast.
 Error handling mechanism: - the system must have error handling mechanism. It is not stop
functioning rather it must report an error message
 Documentation:-the system will provide the system description document for the client.
1.5 Dynamic Modeling
1.5.1 Sequence Diagram

Sequence diagram is a system model that is used to depict the interaction between participating
objects in a given use case. The sequence diagrams for automated postal service system is clearly
show the participating objects in the given use case.
A sequence diagram shows object interactions arranged in time sequence. Sequence diagram is a
system model that is used to depict the interaction between participating objects in a given use
case. It depicts the objects and classes involved in the scenario and the sequence of messages
exchanged between the objects needed to carry out the functionality of the scenario. A sequence
diagram shows, as parallel vertical lines (lifelines), different processes or objects that live
simultaneously, and, as horizontal arrows, the messages exchanged between them, in the order in
31 | P a g e
which they occur. The sequence diagrams for our automated postal service system is clearly show
the participating objects in the given use case as follows.
System Login Login controller Login Form Home Page Database

<<Boundary>> <<controller>> <<UL>> <<Boundary>> <<Boundary>>
1: Start
1.1 Click ()
1.1.1:Display ()
2. Enter user name and password ()

2.1: Login
3: Submitted
()
3.1: Check()
4.Invalid ()
4.1: Error Message ()
6:Display ()
5: Valid ()
7:Acknowledment ()
X X X X X X
Figure 3 sequence diagram for login to the system
32 | P a g e
System Login Add User Menu User Controller User Register form Database
<<Boundary>> <<Boundary>> <<Controller>> <<Boundary>> <<Boundary>>
1: Start
1.1 Click ()
1.1.1:Create ()
3:Fill
2:If invalid_entery
()
4:Fill_again
()
5:else()
6:Register
7:Acknowledment ()
X X X X X X
Figure 4 sequence diagram for user registration

System Login Add Postbox Menu Postbox Controller Rent Postbox form Database
<<Boundary>> <<Boundary>> <<Controller>> <<Boundary>> <<Boundary>>
1: Start
1.1 Click ()
1.1.1:Create ()
2:Enter username and password
3:Fill
4:Submit ()
4.1:display()
5:stste()
7:Acknowledment ()
X X X X X X
Figure 5 sequence diagram for renting post box
33 | P a g e
System Login Add sent airmail Menu Airmail Controller Sent airmail Register Database
<<Boundary>> <<Boundary>> <<Controller>> form<<Boundary>> <<Boundary>>
1: Start
1.1 Click ()
1.1.1:Create ()
1.1.1.1:display ()
2:Fill
3:invalid()
4:validate()
5:Check()
7:Acknowledment ()
X X X X X X
Figure 6 Sequence diagram for sent airmail registration

Home Main_menu Logout
<<UL>> <<UL>> <<UL>>
1: Start 1.1:want to logout

()
2:click_Logout
3:Acknowledment ()
X X X X
Figure 6 Sequence diagram for logout
34 | P a g e
1.5.2 Activity Diagrams
An activity diagram describes a system in terms of activities. Activities are states that represent
the execution of a set of operations. The completion of these operations triggers a transition to
another activity. Activity diagrams are also similar to flowchart diagrams in that they can be used
to represent control flow (i.e., the order in which operations occur) and data flow (i.e., the objects
that are exchanged among operations).
Administrator
Administrator login system
valid
invalid
Select Action
Create user Manage user Assign Mail view Generate

account account cost feedback Report
Figure 7 Activity diagram for administrator
35 | P a g e
Counter
Counter login system
valid
invalid
Select Action
View Airmail Material Manage Manage Manage

Rent postbox Post Notice
Amount Cost Register Airmail Postbox payment
Figure 8 Activity diagram for Counter
Post Man
Post Man login system
valid
invalid
Select Action
View
Register Material View Sent Deliver
material
airmail Register Material Material
cost
Figure 9 Activity diagram for Post Man
36 | P a g e
Customer
Customer login system
valid
invalid
Select Action
Give
Check_Truck
Feedback
Figure 10 Activity diagram for Post Man
37 | P a g e
CHAPTER FOUR
4 SYSTEM DESIGN
Introduction
System design is the transformation of the analysis model into a system design model. During
system design, we are going to define the design goals of the project and decompose the system
into smaller subsystems that can be realized by individual teams. The result of system design is a
model that includes a clear description of each of these strategies, subsystem decomposition, and
a UML deployment diagram representing the hardware/software mapping of the system. This
chapter mainly concerned with the design part of all about the postal system. In this section we
will see the different types of class type architectures, such as user interface layer, process control
layer, persistent layer, and system layer and also different types of system modeling techniques
that are used for the implementation types of the system such as class modeling, state chart
modeling, component modeling, deployment modeling and also some system design techniques
such as user interface designing are also to be covered in this design chapter.
4.1 Design goals

Design goals identify the qualities that our system should focus on.And provide a consistent set of
criteria that must be considered when making design decisions. The design goals are derived from
the non-functional requirements. So based on those non-functional requirements the following
design goals will have to achieve in order to qualify the system as successful.
 Robustness:
 The system should be robust while validating data during data entry.
 It also ability to survive invalid user input
 Security:
 The system should be secured and protected from unauthorized user.
 It should have a user’s database and should authenticate each user on login and should
grant user specific services.
38 | P a g e
 Usability: - centralized billing system provide easy user friendly interface for users of the
systems. It also provides help menu which gives brief description how to use the system so
that user can be able to use it easily.
 User interface:
 the system should have user friendly interface
 Performance:
 System will have good performance as much as possible this will be attained via easily
loadable interface components and optimal algorithms which make searching,
updating, deleting, inserting and saving easy and fast.
 Error handling mechanism:
 The system must have error handling mechanism. It is not stop functioning rather it
must report an error message
N.B:-The goal of system design is to manage our system complexity by dividing the system into
smaller, manageable pieces in general.
4.2 Proposed System Architecture

As we discussed earlier online postal service management system have so many advantages such
as it can save the postal information in the database, employees can add/delete data, manage user
account, manage postal services and payments, Customers can deliver materials and airmails, track
their materials and rent postbox from the post office. The proposed system is expected to replace
the existing works that are being performed manually by a web-based system which is all aspects
of postal services.
In this section we are going to show what our proposed system looks like and how it differs from
the current existing system. The online postal service management system uses client/ server
architecture. At the client by using a web browser can connect via internet or local host with the
server where PHP and MySQL in the server side are responsible for the preparing exams processes
and save and return data from database.
39 | P a g e
OPSMS
HOME
ADMIN COUNTER POST MAN CUSTOMER
LOG IN
LOG IN LOG IN
CREATE RENT REGISTER

POSTBOX MATERIAL
ACCOUNT
MANAGE
MANAGE MATERIAL REGISTER TRACK
ACCOUNT AIRMAIL MATERIAL
MANAGE
AIRMAIL
VIEW DELIVER
FEEDBACK MATERIAL
MANAGE GIVE
POSTBOX FEEDBACK
GENERATE DELIVER
REPORT AIRMAIL
POST
NOTICE
Assign
sent mail MANGE Manage
cost PAYMENT MAterial
Figure 11 Proposed system architecture
4.2.1 Proposed software architecture

The proposed software has three- tier architecture.
 The presentation tier: is the top most level of the application. It is the one the clients directly
interacted. It provides GUI to allow the client gaining access of the system.
 Logical tier/ middle tier: It accepts inputs from the client and performs detailed processing.
It is a bridge between data access tier and presentation tier.
 Data access tier: provides data persistence mechanism and storage to the data. It consists
of a mechanism to access the database without installing data base dependent drivers and
libraries on the client device
40 | P a g e
Figure 12 Proposed software architecture
4.2.2 Subsystem Decomposition

Subsystem decompositions will help reduce the complexity of the system. The subsystems can be
considered as packages holding related classes/objects. These subsystems are further decomposed
into other subsystems. The major subsystems identified are “Admin module”, “Counter module”,
“Customer module”, and “Tracking” subsystems. Users are classified in to roles. The “Login”
subsystem authenticates a user to grant access based on the role of the user.
41 | P a g e
Figure 13 Subsystem decomposition diagram
4.1Hardware/Software Mapping
We are developing the web application Ethiopian Postal service that will be a web based for any
customer i.e. which can be run anywhere through a browser. And the system will also run over
any operating systems. The web server will run over xampp server and the programming languages
used for developing this system are;
 Html(Hypertext Markup Language)
 Css(Cascading Sheet Style)
 Js(Java Script)
 Php(Hypertext Preprocessor)
 MS-Office 2016
 Visio 2016 (Trial version ) 7.9
 Star UML 5.0 and also star UML 2.01
We have also selected MySQL database as the database management system.
The Software components that have role in our system are the following: -
1. At client side: the responsibility is given to the web browser that handle the client request and
forward to the Web server to provide what they ask. Those users that interact with web browser
are the following:
42 | P a g e
 Post man
 Counter
 Administrator
 Customer
2. Web Server: Responsible to provide user with the response. Here the web server listens for an
HTTP request and Provide web browser with HTTP Response. We have so many modules at
the web server that provide response to users some of them are: -
 Manage material
 Manage account
 Manage postbox
 Assign sent mail cost
 Take Backup and so on.
3. Database Server: it is responsible for the processes that are stored in the database such as user
details, post details, and payment details.
It uses scripting language to access and modify the database such as PHP, Biscuit,
ADO.net etc. also it retrieves or perform operation if user full fills the security
requirements. I.e. Authentication and Authorization.
4.2Persistent Mapping
Physical database model shows all table structures, including column name, column data type,
column constraints, primary key, foreign key, and relationships between tables. Features of Online
postal service management System physical data model includes: Specification of all tables and
columns.
The purpose of persistence modeling is to identify which objects in the system design are required
to be stored persistently and also it deals with how the persistent data (file, database, etc.) are stored
and managed and it outlives a single execution of the system.
43 | P a g e
c an have
cost Mat erial
PK c ost id
PK Ma te r ial id
sr nde r br anc h Se nder br anc h
r ec e iver br anc h De st inatio n bar anc h
am ount se nder fir st nam e
se nder la st na me
se nder phone
se nder e ma il
Accou nt r ec ie iver fir st na m e
r ec e iver las t nam e

PK use r id
r ec e iver phone
fir st na m e
r ec e iver e ma il
las t na me
at tr ibut e na me
use r nam e c re ate
&
manage w eig ht
pas swor d
pay
pr ice
use r type
se nt da te
phone
Re c eive d dat e
at tr ibut e na me
c urr e nt pla ce
e ma il
st at us
send
or
rec eive
Tr a ck num be r
c an have
C ust omer
Po st bo x
PK id
PK post box id
fir st na m e c re ate
& Re nt da te
manage rent
las t na me
e xpir e dat e
ag e
pr ice
se x
se cur it y numbe r
addr e ss
phone
e ma il give
feedb ack
PK fe ed ba ck i d
c ustom e r e nque ry
admin
e ma il
PK id
fe edba ck
fir st na m e
vie w
st at us
las t na me
ag e
se x
phone
e ma il
Figure 14 Diagram for persistence mapping
4.3Class/Package Diagram
Class diagram describe the structure of the system in terms of classes and objects .Classes are
abstractions that specify the attributes and behavior of a set of objects whereas objects are entities
that encapsulate state and behavior. The class diagram is a static diagram. It represents the static
view of an application. Class diagram is not only used for visualizing, describing and documenting
different aspects of a system but also for constructing executable code of the software application.
The class diagram shows a collection of classes, interfaces, associations, collaborations and
constraints. It is also known as a structural diagram.
So the purpose of the class diagram can be summarized as:
 Analysis and design of the static view of an application.
44 | P a g e
 Describe responsibilities of a system
 Base for component and deployment diagrams
In our system admin module, counter module or airmail page, postman module or material page,
customer page, and tracking page are classes. The class diagram for automated Ethiopian postal
service system as shown below.
Figure 15 Class diagram of the system
4.4State Modeling
A state chart diagram is a view of a state machine that models the changing behavior of a state.
State chart diagrams show the various states that an object goes through, as well as the events that
cause a transition from one state to another.
The common model elements that state chart diagrams contain are:
 States
 Start and end states
 Transitions
45 | P a g e
A state represents a condition during the life of an object during which it satisfies some condition
or waits for some event. Start and end states represent the beginning or ending of a process.
Idle
open system
OPSMS login page

select page
HOME page
enter username
and password
login form
check validity
if invalid
if valid
user page
successs
Figure 16 State diagram for user login
46 | P a g e
IDLE
Open system
OPSMS
HOME PAGE
select pages
enter user and pass
LOGIN FORM
check validity
if invalid
ADMIN PAGE ACCOUNT FORM
if valid clllick register user
fill form
and check validity
if invalid
if valid
CONFIRM ACCOUNT
click confirm
ACCOUNT LIST
success
Figure 17 State diagram for create user account
OPSMS click track

track page shipment form
click shipment
and trace
Home page
enter shipment id
if invalid
if valid
show location
asuccess
Figure 18 State diagram for tracking material
47 | P a g e
idle
OPSMS
Home page
select pages
feedback page
if valid
comment form
asuccess
Figure 19 State diagram for give feedback
48 | P a g e
POSMS
Home page
open system
OPSMS login page

select pages enter user name
Home page and password
if invalid if valid
post man
select send material
material form
enter datas
if invallid
if valid
sentmaterials list
asuccess
Figure 20 State diagram for sending material
49 | P a g e
4.5Component Modeling
Online postal service management system component diagram show how its Components are
wired together to form larger components and also it shows software system how they are used to
illustrate the structure of arbitrarily complex postal service management system. This diagram
helps us to model the physical aspect of our system. It illustrates the architectures of the software
components and the dependencies between them.
Web Server
Track material
Give feedback
Client
Database Serveer
Create account
Customer
Manage account
admin Security
View feedback
GENERATE REPORT
Log in
Database
MANAGE Material
DELIVER MATERIAL
DELIVER AIRMAIL
postman
View Delivered mail
Manage material
counter Manage airmail
MANAGE COST
Figure 21 Component diagram
50 | P a g e
4.6Deployment Modelling
Deployment diagram depicts a static view of the run-time configuration of processing nodes and
the components that run on those nodes. In other words, deployment diagrams show the hardware
for our system, the software installed on that hardware, and the middleware used to connect the
disparate machines to one another. Accordingly; online postal service management system
deployment diagram consist the system software installed on electronic devices with browsers
acting as middleware to connect client side to the server side we used it to visualize the topology
of the physical components of our system where the mentioned software component diagrams are
deployed.
Application
Server
Manage
Material
Client Machine
Manage Database Server
Account
Rent box
Give
Feedback
WEB mysql
BROWSER HTTP View
connection Post office
Notice
<<DB>>
Track
Material
Post
Notice
Manage
Air mail
Manage
Payment
Figure 22 Deployment diagram
51 | P a g e
CHAPTER FIVE
5 IMPLEMENTATION
5.1 Introduction
In implementation phase involves putting the project plan into action. We coordinate and direct
project resources to meet the objectives of the project plan. As the project unfolds, we direct and
manage each activity, every step of the way.
In our Ethiopian postal services project implemented each and every functionalities that included
in the project
5.2 Environmental Setup

In our Ethiopian postal services project there is a configuration of hardware and software
platform for the purpose of developing this system.
HARDWARE CONFIGURATION
Hardware configuration tools are primary requirement to develop our system. Although the team
of the project takes different kinds of hardware tools, to develop this project we take the following
Hardware tools requirements:
Processer: this is the basic hardware component to develop our system so in the client side we
needs 3.30MHZ and in the server side also 6MHZ is needs.
RAM Size: also another type of hardware component to develop our system and it is a storage
device and we need 4GB and 8GB in client and server side respectively.
Internal Hard Disc Space: this is another type of hardware component to develop our system so in
the client side we need 500GB and in the server side also 1TB is needs.
SOFTWARE CONFIGURATION
Software configuration tools are primary requirement to develop our system. Although the team
of the project takes different kinds of software tools.
The different kind of software we used for developing the project is:-
52 | P a g e
 Xampp Server 2.5(MYSQL) or xampp-win32-1.7.3: to develop database application
 PHP, HTML, CSS, Java Script –Programming Languages,
 Microsoft office word 2016 for documentation.
 Windows 10 Operating system- will be used for the system since it is readily available in
our laboratories
 Microsoft Visio 2016- to design Sequence Diagram, Class Diagram, and Use case
Diagram.
 Browsers-since our system is web based, it is very necessary requirement.
 Sublime Text 3- for writing the code.
5.3 Algorithm Design and Coding
5.3.1 Algorithm
Pseudo Random Number Generator (PRNG) refers to an algorithm that uses mathematical
formulas to produce sequences of random numbers by using Rand ().
Rand () function: - rand function used to generate random numbers and strings, We use it for the
purpose of generating track number in the type of selecting items, Those items are EMS, Ordinary
and Parcel then start with EP and continue with 0-9 numbers and EMS for EMS type and start with
EP and continue with 0-9 numbers and RG for Parcel and Ordinary type.
PDO Reports
PDO reports consist of 1 or more SQL statements separated by semicolons. By default, the result
of the last statement is used for the report. At the top of the report is a comment block with name,
description, and any other report headers you need. For the purpose of generating the report to
admin, postman or counter.
53 | P a g e
5.3.2 Sample code
COUNTER for Delivery of Airmail
Delivery of Airmail code is used to delivering the airmail to the receiver of the airmail then the
Counter have to enter full information about the sender address and receiver address including
payment systems such as on cash or bank account, Then the system generate recites and truck
number.
The truck number is used to identify uniquely the customer’s airmail and customer’s helps to
know where the message destination is now by entering the truck number.
<?php <link href="../css/mystyle.css"

rel="stylesheet" type="text/css"
include 'posmansec.php';
media="all">
?>
<link href="../css/font-
<html> awesome/css/font-awesome.css"
rel="stylesheet" type="text/css"/>
<head>
<script
<meta charset="UTF-8">
src="../js/jquery.min.js"></script>
<meta name="viewport"
<script src="../js/jquery.js"></script>
content="width=device-width, initial-
scale=1"> <script
src="../js/bootstrap.min.js"></script>
<link rel="stylesheet"
href="../css/bootstrap.min.css"> <style>
54 | P a g e
.nur{background-color: <span class="icon-
#ADD8E6;}#side{ background- bar"></span>
color:#d5d5d5 ;min-height:
<span class="icon-
500px;}#hallo{background-color:#d5d5d5;
bar"></span>
min-height: 550px;}
<span class="icon-
.active { background-color:
bar"></span>
#4CAF50;color: white;}#top{background-
color: #4c0080} </button>
#but{background-color: <span class="text-muted"

#d5d5d5;text-align: left;} aligne="center"><h3>Well Come To Post
Man Page</h3></span>
</style>
</div>
<title> Post Man Page</title>
<div id="navbar" class="navbar-
</head>
collapse collapse">
<body class="nur">
<ul class="nav navbar-nav
<nav class="navbar navbar-inverse navbar-right">
navbar-fixed-top">
<li><a
<div class="container-fluid" href="changepassword.php"><i class="fa
id="top"> fa-2x fa-key"></i>Change
Password</a></li>
<div class="navbar-header">
<li><a
<button type="button"
href="../customer/logout.php"><span
class="navbar-toggle collapsed" data-
class="fa fa-2x fa-sign-
toggle="collapse" data-target="#navbar"
out"></span>Logout</a></li>
aria-expanded="false" aria-
controls="navbar"> </ul>
<span class="sr- </div>

only">Toggle navigation</span>
55 | P a g e
</div> class="well-sm" id="nur">Reigster
Recieved Material</div></a></li>
</nav>
<li><a
<br><br><br>
href="viewDeleverdMaterial.php"><div
class="well-sm" id="nur">View Delivrd
Material</div></a></li>
<div class="row">
<li><a
<div class="col-md-2" id="side">
href="returnMaterial.php"><div
class="well-sm" id="nur">View Sent
<ul class="nav nav-sidebar">
<li><a
<li class="active"><a
href="sentairmail.php"><div class="well-
href="index.php"><i class="fa fa-2x fa-
sm" id="nur">View Sent
home"></i>Home </a></li>
Airmail</div></a></li>
<li><a
</ul>
href="viewMaterialCost.php"><div
class="well-sm" id="nur">View Material <button type="button" id="but"
Cost</div></a></li> class="btn btn-default btn-block" data-
toggle="collapse" data-
<li><a
target="#demo">Manage Material</button>
href="registermaterial.php"><div
class="well-sm" id="nur">Reigster <div id="demo" class="collapse">
<li><a
<li><a
href="recivedAirmail.php"><div
href="searchmaterial.php"><div
class="well-sm" id="nur">Reigster
class="well-sm" id="bb"><i class="fa fa-2x
Recieved Airmail</div></a></li>
fa-search-plus"></i>Search
<li><a Material</div></a></li>
href="recievedmaterial.php"><div
56 | P a g e
<li><a <li><a
href="updatematerial.php"><div href="delivermaterial.php"><div
class="well-sm" id="bb"><i class="fa fa-2x class="well-sm" id="bb">Diliver
fa-refresh"></i>Update Material</div></a></li>
<li><a

</div>
<li><a
href="deletematerial.php"><div </div>
class="well-sm" id="bb"><i class="fa fa-2x
<div class="col-md-10">
fa-deviantart"></i>Delete
Material</div></a></li> <div class="row">
</ul> <div class="col-md-10">
</div><br> <form class="form-

horizontal" role="form" name="form"
method="POST">
</ul>
<p align="right">
<button type="button" id="but"
<table width="80%">
class="btn btn-default btn-block" data-
toggle="collapse" data-target="#de">Diliver <tr>
Mail</button>
<td align="left"><h2
<div id="de" class="collapse"> class="" align="left">Dliver Airmail
</h2></td>
<td><input
name="searchvalue" type="text"
57 | P a g e
class="form-control" placeholder=" Search Name</th><th>Sender Last
Airmail by Id"></td><td></td> Name</th><th>Reciever First
Name</th><th>Reciever Last
<td><button
Name</th><th>Reciever
class="btn btn-default"name="search"
Email</th><th>Track
type="submit"><i class="fa fa-
Number</th><th>Action</th></tr>';
search"></i></button></td>
while ($row =
</tr>
mysqli_fetch_assoc($one)) {
</table>
</p>
echo '<tr><td>' .
</form> $row['airmailId'] . '</td><td>' .
$row['senderfirstname'] . '</td><td>' .
<?php
$row['senderlastname'] . '</td><td>' .
include '../connection.php'; $row['recieverfirstname'] . '</td><td>' .
$row['recieverlastname'] . '</td><td>' .
if (isset($_POST['search'])) {
$row['recieveremail'] . '</td><td>' .
$searchvalue = $row['tracknum'] . '</td>';
$_POST['searchvalue'];
$one =
mysqli_query($con,"SELECT * FROM
echo '<td><a
airmail WHERE airmailId='$searchvalue'
href="deliverairmail.php?aid=' .
and status = 'Recieved'");
$row['airmailId'] . '" role="button"
if class="btn btn-default btn-sm"
(mysqli_num_rows($one) > 0) { >Deliver</a></td></tr>';
echo '<table class="table

table-hover">'; }
echo '<tr><th>Airmail echo '</table>';

Id</th><th>Sender First
58 | P a g e
} else {
$dis =
echo '<div class="alert
$row['decitinationbranch'];
alert-info">there is no result in your Search
Value.</div>'; echo '<tr><td>' .
$row['airmailId']. '</td><td>' .
}
$row['senderfirstname'] . '</td><td>' .
} $row['senderlastname'] . '</td><td>'.
'</td><td>' . $row['recieverfirstname'] .
'</td><td>'
else{
.
$query1 =
$row['recieverlastname'] . '</td><td>' .
mysqli_query($con,"SELECT * FROM
$row['recieveremail'] . '</td><td>' .
airmail WHERE status='Recieved'");
$row['tracknum'] . '</td>';
if
echo '<td><a
(mysqli_num_rows($query1) > 0) {
href="deliverairmail.php?aid=' .
echo '<table $row['airmailId'] . '" role="button"
class="table table-hover">'; class="btn btn-default btn-sm"
>Deliver</a></td></tr>';
echo
'<tr><th>Airmail Id</th><th>Sender First //echo'<a name="detail"
Name</th><th>Sender Last href="searchuser.php?uide='.$row['actorId'].
Name</th><th>Reciever First '" class="btn btn-default" role="button"><i
Name</th><th>Reciever Last class="fa fa-edit"></i></a>';
Name</th><th>Reciever
?>
Email</th><th>Track
Number</th><th>Action</th></tr>'; <?php
while ($row = echo '</td></tr>';

mysqli_fetch_assoc($query1)) {
}
59 | P a g e
echo '</table>'; ?>
else {
</div>
echo '<div class="alert
<div class="col-md-2"
alert-info">There is No Recived Material
id="hallo">
For this Place</div>';
<div class="alert alert-info">
}}
<script
language="JavaScript">
if (document.all ||
if (isset($_GET['aid'])){
document.getElementById)
$aid = $_GET['aid'];
$query = document.write('<span id="worldclock"

mysqli_query($con,"update airmail set style="font:bold 20px
status='Dlieverd' where airmailId='$aid'"); Arial;"></span><br>')
if ($query){ zone = 0;
echo '<script isitlocal = true;

type="text/javascript"> alert("You are
ampm = '';
Successfuly
Delivered");window:location=\'deliverairma function updateclock(z)
il.php\';</script>'; {
zone =
z.options[z.selectedIndex].value;
}
isitlocal =
}
(z.options[0].selected) ? true : false;
60 | P a g e
} ampm = (hr > 11) ?
"PM" : "AM";
function WorldClock() {
statusampm =
now = new Date();
ampm.toLowerCase();
ofst =
hr2 = hr;
now.getTimezoneOffset() / 60;
if (hr2 == 0)
secs =
now.getSeconds(); hr2 = 12;
sec = -1.57 + Math.PI (hr2 < 13) ? hr2 : hr2

* secs / 30; %= 12;
mins = if (hr2 < 10)

now.getMinutes();
hr2 = "0" + hr2
min = -1.57 +
var finaltime = hr2 +
Math.PI * mins / 30;
':' + ((mins < 10) ? "0" + mins : mins) + ':' +
hr = (isitlocal) ? ((secs < 10) ? "0" + secs : secs) + ' ' +
now.getHours() : (now.getHours() + statusampm;
parseInt(ofst)) + parseInt(zone);
if (document.all)
hrs = -1.575 +
Math.PI * hr / 6 + Math.PI *
worldclock.innerHTML = finaltime
parseInt(now.getMinutes()) / 360;
else if
if (hr < 0)
(document.getElementById)
hr += 24;
if (hr > 23) document.getElementById("worldclock").in

nerHTML = finaltime
hr -= 24;
else if
(document.layers) {
61 | P a g e
<div class="well">
document.worldclockns.document.worldclo
<footer class="container-fluid text-
ckns2.document.write(finaltime)
center">
<p>&copy <?php echo date("Y");

document.worldclockns.document.worldclo
?> Ethiopian Post Office Interprise</p>
ckns2.document.close()
</footer>
}
</div>
setTimeout('WorldClock()', 1000);
window.onload =
WorldClock
</body>
</script>
</html>
</div>
</div>
</div>
</div>
</div>
<br>
62 | P a g e
5.4 User Interface(GUI)design
Ethiopian postal service User Interfaces see below
Figure 24 Ethiopian postal services Home Page
63 | P a g e
Figure 25 Ethiopian postal services Admin Page
64 | P a g e
Figure 26 Ethiopian postal services Postman Page
65 | P a g e
Figure 27 Ethiopian postal services Counter Page
66 | P a g e
CHAPTER SIX
6 Conclusion and Recommendation

6.1 Conclusion
Ethiopian postal services is one of the system needed in Ethiopian post. After we have
completed this project we are sure the problems in the existing system will be eliminated at least
by half. This project computerizes the trucking process and email notification for the customers,
fully delivery of materials and airmail
Through various challenging, now we are coming to the end of this project. We face those
different challenges made it possible by the cooperation. In developing this project we
contributed our full capability with maximum interest and get ways toward developing a project.
Generally making computerized postal is very important to save time, get reliable information
and generate appropriate truck number for customers.
67 | P a g e
6.2 Recommendation
The system we have developed is a Web based application it needs a skilled person to work with
the system. So, we recommend the system should be entitled to the responsible and skilled
person. Due to time limitation our system doesn’t include Digital Signatures, Foreign Services,
and Commission services such as pay pension, Western Union Services, Forming DV Lottery,
Distributing SIM Cards and Mobile Card and Income tax collection. So, we recommend for the
future to improve the system by including the above points.
68 | P a g e
Reference
1. http://creately.com/diagram/example/hhn6mvel/Subsystem+decomposition
2. http://creately.com/blog/giagrams/uml-diagram-types-examples/
3. https://en.wikipedia.org/wiki/Component_diagram
4. Ethiopian postal Services charter
5. Scott Ambler-the _Element _of_ UML_ style (2003).
6. Booch, gradyRambaugh, jemes Jacobson, Ivare(2005) the unified modeling language user
Guide Second Edition Addison Wesley professional USA
7. (http://shodh.inflibnet.ac.in/bitstream/123456789/2772/3/93%20literature%20review.pdf)
8. Websites of Ethiopian postal system (www.ethiopianpostal.com)
69 | P a g e

Final Project Web Based Ethiopian Postal Service

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

Final Project Web Based Ethiopian Postal Service

Uploaded by

Copyright:

Available Formats

Mizan-Tepi University

School of computing and informatics

Department of Information systems

Industrial project on Web Based Ethiopian Postal Service Management System

Submitted to the department of Information Systems in partial fulfillment of the

Advisor (s) Tepi, Ethiopia Month, Yea

Advisors: Mr.Tibebu & Ms.Alemitu

Tepi, Ethiopia 25th Aug 2021 GC

Name and signature of Members of the Examining Board

Name Signature Date

1. ______________________ __________ __________

Name Signature Date

__________________________ __________ __________

Subject: Industrial Project Submission

Name of advisor Signature Date

______________ ___________ __________

GROUP MEMBERS SIGNATURE DATE

1) NURADDIS JEMAL ____________ ____________

4) KORMA NURE ____________ ____________

5) ABRAHAM TAMIRATN ____________ ____________

6) ZEWDITU EBABU ____________ ____________

CHAPTER ONE ..................................................................................................................................... 1

1.1 Background of the organization ..................................................................................................... 1

1.2 Background of the project .............................................................................................................. 2

1.3 Motivation ..................................................................................................................................... 3

1.4 Statement of the problem ............................................................................................................... 3

1.5 Proposed System............................................................................................................................ 4

1.6 Objective of the project .................................................................................................................. 4

1.6.1 General objective .................................................................................................................... 4

1.6.2 Specific objective .................................................................................................................... 5

1.7 Scope and limitation of the project ................................................................................................. 5

1.7.1 Scope ...................................................................................................................................... 5

1.7.2 Limitation ............................................................................................................................... 5

1.8 Methodology and tools................................................................................................................... 6

1.8.1 Methodologies ........................................................................................................................ 6

1.8.1.1 Data gathering methodologies .............................................................................................. 6

1.8.1.2 Design methodology............................................................................................................. 7

1.8.1.3 Implementation Methodology ............................................................................................... 8

1.8.1.4 Testing methodology ............................................................................................................ 9

1.8.2.1 Hardware Tools .................................................................................................................. 10

1.8.2.2 Software Tools ................................................................................................................... 10

1.9 Feasibility analysis....................................................................................................................... 11

1.9.2 Technical feasibility .............................................................................................................. 11

1.9.3 Operational feasibility ........................................................................................................... 11

1.10 Benefits and Beneficiaries of the project .................................................................................... 12

1.11 Risk and constraints ................................................................................................................... 13

2. OVERVIEW OF EXISTING SYSTE............................................................................................. 15

2.1 Introduction ........................................................................................................................... 15

2.2 Literature Study ..................................................................................................................... 15

2.3 Weakness and strength of the existing system ......................................................................... 17

2.3.1 Weakness of the existing system ..................................................................................... 17

2.3.2 Strength of the existing system ....................................................................................... 17

2.4 Business rules ........................................................................................................................ 17

CHAPTER THREE ............................................................................................................................... 19

3 REQUIREMENT ANALYSIS ....................................................................................................... 19

3.1 Introduction ........................................................................................................................... 19

3.2 System Requirement Specification ......................................................................................... 19

3.3 Functional requirements ......................................................................................................... 19

3.3.1 Actors Specification ....................................................................................................... 20

3.3.2 System Use-case Identification ....................................................................................... 20

3.3.3 Use Case Description and Scenario ................................................................................. 22

1.3.4 Use case diagrams .......................................................................................................... 29

1.4 Non Functional requirements.................................................................................................. 31

1.5 Dynamic Modeling................................................................................................................. 31

1. __________

______________

________ _ ______

1) NURADDIS JEMAL

4) KORMA NURE

5) ABRAHAM TAMIRATN

6) ZEWDITU EBABU