PostOffice (Repaired)

8/10/2019 PostOffice (Repaired)

1/76

DEBRE BERHAN UNIVERSITY

SCHOOL OF COMPUTING SCIENCE

DEPARTMENT OF COMPUTER SCIENCE

ONLINE POST OFFICE MANAGEMENT SYSTEM

BY:

NAME ID

1.Besufikad Mulat 152/03

2.Juhar Seid 168/03

3.Lake Mekuriaw 169/03

4.

Natnael Moges 178/03

5.Yemane Kenife 187/03

INDUSTRIAL PROJECT I AND II

ADVISOR: CHALI ABERHAM

FINAL PROJECT SUBMITED TO DEPARETEMENT OF COMPUTER

SCIENCE IN PARTIAL FULFILLEMENT OF THE REQUIREMENTS

FOR THE DEGREE OF BACHELOR OF SCIENCE IN COMPUTER

SCIENCE

JUNE, 2014

DEBRE BERHAN, ETHIOPIA


2/76

PROJECT TITLE: ONLINE POST OFFICE MANAGEMENT SYSTEM

Advisors Name: _____________________________________

School: __________________________

Department: ______________________

Signature: _____________ Date: ______/______/__________

Approved By:

_________________________________________ ________/______/_______

Computer Science Department Head Date

_________________________________________ ________/_______/________

Dean of School of Computing Date

June, 2014 G.C

DEBRE BERHAN UNIVERSITY, ETHIOPIA


3/76

Acknowledgment

First of all we would like to thank to our enormous God for blessing us every time, everywhere

to perform our task with a healthy condition.

We would like to thank to our Advisor Mr. Chale.T for his talent and best effort, in which he

can enforce us to have a massive knowledge about the project to easily familiarize with theconcept of project development.

Then we express our deep gratitude to our Department Head Mr. GETACHEW .M,our friends

for their encouragement and support for guiding us towards the project.

Secondly we would like to thank Debre Berehan post office manager personnel for his partial

willingness of interview, patience in answering to our numerous questions, giving existing

activity materials and reading materials that help us to precede our project.


4/76

i

Table of Contents Page

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

1 Introduction of the project ...................................................................................................................... 1

1.1 Back ground of the organization ...................................................................................................... 1

1.2 Structure of the organization ............................................................................................................ 2

1.3 Statement of the problem ................................................................................................................. 2

1.4 The objective of the project ............................................................................................................. 2

1.4.1 General objective ....................................................................................................................... 2

1.4.2 Specific objective ...................................................................................................................... 2

1.5 Methodology and Tools ................................................................................................................... 3

1.5.1 Fact Finding Techniques ........................................................................................................... 3

1.5.2 System analysis and design techniques ..................................................................................... 4

1.5.3 Tools used in the project ........................................................................................................... 4

1.6 Scope of the project ......................................................................................................................... 5

1.7 Feasibility report .............................................................................................................................. 5

1.8 Gantt chart ........................................................................................................................................ 9

1.9 Team organization ......................................................................................................................... 10

CHAPTER TWO ........................................................................................................................................ 11

2 DESCRIBING THE EXISTING SYSTEM ......................................................................................... 11

2.1 Introduction .................................................................................................................................... 11

2.2 Description of the existing system ................................................................................................. 11

2.3 Player of the existing system ......................................................................................................... 11

2.4 Work flow the existing system ...................................................................................................... 12

2.5 Report generating of existing system............................................................................................. 12

2.6 Business Rules in the Existing System .......................................................................................... 12

2.7 Paper document system system of the existing system.................................................................. 13

2.8 Problem in the existing system ...................................................................................................... 13

2.9 practice to be preserved ................................................................................................................. 14

2.10 Alternative solution ........................................................................................................................ 15

2.11 Proposed system ............................................................................................................................ 15

2.11.1 Functional requirement of the project ..................................................................................... 15

2.11.2Non functional requirement..................................................................................................... 16


5/76

ii

CHAPTER THREE .................................................................................................................................... 17

3 ANALYSIS DELIVERABLES OF THE NEW SYSTEM.................................................................. 17

3.1 Introduction .................................................................................................................................... 17

3.2 Use case diagram of post office ..................................................................................................... 17

3.3 Analysis level of class diagram...................................................................................................... 22

3.4 Sequence diagram .......................................................................................................................... 23

3.5 Activity diagram ............................................................................................................................ 26

CHAPTER FOUR ....................................................................................................................................... 30

4 DESIGN DELIVERABLE OF THE NEW SYSTEM ......................................................................... 30

4.1 INTRODUCTION............................................................................................................................... 30

4.2 DESIGN CLASS DIAGRAM ................................................................................................................ 30

4.3 Collaboration diagram ................................................................................................................... 31

4.4 State chart diagram ........................................................................................................................ 344.5 Database design ............................................................................................................................. 35

CHAPTER FIVE ........................................................................................................................................ 39

5 Implementation deliverable of the new system .................................................................................... 39

5.1 Introduction .................................................................................................................................... 39

5.2 Component diagram ....................................................................................................................... 39

5.3 Deployment diagram ...................................................................................................................... 41

5.4 User Interface ................................................................................................................................. 42

CHAPTER SIX ........................................................................................................................................... 45

6 PROTOTYPE DEVELOPMENT ........................................................................................................ 45

CHAPTER SEVEN .................................................................................................................................... 64

7 Conclusion and recommendation ......................................................................................................... 64

7.1 Conclusion ..................................................................................................................................... 64

