Development of a Web-based Transport Management System of a Company

by
Muhammad Edi Amin
.1.-

POST GRADUATE DIPLOMA IN INFORMATION AND COMMUNICATION

TECHNOLOGY

Institute oflnformation and Communication Technology

BANGLADESH UNIVERSITY OF ENGINEERING AND TECHNOLOGY
December, 2009

.,
The project report titled "Development of a Web-based Transport Management
System of a Company" submitted by Muhammad Edi Amin, Roll No: DP0731006,
Session 2007-2008 has been accepted as satisfactory in partial fulfillment of the
requirement for the Post Graduate Diploma in ICT held on 19th December, 2009.

BOARD OF EXAMINERS

I. Mr. Md. Rubaiyat Hossain Mondal Chairman

Assistant Professor
Institute oflnformation and Communication Teclmology
BUET, Dhaka-lOOO

2. Dr. Md. Abul Kashem Mia Member

Professor and Associate Director
Institute of Information and Communication Technology
BUET, Dhaka-lOOO

3. Dr. Md. Liakot Ali Member

Associate Professor
Institute oflnformation and Communication Technology
BUET, Dhaka-lOOO
 CANDIDATE'S DECLARATION

It is hereby declared that this project report or any part of it has not been submitted
elsewhere for the award of any degree or diploma.

Muhammad Edi Amin

ii
 Dedicated
to
My Parents and My Brother

iii
Table of Contents

Title Page No.

Board of Examiners

Candidate's Declaration l!

Dedication III

Table of Contents IV

List of Tables VIII

List of Figures IX

List of Abbreviations Xl

Acknowledgement Xl!

Abstract Xlll

Chapter 1 Introduction 1

1.1 Introduction 2

1.2 Objective with Specific Aims and Possible Outcome 3

1.3 Possibility/Scopes 4

Chapter 2 Development Process of the System 5

2.1 Outline of Methodology 6

2.2 Feasibility Study 7

2.3 Requirement Gathering, Specification and Planning 7

2.3.1 Identify User 7

2.3.2 Analysis of Main Features 8

2.3.3 Web-based Software Architecture 9

2.3.4 Hardware Interfaces 10

iv
 2.3.5 Software Interfaces 10
2.3.6 Security Requirements 12
2.3.7 Easy to Use
12
2.4 Design
12
2.5 Coding and Model Testing
13
2.6 Integration and System Testing 13
2.7 Operational Mode
13
2.8 Modification and Maintenance 13

Chapter 3 System Design 14

3.1 Introduction 15

3.2 Database Design 15

3.2.1 E-RDiagram 15

3.2.1.1 E-R Diagram of Vehicle Information Table 18

3.2.1.2 E-R Diagram of Fitness Information Table 19

3.2.1.3 E-R Diagram of Workshop Vehicle Table 19

3.2.1.4 E-R Diagram of Tax Information Table 20

3.2.1.5 E-R Diagram of Vehicle Insurance Information 20

Table

3.2.1.6 E-R Diagram of Requisition Information Table 2I

3.2.1. 7 E-R Diagram of Driver Information Table 22

3.2.1.8 E-R Diagram of Fuel Consumption Information 22

Table

3.3 Data Dictionary 23

3.4 Software Design 33

v
 3.4.1 UML Diagram 33

3.4.1. I Use Case Diagram 33

3.4.1.1.1 Use Case Diagram of User (Employee) 34

3.4.1.1.2 Use Case Diagram of Administrators 34

3.4.1.2 Activity Diagram 35

3.4.1.2.1 Activity Diagram of Requisition 36

Chapter 4 Functionalities of the Web Site 37

4. I System Features 38
4.1.1 Home Page 38
4. 1.2 Sign Up Page 38

4.1.3 Empowered User Home Page 39

4.1.4 Requisition Form 39
4.1.5 Requisition Status 40
4.1.6 Administrative Index Page 40
4.1. 7 Inbox Page 41

4.1.8 Requisition Status Page 42

4.1.9 Distribution Chart Page 42

4. 1.10 Vehicles Summary Page 43

4.1.11 Vehicle Information Form 43

4.1.12 Vehicles Information Page 44

4.1.13 Vehicle to Workshop Page 45

4.1.14 Vehicle Return from Workshop Page 45

4.1.15 Vehicle Insurance Form 46

4. I .16 Tax Information Form 47

vi
 4.1.17 Fitness Information Form 48

4.1.18 Fuel Consumption Record Form 49

4.1.19 Driver Information Form 50

4.1.20 Change Password Page 50

Chapter 5 Conclusion 51

5.1 Conclusion 52

5.2 Future Works 52

References 53

Appendix A: Sitemap for Employee (User) 55

Appendix B: Sitemap for Administrators 56

•.

vii
 List of Tables:

Table Number Figure Caption

Page No.
Table 3.1 Vehicle Information
23
Table 3.2 Workshop Infonnation
24
Table 3.3 Vehicle Workshop Information
24
Table 3.4 Insurance Company Infonnation
26
Table 3.5 Vehicle Insurance Information
26
Table 3.6 Employee Information
27
Table 3.7 Requisition Information
27
Table 3.8 Tax Information
29
Table 3.9 Fitness Information
30
Table 3.10 Driver Information
30
Table 3.11 Pump Station Information
31
Table 3.12 Fuel Consumption Information
31
Table 3.13 Administrators
32
Table 3.14 Notes
32
Table 3.15 Left List
32

viii
 List of Figures:

Figure Number Figure Caption

Page No.
Figure 2.1
Rapid Prototype Software Life Cycle Model 6
Figure 2.2 Web-based Software Architecture
9
Figure 3.1
E-R Diagram of Transport Management System 17
Figure 3.2
E-R Diagram of Vehicle Information Table 18
Figure 3.3
E-R Diagram of Fitness Information Table 19
Figure 3.4
E-R Diagram of Workshop Vehicle Table 19
Figure 3.5
E-R Diagram of Tax Information Table 20
Figure 3.6
E-R Diagram ofInsurance Vehicle Information 20
Table
Figure 3.7
E-R Diagram of Requisition Information Table 21
Figure 3.8
E-R Diagram of Driver Information Table 22
Figure 3.9
E-R Diagram of Pump Station Information Table 22
Figure 3.10 Actor and Use Case
33
Figure 3.11 Use Case Diagram of User (Employee)
34
Figure 3.12 Use Case Diagram of Administrators
35
Figure 3.13 Activity Diagram of Requisition
36
Figure 4.1 Home Page
38
Figure 4.2 Sign Up Page (User)
38
Figure 4.3 Index of User (Employee)
39
Figure 4.4 Requisition Form
39
Figure 4.5 Requisition Status for Specific User 40
Figure 4.6 Admin Index Page
41
Figure 4.7 Inbox Page
41
Figure 4.8 Requisition Status Page
42
Figure 4.9 Distribution Chart Page
42
Figure 4.10 Vehicle Summary Page
43
Figure 4.11 Vehicle lnfomlation Form
44
Figure 4.12 Vehicles Information Page
44
Figure 4.13 Vehicle to Workshop Page
45
ix
Figure 4.14 Vehicle Return from Workshop Page 45

Figure 4.15 Vehicle Insurance Form 46

Figure 4.16 Tax Information Form 47

Figure 4.17 Fitness Information Form 48

Figure 4.18 Fuel Consumption Record Form 49

Figure 4.19 Driver Information Form 50

Figure 4.20 Change Password Page 50

x
List of Abbreviations:

ERD Entity Relationship Diagram

HTML HyperText Markup Language
HTTP HyperText Transfer Protocol
PHP Personal Home Pages
UML Unified Modeling Language
XML Extensible Markup Language
DBMS Database Management System

xi
 Acknowledgement

First of all, I would like to thank Almighty Allah for giving me the strength and
patience for carrying out this work and to complete this project.

I would also like to thank Mr. Md. Rubaiyat Hossain Mondal, Assistant Professor,
Institute of Information and Communication Technology, Bangladesh University of
Engineering and Technology, Dhaka, Bangladesh for his valuable suggestions and
constant encouragement throughout the whole period of the work, which inspired
and guided me in each and every step of the project.

I would like to acknowledge the efforts given by my family members especially my

parents for their continuous support and inspiration, which helped me to complete
the project successfully.

I would also like to remember the contributions and support given by my relatives
and friends for completing the project in time.

xii
 Abstract

