UNION CHRISTIAN COLLEGE ALUVA

[Re-accredited with A grade (cycle 4) by National Assessment and Accreditation council

(NAAC)]

FASTTRACK
REPORT OF MINIPROJECT
Submitted in partial fulfilment of the requirement for the award of the degree of

B.Sc. COMPUTER SCIENCE

By Mahatma Gandhi University, Kottayam during 2022 – 2025

Submitted by

ANJOLI THANKACHAN(Reg No: 220021026099)

ANISHMA VA(Reg No: 220021026098)

Under the guidance of MR.CIJIN K PAUL

1
 UNION CHRISTIAN COLLEGE ALUVA
[Re-accredited with A grade (cycle 4) by National Assessment and Accreditation council
(NAAC)]

Department of Computer Science

CERTIFICATE
This is to certify that the Mini Project report entitled ‘FAST TRACK submitted by

ANJOLI THANKACHAN(Reg No:220021026099) and ANISHMA VA(Reg No:220021026098)

In partial fulfilment of the requirements for the award of BSc in Computer Science during the academic
year 2021 – 2022. The project report has been approved as it satisfies the academic requirements in
respect of project work prescribed for the Bachelor of Computer Science.

Mr.CIJIN K PAUL Mr.CIJIN K PAUL

Project Guide Head of the Department
Dept. of Computer
Dept. of Computer Science Science

Submitted for the university examination held on: …………………………………

Internal Examiner External Examiner

ACKNOWLEDGEMENT

2
 First of all, we thank God Almighty for His grace and mercy that enabled us in the
finalization of this project.

Our sincere thanks to our project guide, Mr.Cijin k paul for his valuable suggestions and
for the overwhelming concern and guidance from the beginning to the end of our project.

We are grateful to all my teachers of the department of Computer Science for the
encouragement given to us during this period. We express our heartfelt thanks to all our
friends and family members for their cooperation and support.

ANJOLI THANKACHAN
ANISHMA VA

ABSTRACT

Our project, Courier Management System, is a PHP, MySQL, and HTML-based

application designed to manage courier services efficiently. The system is tailored for local courier
operations and eliminates the need for manual processes. It provides a streamlined interface for admins,
staff, and users, each with specific roles and access levels.

The system focuses on:

3
  Automating sender/receiver details entry and courier status updates.

 Enabling users to track their packages through a unique tracking ID.

 Facilitating role-based access with modules for admin, staff, and users.

This project addresses inefficiencies in manual courier systems and ensures real-time updates and
centralized management of courier data.

The “ FAST TRACK“ is an application developed using HTML,CSS,JAVASCRIPT as front end and
MySQL as back end .The proposed system consists of three modules Admin,staff and Users.

CONTENTS

1. INTRODUCTION 7
1.1 OVERVIEW OF THE SYSTEM 7
1.2 PROBLEM DEFINITION AND OBJECTIVE 7

2. SYSTEM ANALYSIS 8
2.1 INTRODUCTION 8

2.2 EXISTING SYSTEM 9

2.3 PROPOSED SYSTEM 9

2.3.1 MODULE DESCRIPTION 10

2.4 FEASIBILITY STUDY 11

2.4.1 TECHNICAL FEASIBILITY 12

4
 2.4.2 ECONOMICAL FEASIBILITY 12

2.4.3 OPERATIONAL FEASIBILITY 13

2.5 SYSTEM SPECIFICATION 13

2.5.1 TOOLS/PLATFORM 14

2.5.2 HARDWARE SPECIFICATION 18 2.5.3

SOFTWARE SPECIFICATION 18

3. SYSTEM DESIGN AND DEVELOPMENT 19

3.1 DATA FLOW DIAGRAM 20

3.2 DATABASE DESIGN 25
3.3 INPUT AND OUTPUT SCREENS 30

4. SYSTEM TESTING 67

5. SYSTEM IMPLEMENTATION 71

6. LIMITATIONS AND FUTURE ENHANCEMENTS 73

7. BIBLIOGRAPHY 74

5
 1.INTRODUCTION

1.OVERVIEW OF THE SYSTEM

The Courier Management System is a robust web application designed to automate and
simplify courier operations. With a focus on local courier services, the system provides tools
for efficient package tracking, status updates, and management of sender/receiver details.

The application incorporates three primary roles:

1. Admin: Responsible for managing staff, entering sender/receiver details, and updating
courier statuses.

2. Staff: Assists in updating package statuses and ensuring operational efficiency.

3. User: Tracks packages using a tracking ID and stays updated on delivery statuses.

By automating these processes, the system eliminates errors, reduces manual workload, and
ensures seamless courier management.

1.1PROBLEM DEFINITION AND OBJECTIVE

Manual courier systems are prone to errors, inefficiencies, and delays. There is a lack of real-time
tracking, making it difficult for users to stay informed about their package statuses.

6
Objectives:
1. Develop a user-friendly web application for courier management.
2. Automate sender and receiver data entry and tracking.
3. Provide a centralized database for real-time updates.

2.SYSTEM ANALYSIS

2.1 INTRODUCTION

System analysis is the detailed study of various operations performed by the system and their
relationships within and outside the system. It is a process of gathering and interpreting facts,
diagnosing problems and using this information to recommend improvements to the system.

