WACHEMO UNIVERSITY

FACULITY OF ENGINEERING AND

TECHNOLOGY
DEPARTMENT OF INFORMATION
TECHNOLOGY
TITLE:-ONLINE POSTAL SERVICE
GROUP FOUR (4)
MEMBER OF STUDENTS ID
1.BEREKET BABISO 000731
2.HILUF GIRMA 000
3.BETHEL HAILE 00
4.DIRES AMOGNE 000
5.ENYEW AWOKE 000
6.MINAHILE TILAHUNE 000

SUBMITE DATE 18/07/2011 E.C

1|Page
 CONTENTS
CHAPTER ONE
1. Introduction-------------------------------------------------------5
1.1 Background of organization-----------------------------5
1.2 Statement of problem--------------------------------------6
1.3 Objective of the project------------------------------------7
1.3.1 General objective of the project--------------------7
1.3.2 Specific objective of the project--------------------7
1.4 Methodology---------------------------------------------------8
1.4.1 Fact finding techniques---------------------------------8
1.5 Feasibility study of the new system------------------9
1.5.1 Operational Feasibility---------------------------------9
1.5.2 Technical Feasibility------------------------------------9
1.5.3 Economical Feasibility---------------------------------10
1.5.4 Political Feasibility---------------------------------------10
1.6 Scope and limitation of project-----------------------10
1.7 Significance of the project-------------------------------11
CHAPTER TWO
ANALYSIS
2.1 Introduction--------------------------------------------------13
2.1.1 Existing system-------------------------------------------13
2.1.2 Over view of new system----------------------------14

2|Page
 CHAPTER THREE
SYSTEM DESIGN
3.1 Essential use case diagram-----------------------------------15
3.1.2 System use case diagram----------------------------------15
3.1.3 Use case documentation-----------------------------------19
3.2 Sequence diagram------------------------------------------------31
3.3 Activity diagram---------------------------------------------------37
3.4 Class diagram-------------------------------------------------------42
3.5 Deployment diagram-------------------------------------------43
3.6 Collaboration diagram------------------------------------------45
3.7 Component diagram--------------------------------------------46
3.8 Entity Relation Model(ER-Model) -----------------------47
3.9 Class Type Architecture---------------------------------------48
3.10 State chart------------------------------------------------------------54
CHAPTER FOUR
CONCLUSION AND RECOMMENDATION
4.1 Conclusion------------------------------------------------------------59
4.2 Recommendation--------------------------------------------------60
4.3 Reference -------------------------------------------------------------61

3|Page
Abstract
Postal service system is one of the widely used communication media in
the world. Now a day’s technology is highly accelerating throughout the
world.
Due to this reason computerizing the postal service system has a lot of
advantages.
This project is aimed to automate Ethiopian postal service system. The
proposed system will have the capabilities to store information about
airmail transaction, update information, search information, store
information about material that stored in store room and store contact
information of renting post box.

Acknowledgement
First of all we would like to thanks our God because helps us in
every success of our work. Next to this we would like to express
deepest gratitude our instructor Redwan. Finally we would also like
to thanks our team members for our contribution and shared ideas
for the successful completion of the project.

4|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.
Ethiopia has at present 1139 post offices. Out of this 746 Permanent
post offices, 130 Departmental sub-post offices, 261
Sub-post offices and 2 Visiting postmen in rural areas and over
170000 post boxes. It is estimated that one post office is serving
79016 inhabitants while one private box serves 529 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
5|Page
 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 Statement of the problem

Still know 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 is very high means takes much

time to perform simple tasks,
 Takes time to retrieve data,
 Difficult to update data,
 Wastage of resources,
 Needs more space to store file cabinet,

6|Page
  Loss of data and poor organized and unsecured data. This
also leads to Security problem not protect the data from an
unauthorized person and doesn’t keep the organizations’
safety.

1.3 Objective of the Project

1.3.1 General Objectives of the Project

The general objectives of this project is to develop and implement
web based Online postal service for Ethiopia .That is to develop
and provide a full internet application or web based application,
then can be accessed by any customers throughout the world as well
as branch organizations are communicate each other through online
network application.

