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

PROJECT TITLE: ONLINE POST OFFICE MANAGEMENT SYSTEM Advisor‟s 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

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 the concept of project development. Then we express our deep gratitude to our Department Head Mr. GETACHEW .M,our friends for their encouragement and 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.

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.2 Non functional requirement..................................................................................................... 16 i

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 ........................................................................................................................ 34

4.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

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

ii

List table

page

Table1: hard wear cost schedule……………………………………9 Table2: software cost schedule………………………………… ….9 Table3: gant chart…………………………………………………. 10 Table4: team organization………………………………………….11 Table5: use case ………………………………………………21 Table6: use case registration…………………………………………22 Table7: use case place order………………………………………23 Table8: use case search order……………………………………24 Table9: use case generate report………………………………..25

iii

LIST OF FIGURE Figure1: sender registration form………………………………………………14 Figure2: use case diagram……………………………………………………20 Figure3: class diagram of post office………………………………………….28 Figure4: sequence diagram………………………………………………30 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……………………………….36 Figure11: form of activity diagram……………………………………..38 Figure12: placing order of activity diagram……………………………………39 Figure13: cancel order of activity diagram……………………………………40 Figure14: search record of activity diagram…………………………………..41 Figure15: generate report of activity diagram…………………………………42 Figure16: design of class diagram…………………………………………….45 Figure17: form of collaboration diagram………………………………47 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: page of state chart diagram………………………………54 Figure26:-placing order state chart diagram…………………………………55 Figure27: cancele order of stat chart diagram…………………………………....56 iv

Figure28: search custom………………………………….…………………..56 Figure29: generate report of state chart diagram……………………………….57 Figure30: organization database………………………………………………..59 Figure31: bank database…………………………………………………………60

v

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 in managing the various types of records online. The product will help the 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 deg 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 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.

vi

List of abbreviation  Sql –structured query lanquage  Uml –unified modeling lanquage  Cd –compact disc  Atm –automated teller machine  Uc –use case  Php –hayper text pre processor  url –uniform resource locator  dbms – data base management system  css –cascaded style sheet

vii

CHAPTER ONE 1 Introduction of the project The 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 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 s itself in the e-Post Office and receives a 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.

1

1.2 Structure of the organization Federal Zone manager

Finance room

Message room

Auditor

Seller

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 can‟t know the material available 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

1.4.1

The objective of the project 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 ‟s request in 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.

2

1.5

Methodology and Tools

1.5.1 Fact Finding Techniques The Method and techniques used to analyze the existing system and deg 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 organization‟s 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 the interview done with aim to understand the overall activities in the post office. The team 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?

3

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: reusability of the system‟s 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 4



Pen



A4 size 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



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 time period. That‟s why we have 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 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 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 Feasibility 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

5

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 the number or location of s?



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 interface. Thus it provides an easy access to the s. The database‟s purpose is to create, establish and maintain a workflow among various entities in order to facilitate all concerned s in their various capacities or roles. Permission to the s 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 to the s irrespective of the number of s 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 organization‟s 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 for the management from the s? 6



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



Will there be any resistance from the 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 requirements have been taken into consideration. So there is no question of resistance from the s 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 7

Software cost 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 Table 2: Software cost schedule

8

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

week

week

week

week

week

week

week

week

1 2 3 4

1 2

name 1

2

3

4

1

2

3

4

1

2

3

4

Title selection

Proposal writing

Requireme ntanalysis Design phase

implement ation

presention

9

1

2

3

4

1

2

3

4

1

2

3

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

10

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

Description of the existing 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 came back without buying the material. The post office perform the activity sending post from one country to other country the activity performed by ing 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 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 existing system 

Manager:  he generates reports.  he manages or leads the other employees.



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

2.4 Work flow the existing 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 generating of existing system Report 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 in which the proposed system operates accordingly. It deals with access control issues. It often pertains to access control issues, operating policies and principles of the organization.The organization has the following principles in the existing system which includes: 

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:3011: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.

12

2.7 Paper document system system of the existing 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 ed in the post office. Sender registration form It used to record the all necessary details of the sender . Sender name ………………. Receiver name ……………

Employee sign ……….

Destination………………… Postage………………In figs

Birr…… cents…..

In words……………… 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 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 13

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 it‟s 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 ed .



Generating report periodically on Employees information such as compensation and evaluation.



All forms and documents mentioned above must be used. 14



Using Employee information document (files), which makes managing Employee simple and easily.



2.10

Information that is too sensitive has to be kept in hard copy.

Alternative solution

In order to overcome the current system problems that exist in the functioning of post office, our project team have put down alternative solution. These are:  Changing the structure of the manual system in to organized manner  Completely changed manual system in to computerized system without affecting the structure of the post office .

2.11

Proposed system

To debug the proposed system, remove procedures those cause data redundancy, make navigational sequence proper. To provide information about audits on different level and also to reflect the current work status depending on organization/auditor or date. It required building strong mechanism. We all know the importance of computerization. The world is moving ahead at lightning speed and everyone is running short of time. One always wants to get the information and perform a task he/she/they desire(s) within a short period of time and too with amount of efficiency and accuracy. The application areas for the computerization have been selected on the basis of following factors: 

