TAMALE TECHNICAL UNIVERSITY

JOB MANAGEMENT SYSTEM FOR CARPENTRY SHOP

BY

ALHASSAN Z YAKUBU, INUSAH ALHASSAN, SAMADU ABRAHAM

2021

ii
 TAMALE TECHNICAL UNIVERSITY

DESIGN JOB MANAGEMENT SYSTEM FOR A CARPENTRY

SHOP SELLING AND DISTRIBUTION OF FURNITURE

BY

ALHASSAN Z YAKUBU

INUSAH ALHASSAN

SAMADU ABRAHAM

PROJECT WORK SUBMITTED TO THE DEPARTMENT OF

COMPUTER SCIENCE OF THE SCHOOL OF APPLIED
SCIENCE AND TECHNOLOGY, TAMALE TECHNICAL
UNIVERSITY IN PARTIAL FULFILMENT OF THE
REQUIREMENTS FOR AWARD OF HIGHER NATIONAL
DIPLOMA IN INFORMATION AND COMMUNICATION
TECHNOLOGY

SEPTEMBER, 2021

iii
DECLARATION

Candidates’ Declaration

We hereby declare that this project work is the result of our own original work

and that no part of it has been submitted for any other award in Tamale Technical

University, or elsewhere.

ALHASSAN Z YAKUBU MatriculationNumber……………….....

Signature:……………………………. Date…………………………………….

SAMADU ABRAHAM Matriculation Number……………….....

Signature:……………………………. Date……………………………………

INUSAH ALHASSAN Matriculation Number……………….....

Signature:……………………………. Date……………………………………

iv
Certification

We hereby certify that the preparation and presentation of the project work were

supervised in accordance with the guidelines on project work laid down by the

Computer Science Department, Tamale Technical University.

Internal Supervisor’s

Name:……………………………………………………...…………………………

Signature:…………………………………… Date………………………………….

External Supervisor’s Name:………………………………………………………….

Signature:…………………………………… Date………………………………….

HOD’s Name:…………………………………………………………………………

Signature:…………………………………… Date………………………………….

v
ABSTRACT

The job management system is a web based system intended for online retailers. The

main objective of this system is to make it interactive and its ease of use. It would make

searching, viewing and selection of a products such as furniture, beds, chairs etc easier.

It contains a sophisticated search engine for clients to search for products specific to

their needs. The search engine provides an easy and convenient way to search for

products where a user can Search for a product interactively and the search engine

would refine the products available based on the user’s input when the product are not

yet available it be pending on the clients status. The client can then view the complete

when the job is completed, specification of each product. They can also view the

product reviews and also write their own reviews. The software also provides a

pending, processing, and completed job feature so that clients can add . The main

emphasis lies in providing clients friendly search engine for effectively showing the

desired results

vi
ACKNOWLEDGEMENT

We would like to extend our heartiest thanks with deep sense of gratitude and respect to

all those who provides us immense help and guidance during our training period.

We would like to thank our project internal supervisor Mr. Ibrahim for providing vision

about the system we have been greatly benefitted from their regular critical review and

inspiration throughout the work

We would also like to thank or express our sincere thank to our Head Of Department

(HOD) Dr. Kennedy who gave us an opportunity to undertake such a great challenging

and innovative network. We are much grateful for your support throughout the entire

project

vii
DEDICATION

We would like to thank our able senior for his effort and unfailing co-operation and

sparing his valuable time to assist us in our project work

We would also like to thank the entire staff of Computer Science Department for their

constant support and encouragement, suggestions and moral support throughout the

duration of the project

Last but not least we would like to dedicate our heartiest gratitude to our parent, friends

and to everyone who has been associated with our project at my stage but whose name

does not find place in our project in this dedication

viii
Table of Contents
DECLARATION.............................................................................................................ii

ABSTRACT....................................................................................................................vi

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

1.0 INTRODUCTION......................................................................................................1

1.1 Background.........................................................................................................1

1.2 Problem Statement..............................................................................................2

1.3 Objectives of the study........................................................................................3

1.4 Research questions..............................................................................................3

1.5 Significance of the study.....................................................................................3

1.6 SCOPE OF THE PROJECT................................................................................3

1.7 Limitations of the existing system.......................................................................4

1.8 Definition of terms..............................................................................................4

1.9 Methodology.......................................................................................................5

1.10 Organization of Chapters...................................................................................6

1.11 Application Software requirements...................................................................6

ix
 1.12 System Requirements:.......................................................................................6

1.13 System Software requirements..........................................................................7

2.1 Introduction.........................................................................................................8

2.2 Literature Review................................................................................................8

2.3 The Existing System............................................................................................9

2.4 Limitations of the existing manual system........................................................13

2.4 System study......................................................................................................14

2.4.1 Feasibility Study.............................................................................................14

2.5 System requirements.........................................................................................17

CHAPTER THREE........................................................................................................18

3.0 THREE SYSTEM DESIGN, METHODOLOGY AND IMPLEMENTATION.....18

3.1 Introduction.......................................................................................................18

3.2 Propose system & it’s advantages...................................................................18

3.2.1 Proposed System............................................................................................18

3.2.2 Advantages of proposed system:....................................................................21

3.4 System design....................................................................................................21

3.4.1. SDLC Activities............................................................................................24

3.6 Implementation..................................................................................................31

3.6.1 The E-R diagram............................................................................................31

3.6.2 Data Flow Diagrams......................................................................................32

x
 3.6.3 Use Cases Diagrams.......................................................................................35

3.6.4 Back-end coding.............................................................................................36