1.3.2 Specific Objectives

The specific objectives are listed below:-

 To encourage data security

 To design central and well-structured database management system
 To eliminate redundancy of data
 To make online with web based application through an internet
connection.
 To keep truck mails.
 To minimize resources.

7|Page
 1.4 Methodology
1.4.1 Fact finding techniques
The data collection instruments used to gather accurate information about
the existing system and the requirements for the new system.
To get a precise data, the team member has used the following data
collection techniques. Those are: -
1. Interview: - to get the basic information and background
information about the existing management system, the team
members has interviewed the managers and some customers
about the services that are given to them, and the problems
associated with that environment.
2. Direct observation: even though interview is very important to
gather information, direct observation is simple and we project
team members physically observe information that cannot
maintain from the interview or others and also it is important
if they are unable to communicate with others because of the
difficulties they have to the language.
3. Questionnaires: since managers as well as higher officials of
postal service have work load they cannot able to answer/give
information what we ask. So we prepare some sample
questions to get précised information.

8|Page
 4. Existing document: To get more information about the project
we use earlier documents that help us to develop the project.
During the analysis of documents, we give a special
consideration to those documents which can bring more
features to the project.

1.5 Feasibility Study of the new System

Feasibility study is essential to evaluate the cost and benefits of the new
system. On the basis of the feasibility study, decision is made on whether
to proceed or to cancel the project.
Need of the feasibility study:
 It determines the potential of the existing system.
 It used to determine/finds out the problem of the existing
system.
 To determine all goals of the new system.
 It finds all possible solutions of the problems of the existing
system.

1.5.1 Operational Feasibility

The system to be developed will provide accurate, active, secured service
and decreases labor of workers and also it is not limited to particular
groups or body. And also it is plat form independent i.e. it run’s in all
operating system.

1.5.2 Technical Feasibility

9|Page
The system to be developed by using technologically system development
techniques such as PHP, Java script, and MySQL database without any
problems and the group members have enough capability to develop the
project. So the system will be technically feasible.

1.5.3 Economic Feasibility

The system to be developed is economically feasible and the benefit is
outweighing the cost. Since this project already computerizes the existing
system, by now the reduction of cost for materials used in manual
operation becomes beneficiary to the organization.

1.5. 4 Political feasibility

The system to be developed is not conflict with any government
directives, because it gives services for the people effectively and
efficiently, all the stakeholders also agreed before the system developed.
So the government is profitable and the system will be politically feasible.

1.6 Scope and limitations of the

project
A. Scope: -
Scope of this project means the boundary that we are performing
tasks in this project. The project covers the postal management part
of the system. The proposed system that we will try to automate is
limited and bounded on the Ethiopian postal services. It will
perform how to:-

10 | P a g e
  Manipulate information
 User management
 Store data in data base
B. 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 is limited to perform the following tasks because of
the above mentioned factors.

 Paying pension
 Forming DV lottery
 Selling SIM cards, mobile cards
 Western Union services

1.7 Significance of the project

The proposed project has many benefits. Those are listed below:-
 Speed up the system: - this project will increases the
performance speed of Ethiopian postal service .The
present service of Ethiopian postal service is not that much
fast than the new system which is implemented in future.
 Perform data updating easily:-we can easily update data
within the system so the system provides better updating
performance and updated futures.

11 | P a g e
  Reduce resource wastage:- resources’ are not reduced
anymore .wastage of resources are not the futures of the
new system
 Protect data/files from unauthorized users:-data are only
accessed by authorized users so no one can access the data
without authorization this leads to best data security.
 Reduce work load of the employee of the organization:-
this system reduces workload of workers because all the
activities are easy within the new system
 Enable the organization to have centralized DBMS: - this
system enables the organization to have a centralized
DBMS.

12 | P a g e
 Chapter 2
Analysis
2.1 INTRODUCTION

2.1.1 Existing system