System analysis is an important activity that takes place when building new information
system or changes the existing ones. The systems are often made up of many interrelated tasks.
Changes to many of these tasks or addition of new tasks can affect existing ones. The investigation into
the system operation and possible changes to the system is called analysis.

System analysis is the way of studying a system with an eye on solving its problem
using computers. It is the most essential part of the project development. During analysis, data are
collected on available files, decision points, and transactions handled the present system. Training
experience and common sense are required for the collection of information need to do the analysis.
Once the analysis is completed, analyst has firm understanding of what is to be done. To analyse a
system, one has to study the system work in detail, before designing to the appropriate computerbased
system that will meet all requirements of the system.

System analysis includes the following steps:

• Requirement analysis

• Feasibility study

• Analysis

• Design

7
 • Implementation

• Post implementation and maintenance

The above steps constitute a logical framework for the system analysis.

2.2EXISTING SYSTEM

In manual courier systems, data is recorded in physical ledgers or spreadsheets. This process is time-
consuming, error-prone, and lacks transparency. Key challenges include:

 Delays in updating courier statuses.

 Difficulty in tracking packages.

 Errors in manual data entry and retrieval.

 Lack of accountability in operations.

2.3PROPOSED SYSTEM

The proposed Courier Management System is designed to overcome these

challenges by automating the process. The system provides role-based access to
admins, staff, and users, ensuring smooth operations and transparency.

Features:
1. Admin Dashboard:

o Manages staff details.

o Adds courier entries, including sender and receiver details.

o Updates courier statuses such as “Order Created”, “Order Dispatched”, or

“Reached Nearest Hub”.

8
 2. Staff Dashboard:

o Updates courier statuses such as "In Transit," "Delivered," or "Pending."

o Ensures operational smoothness.

3. User Interface:

o Tracks packages using unique IDs.

o Provides real-time updates on courier statuses.

Our proposed system has the following advantages:

▪ User friendly interface.

▪ Fast access to database.
▪ Less error.
▪ More Storage Capacity.
▪ Look and Feel Environment.
▪ Quick tracking.

2.3.1MODULE DESCRIPTION

This website is comprised of the following modules:

1. Admin

2. User

3. Staff

1. ADMINISTRATOR

An administrator is the super user of the system

▪ Admin can login using their username and password and can access admin
dashboard.

▪ Features such as deleting staffs as well as updating order status .

9
 ▪ The roles granted by the administrator cannot be changed by the staff.

▪ The admin has the ability to add new orders along with its details ,manage
activities.

▪ Admin has access to the admin dashboard that contains all information such
as order table and staff tables.

2. USER

▪ Tracks courier statuses using tracking IDs.

▪ Provides feedback and suggestions.

3. STAFF

▪ Staffs can login using their username and password and can view
the status of orders by user.

▪ Updates courier statuses such as "In Transit," "Delivered," or "Pending."

2.4 FEASIBILITY STUDY

The feasibility study assesses whether the proposed Courier Management System is viable and practical.
This study includes three major aspects: Technical Feasibility, Economic Feasibility, and Operational
Feasibility.

2.4.1 TECHNICAL FEASIBILITY

1 TECHNOLOGY STACK

• The system uses proven and widely used technologies, making it technically feasible to
develop and maintain:
• Frontend: HTML, CSS

• Backend: PHP

10
 • Database: MySQL

• Server Environment: WAMP (Windows, Apache, MySQL, PHP)

• These technologies are well-supported with extensive documentation and developer

communities, ensuring a smooth development process.

2 TECHNICAL CAPABILITIES

 The team has the necessary skills and expertise in PHP, MySQL, and web development.

 The application design is based on a modular architecture, ensuring scalability and maintainability.

 Compatibility with various operating systems (Windows/Linux) and web browsers makes the
system accessible to users.

2.4.2 ECONOMICAL FEASIBILITY

1 COST ANALYSIS

 Development Costs: Minimal as the system is developed in-house using open-source technologies.

 Operational Costs: Includes hosting, maintenance, and occasional updates. These are significantly
lower due to the use of free software (e.g., PHP, MySQL).

 Training Costs: Minimal, as the system is user-friendly and requires only basic training for admins
and staff.

2 BENEFITS

 Eliminates costs associated with manual data handling (e.g., paper records, human errors).

 Improves efficiency and productivity, reducing operational delays.

 Centralized tracking leads to faster resolution of courier-related issues, improving customer

satisfaction.
2.3 Return on Investment (ROI)

The system enhances operational efficiency, reduces manual errors, and improves customer experience.
These factors contribute to cost savings and a faster ROI.

2.4.3 OPERATIONAL FEASIBILITY

11
1 End-User Support

 Admin Module: Designed to provide intuitive tools for managing couriers and staff.

 Staff Module: Ensures ease of status updates and task management.

 User Module: Simple and accessible interface for tracking couriers with real-time updates.

2 User Acceptance

 The system is designed with a user-friendly interface that minimizes the learning curve for all
stakeholders.

 Feedback mechanisms can be incorporated to continuously improve the application.

3 Implementation Readiness

 The proposed system is aligned with the operational goals of the organization.

 Adequate training and documentation will ensure smooth adoption by users.