3.7 Deployment and installation..............................................................................36

CHAPTER FOUR..........................................................................................................37

4.0 RESULTS AND ANALYSIS..................................................................................37

4.1 Introduction.......................................................................................................37

4.2 Procedures in Proposed Step.............................................................................37

4.3 Input Forms of the proposed system.................................................................38

4.4 Output (Reports Generated) by the Proposed System.......................................38

4.5 System Requirements........................................................................................38

4.5.1 Application Software requirements................................................................38

4.5.2 System Requirements:....................................................................................39

1.5.3 System Software requirements.......................................................................39

4.6 Challenges and Limitations of the Proposed System........................................39

CHAPTER FIVE............................................................................................................41

5.0 SUMMARY OF FINDINGS, CONCLUSION AND RECOMMENDATION.......41

5.1 Introduction.......................................................................................................41

5.2 Limitations of the system..................................................................................41

5.3 Summary of comments from supervisor, users and your self...........................41

5.4 Conclusion of Courier Management System.....................................................41

xi
 5.5 Recommendations.............................................................................................42

5.5.1 Recommendations on future enhancement of courier management system. .42

5.5.3 Recommendations for users...........................................................................42

5.5.4 Recommendations for academicians..............................................................42

6.0 REFERENCES.........................................................................................................44

LIST OF FIGURES

Figure 1: LEVEL 0 DATA FLOW DIAGRAM……………………………………………34

Figure 2: Use-case Diagram……………………………………………………………….34

Figure 3: Use case2 Diagram………………………………………………………………34

xii
CHAPTER ONE

1.0 INTRODUCTION

1.1 Background

A job management system organised collection of

information sources which is made accessible to the people. The
management system for a carpentry shop usually contains the information
physically or in a digitized format. In the olden period the access was usually in
the manual form as the technology grew up the access that was made online
(Dinesh et al.,2015).Library is a fast growing organism. The ancientmethods
to maintain it are no longer dynamic and efficient. For expeditious retrieval
anddissemination of information and better service for the clientele, application of
moderntechniques has become absolutely indispensable (Neelakandan et al.,
2010).Libraries can be divided into categories by several types, which
are:Academic libraries,Corporate libraries, Government libraries such as
national libraries,Historical
societylibraries,Private libraries,Public libraries,School libraries,Special lib
raries,Digital libraries,P i c t u r e ( p h o t o g r a p h ) l i b r a r i e s , S l i d e
libraries,Tool libraries,Architecture libraries,Fine
a r t s l i b r a r i e s , M e d i c a l l i b r a r i e s , T h e o l o g i c a l l i b r a r i e s e t c . A libraryis
comprised of the following sections,based on the services rendered. i.
Acquisition Section
: The books demanded by different departments aredoneby
t h e Acquisition section. University book centre is also working in this section for
supplyof books to thelibraries in this university. ii.
Technical Section
:To classify, catalogue, OPAC,Barcodeetc.the documents
o f t h e University Library this section is working.

2
iii.
Circulation Section
:This sectionprovidesdocumentsto the membersand
u s e r s o f library forhome reading as well as reading in the library.The
documents are arrangedon the racks in stacksas per the Dewey Decimal
Classification Scheme.iv.
PeriodicalSection
:To procure, maintain and arrange periodicals services
tolibrarymembers.Periodical section provides reference service with
respect to therequirement of the reader. Reference section is attached to periodical
section forconvenience of the Library users.v.
Databases

1
:Databaseslike OPAC, CAB-CD ROM abstracting databases,
DELNETonline Network Service etc.are available for the library
members.vi.
Reprographic Section
:
This Section has twoautomatic plain paper copiers and aduplicating
machine throughwhichthe services of photocopy are provided to
thereadersvii.
Binding Section
:This section is working for binding work of the damaged books. B a c k
Volumes and other documents of thisLibrary.The required
b i n d i n g m a c h i n e r y is available in this section.Library managementis a sub-
discipline ofinstitutional managementthat focuses on specificissues faced by
libraries and library management professionals. Library managementencompasses
normal management tasks as well asintellectual freedom,anti-censorship,
andf u n d r a i s i n g t a s k s . I s s u e s f a c e d i n l i b r a r y m a n a g e m e n t f r e q u e n t l y
o v e r l a p t h o s e f a c e d i n management ofnon-profit organizations(Sharma
et al.,2005).Library Management System isan application that portraits
library system which couldbe generally small or mediumin size.It is used by
the librarian to categorically manage the library by the virtue of using acomputerized
system where he/she can record various transactions like issue of books, returnof
books, addition of new books, addition of new students etc. (Ashutoshand
Ashish., 2011).

3
Books andusermaintenance modules are also included in this system which
would keeptrack of theusersusing the library and also a detailed description
about the books a librarycontains. With this computerized system there will be no
loss of book record or memberrecord which generally happens when anon-
computerizedsystem is used. In addition, report
module is also included in Library Management System. If user’s position is admin, the
user
is able to generate different kinds of reports like lists ofusersregistered, list
of books, issueand return reports. All these modules are able to help librarian to
manage the library withmore convenience and in a more efficient way as compared to
library systems which are notcomputerized.This system will be developed and
designed to help librarian record every booktransaction soas to reduce and
eradicateproblem of loss of books and files in the library.
1.2 Problem Statement

People when transfer their products using any courier service wants to know whether

their product has been shifted to their right place or not, if not then by what time it will

be shifted and where it is now. Taking all this information manually is very difficult

2
and time taking process. To handle all these activities include various processes and

paper work from the management side also.

Keeping record of parcels in a courier service company and their delivery information