With existing system it is highly labor intensive to operate because
it requires a lot of human power and takes much more time to
operate.
Currently the Ethiopian Postal Service System mostly follows manual
based system and somewhat automated to provide service to its
customers. The services provided by the system are:-

 Paying pension
 Forming of DV lottery
 Selling SIM ,mobile cards
 Income tax Collection
 Tele agency license tax collection

13 | P a g e
Weakness and strength of existing system

A. Strength of existing system

The employees provide service to the society by:-

 Loyal able to the customers.

 Punctual to the society.
 Honesty to the users
 Responsible and transparent for their actions.

B. Weakness of existing system

The weaknesses of the existing system are:-

 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 disorder of data: - because the data are not
stored sequentially.

2.1.2 Overview of the new system

A new system that controls and manages the existing postal management
processing of the postal service using a connection of application software
and a database to store the permanent data is proposed as a best solution
for the above problem.

14 | P a g e
 The Online Ethiopian Postal Service automates each and every
activity of the current manual system and increases its throughput. It will
try to eliminate the drawbacks of the existing system by improving:

 Time accuracy
 By reducing system complexity
 Improving security issue
 Improving efficiency
 By designing new model
 Make transaction very easy and fast
 Simplifying manipulation of data.

UNIT THREE
3. SYSTEM DESIGN
System design is the transformation of the analysis model into a
system design model. The purpose of this document is to provide
an overview as to how to actually build the proposed system and to
obtain the information needed to derive the actual implementation
of our system. During the last phase we, the team has extensively
worked on the system analysis to understand what will be built. In
many ways, this is a continuation of that work, only here we draw the
system closer towards implementation.

15 | P a g e
 In this part of the document, we have used include the following
diagram to understand our system

3.1 Essential Use case diagrams

Use Case represents interaction between a user (human or machine) and the system.
Use case components:
 Actor: is a person, or external system that plays a role in one or more
interaction with the system. And represented with:

 Use case: describes a sequence of actions that provides something of

measurable value to an actor and is drawn as a horizontal ellipse.


 System boundary: indicates the scope of the system project. Anything within
the box, represent functionalities in side in scope.

16 | P a g e
 3.1.1 ENSSENTIAL USE CASE DIAGRM

search user search air maill

registration

register user
recieve air maill
update user registration
ADIMNSTOR

delete user update&deleteair maill

registration
search
materials
COUNTER
rent post box
material
registration
search rent
post box

update materials

POST MAN update &delete

delete materials rent post box

create account

send messages check track

CUSTOMER

17 | P a g e
 3.1.2 SYSTEM USE CASE DIAGRAM

search user search air maill

registration

register user <<include>>

<<include>>
recieve air maill
<<include>>
update user registration
ADIMNSTOR <<include>>
<<inclde>>
log in
<<include>>
delete user update&deleteair maill
<<include>>
<<include>>
registration
<<include>>
search <<include>>
materials <<include>>

COUNTER
<<include>> rent post box
material <<include>>
<<extend>> <<include>>

registration
<<include>> search rent
post box
<<include>> <<include>>

update materials

POST MAN log out update &delete

delete materials rent post box

create account

send messages check track

CUSTOMER

18 | P a g e
 3.1.3 Use case documentation
UC Name Login

UC Description Enables all users of the system to login.

Actor Administrator, Counter, Postman, Customers
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 id and password and click login
button.
4. The system checks and validates the entered user id
and password. [A1:A2].
UC-01

5. The system displays the main window.

6. The system displays access page for the respective
user.
7. Use case ends.
Post condition The user entered to the system and can access the
system.
Alternative A1: Information Not Filled Message
course 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.
2. The system resumes at step 3.

19 | P a g e
 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
UC-02

by clicking “Add” button

4. The system checks and validates the entered
data. [A1:A2].
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 A1: Wrong data Entry Message
course of action 1. The system displays “Wrong data Entry!”
message.

20 | P a g e
 2. The system resumes at step 3.
A2: Missing of Required Information Message
1. The system displays “Fill all information!”
massage.
2. The system resumes at step 3.

UC Name Renting post box

UC-

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
03