2.5SYSTEM SPECIFICATION

1. HARDWARE SPECIFICATIONS

1.1 Development Environment

 Processor: Intel Core i5 or higher (2.4 GHz or better)

 Memory (RAM): Minimum 8 GB (16 GB recommended for faster performance)

 Hard Disk: 500 GB or higher (SSD recommended for faster read/write speeds)

 Monitor: VGA or higher resolution monitor (1920x1080 Full HD recommended)

 Input Devices: Standard Keyboard and Mouse

 Networking: Ethernet or Wi-Fi connectivity

1.2 Deployment Environment

 Server:
12
 o Dedicated or shared hosting server capable of running PHP and MySQL

o Minimum 2 GHz dual-core processor

o Minimum 4 GB RAM

o Minimum 50 GB disk space

 Client Machines:

o Any device capable of running a modern web browser (e.g., desktops,

laptops, tablets, smartphones)

o Browsers like Google Chrome, Mozilla Firefox, or Microsoft Edge

2.SOFTWARE SPECIFICATIONS

 Operating System: Windows 10/11, Linux (Ubuntu 20.04+), or macOS

 Text Editor/IDE:

o Visual Studio Code

o Sublime Text

o Notepad++ (optional)

 Local Server:

o WAMP (Windows)

o XAMPP (Cross-platform)

o LAMP (Linux)

2.2 Backend

 Programming Language: PHP (version 7.4 or later)

 Database: MySQL (version 5.7 or later)

2.3 Frontend

 Markup and Styling:

13
 o HTML5

o CSS3

 Frameworks and Libraries: Optional use of Bootstrap for responsive design

2.4 Browser Requirements

 Supported Browsers: Google Chrome, Mozilla Firefox, Safari, and Microsoft Edge

 Browser Compatibility: HTML5 and CSS3 compliant

2.5.1 TOOLS/PLATFORM

FRONT END
➢ HTML

Hypertext Markup Language (HTML) is the standard markup language for creating web pages and
web applications. With Cascading Style Sheets (CSS) and JavaScript, it forms a triad of cornerstone
technologies for the World Wide Web.
Web browsers receive HTML documents from a web server or from local storage and
render the documents into multimedia web pages. HTML describes the structure of a web page
semantically and originally included cues for the appearance of the document.
HTML elements are the building blocks of HTML pages. With HTML
constructs, images and other objects such as interactive forms may be embedded into the
rendered page.

HTML provides a means to create structured documents by denoting structural semantics for text
such as headings, paragraphs, lists, links, quotes and other items. HTML elements are delineated by tags,
written using angle brackets. Tags such as and directly introduce content into the page. Other tags such as
surround and provide information about document text and may include other tags as subelements.
Browsers do not display the HTML tags, but use them to interpret the content of the page. HTML can
embed programs written in a scripting language such as JavaScript, which affects the behaviour and

content of web pages. Inclusion of CSS defines the look and layout of of content. The World Wide Web
Consortium (W3C), maintainer of both the HTML and the CSS standards, has encouraged the use of CSS
over explicit presentational HTML since 1997.

14
 ➢ CSS

Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a
document written in a markup language like HTML. CSS is a cornerstone technology of the World
Wide Web, alongside HTML and JavaScript.
CSS is designed to enable the separation of presentation and content, including layout,
colours, and fonts. This separation can improve content accessibility, provide more flexibility and
control in the specification of presentation characteristics, enable multiple web pages to share
formatting by specifying the relevant CSS in a separate .css file, and reduce complexity and repetition
in the structural content.

Separation of formatting and content also makes it feasible to present the same
markup page in different styles for different rendering methods, such as on-screen, in print, by voice
(via speech-based browser or screen reader), and on Braille-based tactile devices. CSS also has rules
for alternate formatting if the content is accessed on a mobile device.
The name cascading comes from the specified priority scheme to determine which
style rule applies if more than one rule matches a particular element. This cascading priority scheme is
predictable.
The CSS specifications are maintained by the World Wide Web Consortium (W3C).
Internet media type (MIME type) text/CSS is registered for use with CSS by RFC 2318 (March
1998). The W3C operates a free CSS validation service for CSS documents.
In addition to HTML, other markup languages support the use of CSS
including XHTML, plain XML, SVG, and XUL.

➢ JAVASCRIPT

JAVASCRIPT is a often abbreviated as JS, programming language that is one of the core technologies,
alongside HTML and CSS. As of 2022, 98% of websites use JavaScript on the client side for webpage
behavior, often incorporating third-party libraries. All major web browsers have a dedicated JavaScript
engine to execute the code on users' devices.

15
 The ECMAScript standard does not include any input/output (I/O), such as networking,
storage, or graphics facilities. In practice, the web browser or other runtime system provides
JavaScript APIs for I/O. JavaScript engines were originally used only in web browsers, but are now
core components of some servers and a variety of applications.

BACK END

➢ PHP

PHP started out as a small open source project that evolved as more and more people found out
how useful it was. Rasmus Lerdorf unleashed the first version of PHP way back in 1994.

• PHP is a recursive acronym for PHP: Hypertext Pre-processor.

• PHP is a server-side scripting language that is embedded in HTML. It is used to