is carried out manually. A lot of files are opened for daily record of parcels received or

delivered. This litters the office with much paper documents. Most often records are

misplaced and when a client comes to collect his parcel, he/she spend some hours

waiting for confirmation of the parcel. Hence delay is bound to occur while delivering

parcel to customers. Also, customers must visit the post office before they can purchase

stamps or any other item.

1.3 Objectives of the study

The objectives of this project are as follows.

 Analyzing global trends in e-commerce and why it is important for economic

developments.

 Identifying benefits of the adoption of e-post management system by courier

Service Company.

 Developing an e-post platform that can be used by customers to order for post

office items and make payment online.

1.4 Research questions

1.5 Significance of the study

A Courier Management System, when developed tends to increase and improve the

efficiency, effectiveness and productivity of a courier company. It tends to simplify the

work process of recording details of consignments received, dispatched, record keeping

etc. which will be adequately handled with which the courier company will get more

3
returns from and attain better customer satisfaction. (Eduproject.com.ng logo –

(RESEARCH PROJECT TOPICS AND PROJECT TOPICS ON EDUCATION)

1.6 SCOPE OF THE PROJECT

The scope of this project covers all details of a typical e-post application, with

emphasis on the front-end portal but excludes the gateway application implementations

and technologies. The gateway end which is a very secure e-payment environment is

often times built using SSL protocol, which can be procured from the gateways

companies and integrated to the e-commerce site to support online, onsite payment

management. However we have chosen to incorporate a demo copy of the gateway end

to showcase its activities for the audience to appreciate such integration.

1.7 Limitations of the existing system

Due to the manual means being used by courier Service Company in keeping parcel

records information, lots of problems was encountered which includes:

 Damage of documents due to fire incident.

 Illegal removal of files by fraudulent staff leading to insecurity

 Loss of vital documents as the filing system is manual.

 Delay in processing parcel files

1.8 Definition of terms

Courier: A courier is a person or company employed to deliver messages, packages and

mail. Database: A systematically arranged collection of computer data, structured so

that it can be automatically retrieved or manipulated. It is also called databank. File

Transfer: Any kind of computer file can be sent via the Internet from one Internet user

4
to another. Table of accounts on spreadsheets, design by a graphic artists, music sound

files etc, can all be exchanged in this way.

DEFINITION OF TERMS

Courier: A company or employee of a company that transports commercial packages

and documents.

Consignment: A batch of goods destined for or delivered to someone

Consignee: Is the party who delivers goods that they own to another party.

Consignor: Is the party who delivers goods that they own to another party.

Source: Is the owner branch from where a consignment originates.

Destination: The city or courier branch where a consignment is to be delivered.

Logistics: Is the process of coordinating and moving resources between one point of

origin and the point of consumption in order to meet some requirements

Desk officer: Is the worker at the courier company that accepts the consignment from

the consignor.

Manifest: A document listing the consignments transported at a particular time from a

courier branch to another

Delivery run sheet: A document carried along by a delivery worker of a courier

company containing details of the parcels to be delivered, with a provision for where

the receiver will sign to show receipt of items.

Reference number: Is a number given to all the consignments by the courier company

for unique identification and record purposes.

Courier management system: Is a computer application created to automate most of the

processes of the courier company especially as concerned with the recording of receipts

5
and delivery of goods. (Eduproject.com.ng logo - RESEARCH PROJECT TOPICS

AND PROJECT TOPICS ON EDUCATION)

1.9 Methodology

Php – Php-Hypertext processor

Xampp server

WordPress

SQL Database

1.10 Organization of Chapters

The project is organized as follows: - Chapter one comprises the background of the

project with the statement of the problems, objectives of the project, scope of the

project, and definition of terms pointed out. Chapter two reviews previous literatures

Chapter three discusses methodology and system analysis. It deals with the approach

used for the project, tools used, information gathering, data analysis and limitations of

the existing system. Chapter four covers the system analysis and design. It highlights

the project modules, system and program flow charts, and the database design. Chapter

five discusses the system implementation and testing. Chapter six covers the summary

and conclusion of the project.

1.11 Application Software requirements

Clients End:

 Browser: Any Web Browser (Chrome/Firefox Considered Best)

 Processor: Atom Processor or more

 RAM: 512MB or More

 Disk space: 128GB or more

6
Server End:

 Web Server: IIS6 or Higher

 Database Server: Xampp server

 Processor: Atom Processor or more

 RAM: 2GB or more

 Disk Space: 128GB or more

1.12 System Requirements:

 Operating System:Any (Linux, Windows, Macetc)

1.13 System Software requirements

Tracking device

Disk 150 MB or above.

7
. CHAPTER TWO

2.0LITERATURE REVIEW AND STUDY OF EXISTING SYSTEM

2.1 Introduction

This chapter is devoted to the review of existing literature related to the topic.

For the development of the proposed system for the Courier Management system, to be

effective and efficient, a review of the existing system (operations and reports) was

necessary. Most of the literature review was taken from documents on operations of the

Courier Companies and some other policy books available. The preceding chapters talk

about what the system is all about: its functionalities, how it is built, how it works, the

graphical user interfaces, the languages used and so on.

2.2 Literature Review

Analysis of Sample Application or Existing System. As a way of managing its activities

manually, Courier services relies on various journals to record its transactions. The

registration of personnel records, all registered packages in a journal, taking into

consideration the type, name, color, date of manufacture, the weight and package and

amount paid. For example, any package that was to be delivered by this department is

recorded in the package registration journal. Considering the work involved in recording

these transactions; issuing receipts and generating statistical reports was time consuming.

The people sometimes forget to record some data due to the pressures from the waiting

queue, which may affect the accuracy of the information and the final decision to be made.

“This project provides the facility to all users to send and receive the courier. They can

also update and delete the courier, and also get the information of the status of the courier.”

8
In this chapter the outlook of the existing systems comparatively to the new system studies

the problem, identifies alternate Solutions evaluate those solutions and finally recommends

the best solution. The system study gives an idea of the user requirements. A detailed

system study is an essential for developing an efficient system. The techniques used are:

 Observation

 Interview

 Discussion

The courier company is a new but wish to spread over the country and the world at large so

that when person wants to send things then he has to contact them for the service. The

courier company creates the schedule & gives internal/external services. The courier

service work as destination office or source office. The source office branch receives the

order means consignments & sends it to the destination courier branch. The company has

certain rules according to the weight.

2.3 The Existing System

As the company is new and growing, it has no existing electronic system but uses the

traditional system in total manual, the activity takes place in the system as following. All

records are kept on books for references and wait till products are delivered.

2.3.1 Related Existing systems

As the system is totally manual, the activity takes place in the system as following.

In this system first of all consignors placed their consignments like covers, documents,

non-documents etc. to the officer of the courier branch. Here this branch acts as a source

9
branch. Then the branch officer prepares the consignment note. The details of the

consignment note are as follow.

ORG: It indicates the name of the city from where the consignment is received from the

consignor.

DEST: It indicates the name of the city or destination to where the consignment is sent.

DATE: On which consignment is received.

NON-DOCS/DOCS: mark the category of consignment like documents or no documents.

BOOKED BY: If there is any franchise then write the name of it.

CONSIGNOR: It indicates name & address of the person who placed the consignment.

CONSIGNEE: It indicates name & address of the person who received the consignment.

DECLARED VALUE: If the cost of consignment is very high then it is written in this box.

INSURANCE: If any consignment has insurance then it is indicated by YES otherwise by

NO.

WEIGHT IN KGS: It indicates weight of consignment in kilograms.

WEIGHT IN GMS: It indicates weight of consignment in gramms.

PKGS: It contains no. Of packets of consignments.

CHARGES: According to the weight of consignment they provide charges of

consignments.

10
SPECIAL CHARGES: When they provide any special services then the charge of it treated

as special charge.

SERVICE TAX: They also include charge of government tax.

TOTAL RS: It is summation of charges, special charges & service tax.

Make the 3 copies of the consignment note. From which one is given to the sender, one is

use as cash or invoice in office purpose & other is use as ‘Proof of Delivery (POD)’, which

is sent with consignments

After receiving all consignments, they sort out the consignments according to the

destination. Then based on destination, they prepare ‘Manifest’.

Manifest is one type of note, which contains all the consignments having same destination.

They contain the following details.

Manifest No: It contains the no. of manifest.

From: It contains the name of city from where the consignment is sent.

TO: It contains the name of city means destination, to where the consignment are received.

Date: Date on which the manifest is prepared.

Consignment No: It contains all the consignments numbers.

Total Consignments: It indicate total no. of consignments.

Total WT: It contains the total weight of all consignments

Total Bags: It contains the total no. of bags of consignments.

11
Make 3 copies of the manifest. From which one is used for the source office, other 2 are

sent to the destination office. Then from these two copies one is return back to the source

branch for conformation of delivery.

After preparing Manifest all the consignments are packed & then transship the

consignments. There are 3 ways to transship the consignments.

1) By air.