data.[A1:A2]
4. The system display “Renting is successfully
completed” message.
5. The system display “Renting is unsuccessfully”
message.
6. The system resumes at step 2.
7. Use case ends.

21 | P a g e
 Post condition The account of the users registered (created).
Alternative course A1: The post box was rented by other user.
of action 1. The system displays “The post box was rented by
another user!” message.
2. The system resumes at step 2.

UC Name Material registration

UC Description Allows the postman and counter to recorded
information regarding to material stored in store
UC-04

room.
Actor Counter or postman
Precondition The counter and postman should have logged into
the system
Flow of event 1. They selects “Add material” menu.
2. They should complete and submits
material’s registration form by clicking
“Add” button.
3. The system checks and validates the entered
data.[A1:A2]
4. The system displays “material information
recorded” message
5. Use case ends
Post condition Material information is registered.
Alternative A1: Wrong data Entry Message
course of action 1. The system displays “Wrong data Entry!”
message.

22 | P a g e
 2. The system resumes at step 2.
A2: Missing of Required Information Message
3. The system displays “Fill all information!”
massage.
3. The system resumes at step 2.

UC Name Sent airmail register

UC Description Allows counter to register sent airmails.
Actor Counter
UC-05

Precondition The counter should have logged into the system

Flow of event 1. They selects “Add material” menu.
2. They should complete and submits airmail’s
registration form by clicking “Add” 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 A1: invalid data
course of action A.1 The system informs the counter the entered
data is invalid by displaying “you have entered
invalid data” message and prompts the user to
enter the data correctly.
A.2 Use click “ok” button.
A.3 Use case resume at step 2

23 | P a g e
 UC Name Received airmail registration
06
UC
UC Allows counter to register received airmails.
Description
Actor Counter
Precondition The Counter should have logged in to the system.
Flow of event 1. Counter selects “Add received airmail” menu.
2. Counter completes and submits the received
airmail registration form by clicking “Add”
button.
3. The system checks and validates the entered
data. [A1].
4. The system displays “airmail is successfully
registered” message
5. Use case ends.
Post condition Received airmail information is registered
Alternative A1: invalid data
course of action A.1 The system informs the counter the entered
data is invalid by displaying “you have entered
invalid data” message and prompts the user to enter
the data correctly.
A.2 Use click “ok” button.
A.3 Use case resume at step 2.

UC Name Search user

UC-07

UC Allow administrator to search or view user data

Description from the database.

24 | P a g e
 Actor Administrator
Precondition The administrator should have logged in to the
system.
Flow of event 1. The administrator selects the “Search” button.
2. The system requests the user to enter correct
registration number.
3. The system checks and validate the entered
registration number[A1]
4. The system display and view the searched
information
5. Use case ends.
Post condition Administrator will view the searched information.
Alternative A1: invalid registration number
course of action A.1 The system informs the administrator the
entered registration number is invalid by displaying
“you have entered invalid registration number”
message and prompts the administrator to enter the
registration number correctly.
A.2 Use click “ok” button.
A.3 Use case resume at step 2.

UC Name Update user

UC Allows administrator to update user information to
UC-08

Description the database.

Actor Administrator
Precondition The administrator should have logged in to the

25 | P a g e
 system.
Flow of event 1. The user selects the “Update” button.
2. The system requests the user to enter correct
registration number.
3. The system display and view the searched
information.
4. The administrator selects “clear” button.
5. The administrator fills update form
6. The administrator click “Add” Button
7. The system checks and validates the entered
data. [A1].
8. The system displays “update is successfully
completed” message.
9. Use case ends.
Post condition Administrator will view the searched information.
Alternative A1: invalid data
course of action A.1 System displays “Invalid data entries please
try again”
A.2 User click “ok” button.
A.3 Use case resume at step 7.

UC Name Delete user

UC Allows administrator to delete user information to
UC-09

Description the database.

Actor Administrator
Precondition The administrator should have logged in to the

26 | P a g e
 system.