7.2 Recommendations .......................................................................................................................... 64

References: .................................................................................................................................................. 66


6/76

iii

List table page

Table1: hard wear cost schedule9

Table2: software cost schedule .9

Table3: gant chart. 10

Table4: team organization.11

Table5: use case login21

Table6: use case registration22

Table7: use case place order23

Table8: use case search order24

Table9: use case generate report..25


7/76

iv

LIST OF FIGURE

Figure1: sender registration form14

Figure2: use case diagram20

Figure3: class diagram of post office.28

Figure4: login sequence diagram30

Figure5: placing order of sequence of diagram.31

Figure7: cancel order sequence diagram.33

Figure8: process order sequence diagram..34

Figure10: generate report sequence diagram.36Figure11: login form of activity diagram..38

Figure12: placing order of activity diagram39

Figure13: cancel order of activity diagram40

Figure14: search record of activity diagram..41

Figure15: generate report of activity diagram42

Figure16: design of class diagram.45

Figure17: login form of collaboration diagram47

Figure18: placing order of collaboration diagram..48

Figure20: cancel order of collaboration diagram.50

Figure22: process order of collaboration diagram..51

Figure24: manager report of collaboration diagram...53

Figure25 25: login page of state chart diagram54

Figure26:-placing order state chart diagram55

Figure27: cancele order of stat chart diagram....56


8/76

v

Figure28: search custom...56

Figure29: generate report of state chart diagram.57

Figure30: organization database..59

Figure31: bank database60


9/76

vi

Abstraction of the project

The project online post office management deals with the mechanism of order the material this

project will help to order material in online and user in managing the various types of records

online. The product will help the user to work in highly effective and efficient and efficient

environment.

On line post office management system mainly provides effective and fast data processing and

controlling of record. In designing such a system, PHP has been employed as a development

language and MYSQL as a backend database with CSS implemented for the interface and java

script can use for from validation.

In the manual System, there are number of inefficiencies that reserved user faces.The

information retrieval is one of the most problems. It is very difficult to gather the overall

performance reports of the customer. Generally, the main goal of online post office management

system is to shorten data-processing time, to reduce errors, to improve the accuracy of input and

reduce employee work load.


10/76

vii

List of abbreviation

Sql structuredquery lanquage

Umlunified modeling lanquage

Cdcompact disc

Atmautomated teller machine

Ucuse case

Phphayper text pre processor

urluniform resource locator

dbms data base management system

csscascaded style sheet


11/76

1

CHAPTER ONE

1 Introduction of the projectThe e-Post Office is the shopping portal of the world-renowned postal service on the Internet and

an additional distribution channel. It sells Stamps, Postcards, Packets, and Cartons and has

services like courier, selling mobile cards, mobile phone, etc. Under e-post office website many

products and services can be ordered, that are also available in the office.

The e-Post Office is expanded permanently through new products and services in order to offer a

product collection corresponding to the market. Private customer and business customers can

order the selected products of the postal service online quickly and comfortably. Besides this,

the e-Services offer new flexibility through e-Packet, the pickup order for packages over the

Internet as well as the online forwarding order and storage order. For the case of the absence or

the move, one can let delegate here the after shipment of the postal service at another address or

store the letter shipments. The customers can register themselves and can be served individually.

Target groups of customer of the e-Post Office are predominantly little and middle-class

business. The customers can have a payment alternative through credit card. In order to use the

load writing procedure, the customer registers itself in the e-Post Office and receives a login for

its purchases name. You have to develop this website, which captures the above functionality. It

is an Internet application.

1.1

Back ground of the organization

Debre Birhan post office established in 1933 E.C.it found in Amhara region far from 130

kilometer from Addis Ababa .it performs many activity to satisfy the customer need, the main

service to performed in the post office is Door to door acceptance and delivery service, Rental of

post office box, Sell of postage stamps, involves post card, Business reply coupon service /sale

and exchange, and Post shop service /sell of stationary and other postal material.


12/76

2

1.2

Structure of the organization

Fig 1. Structure of the organization

1.3

Statement of the problem

The current send and receive system of Debre Birhan post office is most of work manually and

using of different techniques like announce on board, phone call and, if the customer want to buy

material they cant know the materialavailable or not available in the counter of the office.

Most of the time employee information record in manual system as a result if lead the record

redundancy and not manage properly. The Debre Birhan post office has the problem because it

works manually.

1.4

The objective of the project

1.4.1 General objective

The general objective of the project is to automate the existing manual system and to develop

web based post office automation system.

1.4.2

Specific objective

The specific objectives of the project are:

Enable to manage the users requestin timely manner.

Computerized reservation.

Enables to generate reports periodically.

Helps to store the data in a computerized.

To generate report quickly.

To search customer information in a few time.

Zone mana er

Finance AuditorMessage room

Federal

Seller


13/76

3

1.5

Methodology and Tools

1.5.1

Fact Finding Techniques

The Method and techniques used to analyze the existing system and designing electronic system

includes, interview, questionnaires and observation. Those methods which help us to gather the

required data to analyze our project and those methods selected due to the time and the

organizations willingness.

1.5.1.1.

Interviewing

It is the primary technique used to elicit the necessary information from the manager of post

office who takes the responsibility to manage post office. The manager gives us valuable

information about the overall activity they perform, concerning on how they sell the ticket and

the show time of the movies.

1.5.1.2. Observation

Site visiting was made to support the interview done with aim to understand the overall activities

in the post office. The team members have observed physically by going to the place. Also the