2) By cargo.

3) By surface.

In air delivery boy takes the all consignments in the plane. It is also known as onboard

courier. In cargo source branch booked the plane & the delivery boy of the destination

branch received all the consignments. In surface courier services is provided by road.

After receiving consignments destination branch checked the manifest, whether any

consignment is left or not. Then based on manifest the destination branch prepared the

‘Delivery Run Sheet’. It contains the following details.

DRS NO: It contains the number of the delivery run sheet.

Consignment no: It contains all the consignment numbers.

PCS: It contains numbers pieces of the consignments.

Consignee: It contains the name of the person, who received the consignments.

Name & sign of the consignee: Here the name of the consignee & sign of his/her is taken.

Received Date: It contains the date on which the consignee received the consignments.

12
The delivery boy of destination branch prepares this form. Then he gives the consignments

to appropriate cons ignee& take his/her sign. In the courier services, charges of

the consignments is obtained from the rate table, which contains the different rate for the

different weight of the consignments.

2.4 Limitations of the existing manual system

The existing manual system has got following disadvantages:

 Using manual courier services, we have to make the whole Export Report, which

contains the record of the consignments. It requires more time & more calculation.

 In courier service the rate of the each consignment or item is fixed. The rate of

consignments is depending on the weight of the consignments. So the calculation of

rate & monthly income are not done easily.

 In courier services, the payment is made in credit or cash. So for the billing

procedure for the regular customer, we have to refer all the records in Export

Report. For this reasons this task is more time consuming.

 It is time consuming job.

 It is difficult to maintain the courier detail.

 Preparation of reports is not an easy work.

Maintaining information and retrieving information according to our needs are limited.

Computerization is economical both in terms of economy and manpower uses. Manually

maintaining the data’s is tedious and tedious and sometimes information maybe lost or

overloaded by human

13
14
2.4 System study

2.4.1 Feasibility Study

A feasibility study aims to objectively and rationally uncover the strengths and weaknesses

of an existing business or proposed venture, opportunities and threats present in the

environment, the resources required to carry through, and ultimately the prospects for