Flow of event 1. The administrator enter registration number.
2. The administrator click “Search” button.
3. The system checks and validates the registration
number. [A1:A2].
4. The system displays the searched information.
5. The administrator click “Delete” button.
6. The system displays “Data is deleted” message.
7. Use case ends.
Post condition Data will be deleted from the database.
Alternative A1: Warning!
course of action 1. System displays “Are you sure to delete
this data?”
2. User click either “yes” button or “no”
button.
3. Use case resume at step 3.
A2: Invalid registration number
2 System displays” please the correct registration
number!”
3 Use case resume at step 3.

UC Name Search airmail

UC Allow counter to search or view user data from the
UC-10

Description database.
Actor Counter
Precondition The Counter should have logged in to the system.

27 | P a g e
 Flow of event 1. The user selects the “Search” button.
2. The system requests the user to enter correct
registration number.
3. The system checks and validates the entered
registration number [A1].
4. The system display and view the searched
information
5. Use case ends.
Post condition Counter will view the searched information.
Alternative A1: invalid data
course of action A.1 System displays “Invalid data entries please
try again”
A.2 User click “ok” button.
A.3 Use case resume at step 2.

UC Name Update airmail

UC Allow counter to update or change user data from
Description the database.
Actor Counter
Precondition The Counter should have logged in to the system.
UC-11

Flow of event 1. The counter selects the “Update” button.

2. The system requests the user to enter correct
registration number.
3. The system checks registration number.[A1]
4. The system display and view the searched
information.

28 | P a g e
 5. The counter selects the “clear” button.
6. The counter fills update form.
7. The counter click “Add” Button
8. The system displays “update is successfully
completed” message.
9. Use case ends.
Post condition Counter will view the updated information.
Alternative A1: invalid data
course of action A.1 System displays “Invalid data entries please
try again”
A.2 User click “ok” button.
A.3 Use case resume at step 3.

UC Name Delete airmail

UC Allow counter to update or change user data from the
Description database.
Actor Counter
Precondition The Counter should have logged in to the system.
Flow of event 1. The counter enter registration number.
UC-12

2. The counter click “Search” button.

3. The system checks and validates the registration
number.
4. The system displays the searched information.
5. The counter click “clear” button.
6. The counter enter registration number
7. The counter click “Delete” button.

29 | P a g e
 8. The system displays “Data is deleted” message.
9. Use case ends
Post condition Airmail data will be deleted from the database.
Alternative A1: Warning!
course of action 1. System displays “Are you sure to delete
this data?”
2. User click either “yes” button or “no ”
button.
3. Use case resume at step 3.
A2: Invalid registration number
1. System displays” please the correct
registration number!”
2. Use case resume at step 3

UC Name Search material

UC Allow postman to search or view material
Description
Actor Postman
Precondition The postman should have logged in to the system.
Flow of event 1. The store keeper selects the “Search” button.
UC-13

2. The system requests the user to enter correct

registration number.
3. The system checks and validates the entered
registration number
4. The system display and view the searched
information

30 | P a g e
 5. Use case ends.
Post condition Postman will view the updated information.

3.2 Sequence Diagram

Sequence diagram is a system model that is used to depict (show) 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.

SEQUENCE DIAGRAM FOR LOG IN

log in Database
Home System log
log in form controller <<boundery
paqge in
<<user <<controller >>
<<boundery <<boundery
interface>> >>
USER >> >>

1.start

2.create
3.display

4.enter username and password

5.LOG IN

8.invalid
6.submit
7.check

9.error messsage

10.valid
11.display

12.acknowledgement

31 | P a g e
SEQENCE DIAGRAM FOR RENT POST BOX

System log in Add post box menu rent post box form post box controller database
<<boundery>> <<boundery>> <<boundery>> <<controller>> <<boundery>>

COUNTER

1.start

2.click
3.create

4.enter username and password

5.log in
6.check 7.invalid

8.error message

10.store
9.valid

11.display
12.ackonwledgement

32 | P a g e
SEQUENCE DIAGRAM FOR CREATE ACCOUNT

create
account menu create
home page account database
item account page
controller

user

enter()
create()
create()
click() initiate()

display to user

fill field
check

validation

display message
account create