team has seen that there was no any well developed computerized and online system in the post

office and also information about the post and the service that the post office provides were not

available easily.

1.5.1.3 Questionnaires

In the method of data gathering we prepared questionnaires for analyzing the post office

activities to understand the current system architecture of post office. Some of the questionnaires

are the following:

How people or customers get service?

What is the organizational structure of post office?

How people or customers get information about the post office ?

How to manage the customer?

How the customers buy the material?


14/76

4

1.5.2

System analysis and design techniques

We have decided to propose this system by raising some problem and draw back with the current

system that is on use. These analyses were done through gathering or collecting data in the

course of traditional mechanisms, organized, structured, and analyzed using object oriented,

system analysis, design tools, and techniques. The tools have helped in building the logical and

the physical model of the system and this in turn has enabled to have a better understanding of

the system. The reason is why we are using object oriented programming are we can write clear,

more reliable, more easily mentioned programs.

We prefer object oriented approach the following advantages:-

To simplify the design and implementation of complex programs.

Increase reusability: support reusability of the systems code.

Increased extensibility: to add and change the existing module without affecting

the rest of the program.

To make it easier for teams of designer and programmers to work on to decrease

the burden of maintenance.

1.5.3 Tools used in the project

In the analysis, design and implementation of the project, the team uses the following front end

and back end software which are used for developing the proposed system.

Software requirement

Microsoft SQL server

Microsoft office 2007

Rational roses

A pache Xamp server

E draw

Visual paradigm for UML11.0

Notepad++

Hardware requirements

computer

CD

Flash disk


15/76

5

Pen

A4size paper

1.6

Scope of the project

The project that we are trying to focus on post office system will cover only on the DebreBrihan

city branch. The project will cover the following activities:-

Placing order item online.

Registration

Online bill generation for orders.

Online tracking and shipment.

Searching of customer record.

Manage user account

To generate report.Although we have tried to do the best and try to do well all the things that are possible in a e post office,

but still the system contains some of the limitations. The reason of this limitation is the time constraints.

Time is the major problem. We have to deliver the project in a particular timeperiod. Thats why wehave

to leave some topics that actually we want to cover. Limitations of the system:-

The project may be difficult to apply at the end i.e. our society is most illiteracy and most

live in rural area.

The project asks high technical support and maintenance.

The project does not include the taxation system. Because of the complexity of

calculation and not availability of time.

The payment system concerned/restricted on the commercial bank only and focus on the

stored account value or deposit system i.e. not include the visa card, smart card, ATM .

The tracking system used only at destination point because it system need many material

like RFID and smart phone.

After removing these and other minor limitations I hope this project will be very efficient and effective.

1.7 Feasibi li ty report

Preliminary investigation examine project feasibility, the likelihood the system will be useful to

the organization. The main objective of the feasibility study is to test the Technical, Operational

and Economical feasibility for adding new modules and debugging old running system. All


16/76

6

system is feasible if they are unlimited resources and infinite time. There are aspects in the

feasibility study portion of the preliminary investigation:

Technical Feasibility

Operation Feasibility

Economical Feasibility

1.7.1. Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation includes the

following:

Does the necessary technology exist to do what is suggested?

Do the proposed equipments have the technical capacity to hold the data required to use

the new system?

Will the proposed system provide adequate response to inquiries, regardless of thenumber or location of users?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy, reliability, ease of access and data security?

Earlier no system existed to provide to the needs of Secure Infrastructure Implementation

System. The current system developed is technically feasible. It is a web based user interface.

Thus it provides an easy access to the users. The databases purpose is to create, establish and

maintain a workflow among various entities in order to facilitate all concerned users in their

various capacities or roles. Permission to the users would be granted based on the roles specified.

Therefore, it provides the technical guarantee of accuracy, reliability and security. The work for

the project is done with the current equipment and existing software technology. Necessary

bandwidth exists for providing a fast feedback to the users irrespective of the number of users

using the system.

1.7.2. Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information system. That will

meet the organizations operating requirements. Operational feasibility aspects of the project are

to be taken as an important part of the project implementation. Some of the important issues

raised are to test the operational feasibility of a project includes the following: -

Is there sufficient support for the management from the users?


17/76

7

Will the system be used and work properly if it is being developed and implemented?

Will there be any resistance from the user that will undermine the possible application

benefits?

This system is targeted to be in accordance with the above-mentioned issues. Beforehand, the

management issues and user requirements have been taken into consideration. So there is no

question of resistance from the users that can undermine the possible application benefits.

The well-planned design would ensure the optimal utilization of the computer resources and

would help in the improvement of performance

1.7.3. Economic Feasibility

A system can be developed technically and that will be used if installed must still be a good

investment for the organization. In the economical feasibility, the development cost in creating

the system is evaluated against the ultimate benefit derived from the new systems. Financial

benefits must equal or exceed the costs. The system is economically feasible. It does not require

any addition hardware or software. Since the interface for this system is developed using the

existing resources and technologies available at the university, There is nominal expenditure and

economical feasibility for certain.

Cost schedule

Hardware cost

No Material Amount Price per unit Total price

1 A4 size paper 3 Destin 95 Birr 285Birr

2 pen 6 5Birr 30Birr

3 Flash disk 3 300 Birr 900Birr

4. For Print 100 sheet 1 Birr 100Birr

5 CD 8 8 Birr 89 Birr

6 Dell computer 1 10,000 Birr 10,000 Birr

Total

11,404.00 birr

Table 1: Hardware cost schedule


18/76

8