The use of different types of vehicles in organizations has drastically increased over
the years. Consequently the management of these vehicles has become more
complicated than ever. The combined or stand alone use of spreadsheets and word
software have reduced the level of complexity in dealing with the transport system.
However, these traditional tools do not provide the interlinked information in precise
and usable way. So, there is a need for a development of complete transport
management software that will overcome the limitations of using discontinued

software and paper works. In this work, a complete web-based system has been
developed to keep records and track of vehicles in any organization. The developed
scheme keeps records of vehicles and their time to time maintenance. In addition,
the software provides fuel usage information, and also enables a complete
requisition system. Data related to tax, fitness and insurance of vehicles are also
maintained in the software. Moreover, different records regarding drivers,
workshops, pump-stations can also be viewed. As a result, the tracking of vehicles
becomes easier. The scope of irregularities in the usage of vehicles cost of
maintenance and fuel consumption reduces significantly.

Thousands of industries and offices have been established in Bangladesh in the last
decade. Unfortunately these organizations are still working with the traditional paper
based system to manage the transport section. They often decline to buy high cost
sofiware from abroad. This developed software is of low cost and can be easily
adopted by Bangladeshi offices. Therefore, this web-based system can playa vital
role in removing the ongoing difficulties and irregularities in the transport
management in Bangladesh.

xiii
 1

Chapter 1

Introduction
 2

1. 1 Introduction

Any web-based system is defined as a system that can be accessed via web browsers
within a network [1]. Web-based systems need only to be installed on the server
placing minimal requirements on the end user workstation. This makes maintaining
and updating the system much simpler as it can be done on the server [2]. Most web
based applications are far more compatible across platforms than traditional installed
software [3]. Web browsers are available for a multitude of operating systems. For
these reasons, many of the management systems are now being developed as web-

bascd systems.

Transport management system IS used to keep records of vehicles and manage

vehicles of any particular organization [4]. In Bangladesh most of the organizations
arc dependent on different vehicles of their own for transport purposes. It is very
difficult to maintain this large number of vehicles that are spread and used by
different branch or site offices every day. It needs man power and hours to maintain
these vehicles. Some of these organizations already use desktop based software and
others use web-based software with limited functionalities, So, they require a

complete low cost system.

In Bangladesh many organizations have branch offices in different places over the
country. Many of them maintain their own LAN either through permanent
connections or through leased lines. They can use web-based vehicle management
software to maintain and collect information within their LANs. So, a web-based
vehicle management system should be developed that can include different issues
related to vehicles such as fitness, tax, insurance, scheduling, requisition etc.
 3

1.2 Objectives with Specific Aims and Possible Outcome

The objectives of this project are to:

.:. Keep records of vehicle maintenance .

•:. Keep information about drivers .
•:. Track requisition of vehicles .
•:. Provide information about insurance, tax and fitness certificates .
•:. Enhance the availability of information collection through search options .
•:. Facilitate the management system and make it faster.
.:. Provide appropriate interfaces to the administrator and the users .
•:. Add new vehicle information.
 4

1.3 Possibility/Scopcs
Some scopes of this software are given below:

I. Any particular organization which has vehicles can use this software to keep
records of vehicles and to manage vehicles.
2. An employee can have access via any browser within a network.
3. An employee will be able to know about requisition, service and
management information.

4. An employee will be able to sign in into the system after sign up.
5. After signing in an employee will be able to

• Edit personal information.

• Change the password.
• View vehicles and drivers information.
• Submit requisition for a vehicle for specific time.
• View requisition status.

• Can cancel the requisition result if required.

6. An administrator will be able to log in into the system using given password.
7. After signing in an administrator will be able to
• Change the password.

• Add, view, edit and delete; vehicle, workshop, driver etc. information.
• Keep record of repair work, insurance, tax and fitness certificate
information.

• Grant or cancel requisition request.

• View distribution chart for specific date.
• Print recorded allocation information.

8. This system will make sure that the specific time and date is free for
allocation or not.
 5

Chapter 2

Development Process of the System

 6

2.1 Outline of Methodology

The project consists of the following stages:
1, Feasibility Study
2. System Study Stage
i. Requirement gathering
ii. Specification
iii. Planning
3. Design Stage
4. Coding Stage
5. Testing Stage
6. Operational Mode
7. Modification Stage
This process followed the "Rapid Prototype Software Life Cycle Model". The
brief'overview of the process is depicted below.

Feasibility

Requirement ....................................................... Modification