33 | P a g e
SEQENCE DIAGRAM FOR MATERIAL REGISTRATION

material matrial
add material
log in regstration control database
menu
<<boundary>> form <<controller> <<oundary>>
<<boundary>>
<<bondary>> >

postman

1.start

2.click

3.create

4.display

5.enter user nme password

6..log in 8.invalid
7.check

9.error message

10.valid

11.register

12.aknowledgment

34 | P a g e
SEQUENCE DIAGRAM FOR SENT AIR MAILL
sent air maill
add air maill
Home page system log in registration air maill database
menu
<<boundery> <<boundery> form controller <<bounder
<<boundery>
> > <<boundery> <<controller> y>>
>
COUNTER >

1.start

2.click
3.create
4.display
5.log in

6.enter user name and password

7.submit

8.check 9.invalid

10.error message

11.valid
12.register

13.display

14.accknowledgement

35 | P a g e
SEQUENCE DIAGRAM FOR RECIVE AIR MAILLS

recived air
add recieved maill air maill
system log in database
air maill menu registration controller
<<boundary>> <<boundary>>
<<bondary>> form <<controller>
<<boundary>>

COUNTER

1.start
2.create
3.display
4.log in
6.check
5.enter user name and password 7.invalid

8.error message

10.register 9.valid

11.acknowledgement

36 | P a g e
SEQUENCE DIAGRAM FOR MATERIAL SEARCHING

material
search search
add material registrati datbase
system log in control botton
menu on form <<bound
<<boundary>> <<controller <<bound
<<boundary>> <<bound ary>>
>> ary>>
ary>>

POST MAN

1.start

2.click
3.create

4.enter user name and password

6.invalid
5.click

7.error

9.accept 8.valid

10.submit

12.acknowledgement

3.3 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
37 | P a g e
 completion of these operations triggers 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).
ACTINITY DIAGRAM FOR LOG IN

Start

Enter name and

password

click in log in
button

return Invalid Valid open main page

End

38 | P a g e
ACTIVITY DIAGRAM OF REGISTER

Enter name and

password

Invalid

Verificati
on

Valid Register user

Select action Delete user

Search user

Update user

39 | P a g e
ACTIVITY DIAGRAM For REGSTER AIR MAILL selection

Enter name and

password

Invalid Register air

mails

Verification Delete air

mails

Valid Rent post

box
Select action
Update air
mails

Control air
mails

Mange post
box

40 | P a g e
ACTIVITY DIAGRAM FOR MATERIALS

Enter name and

password

Invalid

Verification
Register
materials

Delete
materials
Select action Valid

Search
materials

Update
materials

41 | P a g e
Activity diagram for CREATE ACCOUNT

START

Click on create
account button

Enter data

Retry Invalid Valid succes message

Verification

END

3.4 CLASS DIAGRAM

Class diagram depicts the system’s object structure. They show object
classes that the system is composed of as well as the relationships between
those object classes. UML class diagram show the classes of the system,
their inter-relationships, and the operations and attributes of the classes.
42 | P a g e
 CUSTOMER
REGISTRATION SERVICE
costomer name
service date
costomer ID registrater date
service time
costomer address registrater time
from service
costomer sex register number
to service
costomer phone register ID
+show time and date messages
costomer age +get information()
costomer birth date
+create account()

ADDRESS
country
city
region
zone
woreda
kebele
house number
phone
e-maill

+gets()

3.5 DEPLOYMENT DIAGRAM

The deployment diagram shows how the software components, processes,
and objects are deployed into the physical architecture of the system. It
shows the configuration of the hardware units (e.g. Computers,
communication devices, etc.) and how the software components are
distributed across the units. The deployment diagram for our project is
presented below.

43 | P a g e
Deployment diagrams are used to visualize the topology of the physical
components of a system where the software components are deployed.
So, deployment diagrams are used to describe the static deployment view
of a system. Deployment diagrams consist of nodes and their
relationships.

Web server <<Applicatio>>

Manage account :DB-Server
CLIENT

manages list of city

ADMINSTRATOR
Manages list Office
persistance
COUNTER
Manages list of Service
OPS-DB
Manages free charge fee
Customer