Software cost

Table 2:Software cost schedule

No Material Price per unit

1 Microsoft office 2007 free

2 Microsoft office 2010 free

3 Micro soft Visio 2008 free

4 Apache Xamp server free

5 Notepad++ free

total

00.00 Birr


19/76

9

1.8

Gantt chart

Gantt chart is a graphical representation of project that shows each task as a

horizontal bar whose length is proportional to its time for completion.

Month November December January February March April may june

Task

name

week week week week week week week week

1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 1 2 3 4 1 2

Title

selection

Proposal

writing

Requireme

nt-

analysis

Design

phase

implement

ation

presention


20/76

10

Table 3: Gantt chart

1.9 Team organization

To assign own work to the group member is to reduce the work load and to accomplish the

project on time.

Name Tasks

Besufikad mulat Data collector

Natnael moges Requirement analysis

Yemane kinfe System tester

Lake mekuriaw Vice leader (System designer)

Juhar seid G leader (project Implementer)

Table 4: team organization


21/76

11

CHAPTER TWO

2 DESCRIBING THE EXISTING SYSTEM

2.1

Introduction

Studying the existing system brings about an important contribution to the entire development

process. It is only after doing this phase that we can realize what is going wrong, what to change,

what activity or practice to encourage, and what alternative solution to propose.

2.2 Descri ption of the exi sting system

The Debre Berehan post office is using a manual system. This system has some drawback like

consuming a lot of manpower which leads to be unmanageable. Since it works manually,

information accessing is very slow and to get some task to be accomplished it goes through much

process and this is time consuming. The post office System has four major subsystems namely

selling material , send post, receive post, order product . Among these subsystems we are going

to automate are: online payment and ordering product.

Post office selling many material available in the office such as stamp, mobile card ,mobile

phone. if some want to buy the material they will come to the office .if the material is not

available in the office the user came back without buying the material.

The post office perform the activity sending post from one country to other country the activity

performed by registering the sender and receiver information in manually, and receive material

from other branch of the post office after receiving the material to announce the reached material

in that office in post office board. The customer also see the reached material from office board

and receive material by their id or post number.

In this time the user can not order the sending item set on remote area so it leads to increase the

crowed of people around the post office and the customer stayed till get to chance to order the

send item. As the result the customer consume more time and many.

The customer cannot see the material where it found. They have not chance to attend the material

where place it found.

2.3

Player of the exi sting system

Manager:

he generates reports.

he manages or leads the other employees.

Staff workers:-they perform the activities of the post office.


22/76

12

2.4

Work f low the exi sting system

In Debreberhan post office working flow in the manager to manage day to day activities of the

staff worker, to control the financial process, and the sealer also power to sell the materials and

available in the post office. The staff workers is to perform their duty.

2.5

Report generati ng of exi sting systemReport generating in the post office the head office generates report weekly and monthly

what activities are performed, the report is manual, it takes time to reach the main office. This

report which includes all works in the office. This report submits to Addis Ababa to which the

head office is located, and the office sends the response to the branch office which is the sender.

2.6 Business Rules in the Existing System

A business rule is effectively an operating principle or polices that we try to specify for both the

existing system and the new system must satisfy. The business rule is a principle or a policy inwhich 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:

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:

Business Rule1: the customer uses the application properly.

Business Rule2: the customer fills the form properly.

Business Rule3: the system gives fast responses to the customer.

Business rule4: the system helps to arrive the books to the customer place.

Business rule5: it provides more options to customers.

Thise system allow the customer order all time.


23/76

13

2.7

Paper document system system of the exi sting system

In any business documents and forms are the fundamental for the existence of different process.

The existing post office uses the following paper documents:

Employee registration form

The respective departments will fill the necessary description of the employee they need from the

post office in this form.

Employee information form

It is used to record all the necessary details and amount of each employee registered in the post

office.

Sender registration form

It used to record the all necessary details of the sender .

Fig2: sender registration form

2.8

Problem in the existing system

Fig:1sender registration form

A . Lack of immediate retrieval of information

In manual system, lot of time is wasted in retrieving information. Much searching is required

before required is found. This wastes a lot of time of the user as well as the person.

B . Lack of immediate information storage

In manual system, it is difficult to store information at proper place at that very moment. This is

because the person is unable to quickly locate the place where the information is to be stored.

C . Prompts updating not possible

Changes are quite natural in all walks of life. Information and stored data also changes from time

to time. These changes should be incorporated in the working also to keep the information up to

Sender name .

Receiver name Employee sign .

Destination

PostageIn figs Birr cents..

In words


24/76

14

date. However, bringing about changes through the manual system is a slow and tedious process

because of which inaccurate information storage occurs.

D .Unplanned working

The manual system lacks the element of planned working. Records are not properly maintained.

This creates a lot of problems at times like during information retrieval and storage

E. Insignificant generation of managerial and strategic reports

In manual system, reports for management are difficult to be generated and strategic reports are

impossible. This is because for these reports proper storage of information, its retrieval and its

filtering are very important and very tough in manual system.

F . Accuracy

The manual system lacks accuracy in working and a number of operations may be performed

incorrectly, the computations that are done in the organization may be incorrect and whatever are

generated in the system may be inaccurate.

G. Reliability

The reliability of the manual system is considered to be low because of the above given reasons

including the fact that TO error is human. Any task that is performed by men, always contain

the risk of errors.

H. Redundancy of information

In manual system, particular information may be stored at a number of places, lending to

redundancy. Redundancy of data or information creates a number of problems storage space is