success. In its simplest terms, the two criteria to judge feasibility are cost required and

value to be attained.

A feasibility study evaluates the project's potential for success; therefore, perceived

objectivity is an important factor in the credibility of the study for potential investors and

lending institutions. It must therefore be conducted with an objective, unbiased approach

to provide information upon which decisions can be based.

In the Courier Management System project, the project can give any kind of information

through reports and queries if required.

This is very sophisticated to use and modify. The project is designed in such a way that it

can afford any changes that occurs in feature. The project can also be modified according

to the needs.

It is feasible to have an integrated system with GUI and Relational Database for the

courier System. The wastage of storage space is avoided by eliminating the data

redundancy, which needs careful programming. The careful programming minimizes the

processing time. The user can easily handle the system.

15
2.4.1.1 Technical feasibility:

The minimum hardware configuration for his Project to run is as follows:

Atom Processor Onwards

512 MB RAM

For its execution it is mandatory that it be used with a GUI based Operating System like

Windows XP and above.

Technical feasibility report:

Since the institution already has the required hardware and a supporting Operating

System, it is technically feasible.

Hardware

Intel based processor-run computer system, which have keyboard and mouse as input

devices. This has been decided for its case of availability and up-gradation. The various

registers maintained at the different department have enough information recording,

which will help in digitizing the available data.

Technical feasibility centre on the existing computer system (hardware, software) and to

what extent it can support the proposed addition. If the budget is a serious constraint, then

the project is judged not feasible.

 Behavioral feasibility

The project has a very user friendly, GUI based interface also featuring help menu, which

leaves no room for any confusion at the user end. There were some errors at the beginning

of the project but it all has been taken out. It was made for the user clean UI programing

16
that means it was made with very simplistic UI (user interface) so the user can understand

easily at the very first time.

No need for training the user to use the Project. Hence it is operationally feasible.

The aim of the system is only to satisfy the information needs; no employees will lose

their position by the proposed system. In fact, the proposed system will help the

organization in reducing the voluminous work involved. Also the involvement of users in

every stage of the project is going to increase the success factor. The staff in not well

educated for running a computerized system. They are adamant in perceiving a

mechanical process of working as they have long been used to the manual entry system.

This aspect needs considerable amount of attention.

Our system is also feasible for organization because it supports of the organization and its

strategic plan.

2.4.1.2 Economic feasibility

The cost of developing this project is merely the man-hours that are put into it, apart from

this, on the institutional front the costs that it will be bearing is to comply with the

minimum system requirements for the same. Since the institution that will employ this

project already has the required facilities.

This project is economically feasible. The procedure is to determine the benefits and

savings that are expected from a candidate system and compare it with the costs. If a

benefit outweighs costs, then the decision is made to design and implement the system.

Otherwise further alterations are made in the proposed system.

1. Manpower cost

2. Hardware and software cost

17
2.5 System requirements

Software Requirement:

 Apache Server 2.0

 PHP Version 5.3 or above

 MySQL Version 5.5 or above

 Latest browser: Chrome, Firefox, Safari etc.

 Operating System: Any (Linux, Windows, Mac etc.)

Hardware Requirements:

 Processor Pentium IV or higher version.

 Ram 128 MB or above

 Hard disk

18
CHAPTER THREE

3.0 THREE SYSTEM DESIGN, METHODOLOGY AND IMPLEMENTATION

3.1 Introduction

This chapter is devoted to the system design, systems methodology and implementation of

the system.

3.2 Propose system & it’s advantages

Courier Management System (CMS) is a web-based Courier Management System which

supports the high availability of courier services to the business and to the customer. The

system is being used for day to day activities such as booking a courier, maintain hub

details, and maintain company details, process data of companies and many other things.

CMS is programmed using Java technologies. CMS can be customized to fit your business

and can either be used as a complete system or as separate modules.

The courier management system is simply a way of sending/delivery packages. It allows

people to deliver package to and from the office.

3.2.1 Proposed System

In this section we will discuss to find out our new propose method for the existing system

in order to enhance some of the modules which have some disadvantages. A multinational

company has a very big risk to perform every task in every field and it has to be well

planned with logical reasons.

19
Computerizing of the existing system is done with the help of some programming

language & some database packages. So it will ease the work of the system when system

work as source then in consignment note.

1. It leaves the scope for destination, so the person can select desire destination.

2. It takes current date it means system date. So that person need not to be entered it

very time.

3. AMD-C contains consignment no. It is unique no. & it is use in Manifest & Delivery

Run Sheet forms.

4. If the consignor is regular then user should not need to enter his/her name & address.

It can be derived from the stored database.

5. If the consignor is not regular then the user has to enter the information about

consignor.

6. The information of the consignee means receiver has to be entered by user.

7. The description, which contains declare value, insurance, weight in kilo, weight in

grams, the user enters packets. In this declare value is chosen according to the

kilograms & grams describe in form from the Rate table.

8. If any consignment contains insurance then it is marked in the form.

9. The no. of packets, charges, special charges, and service tax is entered by the user &

according to this ‘Total Rs.’ is calculated.

20
 Then three copies of this consignment note are prepared.

Now all the entered data are stored in database name as Consignment Details and

Consignor Info.

In the Manifest form, the user enters the name of the destination on which user want

to create Manifest.

10. According to the entered destination, all the appropriate consignment nos. are

displayed automatically in Manifest.

11. The no. of consignment, total weight, and total no. of bags is counted by

performing some operation on them.

After this Manifest form is send to the destination branch with the consignments.

When the branch acts as Destination branch, then