Minimizing the manual records kept at different locations.



There will be more data integrity.



Facilitating desired information display, very quickly, by retrieving information from s.



Facilitating various statistical information which helps in decision-making.



To reduce manual efforts in activities that involved repetitive work.



Updating and deletion of such a huge amount of data will become easier.

In many organizations, services and tasks the system required to perform can be categorized in to Functional and Non-Functional.

2.11.1 Functional requirement of the project The functional requirement part discus the functionality required from the system. the system is considered to perform a set of function. Each function of the system can be considered as a transformation of a set of input data to the corresponding output of data. The can get some meaningful piece of work done using function.

15

Functional Requirements are those that refer to the functionality of the system about the services it will provide to the . The following is a list of functionality of the system s of the system: Customer is the of the system. An of the website is the super. When the 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 . has to to Welcome Page before ordering anything. functionality should check the authenticity of the 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 search customer recorded from the database.



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

2.11.2 Non 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:

interface: since s of the system involved people with different back ground, the system should be made with 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.

16

CHAPTER THREE 3 ANALYSIS DELIVERABLES OF THE NEW SYSTEM 3.1 Introduction 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 object – oriented 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.2 Use case diagram of post office 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 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.

17

«extends»

make payment



Regsiter



tracking

order

Customer tracking order

Cancel Order

Manager

Processing Order

Search customer

Manage

genrate report

18

Fig 2: Use case diagram Use case number

UC-01

Use case name



Priority

High

Actor

,manager and customer

Description

This use case describes how they are to to post office system. Use case to ensure security in system usage. The must have name and .

Pre condition Post condition

Basic course of action

Alternate course action

gets access to the system according to their predefined system privilege and family he/she or turn off the page. action system response 1.They are on the 2.The system Home page to promtes them to To the system. enter 3.They enter name name,. and 4.The system ,click on verifies that all the button field have been filled out and valid. 5. The system successfully logs them in the system. 6.Use case exit.

7. if all fields are not filled out or not matched to the name and the system notifies the actor a message to name and and then goses back or return to setep 4 of basic course of Action to enter again.

Table 5: of use case

19

Use case number

UC-02

Use case name



Priority

High

Actor

and customer

Description

Description: use case to new customer

Pre condition

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

Post condition

Customer ed.

Basic course of action

action 1.not include use case. 2.new customer select ‟s link. 3.the customer fill necessary data .

system response 5. system responds by responding criteria form. 6.The system display successfully ed. 7. use case ends.

4. submit

Aleterante course action

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

Tabel6: of use case

20

Use case number

UC-03

Use case name

Place order

Priority

High

Actor

Customer

Description

This use case permits customers to order and make schedule for sending items ,based on the availability of the office. Customer wants to order a item and order details about customer have to be entered. Customer order successfully.

Pre condition Post condition Basic course of action

action 1.the customer wants to order the item. 2.the customer clik on the order page . 4.the customers enters the following information customer (full name, ID/port NO, country, mobile number and type of item, weight of the item) .

system response 3. the system prompts the customer to fill order form. 6.the system checks all required information had been filled and the date and time entered is valid . 7. the system 5. the customer clicks present information order button order button to accept or decline to order. the order agreement. 8.the customer accept the 9. the system shows order and click accept. the customer that the order has been completed , and display payment page. 10.use case ends.

Alternate course action

6.1 if the customer enter invalid order ,the system goes back to step 4 to enter the valid order . 6.2 if the customer fills invalid information ,the system goes back to step 4.

Table 7:place order of use case

21

Use case number

UC-10

Use case name

Manger

Priority

high

Actor



Description

These use case permits to manage . already has and hasn‟t wants to create an or to change their . s successfully changes or crate.

Pre condition Post condition Basic course of action

action 1.the wants to create or modify . 2.the opens change page and clicks on that clicks on that link. 4.the modifies or creates the .

system response 3. the system displays a form. 5.the system verifies the filed out correctly and checks validity of confirmation number ,then popup a message to the cancelling. 6. the system modifies and display a message that is crate or modifies successfully. 8. use case exit

Alternate course action

5.1 if the enters invalid character in the system goes back or returns to step 4 of basic course of action . to fill invalid or the empty field again. 6.1 if the clicks “NO” modify will be terminated. table 6: mange of use case

3.3 Analysis level of class diagram Class Diagrams are used to represent the structure of the system in 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 22

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 system to perform a specific functionality

23

main window (Ul)

:

1 wants to

page

main page (Ul)

2 display page

3 enter name and 4 validate name and ()

5 the name and ()

6 disply

Fig4: of sequence diagram

24

(DB)

:

customer page

order link

order page

payment page

data base

1. activate() 2.click() 3.display() 5. validate the form()

4. fill the form() 6. verifiy the form() 7. display()

8.fill the payment form() 9.check balance()

10 bill generate()

Fig5:place order of sequence diagram

25

manager page 1 activate()