wasted; changes at one

place are to be made at a number of places and so on.

2.9

practice to be preserved

Even if the existing post office of debre berhan it running manually it has its own strength. Its

strengths must be preserved to enhance the new system. The following strength are outlined to be

preserved in the automated system.

For a single Employee it has a unique Employee number(employee id).

Using the Employee registration from when Employee registered .

Generating report periodically on Employees information such as compensation and

evaluation.

All forms and documents mentioned above must be used.


25/76


26/76

16

Functional Requirements are those that refer to the functionality of the system about the services it will

provide to the user. The following is a list of functionality of the system

Users of the system:Customer is the user of the system. An administrator of the website is the super-

user. When the user types in the URL of the website, a Welcome page is shown which has a menu on the

left hand side, a banner at the top and any related links to other sites. This site contains an online catalog

for the user. User has to login to Welcome Page before ordering anything. Login functionality should

check the authenticity of the user from the database.

The functionality requirement is:-

Placing order online-order the material to buy from post office shop.

Online bill generation for orders-after the customer order the material they can print the bill

directly on the internet.

Online payment of orders-after the customer order the material the system generate payment page

the customer can perform payment online without go to the post office. It reduce the time of the

customer and reduce work load of the staff worker.

Searching of customer record-the administrator search customer recorded from the database.

Report generating of the administrator and manager can generate the report daily, weekly,

monthly report.

2.11.2Non functional requirement

Non functional requirement is deals with the characteristics of the system that cannot be experienced as

the function. such as the maintainability of the system, portability of the system, and usability of the

system. . Nonfunctional Requirements pertain to other information needed to produce the correct system

and are detailed separately.

Which includes:-

User interface: since users of the system involved people with different back ground,

the system should be made with user friendly window type.

Performance and Access time: The system will provide fast access to the customer

according to their privilege.

Security: the system should enable to task a back up at any time in point in point and

able to restore from backups.


27/76

17

CHAPTER THREE

3 ANALYSIS DELIVERABLES OF THE NEW SYSTEM

3.1Introduction

Model is an abstraction of the real world. It allows us to deal with the complexity current

in a real-world problem by focusing on the essential and interesting features of an application.

The techniques and associated notation used for object oriented analysis and design in

incorporated in to a standard objectoriented language called unify Modeling language (UML).

An important goal of requirement modeling is come to an understanding of the useless problem

that the new system is to address. This chapter focuses on developing the requirement and

analysis models for the new system using the UML use case model, sequence diagram, activity

diagram and class diagram and interface prototyping are also included.

3.2Use case diagram of post off ice

A use case is a sequence of action that provides a measurable value to an actor another way to

look at it is that a use case describes a way to which a real world to interacts with the system. An

essential use case sometimes called a business the case is simplified, abstract, generalized use

case that captures the intention of the user in a technology and implementation independent

manner.

The case models are used to document the behavioral (functional) requirement of a system or

the what of the system (Scott W. Ambler 2001)

A use case describes a sequence of action that provides a measurable value to an actor

and draw as a horizontal ellipse.

An actor is a person, organization, or external system that plays a role in one or more

interactions with the system and draw as stickman figure.

Relationship between actors and use cases exists whenever an actor is involved with an

interaction described by a use case and modeled as a line connecting use cases and actors.


28/76

18

Login

Cancel Order

Processing Order

Search customer

Manage user account

genrate report

Customer

Admin

Manager

make paymentextends

tracking order

tracking order

Regsiter


29/76

19

Fig 2: Use case diagram

Use case number UC-01

Use case name Login

Priority High

Actor Administrator ,manager and customer

Description This use case describes how they are to log intopost office system. Use case to ensure security insystem usage.

Pre condition The user must have user name and password.

Post condition User gets access to the system according to theirpredefined system privilege and family he/shelogout or turn off the page.

Basic course of action User action system response

1.They are on theHome page to loginTo the system.3.They enter user nameandPassword,click on Loginbutton

2.The systempromtes them toenter Username,Password.4.The systemverifies that all thefield have beenfilled out and valid.5. The systemsuccessfully logsthem in the system.6.Use case exit.

Alternate course action 7. if all fields are not filled out or not matched tothe user name and password the system notifiesthe actor a message to verify User name andpassword and then goses back or return to setep4 of basic course of Action to enter again.

Table 5:login of use case


30/76

20


Use case name Register

Priority High

Actor Administrator and customer

Description Description: use case to register new customer

Pre condition Customer must be able to fill all the criteria Perfectly form.

Post condition Customer registered.


1.not include login use case.2.new customer select registerslink.3.the customer fill necessary data

.

4. submit

5. system responds byresponding criteria form.6.The system displaysuccessfully registered.

7. use case ends.

Aleterante course action 6.1 system display an in correct message.6.2 use case returns to step 4 of main use case.

Tabel6: Register of use case


31/76


32/76

22

table 6: mange user account of use case

3.3

Analysis level of class diagram

Class Diagrams are used to represent the structure of the system in terms of objects, their notes

and nature of relationship between classes. It shows the static features of the objects and do not

represent any particular processing


Use case name Manger user account

Priority high

Actor administrator

Description These use case permits administrator to manageuser account.

Pre condition User already has account and hasnt wants tocreate an account or to change their account.

Post condition User accounts successfully changes or crate.


1.the admin wants tocreate or modify user

account.2.the administrator openschange account page andclicks on that clicks onthat link.4.the administratormodifies or creates theaccount .

3. the systemdisplays a form.