manage dynamic content, databases, session tracking, even build entire e-commerce sites.

• It is integrated with a number of popular databases, including MySQL, PostgreSQL, Oracle,

Sybase, Informix, and Microsoft SQL Server.

• PHP is pleasingly zippy in its execution, especially when compiled as an Apache module on the
Unix side. The MySQL server, once started, executes even very complex queries with huge result
sets in record-setting time.

• PHP supports a large number of major protocols such as POP3, IMAP, and LDAP. PHP4 added
support for Java and distributed object architectures (COM and CORBA), making n-tier
development a possibility for the first time.

• PHP is forgiving: PHP language tries to be as forgiving as possible.

Common uses of php,

16
 • PHP performs system functions, i.e., from files on a system it can create, open, read, write, and
close them.

• PHP can handle forms, i.e., gather data from files, save data to a file, through email you can send
data, return data to the user.

• You add, delete, modify elements within your database through PHP.

• Access cookies variables and set cookies.

• Using PHP, you can restrict users to access some pages of your website.

• It can encrypt data.

Characteristics of PHP,

Five important characteristics make PHP's practical nature possible:

• Simplicity.

• Efficiency.

• Security.

• Flexibility.

• Familiarity.

➢ MySQL

MySQL is a fast, easy-to-use RDBMS being used for many small and big businesses.
MySQL is developed, marketed and supported by MySQL AB, which is a Swedish company.
MySQL is becoming so popular because of many good reasons:

• MySQL is released under an open-source license. So you have nothing to pay to use it.

17
 • MySQL is a very powerful program in its own right. It handles a large subset of the
functionality of the most expensive and powerful database packages.

• MySQL works on many operating systems and with many languages including, PERL, C,
C++, JAVA, etc.

• MySQL works very quickly and works well even with large data sets.

• MySQL is very friendly to PHP, the most appreciated language for web development.

• MySQL supports large databases, up to 50 million rows or more in a table. The default file
size limit for a table is 4GB, but you can increase this (if your
operating system can handle it) to a theoretical limit of 8 million terabytes (TB).

• MySQL is customizable. The open-source GPL license allows programmers to modify the
MySQL software to fit their own specific environments.

OTHER TOOLS

2.5.2 HARDWARE SPECIFICATION

➢ Processor: Any processor with minimum 1.2 GHz clock speed

➢Memory: Minimum of 1GB RAM

➢ Storage: 100 GB or above 2.

2.5.3SOFTWARE SPECIFICATION

➢ Front-End: HTML5 with CSS3 and JavaScript

➢ Back-End: PHP 7.2

➢ Database: MySQL 5.7 with phpMyAdmin 4.8 server interface

➢ Operating System: Windows (Version 7 or Later), Android (Version 8 or Later)

➢ Web Browser: Google Chrome (Version 67 or Later)

➢ Server: Apache HTTP Server 2.4 or WampServer 3.1

18
 ➢ Other Tools: PWA.

3. SYSTEM DESIGN AND DEVELOPMENT

➢ system study started off with initial analysis of the existing system. The
analysis was helpful in giving through understanding of the present system. The analysis of the
existing system is also uncovered many flaws and elimination of flaws formed the major objective
of the proposed system.
➢ A through knowledge the well details of the production terminologies etc.,
were understood clearly before system design was initiated. The study of existing system
ended up with verifying the stock quantity to be issued with the request the database size was
found to ever increasing & that the present set up of following manual method would not service
long. This leads to the idea of introducing the DBMS in developing the software. this idea was
appreciated when the database need hierarchical security & made going in for an DBMS
inevitable due to various other reasons.

Architecture
The system adopts a Three-Tier Architecture, which separates the application into three layers
for better scalability, maintainability, and efficiency:

1. Presentation Layer:

o Composed of user interfaces for admin, staff, and users.

o Built using HTML and CSS for responsiveness and user-friendly navigation.

2. Business Logic Layer:

o Includes PHP scripts to manage core functionalities like adding couriers, updating statuses,
and tracking.

3. Data Layer:

o MySQL database for storing and managing system data, such as sender/receiver details,
courier statuses, and user information.

3.1 DATA FLOW DIAGRAMS

19
 A DFD, also known as a „bubble chart‟ has the purpose of clarifying system requirements

and identifying major transformations that will become programs in system design. A DFD
consists of a series of bubbles joined by lines. The bubbles represent data transformations and
the lines represent the data flow in the system. A data flow diagram may be used to represent a
system or software at any level of abstraction. DFD‟s can be partitioned into levels thatrepresent
increasing information flow and functional details.

A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the processes that
change or transform data throughout a system. It is a structured analysis and design tool that can
be used for flowcharting in place of, or in association with, information oriented and
processoriented flowcharts. When analysts prepare the DFD, they specify the user needs at a
level of detail that virtually determines the information flow into and out of the system and the
required data sources. This network is constructed by using a set of symbols that do not imply a
physical implementation. The DFD reviews the current physical system, prepares input and
output specification, specifies the implementation plan etc.

Basic data flow diagram symbols are:

A “Rectangle” defines a source (originator) or destination of a System data.

An “Arrow” identifies the data flow. It is a pipeline through which

Information flows.