Manages delivery of mail

POSTMAN
POST MAN
Dispatch mail to receiver

Place mail sending order

44 | P a g e
 3.6 COLLABRATION DIAGRAM
COLLABRATION DIAGRAM FOR LOG IN
1.start

USER HOMEPAGE

4.Name&password
2.create
5.log in
3.display
7.validate
LOG IN
DATABASE
FORM
6.verify

COLLABRATION DIAGRAM FOR CREATE ACCOUNT

1:log in
2:validation
4:request account form 5:create account form
6:submite user info
7:check info

customer system
3:display message
8:show successful/unsuccessful message

10:create account

9:send detail

account

45 | P a g e
 COLLABRATION DIAGRAM FOR rent post box

1.enter name&password

CUSTOMER LOG IN
2.validate

5.add rent box

4.show form
3.display
9.display succeed

7.Validate
8.succeed

DATABASE POST BOX MENU

6.verify

3.7 COMPONENT DIAGRAM

Component diagram depicts the components that compose an
application, system, or enterprise. The components, their
interrelationships, interactions, and their public interfaces are depicted.
Component diagrams are physical analogs of class diagram.

46 | P a g e
 Check avialability Home page

Create account
Fill form

Counter
Customer

Post man
Adimistrator

Access database

47 | P a g e
 3.8 ENTITY RELATION MODEL(ER-DIAGRAM)
BIRTH
L-NAME DATE
M-NAME

DATE TIME NUMBER SERVICE TIME

F-NAME NAME SEX

AGE 1 * 1..1
REGISTER
CUSTOMER SERVICE
PHONE

ID
ADDRESS
KEBELE SERVICE
NUMBER DATE
TO SERVICE
COUNTERY ZONE
WOREDA
FROM
SERVICE
CITY

RELATION SCHEMA FOR CUSTOMER

ID F-NAME M-NAME L-NAME SEX AGE BIRTH DATE COUNTERY CITY ZONE WOREDA SERVICE NUMBER

RELATION SCHEMA FOR PHONE

PHONE CUSTOMER ID

48 | P a g e
RELATION SCHEMA FOR SERVICE
SERVICE SERVICE SERVICE TO FROM CUSTOMER
NUMBER TIME DATE SERVICE SERVICE ID

RELATION SCHEMA CUSTOMER REGIST SERVICE

CUSTOMER SERVICE NUMBER DATE TIME YEAR
ID NUMBER

3.9 CLASS TYPE ARCHITECTURE

User interface prototyping (UI) is an interactive analysis technique in
which users are actively involved in the mocking-up of the User Interface
for a system [2]. The team has conducted user interface prototyping and
found the following major user interfaces.

49 | P a g e
 User interface layer ()

Controller/process
layer

System layer
Business /domain layer

Persistence layer

Persistence
store(s)/data store

1. User interface layer:-

 The user interface layer is generally made up of classes that
implement screens and reports.
 User –interface classes are allowed to send messages to classes
within the domain /business layer, the controller /process layer and
the system layer.
 User-interface classes should not directly access your persistence
mechanisms. By encapsulating the business logic of our application
in domain/business classes and controller /process classes, and not
in our user interface, we are able to use that business logic in more
than one place. for example ,you could develop a screen that
displays that total produced by an instance of the domain /business
class as well as a report that does the same.

50 | P a g e
  To obtain information it must interact with objects in the domain
/business layer ,which in turn interact with the persistence layer to
obtain the objects in your persistence mechanism
 2. Business/domain layer:-
 The domain/business layer implements the domain the
domain/business layer of our application
 Are allowed to send messages to classes within the system layer
and the persistence layer.
 Domain/business classes should not directly access your
persistence mechanisms.
 Just like we do not want to allow user –interface classes too
directly access information contained in your persistence
mechanism, neither do you want to.
 Allow domain/business layer and controller /process to do so.
3. System layer:-
 The layer is implemented on the client and that domain
/business, persistence, and system classes are implemented
on the server.
4. Controller /process layer:-
 Implemented message between system layer and