Gathering -
'!'
•.•....................................
i[
T Specification

Planning
1 'i
.
1 Design
14.................................

1
Coding and
i4 ........... "l
~ model testing
~ Development

..........~ Maintenance Integration and

system Testing

!
Operation mode

Figure 2.1 Rapid Prototype Software Life Cycle Model.

 7

2.2 Feasibility Study

A project feasibility study [s an exercise that involves documenting each of the
potential solutions to a particular business problem or opportunity. The purpose of a
Project Feasibility Study is to clarify the wanted outcome of the project. It is
important to understand what the project will deliver. If a project is seen to be
feasible from the results of the study, the project can be continued to the next stage.

For an organization without any software it is very difficult to maintain these large
numbers of vehicle that are spread and used by different branch or site offices every
day. Some of these organizations already use desktop based software and others use
web-based software with limited functionalities. Some organizations maintain a
section for vehicle management. So, a complete low cost system will be financially
feasible. The system will reduce maintenance cost. The system will save employee's
(user) time and give proper information when he/she wants.

2.3 Requirement Gathering, Specification and Planning

Requirement gathering, specification and planning are essential parts of any project
and project management. During this process, different similar software are
analyzed and discussions are made with different companies about the software. The
software and hardware requirements are also studied and specified in this phase.
Different types of idea about the development are written .up. The requirement
process is completed when the specifications for the new software product are
written in a formal document called the requirements specification document. In
planning phase, a plan is made to develop this software with requirement
specification document.

2.3.1 Identify User

Identifying the administrator and the 'users' or 'customers' of a software is very
important. The different categories of users of the software are as follows:

System Administrator: System administrator can do anything on the site, in all

pages. System administrator is responsible for updating and maintaining the
database and codes of the software.
 8

Administrators: An administrator is a responsible person appointed by the

organization, who can approve requisition, send vehicle to workshop and change
his/her own password. The administrators can also view/edit/delete/insert vehicle,
workshop, insurance, tax, fitness, pump station, and driver information. In this
project the followings three administrative levels have been considered.
1. Admin (Administrative officer)
2. Head Admin (Head of the Administrator office section)
3. Director (Supreme higher authority)

Users: Users are employees of the organization who will use this software. To use
this service, an employee should have the basic computer using ability. By signing
in user can see all general information and can also apply for vehicle requisition, can
update personal information etc.

2.3.2 Analysis of Main Features

The Transport Management System software is designed to manage its fleet of
vehicles more effectively and efficiently. An operator can monitor vehicle
distribution, retrieve any vehicle's historical information using this software. Some
key features of Transport Management System are discussed bellow.
Requisition process
Any employee can apply for a vehicle. All personal information of the employee
will be displayed in the requisition form. User can apply for a specific type of
vehicle in a specific time. User can view his requisition status up to the last ten
applications. An administrator can approve/cancel a requisition. There will be an
automatic checkup, so that allocated times are not intersected for a specific vehicle
at a specific time and date. Administrator can see the distribution chart of vehicle
requisition.
Control Information
The administrators can control different information such as vehicles, workshop,
insurance, tax, fitness, pump station, and driver information. Users have no power to
view other user's information. Users can only view limited information.
 9

Search Records
Administrators have power to search previous information from database by date, id
or name. Administrator can search and select different records related to vehicle,
workshop, insurance, tax, fitness, pump station, and driver information.

Sending to Workshop
Administrator can select specific vehicle and add the information regarding sending
of it send to specific workshop. Administrator can also keep information about
problems, repair work, expense and present conditions of a vehicle.

Print Option
Users can print their approved requisition form which contains the information about
user, vehicle, time, date, venue, etc. Administrator can print logbook of a specific
requisition for a driver which contains the information about user, vehicle, time, date
and venue. Administrator can keep hard copies of requisition record through print

option.

2.3.3 Web-based Software Architecture

The developed Web-based Transport Management System works within a network
(Intranet). The architecture for the web based system contains three necessary

components [II]:
• The Data and Data Server
• The Web Application and Web Server
'. The Client Application and Client.

Web Browser The Client Application

(Internet Explorer, Mozilla, and Client
Google Chrome etc.)

Intranet

Web Server Middleware (PHI', r+ TheW cb Application

JA VASCRIPT) and Web Server
(Apache)

Database
The Data and
(MySQL)
Data Server

Figure 2.2: Web-based Software Architecture.

 10

2.3.4 Hardware Interfaces

Nowadays, every company have computer and printers. This system is developed
for the organizations which have their own network. So, there is no need of extra
computer or internet connection. Printer is necessary for printing the documents
generated from the system.

2.3.5 Software Interfaces

In this project the following tools software are used:
Microsoft Internet Explorer

Version number: 6 or later.

Source: Microsoft Corporation.
To display the information on the website 111 a neat and

Purpose: organized way. And also to help one navigate around the web
easily.
The Microsoft Internet Explorer is the software, which provides
Definition of the
a flexible and reliable browsing experience with enhanced Web
Interface:
privacy features for all users.
PHP: Personal Home Pages
Version number: 5.2.6.
Source: PHP Group.
To build web pages, this works with MySQL database and
Purpose:
Apache server.
PHP is a widely-used general-purpose scripting language that is
Definition of the
especially suited for Web development and can be embedded
Interface:
into HTML.
Apache HTTP Server

Version number: 2.0.5.5.

Source: The Apache Software Foundation.
In order to execute the client site of this software, the web server

Purpose: specified above is required as the provider of the client software

at the server site.
 11

The Apache HTTP Server Project is an effort to develop and

maintain an open-source HTTP server for modern operating
Definition of the systems including UNIX and Windows NT. The goal of this
Interface: project is to provide a secure, efficient and extensible server that
provides HTTP services m sync with the current HTTP
standards.

Macromcdia Drcamweaver MX
Version number: 8.
Source: Macromedia Inc.
The web development tool specified above IS helpful for
Purpose:
designing and coding the project.
Macromedia Dreamweaver is the industry-leading web
Definition of the
development tool, enabling users to efficiently design, develop
Interface:
and maintain standard based websites and applications.
MySQL: My Structured Query Language
Version number: 5.0.
Source: MySQL.
Purpose:
Required as database server.
MySQL IS the world's most popular open source database
software. With superior speed, reliability, and ease of use,
Definition of the
MySQL has become the preferred choice of corporate IT
Interface:
Managers because it eliminates the major problems associated
with downtime, maintenance, administration and support.
,JavaScript/ECMAScript
Version number: 1.6.
Source: ECMA organization.
For opening or popping up a new window, Validation of web
Purpose: form (input values to make sure that they will be accepted before
they are submitted to the server) etc.
Definition of the JavaScript IS an object-oriented scripting language used to
Interface: enable programmatic access to objects within both the client
 12

application and other applications. It is primarily used in the

form of client-side lavaScript, implemented as an integrated
component of the web browser, allowing the development of
enhanced user interfaces and dynamic websites.
CSS: Cascading Style Sheets
Version number: CSS 2.1.
Source: World Wide Web Consortium.
To enable the separation of document content from document
Purpose: presentation, including elements such as the colours, fonts, and
layout.

Cascading Style Sheets (CSS) is a style sheet language used to

Definition of the
describe the presentation semantics (that IS, the look and
Interface:
formatting) of a document written in a markup language.

2.3.6 Security Requirements

Most IT departments have security requirements for applications. Web applications
are not exceptional. The requirements are often written as checklists.
• Requires password and have options to change password.
• Web and database servers should be physically secured.
• Username and password will be checked before starting every page.
• Use a secured password for the SQL Server administrator, SA.
2.3.7 Easy to Use
This system is self explanatory. So, minimum computer knowledge is required by
the employee to use this software at ease.
2.4 Design
The design phase describes how the software is constructed so that it fulfills the
specifications agreed upon in the requirements specification document. It explains
required features and operations in detail, including database design, software
design, screen layouts and other documentation. When the design is completed it is
recorded in the design specification document. There are different types of design to
develop this software like ERD, UML etc. Design stage is described in details in
Chapter 3.
 13

2.5 Coding and Model testing

In this stage, the designs are translated into code. The software is divided into
separate units called modules, in order to handle the complexity of the programming
process. All rules and regulations of programming language are maintained
properly. Computer programs are written using Dreamweaver tool. According to the
type of application, the right programming language is chosen. Different high level
programming languages like PHP [6], MySQL [7], Apache [8], JavaScript [9],
AJAX [9], HTML [9], XML [9], CSS [9] etc. are used for coding.

2.6 Integration and System Testing

During this stage, the individual modules of the software product are combined to
form the integrated software product. A special testing environment is created to
check for errors, bugs and interoperability.

2.7 Operational mode

At this stage, the checked software is ready for use. If required, the modification
stage will modify and enhance the system according to the diffIculty.

2.8 Modification and Maintenance

After the system is in operation, various changes are made in order to fix bugs, to
add new functionality, to port the software to new platforms, or to adapt the software
to new technologies during the modification and maintenance phase of the system.
Although it may seem that the development of the software is finished after its
delivery, this is far from true. Even a successful software product need to be
developed/modified to meet the changing needs of the clients.
 14

Chapter 3

System Design
 15

3.1 Introduetion

The software system design describes the desired software features in detail,
including database design (ER diagram), software design (UML is produced here),
screen layouts and other documents. In system design, the software's overall
structure is defined with a full data dictionary. These design elements are intended to
describe the software in detail that helps to develop the software with minimal
additional input.

3.2 Database Design

A database is a collection of information, organized in such a way that a computer

program can quickly select desired pieces of data. The computer program used to
manage and query a database is known as a database management system (DBMS).
Databases are designed to offer an organized mechanism for storing, managing and
retrieving information. This includes detailed specification of data elements, data
types, indexing options and other parameters residing in the DBMS data dictionary.
Many models and languages are used for design of the database. To design the
database the Entity-Relationship (ER) Diagram is used.

3.2.1 E-R Dill gram

An entity-relationship (E-R) diagram is a graphical representation of entities and

their relationships to each other, typically used in computing in regard to the
organization of data within databases or information systems. There are three basic
elements in E-R diagram:

.:. Entities (tables) are the elements about which one seek information. Boxes
are commonly used to represent entities .

•:. Attributes are the data one collect about the entities. Ovals are used to
represent attributes .

•:. Relationships provide the structure needed to draw information from

multiple entities. Diamonds are normally used to represent relationships.
 16

Figure 3.1 shows entire an E-R diagram. There are 16 entities. Some of them are
given in detail in figure 3.1; others will be given in the later figures. The description
of these entities is given bellow.

I. Vehicle Information: The name of this entity set is vehicle_infojorm. Due

lack of space, this entity set will be displayed in figure 3.2.
2. Workshop: The name of this entity set is workshop_info. Workshop id,
name, contact no, address, identification no and no of vehicles are attributes
of this entity set.

3. Fitness: The name of this entity set is fitness_info. Due lack of space, this
entity set will be displayed in figure 3.3.
4: Workshop Vehicle: The name of this entity set IS

workshop_vehicle_info_to. This entity set will be displayed in figure 3.4.

5. Id generator: The name of this entity set is idgenarate. Id generator consists
ofid, category and year of purchase date.
6. Insurance: The name of this entity set is insurance_info. Insurance entities
consist of id, company name, company id, address and phone no.
7. Tax: The name of this entity set is tax_info. This entity set will be displayed
in figure 3.5.

8. Requisition: The name of this entity set is requisition_info. This entity set
will be shown in figure 3.6.
9. Driver: The name of this entity set is driver_info. Due lack of space, this
entity set will be displayed in figure 3.7.
10. Insurance vehicle: The name of this entity set is insurance_vehicle_info.
This entity set will be displayed in figure 3.8.
11. Pump Station: The name of this entity set is pump_station_info. Pump
Station entities consist of id, company name, company id, address and phone
no.

12. Pump Station Fuel: The name of this entity set is pump_stationjuel. Due
lack of space, this entity set will be displayed in figure 3.9.
 17

insurancecomname
idt.:ntification
noofvchicle

workshop info identiticationno

Insurance info

idgenerate

fitness info

driver info

tax info

requisition_info

uscrpassword

userusername

designation

identification no

left list .... password

\'0
C--u-sc-rn-a-m~c~

Figure 3.1: E-R Diagram of Transport Management System.

 18

13. Employee: The name of this entity set is employee_info. Employee entities
consist of employee name, username, password etc.
14. Administrator: The name of this entity set is administrator. Administrator
entities consist of administrator username and password information.
15. Note: The name of this entity set is notes. Note entities consist of note I,
note2 and note3. Administrator can write down their personal note here.
16. Left List: The name of this entity set is left_list. Left List entities consist of
id, name and urI. There are twelve entities, each page left list link is taken
from corresponding entity set.

2.8.1.1 E-R Diagram of Vehicle Information Table

Figure 3.2 shows the entire E-R diagram of vehicle information. Admin users can
add vehicle information in this table.

vehicle_status

battery_value

model_no

manufactured_date purchase_from
manufacturer

Figure 3.2: E-R Diagram of Vehicle Information Table.

1
 19

3.2.1.2 E-R Diagram of Fitness Information Table

Figure 3.3 shows the entire E-R diagram of fitness information of a vehicle. Admin
users can add fitness information in this table.

registration_no

c confirmeby

depositdatc fitness info comment

dcpositamount

expiredate
dcposittypc

Figure 3.3: E-R Diagram of Fitness Information Table.

3.2.1.3 E-R Diagram of Workshop Vehicle Table

Figure 3.4 shows the entire E-R diagram of workshop vehicle. Admin users can add
problems of vehicle, vehicle and workshop information in this table. After returning
admin can add repair work, expense, current status etc. information.

expense
problems registration_no

Ccefercneeno ~ workordcr

milemctcr
vehicle_status

COUleDme:>
scndingdatc

workshopname
returndatc

CvehiClcid ~
rcpairworks

Figure 3.4: E-R Diagram of Workshop Vehicle Table.

 20

3.2.1.4 E-R Diagram of Tax Information Table

Figure 3.5 shows the entire E-R diagram of tax information of a vehicle. Admin
users can add tax information in this table.

vehicleid

registration_no

em:> confirmcby

c dcpos;tdatc ~
tax info comment

givcndate
dcpositamount

deposittype

Figure 3.5: E-R Diagram of Tax Information Table.

3.2.1.5 E-R Diagram of Vehicle Insurance Information Table

Figure 3.6 shows the entire E-R diagram of vehicle insurance information. Admin
users can add insurance information of a vehicle in this table.

certificateno insurancccomnamc

registration_no
msurance vehicle info

insurance_type

given_date

Figure 3.6: E-R Diagram of Vehicle Insurance Information Table.

d
 21

3.2.1.6 E-R Diagram of Requisition Information Table

Figure 3.7 shows the entire E-R diagram of requisition information. Employee can
add demand information in this table. Admin users can add approve or cancel
information in this table.

detail cancelled

Figure 3.7: E-R Diagram of Requisition Information Table.

 22

3.2.1.7 E-R Diagram of Driver Information Table

Figure 3.8 shows the entire E-R diagram of driver information. Admin users can add
drivers' information in this table.

bloodgroup

idcntificationno

registration_flO

Figure 3.8: E-R Diagram of Driver Information Table.

3.2.1.8 E-R Diagram of Fuel Consumption Information Table

Figure 3.9 shows the entire E-R diagram of fuel taking information. Admin users
can add fuel taking information of a vehicle in this table.

buy fuel meter

registration_no

idcntificationno
prefuelmcter

vehicleid

name
fuelamount

moncyamount

~confirmedbY~

Figure 3.9: E-R Diagram of Pump Station Information Table.

 23

3.3 Data Dictionary

Data Dictionary describes the table format which is used in database design. The
following tables are used in database design.
Table 3.1: Vehicle Information
Fields Domains Constraints Description

vehicle id varchar(25) Not null Vehicle Id*

vehicle_type varchar(l5) Not null Vehicle Type

ac nac varchar(lO) Not null AC orNonAC

cubic_capacity varchar(20) Not null Cubic Capacity

vehi~le _status varchar( I0) Not null Condition

gear_type varchar(10) Not null Gear Type

registration_no varchar( 40) Not null Registration No.

engine_no varchar( 42) Not null Engine No.

chassis - no varchar(42) Not null Chassis No.

manufacturer varchar(27) Not null Manufacturer

manufactured_date Date Not null Manufactured Date

model no varchar(55) Not null Model No.

no_ 01:"- doors int(5) Number of Door

no of seats int(5) Number of Seat

fuel varchar(50) Not null Fuel

tank_capacity varchar(l5) Tank Capacity

color varchar( 15) Not null Color

battery_value varchar(50) Battery Value

tyre_size varchar(lO) Tyre Size

purchase_from varchar(50) Purchase Form

pnce int(lO) Not null Price

date_of yurchase Date Not null Date of Purchase

comment varchar(502) Any Comment.

*Vehicle ld will be generated by Vehicle Type, Purchase year and a four digits auto
incrernent number started with 1001.
 24

Table 3.2: Workshop Information

Fields Domains Constraints Description
id int(lO) Primary key Auto Increment
identificationno varchar(20) Workshop Id*
workshopname varchar(50) not null Name of
Workshop.
contractno varchar( I00) not null Contract No.
address varchar(500) not null Address of
Workshop
noofvehicle int(5) not null No. of vehicle in
the workshop. **
*Workshop Id will be generated by "Workshop"-id.
** Plus or minus number of vehicle of the workshop will be shown automatically.
Table 3.3: Vehicle Workshop Information
Fields Domains Constraints Description
ld int( I0) Primary key Auto increment
vehicleid varchar(20) Foreign Key Vehicle Id*
registration_no varchar(20) Foreign Key Vehicle Registration No*
workshop name varchar(50) Foreign Key Workshop Name**
workorder varchar(26) Work Order
milemeter varchar(20) Mile Meter
problem I varchar(l I I) Problem
problem2 varchar(l I I) Problem
problem3 varchar(ll I) Problem
problem4 varchar(1 I I) Problem
problem5 varchar(ll I) Problem
problem6 varchar(ll I) Problem
problem7 varchar( 1I 1) Problem
problemS varchar(lll) Problem
problem9 varchar(ll I) Problem
problem! 0 varchar(lll ) Problem
 25

Fields Domains Constraints Description

repairwork I varchar(lll ) Repair Work
repairwork2 varchar(lll ) Repair Work
repairwork3 varchar(l11 ) Repair Work
repairwork4 varchar(111 ) Repair Work
repairwork5 varchar(l11 ) Repair Work
repairwork6 varchar(lll ) Repair Work
repairwork7 varchar(lll ) Repair Work
repairwork8 varchar(lll) Repair Work
repairwork9 varchar(lll ) Repair Work
repairwork 10 varchar(111 ) Repair Work
expancel varchar(lO) Expanse
expance2 varchar(10) Expanse
expance3 varchar(10) Expanse
expance4 varchar(lO) Expanse
expance5 varchar(lO) Expanse
expance6 varchar(lO) Expanse
expance7 varchar(lO) Expanse
expance8 varchar( 10) Expanse
expance9 varchar(IO) Expanse
expancel0 varchar(10) Expanse
sendingdate date Not null Sending Date
returndate date Not null Return Date
referenceno varchar(50) Not null Reference No'"
expenditure int(20) Total Expanse
outcome varchar( 1000) Outcome
vehicle status varchar(lO) Not null Condition (Default: bad)
'Foreign keys are taken from "Vehicle Information" table.
"Foreign key is taken from "Workshop lnfo" table.
"'Reference no is made by "workshop id-id" workshop id from "Workshop Info"
table.
 26

Table 3.4: Insurance Company Information

Fields Domains Constraints Description
id int(lO) Primary key Auto Increment
identification no varchar(20) Insurance
Company Id.*
insurancecolllname varchar(50) not null Name ofInsurance
Com.
contr:actno varchar(lOO) not null Contract No.
address varchar(500) not null Address of
Insurance Com.
* Insurance Company ld will be generated by "InsuranceCom" -id.

Table 3.5: Vehicle Insurance Information

Fields Domains Constraints Description
id int(lO) Primary key Auto increment
vehicIeid varchar(20) Foreign Key Vehicle Id*
registration_no varchar(20) Foreign Key Vehicle
Registration No*
Insurancecomname varchar(50) Foreign Key Insurance
Company Name**
certificateno varchar(50) Not null Certificate No.
insurance_type varchar(50) Not null Insurance Type
basic int(l2) Not null Basic (Tk)
duty decimal( 12,2) Not null Duty
vat decimal(l2,2) Not null Vat
total decimal(l2,2) Not null Total
givendate date Not null Date
next_premimum date Not null Next Premium
Date.

*Foreign keys are taken from "Vehicle Information" table.

**Foreign key is taken from "Insurance Info" table.
 27

Table 3.6: Employee Information

Fields Domains Constraints Description
name varchar(50) Not null Employee name
designation varchar(50) Not null Designation.
contractno varchar(IOO) Not null Phone no.
section varchar(20) Section.
department varchar(20) Department.
bloodgroup varchar(10) Blood group.
userusername varchar(20) Primary key Username
lIserpassword varchar(20) Not null Password
email varchar(50) E-mail address.

Table 3.7: Requisition Information

Fields Domains Constraints Description
requisition_id int(20) Primary key Requisition ID
(auto increment)
lIserusername varchar(20) Foreign Key User Username'
name varchar(50) Foreign Key Name of user'
designation varchar(50) Foreign Key Designation of
user'
contactno varchar(100) Foreign Key User phone no'
section varchar(20) Foreign Key User section'
department varchar(20) Foreign Key User department'
bloodgroup varchar(15) Foreign Key User blood group'
email varchar(50) Foreign Key User email'
reason varchar(20) Not null Reason
vehicleid varchar(25) Foreign Key Vehicle Id"
registration_no varchar(20) Foreign Key Vehicle
Registration no."
vehicle type varchar(20) Not null Vehicle Type"
no of seats varchar( 15) Foreign Key No of seats"
 28

Fields Domains Constraints Description

ac nac varchar(lO) Foreign Key AC or Non AC**
start hr int(5) Not null Starting hour
start mi int(5) Not null Starting minute
end hr int(5) Not null Ending hour
end mi int(5) Not null Ending minute
startdate date Not null Starting date
enddate date Not null Ending date
startvenue varchar(50) Not null Starting venue
end venue varchar(50) Not null Ending venue
detailreason varchar(500) Detail reason
driverid varchar(l5) Foreign Key Driver id***
drivername varchar(50) Foreign Key Driver name***
outtime hr int(3 ) Out of garage(hr.)
outtime mi int(3) Out of garage(mi.)
intime hr int(3) In garage(hr.)
intime mi int(3) In garage(mi.)
totaltime varchar( 15) Total time needed
outmeter int(21 ) Meter when out
inmeter int(21) Meter when in
total meter int(21) Total distance
prefuelmeter varchar(26) Previous fuel meter
buyfueltneter varchar(26) Buy fuel meter
totalfuelmeter varchar(26) Total fuel needed
totalcost decimal(l5,2) Total cost.
dcomment varchar(lOOO) Comment
note -admin -head varchar(lOOO) Note from admin to
head
note head admin varchar( 1000) Note from head to
-
admin.
note -head -vc varchar(lOOO) Note from head to
director.
 29

Fields Domains Constraints Description

note - ve admin varchar(lOOO)
- Note from director
to admin.
detailcancelled varchar(lOOO) Details reason for
cancelled.
status int(ll) Not Null Default is 1****

*User information is taken from "Employee Info" table.

**Vehicle information is taken from "Vehicle info form" table.
***Driver information is taken from "Driver info" table.

Table 3.8: TllX Information

Fields Domains Constraints Description
id int(lO) Primary key Auto increment
vehicleid varchar(20) Foreign Key Vehicle Id*
registration_no varchar(20) Foreign Key Vehicle
Registration No*
deposittype varchar(50) Not null Type of deposit.
depositamount decimal(l2,2) Not null Deposit amount.
taxno varchar(52) Not null Tax number.
givendate date Not null Given date.
depositedate date Not null Deposit date.
expiredate date Not null Expire date.
comment varchar(lOOO) Not null Comment.
confirmedby varchar(50) Not null Name, who
confirm tax
information.

*Foreign keys are taken from "Vehicle Information" table.

 30

Table 3.9: Fitness Information

Fields Domains Constraints Description
id int(ll) Primary key . Auto increment
vehicleid varchar(20) Foreign Key Vehicle Id'
registration_no varchar(50) Foreign Key . Vehicle Reg. No'
deposittype varchar(50) Not null Type of deposit.
depositamount decimal(l2,2) Not null Deposit amount.
fitnessno varchar(52) Not null Fitness number.
givendate date Not null Given date.
depositedate date Not null Deposit date.
expiredate date Not null Expire date.
comment varchar(lOOO) Not null Comment.
confirmedby varchar(50) Not null .Name, who confirm
fitness information.
'Foreign keys are taken from "Vehicle Information" table.

Table 3. I 0: Driver Information

Fields Domains Constraints Description
id int(ll) Primary key Auto increment
identificationno varchar(l5) Driver id'
name varchar(50) Not null Driver name
licenseno varchar( 42) Not null Driver license no.
grade varchar(5) Not null Driver grade.
vehicleid varchar(20) Foreign Key Vehicle id".
registration_no varchar(20) Foreign Key Vehicle Reg. No"
contractno varchar( 100) Not null Phone no.
bloodgroup varchar(IO) Blood Group.
farmdate date Not null Joining date.
comment varchar(lOOO) Any comment.
• Driver id will be generated by "Drive-joining year-id"
"Foreign keys are taken from "Vehicle Information" table.
 31

Table 3.11: Pump Station Information

Fields Domains Constraints Description
id int(lO) Primary key Auto increment
identificationno varchar(20) Not null Pump station id*
name varchar(50) Not null Name
address varchar(500) Not null Address.
contractno varchar(lOO) Not null Phone no.

*Pump station id will be generated by "Pumpstation-id"

Table 3.12: Fucl Consumption Information

Field's Domains Constraints Description
id int(S) Primary key Auto increment
vehicleid varchar(20) Foreign Key Vehicle Id*
registration_no varchar(50) Foreign Key Vehicle Reg. No*
identificationno varchar(20) Not null Pump station id**
name varchar(50) Not null Pump station
Name**
fuel varchar(50) Not null Fuel type
prefuelmeter varchar(25) Not null Meter reading
buyfuelmeter varchar(25) Not null After taking meter
reading
tdate date Taking date
rate varchar( 40) Not null Rate per unit.
fuelamount varchar( 40) Not null Amount of fuel
moneyamount int(25) Not null Total amount of
money
confirmedby varchar(50) Not null Name of Officer.

'Foreign keys are taken from "Vehicle Information" table.

**Foreign keys are taken from "Pump Station" table.
 32

Table 3.13: Administrators

Fields Domains Constraints Description
id int(5) Primary key Auto increment
username varchar(64) Not null Username
password varchar( 64) Not null Password

*username is fixed. Password can be changed by corresponding administrator.

Table 3.14: Notes

Fields Domains Constraints Description
id int(1l) Default I Number.
note I varchar(2500) Default' Write Admin can write
here' important note
here.
note2 varchar(2500) Default 'Write Head of admin can
here' write important
note here.
note3 varchar(2500) Default' Write Director can write
here' important note
here.

Table 3.15: Left List

Fields Domains Constraints Description
id int(5) Primary key Auto increment
name varchar(20) Not null Left link list name
uri varchar(100) Not null Hyperlinks.

*Every table consider as left list hyperlinks for corresponding page.

 33

I
3.4 Software Design
~
Software design is a process of problem-solving and planning for a software
solution. Object-oriented analysis and design (OOAD) are implemented during the
software design. Each object represents some entity of interest in the system being
modeled, and is characterized by its class, its state (data elements), and its behavior.
Various models can be created to show the static structure, dynamic behavior, and
run-time deployment of these collaborating objects. There are a number of different
notations for representing these models, such as the Unified Modeling Language
(UML). Different diagrams are used to help visualizing the whole development
process.

3.4.1 UML Diagram

The Unified Modelling Language (UML) is graphical notation system for Object-
Oriented analysis and design. UML is the industry-standard language for the
specification, visualization, construction, and documentation of the components of
software systems. UML helps to simplify the process of software design, making a
model for construction with a number of different views. One of the great merits of
UML is the way it helps open up the development process which is called use cases.
These serve to identify principal roles (actors) in the system, boundaries, actions,
and so on. UML Use Case Diagrams can be used to describe the functions of a
system in a horizontal way.

3.4.1.1 Use Case Diagram

A use case diagram in the Unified Modeling Language (UML) is a type of
behavioral diagram defined by and created from a Use-case analysis. It is a set of
scenarios that describes an interaction between a user and a system. The two main
components of a use case diagram are use cases and actors. It can be shown by the
figure 3.10.

x- c__
=:>
Use Case
Actor

Figure 3.10: Actor and Use Case.

 34

An actor represents a person, organization, or external system that will interact with
this system. The symbols of actors are drawn as stick figures. A use case is an
external view of the system that represents some actions the user might perform in
order to complete a task and is drawn as a horizontal ellipse. Lines are used to
represent the relationships between these elements.

3.4.1.1.1 Use Case Diagram of User (Employee)

Figure 3.11 shows the use case diagram for employee (user).

Login ~

.•••.•••••0Pdate~
View Personal
Information •.........~

View Vehicle
Information

View Driver

Employee
Apply for
Vehicle

Cancel
Requisition

C Logout :=>
Figure 3.11: Use Case Diagram of User (Employee).

3.4.1.1.2 Use Case Diagram of Administrators

Figure 3.12 shows the use case diagram of administrators. Admin can log in his/her
account and can insert, update and delete the required information for the system.
He/she can also logout from the account.
 35

Login

Create Vehicle, Workshop

etc. Information

View Vehicle, Workshop

etc. Information
&
, I

~GV
Send to Workshop View/Approve
Requisition
Return from Workshop

View/Edit/Grant
Requisition
Admin
Change Password

Create Insurance Premium

Director
ViewlDelete Insurance
Premium

Create Fuel Information

ViewlDelete Fuel Record

Logout

Figure 3. I2: Use Case Diagram of Administrators.

3.4.1.2 Activity Diagram

An activity diagram illustrates the dynamic nature of a system by modeling the flow
of control from activity to activity. An activity represents an operation of some
classes in the system that results in a change in the state of the system. Typically,
activity diagrams are used to model workflow or business processes and internal
operation. Activity diagrams can show activities that are conditional or parallel.
 36

3.4.1.2.1 Activity Diagram of Requisition

Figure 3.13 shows the activity diagram of requisition. In this case, employee applies
for requisition, administrator can check demand and his/her ability to fulfill demand,
then choose to give the allocation, cancel or forward to higher authority for
recommendation. •

User Login by username & password

Not accept

else

User insert requisition information

Approve by higher authority

Display in Admin account

Not accept
Need higher authority approval

Display in Head of admin account

Approve

Need approval

Accepted
Display in Director account

Approve

Not accept

.User print requisition form Allocate vehicle & Print iogbook

Insert logbook information

Requisition complete

Insert detail reason Insert detail reason

and cancel. and cancel.

Figure 3.13: Activity Diagram of Requisition.

 37

Chapter 4

Functionalities of the Web Site

 38

4.1 System Features

The developed Transport Management System has different essential features codes.
Screen shot of some of the main features are explained below.

4.1.1 Home Page

The home page is very simple. It contains sign up page link and the menu. The user
can find service, management contact information, requisition information and sign
up information. User or Admin can also sign in by clicking in the corresponding link
of the menu. The following figure 4.1 shows the home page.

ABC BANGLA •

Abo"t Requhltloo

If you are a new user please Sign Up

Figure 4.1: Home Page.

4.1.2 Sign Up Page
New user (Employee) can fill up the employee information form. Usemame must be
unique. After clicking the submit button user can find his/her given information. He
can delete or continue. The following figure 4.2 shows the sign up page.

Employ •• Informltlon Form

"Confirm pI

-Department: Section:

Emllil: Blood Group:

L~~_!!J

Figure 4.2: Sign Up Page (User).

 39

4.1.3 Empowered User Home Page

After signing in, user move to this page. This page contains two menus. Left menu
from data base contains Requisition, Vehicle and Drivers. The user can view all
vehicle and driver information by clicking Vehicle and Drivers respectively. Other
menu contains Service, About Requisition, Management Contact No, Personal and
Log Out. The user can edit personal information by clicking in the link name
Personal. Log Out button is used to sign out. The following figure 4.3 shows the user
home page.

CATEGORIES L ••• Out

Figure 4.3: Index of User (Employee).

4.1.4 Requisition Form
User can apply using this form. All user information is shown automatically in this
form. After filling up, all other information user can apply for specific type of vehicle
in specific time. The following figure 4.4 shows the requisition form.

Employe.
I flame: II
Muhammad edl Amin
I
I Usernllme:
lI'I d
'
II Dellignation: II Teacher I
I Contact Uo: 01819132886.029966334

Section: II Science 11 OeplIflmen(; II Malhemabcs

Emllllllddress: II mullammadedlamll"l@~ II Blood Group: 110(.)ve I

I *Reasons:
II Select EJ I
.Vehlcle Type: Coo V," MIcrobus "Bus Truck

*RequiriB'd No of *Air AC NORMAl My

Seats: CondiliOfl :

*Time From; seleclB stilettE} *10: sektcl EJ seleclE]

• , y 2009EJ M OCloberEJ 0 '.Select- EJ

B
*Dale To:
I y 2009EJ M OClobe'EJ 0 ..Select ..
I
1 *Venue Form: 11
II To:
II I
.
OeUlil RVo1l5Ofl

for Travel:

.
- ~ - -
11_ I Reset I II I $,."", I
Figure 4.4: Requisition Form.
 40

4.1.5 Requisition Status

User can view hislher requisition status up to last ten applications. If any demand is
approved, user can click the Approve button and can print accepted application. If it
is not accepted it will be shown with reasons. The following figure 4.5 shows the
requisition status.

HOMEPAGE Servict'S ". About Requision Manaeement Contact No Penonal lOi Out

Your AppliCiitions Infonnillion:

IReq.1l0.IIVehicle Typell From II To I~I To II Slalus I

D~ October 29. October 29,

I 6pf~511830 PMI
Decision

!
,
2009 2009 Pending

U~
/
October 29. October 29,
2009 2009 PM Ml Ilot Approved
~~

! Cancellalion Details
(3) '~o car available at this time,

!
! DO
80
October 26,
2009

October 26,
October 26.
2009

October 26.
I Jpl~511 ~45 PM I
Approve
Print
Preview

i 2009 2009 190.AJ~llll0M'1I Completed

I
Figure 4.5: Requisition Status for Specific User.

4.1.6 Administrative Index Page

After signing in, administrators move to this page. Administrators can sign out when
access is no longer needed, by using Logout button. This page contains two menus.
Left menu from data base contains Requisition, Vehicles, Workshop, Insurance, Tax,
Fitness, Pump_Station, Driver and Change_Password. The administrators can
approve requisition. Add, view, and delete vehicles, workshop, insurance, tax, fitness,
pump station, and driver information are seen by clicking respective link.
Administrators can change password by the link Change_Password. Other menu
contains Homepage, Note Down, Employee and Log Out. Administrators also can
write down necessary notes by clicking Note Down link. Administrators can view or
delete listed employee information by clicking Employee link. Figure 4.6 shows the
administrative index page.
 41

CATEGORIES Not. Down Employ •• Locout

Figure 4.6: Admin Index Page.

4.1.7 Inbox Page

This is an inbox for administrators. There are three administrative levels; Admin,
Head of Admin and Director. When any user applies for a vehicle, admin officer
(Admin) gets this application in his/her inbox. Admin can see specific application by
clicking specific button. Admin can grant it or forward to second level administrator,
Head of Admin. Head of Admin can approve or forward to third level administrator,
Director. Director can approve it. All administrators have power to cancel the
application. Only Admin can grant the application and allocate vehicle. If any
requisition is approved, administrator can print logbook by clicking Approved button.
The following figure 4.7 shows the inbox page.

VEHICLEINFO Homepllg. Note Down Employee Logout

I RerIo.q./ AIl.meplictlntof De'signa Ion Vehicle

t' fr;;,;;-r;;;=;:lG=Jrful Click
T e ~~L:J~
ror
Detail

I:lMdEd,Am,n r==:l~ October October IU5lluo I~

L:J ~O 30.2009 30. 2009 ~ PM ~

LJ Md Ed, Am•• ~r==:lMICrobus 30.October

I:l 2009
October
30. 2009 ~~
fiU51fUlll Adm"
Hand
II
[.;l
U Muhammad
AI Am..
~
Professor ~
October
26.2009
October
26. 2009 ~
l1:i5t:'451~
PM ~

Requlstion Inform.tion will be showed here.

Figure 4.7: Inbox Page.

 42

4.1.8 Requisition Status Page

Any administrator can see requisition status at a specific date. At first, he/she has to
select a date (requisition starting date) and click the button 'Go', then he/she can see
requisition status at that date. If any application is approved at that date, administrator
can see a button named "Approved Add Logbook Info" in status column; by clicking
that button administrator can insert logbook information. After adding logbook
information administrator can view a button named "Completed Print Preview" for
this application. By clicking this button the administrator can print complete
requisition information. The following figure 4.8 shows the requisition status page.
REQUSmON Hom.pIIIC. Note Down Employ ••

S.I.ct R.quitltlon Surtfnl Dlte and Crtckthe Button:

Oct 8 '0 82009 C::J
tq9~;'>'-U

I Req.
Uo.
II
Jt
Uame 01
~ppljclI"t
11"0 I ," ••II
U""es 9"11lonn
Vehicle
.!ype I To Dale jEll T~e II Status I
ul Md Ed, Am,n1/ Teach" 1/ C"
I
,
October 3D,
2009 ~~
rT15lfTJOl In Admin
Hend

ul Md Edi A~I Teacher II MIcrobus

I
,
October 3D,
2009
~1iOl
~~
In Admin
Hend

Figure 4.8: Requisition Status Page.

4.1.9 Distribution Chart Page

By selecting a date, administrator can view distribution chart at that date according to
the given schedule. The following figure 4.9 shows the distribution chart page.
v ••••• DlnItbutlon Chart

v••.••c•• lD.
To s..

-
Dlstlibut60nChIrt 5Mct.
B, B2009
lEEl
o.t •• nd Clicku..luttan;
:J

i"o. ••••
,., ". ".
bJ. 140,
•••••••• ,,
'AM
, 'AM
, 'AM 'AM
., "AM
,, IIAM
,, 12 PM
, , <P. iP.
J to, 30 J
,
•• " • ,15,
•

~i•
, lO:~.lom
~
......~
1lI~
.'M.un
.••• _.QY

~
I
E
>0.
•
I
..
~.ID01

••••••.....,
~ •. Met.. GA.

••• Il
mn
,
.,r,n
IlKw-J009.,tol
, ~
......,
1Ullh.ol._ Un. 114.
111503
I~
.
i~~
" ~

..
~~~;~~ -

Figure 4.9: Distribution Chart Page.

-J.L .U ~ -~- .:;"...;;;
.
 43

4.1.10 Vehicles Summary Page

Administrator can see vehicle id, registration no, Purchase date, driver name, expire
date of tax and fitness, and next premium date according to vehicle's condition in this
page. By clicking the button, "Rejected" administrator can see list of rejected
vehicles. The following figure 4.10 shows the vehicles summary page.

Good Vehicles Information

! Purchase
I
VehiclelD
I Reg. No " Date Driver Name Tax Expire Fitness
Expire
Next
Premium
Bus.200S. Sherpur.Met
Ottober 19.
1002 .KHA-10-
200S Md Abbas Ail I~ovember 1. Ottober 31. November 1.
1212 2010 2010 2010
Bus-200S. Dhaka. Met. September Md Amin November 1. October 31.
1001 GA-99-SS03 23.200S Muhammad 2010 2010 uly 31.2010
Car-2009-
1001
Dhaka- Met- March 24.
KA-11-SS03 2009 IMd, Somon I2S.
November
2009
November
2S.2009
February 2S.
2009
Car-2009- Dhaka. Met.
KHA-11- October 26. Md Akbar October 31. November 1. October 31.
1002 2009 Mia 2010 2010
0004 2010
ruck.2004- Dhaka. Met. May 2S. Md Kamrul November November
1001 November 27.
GA.U-8S03 2004 Hasan 30. 2009 29. 2009 2009
Van-200S. Dhaka. Met. October 24.
1001 KA-11-1112 200S Md,kzrz M,a November 1. October 31. December 1,
,2010 ,2010 ,2009

Inside Workshop Vehicles Information

! I
Vehicle ID I Reg. 110 " Model No I Purchase
Date Tax Expire
Expire
Fitness
Premium
Next

Microbus- Sherpur-Me' MrcModeltlo October 31. October 31. Ottober 31.

200S-1001 II.GA.11-3232 2004 I~uly 20. 200S
2010 2010 2010

Click the 8utton to See Rejected Vehicles Information

II Rejected II
Rejected Vehicles Infonnation will be showed here.

Figure 4.10: Vehicle Summary Page.

4.1.11 Vehicle Information Form

Administrator can fill the form for specific vehicle and submit it. Vehicle id will be
generated automatically. Vehicle id will be generated according to 'Type- YYYY_
NNNN' where Type is vehicle type, YYYY is year part of purchase year and NNNN
is auto increment number starts with 1001 for every purchase year and every type of
vehicle_ Figure 4.11 shows the vehicle information form.
 44

V.hicl. Information form

I*Vehicle Type: I! ,_/ Car ") Van _,' Microbus ,) Bus '.v Truck
I
I "AC: II ,_, AC ,~ "ORMAl
II "Cubic Capacity :11 I
I *Gear Type:
II ' Auto I Manual Both
I
*Reglslrlltion

I
No:

II
I II "Engine 110: II
II *Monufoclurer: II
I
*Ch.llssis Uo:

*Mo1nufactured
I
Year 20098 Month seleelE] Day seleelE}
Date;
I
I *"'odel No:
II II No of Doors:
II I
I *Uo 01 Seots:
II II "Tenk Capacity: II I
I *Fuel: [J Petrol [] Gas EI O<:laM D
I! Diesel
I
I *(0101:
II II Banery Value:
II I
I Tyre Size:
II II I
I Pure has From:
II II .PriceITKJ:
II I
*Oate of
Purchase:
Year 2OO9B Month Oct EJ Day selectE]

.
Comment:

Figure 4, II: Vehicle Information Form_

4.1.12 Vehicles Information Page

Administrator can select specific vehicle and can edit, delete and vIew detail
information about the status of the vehicle, The following figure 4_12 shows the
vehicles information page,
I
I VEHICLE INFO Note Down Employee Locout
!
I
I
V.hiChts Inform.ation:

iI
I
Ice,,»>
I --"'SelecIVehicle Id and Registration No ••--.
B
I ten:»> , .-----SelectVehicle Id and Registrabon No ••---
B
I
! Microbus::>:> :-
I ---Select VehIcle Id and Registration No-- ..
B
!
I
!
/8US: >>>
I, --SelecIVehicle Id and RegistrationNo.---
B
I fruCk:»> "'-"SelectV~cle IdandRegistrationNo-- .•••
B
!
I
I
Vehicle Info will be lisled here.

Figure 4.12: Vehicles Information Page.

 45

4.1.13 Vehicle to Workshop Page

Administrator can select specific vehicle and enter its sending information sentence
to specific workshop. Administrator can write problems, if problem is more than
three, he/she can increase the number ofrows by pressing' Add' button to get up to
ten rows. The following figure 4.13 shows the vehicle to workshop page.

WORKSHOP VEHICLE Note Down Employ •• LOlout

V.hicl. To Workshop:

*Vehicle ID and
RegistratJon Uo:
..:Serect Vehicle Id and Regl9trabon No which Condlbon not Good- B
I *Workshop Name:
I "SelectWOrkshop Name--B

,
I Work Order: *"'liIe
Meler: I
-
I
I * Sending Date:
I Year 20098 Month NovemberBOaYiseleclB

I *Oue Dale 0' Return: I Year 20098 MonthNovemberB Dayr seleclB

No. Problems
1 1 i
2 I
1~3
. I
!
I «Add» I tt Rt:•••r»[s.b;, ••I
Figure 4.13: Vehicle to Workshop Page.

4.1.14 Vehicle Return from Workshop Page

The information of the vehicles in workshop is shown in this page. Administrator can
select specific vehicle and insert repair work, expense and present condition of
vehicle. The following figure 4.14 shows the vehicle return from workshop page.

WORKSHOP VEHICLE Not. Down Employ •• Lo.out

V.hicl. R.turn Form Workshop

Reference No, Vehicle

- -
ID lind Registration "SelectReference No. Vehicle Id and Registrabon No-
tlo:

Return Fann will be showed here.

Figure 4.14: Vehicle Return from Workshop Page.

 46

4.1.15 Vehicle Insurance Form

Administrator will fill the insurance form when the premium for insurance is given
for a vehicle. In the form, if the vehicle id and registration no are selected from the
dropdown list, expire date will be showed for this specific vehicle above the form.
The following figure 4.15 shows the vehicle insurance form.

VEHICLE INSURANCE Homepace Note Down Employee Locout

Vehicle Insur~nce Premjum Inform.tion Form

Excire dale will be showed here

*Vehicle 10 and
Reolstratlon t,o:
-SeleclVehicle Id and Registration No ..
8
"Insur.nce comp.ny
Uarne:
I -
Select Insurance Com Name 8
I
-
I *Certificale tlo:
I I
I "Insurance Type: I
I *Baslc :
I
I .Outy :
I
.Vat:
I II I
I *10181 :
II I
*Oate: Year '-20098 Month NovernberE] Day saleetG

*lasl Date of Uext

Premium:
Year ~E1Month seteclE] Day sel_eetB

I [ Resel II Submd ~I

Figure 4.15: Vehicle Insurance Form.

 47

4.1.16 Tax Information Form

Administrator will fill the form when tax is given for a vehicle. In the form if the
vehicle id and registration no are selected from the dropdown list, expiry date will be
showed for this specific vehicle above the form. The following figure 4.16 shows the
tax information form.

TAX INfO. Homepage Note Down Employee Logout

Add TIX Information

Expire dale will be showed here

'Vehicle 10and
Registration 110:
tSele~tVehicle Id and Registratlon~-- EJ
'0 -
eposlt.
'Deposit Type: ~ep."srtType EJ Amoun~TK):

*Tax flo:

*Oate: ~EJ 3_ EJ 2009 []

I *Oeposit Date: I Year 2~B Month' NovemberE] Day [selectE)

I *Expiry Date: I
Year ~OO9ElMonth se~tBDay ~~!~_~~B
.
Comment

.
I 'Confirmed By: II I
I I Resel II Submrt II

Figure 4.16: Tax Information Form.

d
 48

4.1.17 Fitness Information Form

Administrator will fill the form when fitness charge is given for a vehicle. In the form
if the vehicle id and registration no are selected from the dropdown list, expiry date
will be showed for this specific vehicle above the form. The following figure 4. I7
shows the fitness information form.

FITNESSINFO Homepage Note Down Employee logout

Add Fitne" Information:

Expire date will be showed here

*Vehicle 10 and
-Select Vehicle Id and Registration No-
ReQistration tlo: El

"DePO'it Type: Sel;el Depo,. Ivpe EI "Deposit

AmounIITK):
j I
I *Fitness tlo :
II I
I .Oate:
II 1l,w-E1J E12009 i:::J I
I *Oeposit Date: I Year 2009 B Month November
r- B Day: select El
I *Expire Date: I Year [2009E1 Monlh[,ei-eIEl Day ,eleetEl

.
Comment

.
"Confirmed By : I I
I [ Reset JI Submit II

Figure 4. I 7: Fitness Information Form.

 49

4.1.18 Fuel Consumption Record Form

Administrator will fill the form when fuel is taken for a vehicle. All information
stored in database can be seen and deleted by clicking left menu link record. The
following figure 4.18 shows the fuel consumption record form.

FUEL INFO. Homepage Note Down Employee Logout

Add Fuellnfonnation

*Vehicle IDand - - ----8

c::SelectVehicle Ic!.!lndRegis~ation No- •
Registration flo:

*Pump Station Id --- - -- -8

I-Select Pump Station Idand Pump Station Name-
and flame:
* FuellAeater: * Afier Buy:
I II II I
* Fuel Type:
-
-Select-8 * Fuel Amount
I II -: - II II I
* rate: * Total Money:
I II II I I
I
* Date:
II
INOy 8J
'--'-'--- ,~.- 82009 L3 I
-_ .. -
*Confirmed By: II I
I I Reset II Submn II

Figure 4.18: Fuel Consumption Record Form.

 50

4.1.19 Driver Information Form

Administrator will fill the form when new driver is appointed. In the form if vehicle
id and registration no are selected from the dropdown list, vehicle allocation
information will be showed for this specific vehicle above the form. The following
figure 4.19 shows the driver information form.

V.hicle
.'
.110(; I-on info will be .howed

ilItO,lve,
h.re

Name:

""Llean_
No: II .Grade:
II 'A "
B "
C
Vehleleld
ond
Regletretlon -s=.tecl one Id lind Registration No-- B
No:

*ConuaC1
No:
II Blood Group: 11 i-Sv1tfct-E]
•••
Joining
Y •• r 2009E]Month Novernbe.BOey seled8
Dale:
.
• Addr ••• :

.
.
comment:

.
I Reset Jtl I Submit I

Figure 4.19: Driver Information Form.

4.1.20 Change Password Page

This page is made for security purpose. Any administrator can change hislher
password from this page. The following figure 4.20 shows the change password
page.
Hi I. M8''''''€'S'd'ii 'Me".

CHANGE"II' Hote Down Employ ••

Chanc_ Your Password 111111

.Prevlous Pa••word:

__
•••
Conllrm panword:

._.-....--.--._.---._.--.--.-..-.--.--._. .
Figure 4.20: Change Password Page.
 51

Chapter 5

Conclusion
 52

5.\ Conclusion

This software is developed with the help of different kinds of tools such as PHP,
MYSQL, HTML, AJAX, JavaScript, CSS etc. The developed software is user
friendly. The Administrators (Administrative officer, Head of the Admin section and
Director) can approve/reject application for vehicle requisition with necessary notes.
Only' administrators can insert, delete and update vehicle, tax, insurance, workshop
etc. information. Thus, the security of the system has been maintained.

It is also a multi-user system, which can be used by a number of users

simultaneously. Personal information can be accessed by the particular user only.
None can view other's information. General employee (user) can view/update
his/her personal information by signing in and can apply for vehicle requisition.

The developed software can be implemented for commercial purpose. It also

provides the general guidelines to the company owners who want to develop their
own software for company's vehicle management. The companies in home and
abroad can introduce this software for the betterment and comfort of their
compames.

5.2 Future works

The developed project can be enhanced in a variety of ways. Firstly, the message
alarm and sound alarm systems can be incorporated in the software. These alamlS
will be used to alert administrators of due dates of premium of insurance, fitness
certificate, tax and other vital information of vehicles. The system may also be
modified to provide appropriate messages when the administrator enters unrealistic
maintenance information to the software. As for example, the system will restrict the
user if the user changes the tyre of a vehicle every month.
 53

References
 54

[1]. Powell, T. A., "Web Design: The Complete Reference", Tata McGraw-Hill
Publishing Company Limited, TA TA McGRA W-HILL EDITION 2000, pp
11-15,172-175,2000.
[2] http://www .dbnetso Iutions. co.uk!Arti c1es/Benefi tsOfW eb BasedA pp Iicati 0 ns.
aspx; last accessed on 05.03.2009
[3] http://www.vehicle-manager.com/; last accessed on 05.03.2009

[4] http://www.gbeit.com/pro_vms.htm; last accessed on 05.03.2009

[5] hItp:/ /www.templalesrain.com/free- temp lates/ cars/ cars2/index. php; last

accessed on 05.03.2009
[6] http://www.php.net; last accessed on 05.03.2009

[7] http://www.mysql.com/; last accessed on 05.03.2009

[8] http://www.apache.org/; last accessed on 05.03.2009

[9] http://www.w3schoo1s.com; last accessed on 05.03.2009

[10] http://www.outsource2india.com/software/process.asp; last accessed on

05.05.2009

[11] http://www.gisdeve1opment.net/proceedings/gita/1999/dda/dda003pf.htm;
last accessed on 05.05.2009
 55

Appendix A

Sitemap for Employee (User)

Index

Sign Up

Sign In

User home

Services Personal

Vehicle Information

About requisition Driver Information

Requisition

Management contact no
Form

Status

Log Out
 56

Appendix B

Sitemap for Administrators

Sign In
Services

Admin home
About requisition
Note Down
Management contact no
Change Password

Requisition
Insurance
Inbox

View/Edit/Delete

Add Premium

View/Delete Premium
Details view

Pump Station Vehicle

Summary

View/Edit/Delete Add

Add Fuel Info. View/Edit/Delete

Workshop

Tax
Add

View/Edit/Delete

To Workshop

From Workshop

Summary

Add

View/Edit/Delete