A “Circle” represents a process that transforms incoming

Dataflow(s)into outgoing dataflow(s).

20
 An “Open Rectangle” is a data store.
Steps to construct Data Flow Diagrams:

Two steps are commonly used to construct a DFD:

• Process should be named and numbered for easy reference. Each name should be representative
of the process.

• The direction of flow is from top to bottom and from left to right.

When a process is exploded in to lower-level details they are numbered.

DFD
CONTEXT DIAGRAM

LEVEL- 0

LEVEL- 1 USER

21
LEVEL- 1 STAFF

22
LEVEL- 1 ADMIN

23
 Tbl_Feedback

3.2 DATA BASE DESIGN

24
 The data design transforms the information domain model created during analysis into the data
structures that will be required to implement the software. The data objects and the relationships
defined in the entity relationship diagram and the detailed data content depicted in the data dictionary
provide the basis for the data design activity. The data design transforms the information domain model
created during analysis into the data structures that will be required to implement the software. The
overall objective in the development of database technology has been to treat data as an organizational
resource and as an integrated whole. Database management system allows data to be protected and
organized separately from other resources. Database is an integrated collection of data.
This is the difference between logical and physical data.

The organization of data in the database aims to achieve three major objectives:

• Data Integration

• Data Integrity

• Data Independence

Project scheduling and tracking allows data to be protected and organized separately from other
resources. Database is a collection of data. The database is an organization of all data elements that are
pertinent to the system, with precise definitions so that both user and system analyst will have a common
understanding of inputs, outputs, components of stores and intermediate calculation. There are six major
steps in design process.

The first five steps are usually done on a paper and finally the design is implemented.

• Identify the table and relationships.

• Identify the data that is needed for each table and relationship.

• Resolve the design.

• Verify the design.

• Implement the design.

TABLES

25
ACTIVITIES

FIEL DATATYPE DESCRIPTION

D
ActivityID Int(11),AUTO_INCREMENT ID of activity

ActivityName Varchar(500) Name of activity

URL Varchar(500) URL of the website

Activityimage Varchar(500) Activity image

AUTHOR
FIELD DATATYPE DESCRIPTION

AuthorID Int(20),AUTO_INCREMENT ID of Author

Authorname Varchar(50) Name of Author

AuthorDetails Varchar(50) Details of Author

BOOK CATEGORY
FIELD DATATYPE DESCRIPTION

BookCategoryID Int(11),AUTO_INCREMENT ID of book Category

BookCategory Varchar(500) Category of books

BOOK DETAILS
FIELD DATATYPE DESCRIPTION
BookID Int(20),AUTO_INCREMENT ID of book

26
 BookName Varchar(50) Name of book
AuthorID Int(20) ID of Author
BookCategoryID Int(20) ID of book Category
Bookdetails Varchar(500) Details of book
Price Double(6,2) Price of book
Stock Int(4) Books in stock
Pdf Version Longtext Pdf of book
BookImage Varchar(400) BookImage
ReadFree Int(11) Free book or not

DONATE BOOKS
FIELD DATATYPE DESCRIPTION

dbookid Int(12),AUTO_INCREMENT ID of donated book

dbookname Varchar(50) Name of donated book

dauthor Varchar(50) Author of donated book

dcategory Varchar(50) Categoryof donated book

dbookdetails Varchar(50) Details of donated book

dprice Double(6,2) Price of donated book

dstock Int(12) Donated Books in stock

UserID Int(12) ID of user

DONATION

FIELD DATATYPE DESCRIPTION

donationid Int(10),AUTO_INCREMENT ID of donated amount

27
 UserID Int(10) ID of user

Amount Double(6,2) Amount donated

Status Int(2) Status of donation

Date Varchar (20) Date of donation

DOUBT CLEARANCE

FIELD DATATYPE DESCRIPTION

DoubtID Int(20),AUTO_INCREMENT ID of doubt posted

UserID Int(12) ID of user

Doubt Varchar(100) Doubt posted

Reply Varchar(100) Reply given for doubt posted

Staffid Int(12) ID of staff

date Varchar(100) Date when doubt was posted

FEEDBACK

FIELD DATATYPE DESCRIPTION

feedbac kid Int(11),AUTO_INCREMENT ID of feedback

member name Varchar(100) Name of member

email_id Varchar(200) Email of member

phoneno Varchar(100) Phone no of member

feedback Varchar(500) Feedback given

28
PURCHASE BOOK

FIELD DATATYPE DESCRIPTION

PurchaseI D Int(10),AUTO_INCREMENT ID of purchase

Purchase Date Varchar(100) Date of purchase

UserId Int(10) ID of user

Bookid Int(10) ID of book

Status Int(2) Purchase status

CopiesNo Int(10) No of copies purchased

Pric Int(10) Price of purchased

e
book

REQUEST FOR NEEDY

FIELD DATATYPE DESCRIPTION

RequestID Int(11),AUTO_INCREMENT ID of request

UserID Int(11) ID of user

BookID Int(11) ID of book

RequestDate Varchar(100) Date of request

Qty Int(11) Quantity of book

requested

Description Varchar(500) Description of book

29
Status Int(11) Status of book
requested

USERS

FIELD DATATYPE DESCRIPTION