5.the systemverifies the filed outcorrectly andchecks validity ofconfirmationnumber ,then popupa message to verifythe cancelling.6. the systemmodifies anddisplay a messagethat account is crate

or modifiessuccessfully.

8. use case exit

Alternate course action 5.1 if the administrator enters invalid character inthe system goes back or returns to step 4 of basiccourse of action . to fill invalid or the empty fieldagain.6.1 if the administrator clicks NO modifyaccount will be terminated.


33/76

23

Class diagrams are the most common diagrams used in UML. Class diagram consists of classes,

interfaces, associations and collaboration. Class diagrams basically represent the object oriented

view of a system which is static in nature.

Fig 3:class digram of post office

3.4

Sequence diagram

Sequence diagram is an interaction diagram. From the name it is clear that the diagram deals

with some sequences, which are the sequence of messages flowing from one object to another.

Interaction among the components of a system is very important from implementation and

execution perspective. So Sequence diagram is used to visualize the sequence of calls in a systemto perform a specific functionality


34/76

24

Fig4: login of sequence diagram

: Usermain window (Ul) login page main page (Ul) user account

(DB)

1 wants to login2 display login page

3 enter user name and password

4 validate user name and password ()

5 verify the user name and password ()

6 disply


35/76

25

Fig5:place order of sequence diagram

Admin : Admincustomer page order link order page payment page data base

1. activate()

2.click()

3.display()

4. fill the form()

5. validate the form()

6. verifiy the form()

7. display()

8.fill the payment form()

9.check balance()

10 bill generate()


36/76

26

Fig6: generate report of sequence diagram

3.5 Activity diagram

Activity diagram describes the flow of control in a system. So it consists of activities and links.

The flow can be sequential, concurrent or branched.

Activities are nothing but the functions of a system. Numbers of activity diagrams are prepared

to capture the entire flow in a system. Activity diagrams are used to visualize the flow of controls

in a system. This is prepared to have an idea of how the system will work when executed.

manager : managermanager

page

report link() report form controllerdata base

1 activate()

2 select()

3 display()

4 fill form()

5 validate()

6 continue step 5()

8. check()

7 try agin()

9 display the result()


37/76

27

Fig7: login of activity diagram

fill login form

Login data

display error

message

display home

page

data base

check valid

user


38/76

28

Fig8: cancel order activity diagram

fill cancer order

form

Canel data

Display error

message.

display cancel

conformation

Data base

check

validatein valid

valid

cancelerUsre


39/76

29

Fig9: generate report of activity diagram

fill report form

report data

dissplay errormesage

generate report

Data Base

generate

report()

valid

in valid

systemmanager


40/76

30

CHAPTER FOUR

4 DESIGN DELIVERABLE OF THE NEW SYSTEM

4.1 INTRODUCTION

System design is the transformation of the analysis model into a system design model. Up to

now we were in the problem domain. System design is the first part to get into the solution

domain in a software development. This chapter focuses on transforming the analysis model into

the design model that takes into account the non functional requirements and constraints

described in the problem statement and requirement analysis sections discussed earlier.

The purpose of designing is to show the direction how the system is built and to obtain clear and

enough information needed to drive the actual implementation of the system. It is based on

understanding of the model the software built on. The objectives of design are to model the

system with high quality. Implementing of high quality system depend on the nature of design

created by the designer. If one want to changes to the system after it has been put in to operation

depends on the quality of the system design.

4.2

DESIGN CLASS DIAGRAM

Class diagram depicts the systems 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. Class diagrams are the most common diagrams used in UML. Class diagram consists of

classes, interfaces, associations and collaboration. Class diagrams basically represent the object

oriented view of a system which is static in nature. Class diagram represents the object

orientation of a system. So it is generally used for development purpose. This is the most widely

used diagram at the time of system construction.


41/76

31

Fig 10 : design of class diagram

4.3 Collaboration diagram

Collaboration diagram is another form of interaction diagram. It represents the structural

organization of a system and the messages sent/received. Structural organization consists of

objects and links.

The purpose of collaboration diagram is similar to sequence diagram. But the specific purpose of

collaboration diagram is to visualize the organization of objects and their interaction.


42/76

32

fig11: login of collaboration diagram

: User

main window

(Ul)

login page

main page

(Ul)

user account (DB)

1: 1 wants to login

3: 3 enter user name and password

2: 2 display login page

4: 4 validate user name and password ()

5: 5 verify the user name and password ()

6: 6 disply


43/76

33

Fig 12: order of collaboration diagram

Admin : Admin

customer

page

payment

page

order link

order page

data base

1: 1. activate()

5: 4. fill the form()

8: 8.fill the payment form()

2: 2.click()

9: 9.check balance()

3: 3.display()

4: 5. validate the form()

6: 6. verifiy the form()

7: 7. display()

10: 10 bill generate()


44/76


45/76

35

Fig 15: cancel order of state chart

Fig 16 generate report of activity diagram

4.5

Database design

Database design is the process of producing a detaileddata model of adatabase.Thislogical data

model contains all the needed logical and physical design choices and physical storage

parameters needed to generate a design in aData Definition Language,which can then be used to

create a database. A fully attributed data model contains detailed attributes for each entity.

The term database design can be used to describe many different parts of the design of an

overalldatabase system.Principally, and most correctly, it can be thought of as the logical design

of the base data structures used to store the data. In therelational model, these are

Idle send cancel

form

cancel

confirm

cancel

normal exit

evaluate

un normal exit ignor chance