manager : manager

report link()

report form

data base

controller

2 select() 3 display()

4 fill form()

5 validate()

6 continue step 5() 7 try agin()

8. check()

9 display the result()

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.

26



fill form data base

data

display error message

check valid

display home page

Fig7: of activity diagram

27

Usre

canceler

fill cancer order form

Data base

Canel data

Display error message. check validate

in valid

display cancel conformation

valid

Fig8: cancel order activity diagram

28

manager

system

fill report form Data Base

report data

dissplay error mesage

valid in valid

generate report

Fig9: generate report of activity diagram

29

generate report()

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 the non functional requirements and constraints described in the problem statement and requirement analysis sections discussed earlier. The purpose of deg 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 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. 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.

30

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.

31

main window (Ul) 2: 2 display page 1: 1 wants to

3: 3 enter name and

page

: 6: 6 disply 5: 5 the name and () 4: 4 validate name and ()

main page (Ul)

(DB)

fig11: of collaboration diagram

32

8: 8.fill the payment form()payment page 9: 9.check balance() : 10: 10 bill generate() data base 1: 1. activate() 7: 7. display() 5: 4. fill the form() customer page

4: 5. validate the form() 6: 6. verifiy the form()

2: 2.click()

order link

3: 3.display() order page

Fig 12: order of collaboration diagram

33

manager page

2: 2 select() report link ()

1: 1 activate()

5: 5 validate() 4: 4 fill form() manager : manager

controller 3: 3 display()

6: 6 continue step 5() 7: 7 try agin()

8: 8. check()

report form data base 9: 9 display the result()

Fig 13: generate report of collaboration diagram

4.4

State chart diagram

The state chart diagram used to show the sequence of states that an object goes through the events that cause the transition from one state to the other and the actions that result from a state change. idle

fill form

sender order request

normal exit

select order item

evaluation

un normal exit leave ordering

conform order

complete

Fig 14: sender form of state chart

34

Idle

fill cancel form

normal exit

send cancel form

cancel

evaluate un normal exit ignor chance

complete cancel

confirm cancel

send report requst

normal exit

Fig 15: cancel order of state chart

idel

fill report form

select report type evaluation

in proper select

confirm report

display

complete state

Fig 16 generate report of activity diagram

4.5 Database design Database design is the process of producing a detailed data model of a database. This logical data model contains all the needed logical and physical design choices and physical storage parameters needed to generate a design in a Data 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 overall database 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 the relational model, these are 35

the tables and views. In an object database, the entities and relationships map directly to object classes and named relationships. However, the term database design could also be used to apply to the overall process of deg, not just the base data structures, but also the forms and queries used as part of the overall database application within the DBMS. The process of doing database design generally consists of a number of steps, which will be carried out by the database designer. In database design we will perform the following activities. 

Identifying keys: 

Primary key: Identifies unique instance of an entity. Foreign: This will help us to show the relationship between two

tables or classes. 

Identifying entities: Entities which are the persistent classes will be stated with their attributes.



The methods of the classes will be used.



Inheritances will be included and if there is any associations exist they will also be included.

 The attributes will be given data type and initial sizes

36

Fig17: Organization Database design

37

Fig18: Bank database design

38

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 strategies and coding. We divide the Implementation strategy into two parts: - system conversion and 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 

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 interface class, the business classes, the system classes and the persistent classes. In this diagram 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 () name and .

39

Fig 19:component diagram 40

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 system‟s 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.



regisration security strator

place order

tracking Customer cancel order

processing order Techincal assistance

search customer

manage

generate report

Fig 20: Deployment diagram

41

5.4 Interface In this system s will communicate with the system through the following interfaces. Home Page: This form appears on the site in which the system deployed is opened and contains some links which lead the to other page according to his privilege, and if the is authorized or has an , he/she will directly go to the page that he want by entering correct name , and role.

Fig 21 : inter face Home page

42

Fig 22: interface

43

Fig 23 : inter face page

44

CHAPTER SIX 6 PROTOTYPE DEVELOPMENT Prototype 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

<script type="text/JavaScript"> 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) { document.parent.src = "images/2.jpg"; count = 3; } /*else if(parent.count ==3) { document.parent.src = "pic/3.jpg"; 45

count = 4; } else if(parent.count ==4) { document.parent.src = "pic/4.jpg"; count = 5; } else if(parent.count ==5) { document.parent.src = "pic/5.jpg"; count = 6; }*/ else { document.parent.src = "images/A.jpg"; count = 0; } setTimeout("member()", 2000); }

47 Home Page <script language="JavaScript"> Background 4f291f 51 Debere Birhan post office stablished in 1933 E.c it found in amhara region far from 130 km from adiss ababa.It performs many activity to satisfied the customer needs . NEWS 5g624v $result = mysql_query("SELECT * FROM news"); while($row=mysql_fetch_assoc($result)) { echo ' <marquee direction="up">'.$row['news'].' 545s18 '.$row['Date'].' 52 '; } ?>

debire birhan post office© 2014 COPY RIGHT RESERVED !!! 53