UserID Int(10),AUTO_INCREMENT ID of user

UserName Varchar(50) Username of user

Password Varchar(50) Password of user

UserTy pe Varchar(1) Type of user

Name Varchar(50) Name of user

Address Varchar(50) Address of user

Phone Varchar(12) Phone no of user

Approv eStatus Int(11) Status of approval

BlockStatus Int(11) Block status

30
3.3 INPUT AND OUTPUT SCREEN

The input design is the process of converting the user-oriented data into the computer-based
form. There for user interface design is very important for any application. If the interface design
is good, user will fall into the interactive software application. The input design requirement such
as user friendliness, consistent format and interactive dialogue for giving the right message and
help for users at the right time, are considered for the development of this project.

User-friendly screen format can reduce the burden on end user,

who is not highly proficient in computers. An important step in input design stage is the design
of source document. Source document is the form in which the data are initially captured. The
next step is the design of document layout. In the layout organizes the document by placing
information, where it will be noticed and established the appropriate sequence of items.
Inaccurate input data are the most common cause of error in data processing. Errors entered by
data entry operators can be controlled by input design. Input data are collected and organized
into group of similar data. Appropriate input media are selected for processing. The goal of
designing input data is to make data entry as easy and logical free form errors.

The objectives of input design are:

• To produce a cost-effective method of input.

• To make the input forms understandable to user.

• To ensure the validation of data input.
• To achieve the highest possible level of accuracy.

In the proposed system, data has to be accurate and complete. If not, error messages are displayed to the
user and he is unable to proceeds to the next stage action unless he corrects his data. Duplicate entries
are not allowed. The data validation procedure of the proposed system provides program checks for the
completeness, consistency, reasonableness and sequence of the system. The major step in a system
design is the preparation of the input forms and output reports in the
form application to the user. The major objectives of the system design are to use the package easily by
any computer operator.

31
 Computer output is the most important and direct source of information to the
user. The usefulness of the application depends on the output design. Efficient, intelligible output
design should improve the system relationship with the user and help in decision-making. The most
common are reports, screen formats, printed forms etc. The output from a system is the justification for
its existence. A quality output is one, which meets the requirements of the end user and presents the
information clearly.
The various types of output required by the system are:

• External output, whose destination is within concern and requires special attention.

• Internal output, whose destination is within concern and requires careful design because they
are the user's main interface within the computer.

• Operational output, whose use is purely within the computer department, e.g., program
listening, usage statistics etc.
• Interactive output, which involves the user in communicating directly with computers.

Outputs definition take into account the type of output contents, its frequency
and its volume. The appropriate output media is determined for outputs. Once the output media is
chosen, the detail specifications of output documents are carried out. The nature required from the
proposed system is determined during logical design stage itself. The physical design stage takes the
outline of the output from the logical design and produces the output as specified during the logical
design phase. Outputs from computer systems are required primarily to communicate the results of
processing to the user. They are also used to provide a permanent copy of these results for later
consultation. In the case of administration, viewing the whole information of the system is very
important. So, output design needs to be carefully designed. Here the details of various files are
displayed through table, administrator can select any file or any directory; he can view contents of
those files he has selected. In the output design it is determined how the information s to be
displayed for immediate need and also the hard copy output. A major form of output is a hard copy
from the printed. Printouts should be around the output requirements for the user. CRT screen
displays are the examples for providing computer-based output.

32
LOGIN PAGE

33
COMMON BOOK SEARCH

34
PAINT

FREE GAME

35
CONTACT US

36
37
FEEDBACK

38
REGISTRATION PAGE

39
MEMBERHOME

40
MEMBERBOOKSEARCH

41
PURCHASE BOOKS

REQUEST FOR NEEDY

42
43
ACTIVITIES

44
DOUBTCLEARANCE

45
DONATE AMOUNT

46
DONATE BOOKS

PURCHASE SUCCESS PAGE

47
PURCHASE BOOK STATUS

48
REQUEST FOR NEEDY STATUS

49
DONATED AMOUNT STATUS

50
STAFF HOME

51
52
STAFF REPLY DOUBTS

53
STAFF VIEW ORDERED BOOK BY USER

54
STAFF VIEW BOOK REQUESTS FOR NEEDY

55
ADMIN HOME

56
ADMIN ADD BOOK CATEGORY

57
ADMIN ADD AUTHOR DETAILS

58
ADMIN ADD BOOK DETAILS

59
ADMIN APPROVE/REJECT MEMBER

60
ADMIN ADD/DELETE STAFF

61
ADMIN ADD/DELETE ADMINS

62
ADMIN APPROVE DONATED AMOUNT

63
ADMIN VIEW DONATED BOOK

64
ADMIN ADD ACTIVITIES

65
ADMIN VIEW FEEDBACKS

66
 4.SYSTEM TESTING

This section discusses about the business, technical, or resource related constraint that may keep us
from performing all tests necessary. Time schedule is a major constraint when we talk about testing at
the site. Testing the security of the software is one major constraint so we have to rely on our own
knowledge and have to trust the software for the security.