fill cancel form

complete cancel

idel send report

requst

select

report type

confirm

report

display

fill report form

evaluation

in proper select

normal exit

complete state
http://en.wikipedia.org/wiki/Data_modelhttp://en.wikipedia.org/wiki/Databasehttp://en.wikipedia.org/wiki/Logical_data_modelhttp://en.wikipedia.org/wiki/Logical_data_modelhttp://en.wikipedia.org/wiki/Data_Definition_Languagehttp://en.wikipedia.org/wiki/Database_systemhttp://en.wikipedia.org/wiki/Relational_modelhttp://en.wikipedia.org/wiki/Relational_modelhttp://en.wikipedia.org/wiki/Database_systemhttp://en.wikipedia.org/wiki/Data_Definition_Languagehttp://en.wikipedia.org/wiki/Logical_data_modelhttp://en.wikipedia.org/wiki/Logical_data_modelhttp://en.wikipedia.org/wiki/Databasehttp://en.wikipedia.org/wiki/Data_model


46/76


47/76

37

Fig17: Organization Database design


48/76

38

Fig18: Bank database design


49/76

39

CHAPTER FIVE

5 Implementation deliverable of the new system

5.1

Introduction

The purpose of this part of the document is to provide the highlight of the issues dealt with

the implementation phase.

We have tried to deal with two issues in implementation: -Implementation strategiesandcoding.

We divide the Implementation strategy into two parts: - system conversion and user

documentation.

Coding: - is a phase where all the work during analysis and design will be turn off to a

functional system prototype, it is divided into three parts

User interface Implementation: it is designed and documented in the previous chapter.

Database implementation:- the database implementation is now we are going to

develop in this phase but it is also designed in the previous chapter and

Logical Implementation: -implementation of the functionality of the system.

At the end of this documentation we will use the testing phases.

5.2

Component diagram

Component Diagrams are UML diagrams used to implement component-based software. Component

modeling shows the main components of the system that are the user interface class, the business classes,

the system classes and the persistent classes. In this diagram user interfaces will have a stereotype called

and will be grouped according to which actor or business class they are responsible. The

business classes are the same classes used in class modeling. The system classes are classes, which

address functionality issues such as security (login) user name and password.


50/76

40

Fig 19:component diagram


51/76

41

5.3

Deployment diagram

It describes the physical architecture of the hardware and software in the system. They depict the software

components, processors, and devices that make up the systems architecture.

The hard ware for the system

The software that is installed on the hardware

Depict the hardware/network infrastructure of an organization.

Depict a major deployment configuration of a business application.

Adminstrator

Customer

Techincal assistance

regisration

place order

tracking

cancel order

processing order

search customer

manage user account

generate report

Login

security

Fig 20: Deployment diagram


52/76

42

5.4

User I nter face

In this system users will communicate with the system through the following user interfaces.

Home Page: This form appears on the site in which the system deployed is opened and contains some

links which lead the user to other page according to his privilege, and if the user is authorized user or has

an account, he/she will directly go to the page that he want by entering correct username ,password and

role.

Fig 21 : User inter face Home page


53/76

43

Fig 22: User interface login


54/76

44

Fig 23 :User inter faceAdmin page


55/76

45

CHAPTER SIX

6 PROTOTYPE DEVELOPMENTPrototype development can be defined it is the sample code of the given project. These are some

of the sample codes that we have done it.

Home page

var count = 0;

function member() {

if (parent.count ==0) {

document.parent.src = "images/A.jpg";

title="Deber birhan post office";

count = 1;

}

else if (parent.count ==1) {

document.parent.src = "images/1.jpg";

count = 2;

}

else if(parent.count ==2) {


count = 3;

}

/*else if(parent.count ==3) {

document.parent.src = "pic/3.jpg";


56/76

46

count = 4;

}



count = 5;

}



count = 6;

}*/

else {


count = 0;

}

setTimeout("member()", 2000);

}

Home


57/76

47

Services

About Us

track

comment

contact us

Login

Home Page


58/76

48


59/76

49

// this array gives the number of days in each month

var Mdays = new Array();

Mdays[0] = 31;

Mdays[1] = 28;

Mdays[2] = 31;

Mdays[3] = 30;

Mdays[4] = 31;

Mdays[5] = 30;

Mdays[6] = 31;

Mdays[7] = 31;

Mdays[8] = 30;

Mdays[9] = 31;

Mdays[10] = 30;

Mdays[11] = 31;

// this code gets current date information

var Today = new Date();

var Date = Today.getDate();

var Month = Today.getMonth();

var dow = Today.getDay();

var Year = Today.getYear();

// these are variables for

var day = 1;

var i, j;

// adjust year for browser differences

if (Year < 2000) {

Year += 1900;


60/76


61/76

51

if (day == Date) {

// highlight the current day and display the date for this cell

document.write("" + day +

"");

} else {

// display the date for this cell

document.write("" + day + "");

}

// increment day counter

day++;

}

}

// end of row; determine if more rows needed

document.write("");

if (day > Mdays[Month]) {

i = 6;

}

}

// end of table

document.write("");

// end hiding -->

Background


62/76


63/76

53

';

}

?>

debire birhan post office 2014

COPY RIGHT RESERVED !!!


64/76

54

Login page

var count = 0;

function member() {

if (parent.count ==0) {


title="evahotel build";

count = 1;

}

else if (parent.count ==1) {


count = 2;

}




65/76

55

count = 3;

}

/*else if(parent.count ==3) {


count = 4;

}



count = 5;

}



count = 6;

}*/