business/process layer.
 The layer is implemented between system layer and
business/domain layer.
 It is directed access information from persistence layer
since another layer is finding between persistence and
controller /process layer.

5. A persistence layer :-
 Encapsulates the behavior needed to make objects
persistent, in other words to read.
 Write, and delete objects to/from permanent storage.
Persistence layer should support:
 A persistence mechanism is any technology that can be
used to permanently store objects for later update, retrieval

51 | P a g e
 and/or deletions. possible persistence mechanisms include
flat files ,relational data bases, object-relational databases
,hierarchical databases ,network data bases, and object
bases.

Home Page

It is a page in which the user first interacts and gets all the information.

Login Page

LOG IN FORM FOR ADMINSTRATOR

52 | P a g e
LOG IN FORM FOR POST MAN

LOG IN FORM FOR COUNTER

53 | P a g e
LOG IN FORM FOR CUSTOMER

54 | P a g e
It is a page where administrator (post office manager) will navigate to,
when he has first login to the system.
Employee Home Page

3.10 STATE CHART DIAGRAM

State machine diagram or state chart diagram, is an illustration of the
states an object can attain as well as the transitions between those states.
Is used to model dynamic nature of a system
The main purpose of state chart diagram is to model reactive system.

55 | P a g e
State chart diagram for log in

Enter name and

START password

Log in
Log in to the
system

click
invalid

Process of verifying
password is
whether correct
valid

Processing to open
main page

END

56 | P a g e
State chart diagram for MATERIAL
Registration

click start

ADD MATERIAL

Click add material menu

REGISTER MATERIAL

NO

CHECK VALIDITY

YES

SUCCESSFULY REGISTERED

end

57 | P a g e
STATE DIAGRAM FOR SEND OR RECIVE AIR MAILLS

START

Enter name and password

entered

invalid

Verification

Select option

Select

Select air maill

Selected

Send/recive

sent/recived

END

58 | P a g e
Unit four
Recommendation and conclusion
4.1 Conclusion
 In this project we will develop online post office management
system that facilitates various activities in management and delivery.
The system is made up of web application. As the specified scope
the developed software has achieved its objective by solving the
problems identified. As the computing technologies are being
implemented in many of the organization and being ultimate choice
for fast, accurate and secured information management, the team
also believes this system will help the post office introduces the
company to look to ward the computing technology. Although it is
impossible to list all the result of this system towards every
respective of the organization, Administrator and employees the
team has tried its best to develop efficient system to support the
organization and the user of the system. Although applying and
becoming familiar with the new system is somewhat difficult, the
system will entirely substitute the current spread sheet system of the
company. This will in turn make service delivery efficient, effective,
simple and faster. In general, the project contributes an initial work

59 | P a g e
 on post office and needs great effort on similar project in future
application.

4.2 Recommendation
 Nowadays, the world is highly becoming a competitive world.
Organizations have to divert their attention on using the recent
technology to be on the first line and competitive. This can be real if
they are able to use information communication technology (ICT)
to successfully achieve their objective. As the team described in this
document, almost all activities of the organization is done on manual
basis. From the various facts that constitute the project, the following
recommendations have come to light:
 Attention should be given to the existing practice in the design,
development and utilization of the new system.

 Serious consideration should be given for the introduction of the new

system…

 Behavioral chance of the users of the system to adapt the new system.

 There should be a network infrastructure in order to connect the

different user computers in that live in different place.

 In general, this project contributes an initial work on online post

office management system for Post Office organization. But, this
work needs to mature in other similar projects in the future. We
recommended also that Post Office organization will take this
opportunity to replace the existing manual system with the enhanced
we provide.

60 | P a g e
 4.3 Reference
 Douglas Bell “Software Engineering for Students,”, (4rd Edition),
2001
 James Rumbaugh, “The Unified Modeling Language User Guide”
(2rd Edition), 2004
 Joseph Schuller, SAMS Teach Yourself UML in 24 Hours (3nd
Edition)
 Michele Cyran “Database Concepts” release 2, October 2005

61 | P a g e