Here the branch received Consignments & Manifest. Then it prepares Delivery Run

Sheet according to Manifest. It fills information about:

Branch Name / Regional office, Consignment No, Date, Pieces, Name & address of

consignee

Here we need not to enter the date because it automatically takes the system date.

Above information are stored in ‘Dest_Consignment_Details’.

21
3.2.2 Advantages of proposed system:

1. In computer system of the courier service computation of the rate is easily & quickly

done.

2. Accuracy in work.

3. Easy & fast retrieval of information.

4. Well-designed reports

5. Decrease the load of the person involve in existing manual system.

6. Access of any information individually.

7. Work becomes very speedy.

8. Easy to update information.

9. Computer system of the courier service provide fast access.

3.4 System design

The system was design using the SDLC model.

In systems engineering, information systems and software engineering, the systems

development life cycle, also referred to as the application development life-cycle, is a

process for planning, creating, testing, and deploying an information system. According to

Wikipedia.

It is for the following importance we made use of SDLC

22
If a business determines a change is needed during any phase of the SDLC, the company

might have to proceed through all the below life cycle phases. The life cycle approach of

any project is a time-consuming process. Even though some steps are more difficult than

others, none are to be overlooked. An oversight could prevent the entire system from

functioning as planned.

1. Planning

The company wish to meet or exceed expectations for their employees, customers

and stakeholders too. The purpose of this step is to find out the scope of the

problem and determine solutions. Resources, costs, time, benefits and other items

should be considered at this stage. The planning phase involves aspects of project

and product management. This may include:

 Resource allocation (both human and materials)

 Capacity planning

 Project scheduling

 Cost estimation

 Provisioning

2. Systems Analysis and Requirements

The second phase of the System development. This is where teams consider the

functional requirements of the project or solution. It is also where system analysis

takes place or analyzing the needs of the end users to ensure the new system can

meet their expectations. Systems analysis is vital in determining what a business’s

23
 needs are, as well as how they can be met, who will be responsible for individual

pieces of the project, and what sort of timeline should be expected.

There are several tools businesses can use that are specific to the second phase.

They include:

 CASE (Computer Aided Systems/Software Engineering)

 Requirements gathering

 Structured analysis

3. Systems Design

This is third phase and it describe in detail, the necessary specifications, features

and operations that will satisfy the functional requirements of the proposed system

which will be in place

4. Development

The fourth phase is when the real work begins in particular, we are now in the

major work of the project. Additionally, this phase signifies the start of production.

5. Integration and Testing

The fifth phase involves systems integration and system testing (of programs and

procedures) Testing are be repeated, specifically to check for errors, bugs and

interoperability. This testing will be performed until the end user finds it

acceptable. Another part of this phase is verification and validation, both of which

will help ensure the program’s successful completion.

There is a wide variety of testing necessary to measure quality:

24
  Code quality

 Unit testing (functional tests)

 Integration testing

 Performance testing

 Security testing

6. Implementation

The sixth phase is when the majority of the code for the program is written.

Additionally, this phase involves the actual installation of the newly-developed

system. This step puts the project into production by moving the data and

components from the old system and placing them in the new system via a direct

cutover. While this can be a risky (and complicated) move, the cutover typically

happens during off-peak hours, thus minimizing the risk. Both system analysts and

end-users should now see the realization of the project that has implemented

changes.

7. Operations and Maintenance

The seventh and final phase involves maintenance and regular required updates.

This step is when end users can fine-tune the system, if they wish, to boost

performance, add new capabilities or meet additional user requirements.

3.4.1. SDLC Activities

SDLC provides a series of steps to be followed to design and develop a software product

efficiently. SDLC framework includes the following steps:

25
Communication

This is the first step where the user initiates the request for a desired software product. He

contacts the service provider and tries to negotiate the terms. He submits his request to the

service providing organization in writing.

Requirement Gathering

This step onwards the software development team works to carry on the project. The team

holds discussions with various stakeholders from problem domain and tries to bring out as

much information as possible on their requirements. The requirements are contemplated

and segregated into user requirements, system requirements and functional requirements.

The requirements are collected using a number of practices as given -

 studying the existing or obsolete system and software,

 conducting interviews of users and developers,

 referring to the database or

 Collecting answers from the questionnaires.

26
Feasibility Study

After requirement gathering, the team comes up with a rough plan of software process. At

this step the team analyzes if a software can be made to fulfill all requirements of the user

and if there is any possibility of software being no more useful. It is found out, if the

project is financially, practically and technologically feasible for the organization to take

up. There are many algorithms available, which help the developers to conclude the

feasibility of a software project.

System Analysis

At this step the developers decide a roadmap of their plan and try to bring up the best

software model suitable for the project. System analysis includes Understanding of

software product limitations, learning system related problems or changes to be done in

existing systems beforehand, identifying and addressing the impact of project on

organization and personnel etc. The project team analyzes the scope of the project and

plans the schedule and resources accordingly.

Software Design

Next step is to bring down whole knowledge of requirements and analysis on the desk and

design the software product. The inputs from users and information gathered in

requirement gathering phase are the inputs of this step. The output of this step comes in

the form of two designs; logical design and physical design. Engineers produce meta-data

and data dictionaries, logical diagrams, data-flow diagrams and in some cases pseudo

codes.

Coding

27
This step is also known as programming phase. The implementation of software design

starts in terms of writing program code in the suitable programming language and

developing error-free executable programs efficiently.

Testing

An estimate says that 50% of whole software development process should be tested.

Errors may ruin the software from critical level to its own removal. Software testing is