else {


count = 0;

}

setTimeout("member()", 2000);

}


66/76


67/76

57

Home Page

letter

parcel

location


68/76

58


69/76

59

// this array gives the number of days in each month

var Mdays = new Array();

Mdays[0] = 31;

Mdays[1] = 28;

Mdays[2] = 31;

Mdays[3] = 30;

Mdays[4] = 31;

Mdays[5] = 30;

Mdays[6] = 31;

Mdays[7] = 31;

Mdays[8] = 30;

Mdays[9] = 31;

Mdays[10] = 30;

Mdays[11] = 31;

// this code gets current date information

var Today = new Date();

var Date = Today.getDate();

var Month = Today.getMonth();

var dow = Today.getDay();

var Year = Today.getYear();

// these are variables for

var day = 1;

var i, j;

// adjust year for browser differences

if (Year < 2000) {

Year += 1900;


70/76

60

}

// account for leap year

if ((Year % 400 == 0) || ((Year % 4 == 0) && (Year % 100 !=0)))

Mdays[1] = 29;

// determine day of week for first day of the month

var Mfirst = Today;

Mfirst.setDate(1);

var dow1 = Mfirst.getDay();

// write out current date

document.write("Today is " + Weekday[dow] + ", " + MonthA[Month]);

document.write(" " + Date + ", " + Year);

// construct calendar for current month

document.write("

" +

"" + MonthA[Month] + " " + Year

+ "");

document.write("SunMonTueWed" +

"ThuFriSat");

for (i = 0; i < 6; i++) {

// this loop writes one row of days Sun-Sat

document.write("");

for (j = 0; j < 7; j++) {

// this loop determines which dates to display and in which column

if ((i == 0 && j < dow1) || (day > Mdays[Month])) {

// this puts in blank cells at the beginning an end of the month

document.write("
");

} else {


71/76


72/76

62

NEWS


73/76

63

debire birhan post office 2014

COPY RIGHT RESERVED !!!


74/76

64

CHAPTER SEVEN

7 Conclusion and recommendation

7.1

Conclusion

Conclusions the growing number of operations at the post office, the handling of paperwork had

begun to bottleneck and the updating of records had been difficult. The purpose of this projectwas to enable the post office to carefully document all necessary activities and relatedinformation and to manage and manipulate information effectively. The system also helps them

for the proper functioning of their operation in the considerable time and accuracy. With all ofthat in mind, the newly proposed system will allow customers to get access online on the postoffice and transactions more efficiently and securely and system administrators also participateon the system for managing the user account. The proposed partial system will make it possibleto maintain accurate up-to-date records, access various types of users at any moment, and allowcertain users the capacity to print or display various reports related to post office. Throughseveral iterations of analysis and design, the designers of the newly designed system believe thatthe partial proposed system will be much more efficient and will allow the daily operations of the

post office to run more smoothly. The overall project processes have been a great learningexperience for us and now, having gone through all the processes, we more fully understand theimportance of each process and how each process informs other processes.

7.2

Recommendations

Based on our experience in the process of this project undertaking and as the Computer Science

professional we recommend:-

Firstly,It is very essential to consider that the project development is not an easy task since it requires

time, resource, budget, and other constraints. . The time that we have, the financial intake of the

documentation are the two main types of constraints that greatly affect our system development. Thus the

department, taking in to consideration the above points, should act for proper coordination of senior

projects. In addition to this, accessing information from the personnel department was also difficult in

accomplishing our project thus the respective department should give due consideration in providing

relevant information for those who need.

Secondly, we recommend Deberebirhan post office manager that their contributions play a grate role to

the development of this system, but they were not volunteered to do so and our recommendation is if the

personnel office system is automated the first beneficiary from the system is the officers themselves. To

have the computerized system instead of the manual, the role of personnel officers is very crucial and in

the future if someone wants to update or wants to automate as a whole the information gathered from

them is not a simple and leisure rather it is very important and the foundation of the system development.

Due to the above discussed problems we forced to gather requirements from magazines, News papers,

Bulletins, Announcements from the announcement board (internal and external), our experience through


75/76

65

four years to this university to observe the activities and type of employee and we try to change that

information to our system.

Thirdly, we want to recommend any voluntary persons who have the intension to update, change modify

this project including the all post office sites or anyone who is interested to update or modify our project.

For example in this project we did only the tracking and online shoping subsystems among the personnel

systems. And it is quite possible to add the OIS (organizational information system), and Employee Exit

management system. And to fully automate the personnel systems all the above subsystems are need to be

automated, so that the personnel office of Debreberehan post office will become fully computerize.


76/76

References:

http://www.ethiopostal.com

www.w3cschools

www.mypostoffices.com

http://www.onlinetrackingnumber.com

http://www.sourcecodester.com/php
http://www.ethiopostal.com/http://www.ethiopostal.com/http://www.w3c/http://www.w3c/http://www.w3c/http://www.w3c/http://www.mypostoffices.com/http://www.mypostoffices.com/http://www.mypostoffices.com/http://www.mypostoffices.com/http://www.onlinetrackingnumber.com/http://www.onlinetrackingnumber.com/http://www.sourcecodester.com/phphttp://www.sourcecodester.com/phphttp://www.sourcecodester.com/phphttp://www.onlinetrackingnumber.com/http://www.mypostoffices.com/http://www.w3c/http://www.ethiopostal.com/

PostOffice (Repaired)

Documents

Transcript of PostOffice (Repaired)