The philosophy behind testing is to find errors. Test cases are devised with
this purpose in mind. A test case is a set of data that the system will process as normal input. However,
the data are created with the express intend of determining whether the system will process correctly.
When the testing is over the implementation stages comes. In this the software we so far created and
tested are implemented, i.e., install the new application, check whether the existing equipment are
for it and it also includes training to staffs of the software. Thus, the testing and implementation are two
essential parts of the system development. Without this a system cannot be complete.

During system testing the system is used experimentally to ensure that the
application does not fail. i.e., whether it will run according to its specifications and in the way user
expect. Special test data are proceeded for processing and the results are examined. A limited number
of admin may be allowed to use the system so that the analyst can see whether they try to use it in the
unforeseen ways.
During the test process, only failures are observed by which the presence of
fault is deduced. The actual faults are identified by separate activities commonly referred to as debugging.
In other words,for identifying faults, the expensive task of debugging has to be performed.
This is one of the reasons why testing is an expensive method of identification of faults.

Here the system design was tested. Each of the units was tested individually

and then the entire system was tested. The different test cases were supplied to see whether the
application works, and the unit testing was successful. In that case the system testing was carried out.
The entire module was demonstrated to see whether it satisfies the user needs. The system is tested
using the various test cases. The test cases include the various distributions as part of

67
which the developed system is tested to see whether it yields the necessary results. Let’s consider the
testing of some of processes.
Software testing is a critical element of software quality assurance and represents the ultimate
reviews of specification, design and coding. Testing presents an interesting anomaly for the
software. Testing is vital to the success of system. Errors can be injected at any stage during
development. System testing makes logical assumption that if all the parts of the system are correct,
the goal will be successfully achieved. During testing, the program to be tested is executed with set
of test data and output of the program for the test data is evaluated to determine if the program is
performing as expected. A series of testing are performed for the proposed system before the system
is ready for the acceptance testing.

Following are the different types of testing:

• Unit testing.

• Integration testing.

• Validation testing.

• Output Testing.

• Acceptance Testing.
UNIT TESTING
In unit testing we have to test the programs making up the system. For this reason, Unit Testing is
sometimes called as the Program Testing. The software units in the system are modules and routines
that are assembled and integrated to perform a specific function. Unit testing focuses first on modules,
independently of one another, to locate errors. This enables to detect errors in coding and logic that are
contained within the module alone.
In this system, testing starting from first module i.e., login module. Here, username and password are
tested and if both are correct one can enter into our program. Errors will be located if occurs. In the
user registration section, if a new user gives a username that already exists, then a warning message is
displayed. Such a way all modules in the project are successfully tested. Thus, unit testing is
implemented in this project.

68
INTEGRATION TESTING

Data can be lost across any interface; one module can have an adverse effect on another sub functions

when combined, may not produce the desired major functions. Integration testing is a systematic
testing for conducting tests to uncover ever associated within the interface. The objective is to take
the unit tested modules and build a program structure. All the modules are connected and tested as a
whole. Here corrections are difficult because of the vast expenses of the entire program complicated
the isolation of causes. Thus, in the integration testingsteps, all the errors are corrected for the next
testing steps.
This integration testing is completely tested to see that every unit
of the software work together without any problem. Here integration testing is done by checking
whether the links between the forms are correct. Also testing is done to see the selection of a menu
generates the respective form, i.e., if a particular button in the user home clicks, then the corresponding
form should be shown and so on.

VALIDATION TESTING

At the culmination of integration testing, software is completely assembled as a package; interfacing

errors have been recovered and corrected and a final series of a software tests validation tests begin.
Validation testing can be defined in many ways but a simple definition is that validation succeeds when
the software functions in a manner that can be reasonably expected by the user.
Validation testing is done by the admin. The admin run the entire package and
see whether all their needs are met. They do this by entering valid data into the system and checks
whether they are stored as such, for e.g., if changes are made to the order status, then that change
should be reflected in next view.
In this system validation is incorporated at each level and thus validation testing
is implemented in our system. The system is user friendly with user guide messages to explain further
procedures. An attempt has been made to perfect the process by incorporating validation at each level.

OUTPUT TESTING

After performing validation testing, the next step is output testing of the proposed system, since no
system could be useful if it does not produce the required output in the specific format. The output

69
generated or displayed by the system under consideration is tested by asking the users about the format
required by them. Here the output is considered in two ways: one is on screen 64 and the other is
printed format. The output format on the screen is found to be correct as the format was designed in the
system design phase according to the user needs.
As far as hardcopies are considered it goes in terms with the user requirements.
Hence output testing doesn’t result any correction in the system.
ACCEPTANCE TESTING

User acceptance of the system is a key factor for the success of any system. The system under
consideration is tested for user acceptance by constantly keeping in touch with prospective system and
user at the time of developing and marking changes whenever required.

70
 5.SYSTEM IMPLEMENTATION

A crucial phase in the system life cycle is the successful implementation of the new system design.
Implementation simply means converting a new system design into operation. This involves creating
computer compatible files, training and telecommunication network before the system is set up and
running. A crucial factor in conversion is not disrupting the functioning of organization.
Actual data were input into the program and the working of the system was closely monitored.
It is the essential stage in achieving a successful new system. It should be carefully planned and
controlled to avoid problems. The implementation phase involves the following tasks

• Careful planning

• Investigation

• Design of methods