done while coding by the developers and thorough testing is conducted by testing experts

at various levels of code such as module testing, program testing, product testing, in-

house testing and testing the product at user’s end. Early discovery of errors and their

remedy is the key to reliable software.

Integration

Software may need to be integrated with the libraries, databases and other program(s).

This stage of SDLC is involved in the integration of software with outer world entities.

Implementation

This means installing the software on user machines. At times, software needs post-

installation configurations at user end. Software is tested for portability and adaptability

and integration related issues are solved during implementation.

Operation and Maintenance

This phase confirms the software operation in terms of more efficiency and less errors. If

required, the users are trained on, or aided with the documentation on how to operate the

software and how to keep the software operational. The software is maintained timely by

28
updating the code according to the changes taking place in user end environment or

technology. This phase may face challenges from hidden bugs and real-world unidentified

problems.

Disposition

As time elapses, the software may decline on the performance front. It may go completely

obsolete or may need intense upgradation. Hence a pressing need to eliminate a major

portion of the system arises. This phase includes archiving data and required software

components, closing down the system, planning disposition activity and terminating

system at appropriate end-of-system time.

3.5 Description of the proposed solution and processing algorithm

Courier Management System (CMS) is a modular full business software framework for an

enterprise which possess operations in domestic and international courier services. CMS

performs a variety of activities pertaining to the processes in the logistic context of a

courier business. CMS solution handles the end to end process staring from initiating a

courier order, driver pickup and delivery of a courier business. CMS covers all the controls

and processes involved in International Courier Import Services, International Courier

Export Services and Domestic Pickup & Delivery.

Courier Management System (CMS) is an integrated full business software framework for

an enterprise which possesses procedures in domestic and international courier services.

CMS performs a variety of activities pertaining to the processes in the logistic situation of

a courier business. CMS solution handles the end to end process starting from initiating a

courier order, driver pickup and delivery of a courier business.

29
CMS covers all the controls and processes involved in International Courier Importation

Services, International Courier Export Services, and Domestic Pickup & Delivery.

Check Online Shopping Project in PHP

There Are 3 Module Are Used in This Project Like,

USER

New registration:

The user can register himself in the system. This is fully automated process assign

verification using admin.

View /update login details:

Users can view their details and update his details if required.

View tracking information:

The user can view the information about courier tracking.

View offers:

The user also can view the offer related to him.

30
ADMIN

View/update user details:

Only admin has right to change the user details.

Update policy details:

Only admin has right to change the policy details.

Track the courier details:

Like any other user, admin can also track and instruct his team to manage the consignment.

Update offers:

Admin can update the offer details.

Branch Admin

This module helps the branch admin to use various facilities after the logged on courier

services like: –

Update status:

Their main work is to update consignment details and status of consignment

View status:

View the status of others consignment and add the current information of consignments.

31
3.6 Implementation

3.6.1 The E-R diagram

An entity-relationship diagram (ERD) is a graphical representation of an information

system that shows the relationship between people, objects, places, concepts or events

within that system. An ERD is a data modelling technique that can help define business

processes and can be used as the foundation for a relational database.

The three main cardinal relationships are:

One-to-one (1:1): For example, if each customer in a database is associated with one

mailing address.One-to-many (1:M) : For example, a single customer might place an order

for multiple products. The customer is associated with multiple entities, but all those

entities have a single connection back to the same customer.

Many-to-many (M:N) : For example, at a company where all call centre agents work with

multiple customers, each agent is associated with multiple customers, and multiple

customers might also be associated with multiple agents.

32
 3.6.2 Data Flow Diagrams

FLOWCHART A flowchart is a formalized graphic representation of a logic sequence,

work or manufacturing process, organization chart, or similar formalized structure. The

purpose of a flow chart is to provide people with a common language or reference point

when dealing with a project or process. Flowcharts use simple geometric symbols and

arrows ( ) to define relationships.

In programming, for instance, the beginning or end of a program is represented by an oval

A process is represented by a rectangle ( )

33
A decision is represented by a diamond ( )

And an I/O process is represented by a parallelogram ( ).

The Internet is represented by a cloud ( ).

Data Flow Diagram (DFD)

A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs

and outputs. As its name indicates its focus is on the flow of information, where data

comes from, where it goes and how it gets stored. There are essentially four different types

of notations for data flow diagrams

A) Process Notations

B) Data store Notations

C) Dataflow Notations

D) External Entity Notations

The DFDs also consists of Context Diagrams and DFD Layers and Levels. Context

Diagrams: A context diagram is a top level (also known as "Level 0") data flow diagram

34
DFD Layers: Draw data flow diagrams can be made in several nested layers. DFD Levels:

The first level DFD shows the main processes within the system. Each of these processes

can be broken into further processes until you reach pseudo code.

35
Figure 4: LEVEL 0 DATA FLOW DIAGRAM

Signup courier management system shipment login billing delivery.

3.6.3 Use Cases Diagrams

Figure 5: Use-case Diagram Figure 6: Use case2 Diagram

36
 3.6.4 Back-end coding

3.7 Deployment and installation

Installation generally refers to the activities required to physically instate the system; this

will likely include connecting interfaces to other systems such as electrical, computer, or

security systems, and may include software interfaces as well. Installation planning should

generally document the complexity of the system, the range of environmental conditions

expected in the operational environment, any interface specifications, and human factors

requirements such as safety. When real-world conditions require changes in the installation

requirements, these should be documented and discussed with the relevant stakeholders.

37
CHAPTER FOUR

4.0 RESULTS AND ANALYSIS

4.1 Introduction

Systems development is the process of planning, defining, designing, testing and

implementing a new software application program. It include the internal development of

customized systems, the creation of database systems, or the acquisition of third party

developed software. Written standards and procedures guided all information systems

processing functions. The organization’s management must define and implement

standards and an appropriate system development life cycle methodology was adopted to

governing the process of developing, acquiring, implementing, and maintaining the

system.

This chapter is devoted to show the procedures in proposed system, input Forms of the

proposed system, output (Reports Generated) by the Proposed System, system

Requirements, challenges and limitations of the proposed system.

4.2 Procedures in Proposed Step

The preceding two chapters have discussed the parameterization of existing systems and

evolving systems. In this chapter we consider models of proposed systems: major new

systems and subsystems that are undergoing design and implementation. The process of

design and implementation involves continual tradeoffs between cost and performance.

Quantifying the performance implications of various alternatives is central to this process.

It’s also extremely challenging. In the case of existing systems, measurement of data is

available. In the case of evolving systems, contemplated modifications often are

38
straightforward and limited experimentation may be possible in validating a baseline

model. In the case of proposed systems, these advantages do not exist. For this reason, it is

tempting to rely on unexpected performance projections, which often prove to be

significant in error. Recently, progress has been made in evolving a general framework for

projecting the performance of proposed systems. User satisfaction with a new application

system depends on a significant extent on the system’s ability to deliver performance that

is acceptable and consistent.

4.3 Input Forms of the proposed system

4.4 Output (Reports Generated) by the Proposed System

4.5 System Requirements

39
 4.5.1 Application Software requirements

Clients End:

 Browser: Any Web Browser (Chrome/Firefox Considered Best)

 Processor: Atom Processor or more

 RAM: 512MB or More

 Disk space: 128GB or more

Server End:

 Web Server: IIS6 or Higher

 Database Server: Xampp server

 Processor: Atom Processor or more

 RAM: 2GB or more

 Disk Space: 128GB or more

4.5.2 System Requirements:

 Operating System :Any (Linux, Windows, Macetc)

1.5.3 System Software requirements

 Tracking device

4.6 Challenges and Limitations of the Proposed System

Potential to Not Be as Stable as Larger Couriers

Smaller couriers tend to not have the stability of larger couriers. A lot of this comes down

to financial backing and problems could arise that you’re unaware of when first working

with a smaller firm.

40
With this responsibility on your shoulders, it’s important that you recognise these potential

issues beforehand.

Limited Resources and Network Supply Chain can lead to Service Restrictions

Smaller couriers don’t the same network supply chain or as many resources as large

couriers do. Therefore, there might be fewer options to take advantage of should potential

issues arise.

This shows that smaller couriers might not have the network base to deal with special

requests as large couriers will. Plus, there may also be more restrictions to the service

offered. So, there’s a chance you’ll have to settle for a one-size-fits-all approach rather

than a service catered to your needs.

41
CHAPTER FIVE

5.0 SUMMARY OF FINDINGS, CONCLUSION AND RECOMMENDATION

5.1 Introduction

This chapter comprises of Summary of findings, Limitations of the system and conclusions

made on the system as well as some recommendations for future researchers and

developers.

5.2 Limitations of the system

The system as a web base application is designed purposely to be used online which

requires Internet connection.

The system can’t the current location of a delivery until it reaches the office or a nearby

branch.

5.3 Summary of comments from supervisor, users and your self

5.4 Conclusion of Courier Management System

The project titled ‘Courier Management System’ was developed to the courier services and

direction and with their help. The system was tested and the performance of the system

was found to be acceptable.

All the necessary output was created. The system was found to be user-friendly with help

message for the customer. The menu Driven Architecture of the system provide an easy to

use environment for the users.

42
The system was implemented successfully. The manpower and working hours needed to

operate the system was less and it was seen to be more secure. Thus, the Project was

completed successfully.

5.5 Recommendations

5.5.1 Recommendations on future enhancement of courier management system

It is still mature and fully enthusiastically. Any requirements, this project is completed but

still, they want to update and modify some modules. We are always thinking about

association requirements also growing day by day.

We always want to implement something more. This project is completed when you watch,

but we wish of implementing more things.

 Online Chat

 Overseas Service

 Pickup Request On chat

 Extending geographical research

5.5.3 Recommendations for users

Company wants to computerized system in such a way that the person need not to go

through the rate file every time. But here the “RATE TARIFE” means “RateTable” is

maintain in computer memory so that the values of consignment can be easily derived &

changed if there any it can be accommodated. The file of regular consignor is maintained

so that billing at end of the month is calculated easily.

43
Users of the system are required have the required software, hardware and system

requirements of the system.

5.5.4 Recommendations for academicians

CMS can be personalized to fit your business and can either be used as a complete system

or as separate modules.This idea of the project represents the ‘Courier Service

Management System’. The system is being used for day to day actions such as maintain

employee details, booking a courier, maintain hub details, maintain corporation details,

process data of employees and many other things.

Courier management computerization is “the incorporation of appropriate technology to

help manager manage information. Technology is considered suitable when it utilizes the

most abundant domestic possessions and conserves investment and skilled personnel”.

The main aim of this project is to computerize the maintenance of courier management

44
6.0 REFERENCES

1. Eduproject.com.ng logo - RESEARCH PROJECT TOPICS AND PROJECT

TOPICS ON EDUCATION

2. SEBoK v. 2.2, released 15 May 2020

3. https://www.sebokwiki.org/wiki/System_Deployment

4. http://researchmaterials.com.ng/

5. http://services.lovelycoding

45
46
47