• Training of the staff in the changeover phase

• Evaluation of changeover

We implemented this new system in parallel run plan without making any disruptions to the ongoing
system, but only computerizing the whole system to make the work, evaluation and the retrieval of data
easier, faster and reliable.

After the initial design, the system is made published on the internet and the end user can do

demonstration. In a well-defined software development environment, however the presentation of

implementation documents is essentially an interactive.

The following are the three types of implementation documents:

• Conversion guide.
71
• User guide.

• Operation guide.

1.Conversion guide: The conversion guide outlines the steps required to transition from the existing
manual or legacy system to the new Courier Management System.

1.1 Transition Plan

 Step 1: Data Migration

o Collect all existing courier records, sender/receiver details, and staff data from the manual
system.

o Convert and import the data into the MySQL database using scripts or database tools like
phpMyAdmin.

o Ensure data integrity during migration to avoid missing or duplicate records.

 Step 2: System Setup

o Install the required server environment (WAMP/XAMPP) on the hosting machine.

o Deploy the application files and configure database connections.

 Step 3: Testing

o Conduct end-to-end testing with the migrated data to verify system functionality.

o Check for consistency in courier details, tracking statuses, and user accounts.

 Step 4: Training and Rollout

o Train admin and staff on using the new system.

o Provide demo sessions to demonstrate key functionalities, like adding couriers and tracking.

o Roll out the system in phases, starting with a pilot run for a small set of users.

72
 2. User Guide

This guide provides instructions for using the Courier Management System for all roles (Admin,
Staff, and Users).

2.1 Admin Guide

 Login:

o Navigate to the admin login page and enter credentials.

o Access the admin dashboard.

 Managing Staff:

o Add new staff members by providing their name, contact details, and role.

o Update or delete staff records as needed.

 Managing Couriers:

o Add courier details, including sender and receiver information.

o Assign couriers to staff for delivery.

o Update courier statuses (e.g., "In Transit," "Delivered").

 Monitoring System Activity:

o View reports on couriers, staff activity, and system logs.

o Ensure data consistency and resolve discrepancies.

2.2 Staff Guide

 Login:

o Enter credentials on the staff login page.

o Access the staff dashboard.

 Updating Courier Statuses:

o View assigned couriers and their details.

o Update statuses based on delivery progress (e.g., "Out for Delivery").

73
 Resolving Issues:

o Notify the admin of any inconsistencies or delivery issues.

2.3 User Guide

 Tracking Couriers:

o Enter the tracking ID on the user portal.

o View the current status and progress of the courier.

 Troubleshooting:

o If tracking ID is invalid, contact admin for assistance.

Operation guide: This guide provides detailed instructions for initializing, running, and maintaining
the system.

3.1 Initializing the System

 Ensure the server environment (WAMP/XAMPP) is running.

 Launch the web application by opening the URL in a browser.

 Log in using admin credentials to verify system accessibility.

3.2 Day-to-Day Operations

 Admin Operations:

o Regularly check and update courier records.

o Monitor staff performance and resolve reported issues.

o Back up the database periodically to prevent data loss.

 Staff Operations:

o Check assigned tasks at the start of the day.

o Update courier statuses based on progress.

 User Operations:

o Use the tracking system to check courier statuses.

o Contact support for unresolved tracking issues.

74
 3.3 Maintenance

 Database Maintenance:

o Perform regular backups using phpMyAdmin or command-line tools.

o Optimize database tables to ensure performance.

 Application Maintenance:

o Update PHP and MySQL versions as needed.

o Apply patches or updates to fix bugs or add features.

3.4 Troubleshooting

 Server Down:

o Check if WAMP/XAMPP services are running. Restart if necessary.

 Login Issues:

o Reset the user password using the admin panel if a user cannot log in.

 Tracking Errors:

o Verify that the courier ID exists in the database. Correct any discrepancies.

6.LIMITATIONS AND FUTURE ENHANCEMENTS

LIMITATION

 No Payment Gateway: The system does not support online payments for courier services.

 Local Service Only: Limited to local courier operations; international services are not included.

 Manual Updates: Status updates rely on manual input, which can cause delays or errors.

75
  No Real-Time Tracking: GPS-based real-time courier tracking is unavailable.

 Limited User Access: Users can only track couriers and cannot input sender or receiver details.

 No Notifications: Email or SMS alerts for status updates are not implemented.

 No Mobile App: The system lacks a mobile application, limiting accessibility on the go.

FUTURE ENHANCEMENTS

 Payment Gateway: Integrate online payment options.

 Real-Time Tracking: Add GPS-based live courier tracking.

 Mobile Application: Develop a dedicated mobile app for better accessibility.

 Automated Notifications: Implement SMS and email updates for courier statuses.

 International Support: Extend the system to handle global courier services.

 Enhanced Security: Introduce two-factor authentication and detailed activity logs.

7.BIBLIOGRAPHY

• https://getbootstrap.com/

• https://www.w3schools.com/

• https://www.javatpoint.com/html-tutorial

• https://www.guru99.com/

• https://mode.com/sql-tutorial/

• https://www.codecademy.com/catalog

• https://www.phptpoint.com/php-tutorial/

• https://www.phptutorial.net/

76
77