5Final Year Project Report

Fleet Management System

Student Name: Muzammil Ahmed

Roll Number: 966

Session: 2013-2017

Supervisor: Mr. Ali Sammad

A report submitted in partial fulfilment of the degree of
BS in Information Technology (BSIT)

Department of Computer Science and IT

The Islamia University of Bahawalpur

03/07/2017
Project Summary

Project Title Fleet Management System (FMS)

Major Auto Sale & Rent Management System

Domain

Project The objective of the Project is to design a Fleet Management System which
Abstract provides the framework for organizing and managing vehicles in such a way
that these vehicles deliver all the customers required to within defined quantity,
time and cost constraints.

The system applies only to the management of Vehicles Dealings and is a tool
that facilitates decision making; the FMS does not make decisions.

The Project has been designed in Adobe Dreamweaver CS6 technology and
consists of a My SQL server which acts as the database for the Project.

The Fleet Management System mainly consists of Two type of users. First type
of user is Customer who provide all information related to vehicle and Second
type of user is who perform operations on information provided by the
customer. All the data needed for the system is stored in the form of tables in
the My SQL server.
Project Team Details (if the Project has been done in a group)

Sr.# Student Name Supervisor

1 Muzammil Ahmed Mr. Ali Sammad

2
 DECLARATION

I hereby declare that this Project report is based on my original work except for citations and

quotations which have been duly acknowledged. I also declare that it has not been previously

and concurrently submitted for any other degree or award in Dept. of Computer Science and IT,

IUB or in any other institutions.

Student Name Muzammil Ahmed

Roll Number 966

Class BS(IT) Eve Rangers

Submission Date 09/07/2017

 Final Year Project Approval Letter

Ii is certified that this Project report entitled Fleet Management System prepared by

Muzammil Ahmed has met the required standard for submission in partial fulfilment of the

requirements for the award of Bachelor of Information Technology (BSIT) at The Islamia

University of Bahawalpur.

Internal Supervisor __________________________

(Name, Designation and Affiliation)

External Supervisor __________________________

(Name, Designation and Affiliation)

Head of Department __________________________

Department of Computer Science and IT

GOD HELP THOSE WHO HELP THEM SELVES

MAY ALLAH HELP ME FOR SUCCESS

 ACKNOWLEDGMENT

First of all we praise and pray the almighty ALLAH who blessed us with courage, ability and
opportunity to follow the path of the knowledge seekers. Without guidance we must not have
been able to move even a step forward. May ALLAH guide and help me throughout our life and
shower his blessings. Up and above everything, we are grateful almighty ALLAH The
beneficent, the merciful, and his Holy Prophet Hazarat MUHAMMAD (peace be upon him)
who is forever true light of guidance for whole humanity. We are greatly obliged ALLAH by
whom grace we have been able to complete this project successfully.

We feel much obliged to our families, whom prayers and good wishes have enabled us to
reach at this stage. Our success is the result of the Technical Guidance, invaluable comments and
moral support of our supervisor whose efforts and for the students are not only for projects but
also throughout the session. We are very thankful to his for taking such a pain for us. We extend
our thanks to all our teachers from whom learn a lot during the session and their nice behaviour
and attitude always encouraging us for learning.

I want to say special thanks to Mr. Ali Sammad Lecturer At department of Computer Science
to not only giving us additional guidance to the project research but also helping throughout the
organization of the thesis to meet the standards.
 ABSTRACT

Fleet management system is a model system to store the information about cars purpose is to

dealing keeps store between users.

System has a friendly user interface login which ask the user to browse the whole system and

perform different operations step by step such as entering the name and password. User can view

all their related information administrator hide unnecessary tasks from the user also system

capable for manage the record user record vehicles information .currently the system store

information in database and retrieve information on the interface with the help of data access
TABLE OF CONTENTS
Chap # TABLE OF CONTENTS Page #

FMS introduction 13
1
13
1.0 Introduction
13
1.1 Purpose For Making
14
1.2 Project Overview
14
1.3 Existing System
15
1.4 Proposed System
15
1.5 Project Modules
16
2.1 project viewpoint
16
1.2.1 User Interface
16
1.2.2 Technologies Used
17
1.2.3 Project Features
17
1.3 Basic Requirements
18
1.3.1 Other Interfaces
18
1.3.2 User Interfaces
18
1.3.3 Hardware Interfaces
18
1.3.4 Software Interfaces

1.4.0 Performance requirements 19

1.4.1 Feasibility Report 19

1.4.2 Technical Feasibility 19

1.4.3. Operational Feasibility 20

1.4.4 Economic Feasibility 20

1.4.5 Performance feasibility 20-21

Architectural Design of FMS 22

2
2.0 Introduction 23

2.1 Architecture of The FMS 23

9
 24
2.1 Class Diagram
25
2.2 Sequence Diagram

Component Design 26
3
3.1 Introduction And Purpose 27

3.2 Class Diagram 27

3.2.1 Class Description 27

3.2.1.1 User Registration 27

3.2.1.2 Add Cars 28

3.2.1.3 Add Reservation Car 29

3.2.1.4 Add Booking 30

3.2.1.5 Customer Registration 31

3.2.1.6 Customer Feedback 32

TEST PLANING FOR FMS 33

4
4.1 Introduction 34

4.2. System Implementation 34

4.2.1 Unit Testing 34

4.2.2 Integration Testing 34

4.2.3 System Testing 35

4.2.4 Acceptance Testing 35

4.2.5 Data Flow Testing 35

4.2.6 Validation Testing 35

4.2.7 Performance Testing 36

4.3.1 System Implementation 37

4.3.2 Introduction 37

4.3.3 Software Testing 38

Testing And Evaluation 39

5
5.0 Introduction 40

10
 5.1 Real world testing 40

5.1.1 Testing Procedure 40

5.2 Testing Strategy 40

5.3 Test Cases And Results 41-47

System Design 49
6
6.1 Introduction 49

6.2 Data Flow Diagrams 49

6.3 Symbols 50

6.4 Use Cases Diagrams 51-53

6.5 Sequence Diagrams 54-58

Language overview 59
7
7.0 Introduction Of Php 60

7.1 Application Of Php 61

7.2 Introduction of HTML 62

7.3 Introduction Of database 63

7.2.4 Advantage of DBMS 64

7.2.5 Disadvantage of DBMS 65-66

Output Screen Shots 67-88

8
Code Screenshots 89-94
9

Appendix 95
10
11 Conclusion 96-97

REFERENCES 98-100
12

11
 Chapter: 01

FMS INTRODUCTION

12
 INTRODUCTION

1.1 PURPOSE FOR MAKING

The main purpose of this system is to list the requirements of the Fleet Management System.

This is also helps us to collect and analyse the ideas gathered for the Project to deals the

difficulty we face in manually vehicles dealings. Purpose of this system will be subject to

change, all type of difficulties and problems (booking new and old car payment issues) that is

face by seller and buyer in Fleet management system.

1.2 PROJECT OVERVIEW

We aim to become a pioneer in the vehicle rental and new sales cars industry by completely
focusing on customers, our employees, growth, innovation and efficiency. All of these elements
will drive us towards success and show us as one company that can perform and give value for
money.

When it comes to Bahawalpur rent and motor services, Bahawalpur rent services is the most
trusted and reliable name in the travel business and Sales cars. The most advanced travel agents
offering rent and car booking in Pakistan, making full use of information technology to improve
the level of our efficiency. However, this is only one aspect of services. And this Project
continually strive to offer the best of services - both in terms of man and machine, to our clients
Moreover, this Project has a best cars ranging from luxury to budget cars. While, it offers online
car hire service for corporate houses. And this Project claim to offer the best of rates, which are
tailor-made depending upon the facilities, availed and offer both within city and outside-city car
facilities. All cars have proper permits and documentation so that the clients couldn't be worry
for the lack of documents. However, this Project has strategic backup system for any eventuality.

All new upcoming models booking can be made in advanced with all surety of your advance
payment car delivered according to decided date and time duration to improve customers
feedback and increase the number of customers. System handle all communication and dealing

13
between, user. Further, this Projects utmost priority is quality. To achieve this, vehicles are well
maintained and tested for delivering optimum and uninterrupted performance. Team of
professionals in the travel business enables this system to design trips that suits to all budgets and
preferences of the travellers. In addition, workforce including drivers and administrative staff are
well trained to discharge their duties with a lot of efficiency.

The Fleet Management System for vehicles shops is an implementation of a system for user of

the vehicle shop, which helps the user to search the availability of vehicles. This Project also

covers various features like Add users of the cars, modifying the Profile of the user by update.

Add, manage or update vehicles, budget and issues pending payments and deliveries to

perform daily transactions and also Generate Reports of vehicles status, and customers

feedback.

1.3 Existing System

Fleet Project Service is an innovative thought to simplify the Transportation

problems of Employees of an organization. In the present System, Organization do maintain a
person for the allocating and proper functioning of transportation .The Person appointed needs to
look after the assigning and movement of Projects. Authorized person maintains the
transportation details in papers, which is a tedious task if any updating or changes need to be
done.

Details are stored in Papers.

Maintenance is a huge problem.

Updation, changes in details is a tedious task.

Performance is not achieved up to the requirements.

Difficulty to manage records.

14
1.4 Proposed System

In the Previous System, Details are Stored Manually in papers, to share the
details between employees was a financial drawback. Updating in the details is a tedious task.

But a new system was proposed to overcome the above drawbacks.

Functionalities and advantages of proposed system are:

Data is centralized which has overcome the Sharing problem in previous system.

As data is maintained electronically, its easy for a person to update the details, which has
overcome the tedious updation in previous system.

Maintenance is easy and performance is good.

Mainly the system has automated the Transportation Process.

1.5 Modules of the Projects:

Admin module
Maintenance module
User module

2.1 PROJECT VIEWPOINT

The Fleet Management System uses the Dreamweaver CS6 and is completely Independent. The

Project is a web-based system. It can be accessed using Internet Explorer 8.0 and above, Mozilla

Firefox, and Google Chrome.

15
1.2.1User Interface: Users are able to view dashboard/index of the Fleet Management System,

view available vehicles make reservation for rent/buying. Update their, Feedback, email address

and image etc.

Admin Interface: The administrator has access to entire Fleet Management System, is able to

add, view, update or delete the customers, users and their information their vehicles, or defects

and view Feedback about vehicles, defaulter, and customers.

1.2.2 TECHNOLOGIES USED

PHP: Hypertext Pre-processor

Bootstrap (Responsive)

Html, CSS, JS

1.2.3 User Activity

The users of the Fleet Management System, based on their roles, are (users) and the

administrator (owner). These users are identified based on their experience and technical

expertise.

Admin Activity: The administrator is the owner of the Project Management System. The

administrator can perform the following functions:

1. Add new client, requirement, issues, Customers and Vehicles.

2. View Information, requirements, issues, Customers and vehicles.

3. Update information, about, new, Customers and vehicles.

4. Delete information, issues, Customers and vehicles.

16
Users:

The users of Fleet Management System are all employee. The users should be able to

perform the following functions using this system:

User will be able to make account on system for access system working .view

information details of vehicles / images.

Make booking for new and rent cars in advance to fulfill the decided rules.

1.3.0 OTHER INTERFACES

The different types of interfaces that we would come across while developing the Fleet
Management System are as follows:

User Interface

Hardware Interface

Software Interface

1.3.1 USER INTERFACE

The user interface have divided into many interface like login registration home page and all

page have many other function and interface.

Login interface

Dashboard / Home page interface

User Registration interface

Vehicles interface

Booking vehicle interface

User feedback interface

17
 Fig 1.4 login interface

1.3.2 Hardware Interface

The following hardware configurations are required for a PC using the Fleet Management

System:

Pentium processor

64 MB of free hard-drive space

128 MB of RAM

1.3.3 SOFTWARE INTERFACE

Operating System: Windows (Vista/Windows 7 or 8)

Web Brower: Internet Explorer (8.0 and above), Mozilla Firefox (3.0 and above), or

Google Chrome Apache Tomcat Server MySQL Dreamweaver CS6

. Performance requirements

18
1.4.1 Feasibility Report

Preliminary investigation examine Project feasibility, the likelihood the system will be useful

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

Operational and Economical feasibility for adding new modules and debugging old running

system. All system is feasible if they are unlimited resources and infinite time. There are

aspects in the feasibility study portion of the preliminary investigation:

Technical Feasibility

Operation Feasibility

Economic Feasibility

1.4.2 Technical Feasibility

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

following:

Does the necessary technology exist to do what is suggested?

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

the new system?

Will the proposed system provide adequate response to inquiries, regardless of the

number or location of users?

Can the system be upgraded if developed?

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

1.4.3. Operational Feasibility

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

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

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

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

Is there sufficient support for the management from the users?

Will the system be used and work properly if it is being developed and implemented?
Will there be any resistance from the user that will undermine the possible application
benefits?
1.4.4 Economic Feasibility

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

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

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

must equal or exceed the costs.

1.4.5 Performance feasibility

This section lists the performance requirements expected from the Fleet Management

System.

The users shall be able to add a add vehicles, status, availability, customer or new user in

fewer than 5 seconds.

The users shall be able to view information about Fleet, status, description, user or

customer in fewer than 5 seconds.

The users shall be able to check the feedback or users, customers, tasks and defects in the

Reports within 10 seconds.

The navigation between pages shall take fewer than 5 seconds. The application shall be

able to do a validation check on the information provided in the user-login, user

registration and other form to avoid false or incomplete information.

20
Chapter: 02

21
 Architectural/Basic Design

2.0 INTRODUCTION

The main purpose of the Architecture Design document is to discuss the architectural design for

the Fleet Management System in a clear and concise form. This design document will give a

detailed description of the presentation tier, the middle tier which consists of the class diagrams,

sequence diagrams for the Fleet Management System network and finally the data tier.

2.1. ARCHITECTURE OF THE FMS

The three tiers in a three-tier architecture are:

1. Presentation Tier: Occupies the top level and displays information related to services
available on a website. This tier communicates with other tiers by sending results to the
browser and other tiers in the network.

22
 2. Application Tier: Also called the middle tier, logic tier, business logic or logic tier, this
tier is pulled from the presentation tier. It controls application functionality by
performing detailed processing.
3. Data Tier: Houses database servers where information is stored and retrieved. Data in this
tier is kept independent of application servers or business logic.

CLASS DIAGRAM DATABASE TABLES Fig 2.1

23
 SEQUENCE DIAGRAM OF USER LOGIN Fig: 2.2

User movement in different activity performing on form and result of that is the step by step
move on three tire structure. User registration to user login and view home is the best description
of the three tire architecture.

24
 Chapter: 03

Component Table Design

25
INTRODUCTION AND PURPOSE

The main purpose of the Component Design document is to provide and explain the

component design for the Fleet Management System Project in detail.

3.1. CLASS DIAGRAM

The class diagram of the Project Management System Project would be as follows:

CLASS DESCRIPTION

3.1.1.1. User registration

Fig 3.2 User Registration Table

26
User registration table the attributes for the user are user ID which is unique, First Name, email

Address Name, Password, Cnic No, Date of Birth, and Address. The functions that the user

would be able to perform are:

Register the administration would be able to register new user onto the system.

Login the user can login with the Email and password.

Home page the user view the home page.

3.1.1.2. Add Cars

Fig 3.3 Add Cars Table

In this table user add a new Cars in a data base which insert some values like id will be Unique

in each table Registration No, Car Name, Seats Capacity, Car type, Car Model, Price, Colour,

Fuel Type, Car For/Rent & Sale and Car Image input Progress, output Description and Notes.

.The functions that the Administrator would be able to perform are:

27
Login - the Administrator can login with the email id and password.

Add the Administrator would be able to add new cars

Update the Administrator would be able to update view delete the cars by assign user.

3.2.1.3 Car Reservation

Fig 3.4 Car Reservation Table

In this table user can find the largest categories of cars of each companies make reservation of

own choice by given required inputs these inputs are like Car Name, Start Date , Pickup

Location , Drop-off Location, End Date, Start Date, Rent Amount, Start Time End Time And Car

Colour, input Progress, output Description and Notes.

The functions that the Administrator would be able to perform are:

Login - the Administrator can login with the email id and password. Add the Administrator would be

able to add new Car On reservation /this also done by user if this system work online .

28
3.2.1.4 Add Booking

Fig 3.5 Add Booking Table

In this table user can make booking about their need of car like Car Name, Father Name, Cnic

No, Phone No, Email Address, Car Type, Car Model, Car Colour, Add Amount, Delivery

Duration, Current Address, Permanent Address.

The functions that the Administrator would be able to perform are:

Login - the Administrator can login with the email id and password.

Add the Administrator would be able to add new Booking Of Car.

29
3.1.1.3. Customer Registration

Fig 3.6 Customer Registration Table

Customer registration table the attributes for the user are Customer ID which is unique,

Company/Customer Name, Father Name, Cnic No, Email Address, Date of Birth, Current

Address, and Permanent Address.

The functions that the Administrator would be able to perform are:

Login - the Administrator can login with the email id and password.

Add the Administrator would be able to add new customer.

30
3.1.1Customer Feedback

Fig 3.6 Customer Feedback Table

Customer Feedback table the attributes for the user are Customer ID which is unique, Customer

Name, Email Address, Date of Birth, and Message.

The functions that the Administrator would be able to perform are:

Login - the Administrator can login with the email id and password.

Add the Administrator would be able to view Feedback new customer.

31
 Chapter: 04

Test Planning For FMS

32
 TEST FOR Project Management System (FMS)

4.1. INTRODUCTION

The main purpose of the test plan for the FMS is to describe the testing details of the use cases of

the FMS. The software Project test plan also describes the objective, scope and approach of the

software testing effort for the Fleet Management System.

The test plan for the FMS also indicates the personnel responsible for each task and also

specifies the risks associated with the test plan.

4.2. SYSTEM TESTING AND IMPLEMENTATION.

.Another reason for system testing is its utility as a user-oriented vehicle before implementation.

The best program and the user have communication barriers due to different background.

4.2.1 Unit Testing

Unit testing focuses verification effort on the smallest unit of software design, the module.
The unit testing we have is white box oriented and some modules the steps are conducted in
parallel.
4.2.2 INTEGRATION TESTING

33
 In Integration Testing, the individual software modules are combined and tested as a

whole unit. The integration testing generally follows unit testing where each module is tested as

a separate unit. The main purpose of the integration testing is to test the functional and

performance requirements on the major items of the Project.

All the modules of the Project developed individually would be combined together and tested as

a whole system in the integration testing.

4.2.3 SYSTEM TESTING:

System Testing is executing a program to check logic changes made in it and with the intention

of finding errors making the program fail. Project that has been developed meets all the

requirements. Different type integration tests perform.

4.2.4 ACCEPTANCE TESTING:

Acceptance Testing is running the system with live data by the actual user of
the system. Testing is vital to the success of the system. System testing makes a logical
assumption that if all the parts of the system are correct, the goal will be successfully achieved.
In adequate testing or no-testing leads to errors that may not appear until months later

4.2.5 DATA FLOW TESTING

This type of testing selects the path of the program according to the location of definition and use
of variables. This kind of testing was used only when some local variable were declared. The
definition-use chain method was used in this type of testing. These were particularly useful in
nested statements.

4.2.6 Validation testing:

34
At the end of integration testing, the system is completely assembled as a package with

interfacing errors corrected after which a final series of software tests namely validation testing

begins. Validation succeeds when the software functions in a manner that can be reasonably

expected by the user.

4.2.7 Performance Testing:

For real-time systems, software that provides required function but does not conform to

performance requirement is unacceptable. Performance testing is designed to test the run-time

performance of software within the context of an integrated system. Performance testing occurs

throughout all steps in the testing process. Even at the unit level, the performance of an

individual module may be accessed as tests are conducted. However, it is not until all system

elements are fully integrated that the true performance of a system can be ascertained.

4.3. System implementation:

After proper testing and validation, the question arises whether the system can be implemented

or not. Implementation includes all those activities that take place to convert from the old system

to the new. The new system may be totally new; replacing an existing module or automated

system, or it may be major modification to an existing system.

In either case proper implementation is essential to provide a reliable system to meet

organization requirements. All planning has now, be completed and the transformation to a fully

operational system can commence. The first job will be writing, debugging documenting of all

computer programs and their integration into a total system.

35
But this approach requires careful planning and coordination, particularly during the changeover.

A phased approach, possible implementing the system of the section relating to one operation or

procedure first and processing to more no velour complex subsystems in the fullness of time.

4.3.0 PURPOSE FOR TESTING

The main objectives of the test plan for the Fleet Management System are as follows:

To check ensure the features Functions of the system that will be tested completely.

To check and describe all the activities /functionalities necessary to prepare for and conduct the

testing process.

To discuss the different testing methods techniques being used to test the Fleet Management

System

4.3.1 SYSTEM TESTING AND IMPLEMENTATION

4.3.2 INTRODUCTION

The main purpose of the test plan for the FMS is to discuss the testing details of the use cases of
the FMS. The software Project test plan also describes the objective, scope and approach of the
software testing effort for the Fleet Management System. The test plan for the FMS also
indicates the personnel responsible for each task and also specifies the risks associated with the
test plan.Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and coding. In fact, testing is the one step in the software
engineering process that could be viewed as destructive rather than constructive.

A strategy for software testing integrates software test case design methods into a well-planned
series of steps that result in the successful construction of software. Testing is the set of activities

36
that can be planned in advance and conducted systematically. The underlying motivation of
program testing is to affirm software quality with methods that can economically and effectively
apply to both strategic to both large and small-scale systems.

4.3.3 SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system engineering defines
the role of software and leads to software requirement analysis where the information domain,
functions, behaviour, performance, constraints and validation criteria for software are
established. Testing progress by moving outward along the spiral to integration testing, where
the focus is on the design and the construction of the software architecture. Talking another turn
on outward on the spiral we encounter validation testing where requirements established as part
of software requirements analysis are validated against the software that has been constructed.
Finally we arrive at system testing, where the software and other system elements are tested as a
whole.

SYSTEM TESTING

ACCEPTANCE
TESTING

UNIT TESTING

Component Testing

VALIDATION TESTING

37

VALIDATION
TESTING/PERFORMANC
Integration

Testing

User testing

CHAPTER: 5

TESTING AND EVALUATION

38
5 INTRODUCTION

The chapter describe and discusses both the real world and black box testing carried out

on the Fleet Management system, and gives Evaluation of functionality and user interface of the

system presents the results obtained by testing the Fleet Management System.

5.1 REAL WORLD TESTING

This section describe and shown the output results of real world testing procedure

carried out on the system

5.1.1 TESTING PROCEDURE

To Testing the system in real environment ( where the system work and what its user

think about the system Practice this testing by collecting some users give brief information

about the system . all participants were asked to fill feedback form which contain

questioners regarding overall system behaviour as they experience

The list of the questions in questioners shown below:

Dose system interface user friendly?

How easy to use did you find the system to be?

Does system complete information about Rental and Booking vehicles process?

How can you says system is efficient gives points from 0 to 10?

5.2 TESTING STRATEGY

39
 The software testing methods are divide into two categories:

White Box testing

Black Box testing

This strategy used for testing is black box testing. Every module is tested and after the

integration of all modules again individually testing is done.

5.3 TEST CASES

Test case: 1

System:

Fleet management system

Test:

The login form is opened and login, name and password entered. Or the user enter a

wrong email and password into the given field and push into login button.

Instructions:

Click on the form and open.

Enter user name and password.

Expected result:

Alert message will show this is an invalid name and password, or enter correct name

and password the result of this input is invalid username and password. And user

cant login.

Actual result: An error occurs with following message Please enter valid username

and password:

40
Test case: 2

System:

Fleet management system

Test:

The login form opened the user enter a correct email and password into given field and

push into login button

Instructions:

Click on the form and open.

Enter user name and password.

Expected result:

The main index page will be open.

Actual result: The result of input is valid username and password. And user move

into the home page.

Test case: 3

System:

Fleet management system

Test:

Choose form menu for reservation car enter the required information and click the

submit button

Instructions:

41
 Click on the form and open.

Enter required information in to inputs fields.

Expected result:

Record inserted successfully in to database.

Actual result: The result of input is was as per expected reservation is completely

done.

Test case: 4

System:

Fleet management system

Test:

Update Button: Choose form from menu of Manage booking make change in to the

information according to need.

Instructions:

Click on the booking manage form and open.

Enter desired information in to inputs fields you have to make change click the

update button.

Expected result:

Record updated successfully in to database.

Actual result: The result of input was as per expected record is successfully

updated.

Test case: 5

System:

Fleet management system

42
 Test:

Signup Button: User Registration open form If the user not fill some field and give

irrelevant data according to given from and click on the register button.

Instructions:

Open form and fill the input fields.

Enter all information in to inputs fields of (user name cnic mobile no address) Click

submit button.

Expected result:

User registered successfully and allows access to the mien menu.

Actual result: If field is empty the 1st error is come for required and fill the all

field. And second come if you put a data wrong into the field.

Test case: 5

System:

Fleet management system

Test:

User Registration open form If the user fill all field and give relevant data according to
given from and click on the register button.

.Instructions:

Open form and fill the input fields.

Enter all information in to inputs fields of (user name cnic mobile no address) Click

submit button.

Expected result:

43
 User registered successfully and allows access to the mien menu.

Actual result: The result of this input is you are registered and move into login

page.

Test case: 6

System:

Fleet management system

Test:

Send Button The user enter an email, subject and content into the text field and press
send.

Instructions:

Open form and fill the input fields.

Enter all information in to inputs fields click on Send button.

Expected result:

Message send.

Actual result: When enter an email, subject and content the message is send to that

particular email.

The user choose from given options any car type name.

Test case: 6

System:

44
Fleet management system

Test:

Search Button The user choose from given options any car type name

Instructions:

Open form choose from given options input fields.

Choose from given options information click on Search button.

Expected result:

Show result according to search.

Actual result:

Result was as per accepted

45
5.2 Requirements cases of project

5.3.1 INTRODUCTION

The User Manual explains us the step by step procedure to use the Fleet Management System.

That is more user friendly based system more easily for any type of user working on system

5.3 REQUIRED SOFTWARE

The required software for the Fleet Management System Project would be as follows:

Operating System:

Microsoft Windows Xp, Vista, 7, 8 or 10.

Dreamweaver CS6:

It can be downloaded from Microsoft website

(http://www.microsoft.com/en-in/download/details.aspx).

Microsoft My SQL server:

It can be downloaded from Xampp website

(https://www.apachefriends.org/download.html).

46
 Chapter 6
FMS System Design

47
6.0 Module design:

Software design sits at the technical kernel of the software engineering process and is
applied regardless of the development paradigm and area of application. Design is the first step
in the development phase for any engineered product or system. The designers goal is to
produce a model or representation of an entity that will later be built. Beginning, once system
requirement have been specified and analysed, system design is the first of the three technical
activities -design, code and test that is required to build and verify software.

The importance can be stated with a single word Quality. Design is the place where
quality is fostered in software development. Design provides us with representations of software
that can assess for quality. Design is the only way that we can accurately translate a customers
view into a finished software product or system. Software design serves as a foundation for all
the software engineering steps that follow. Without a strong design we risk building an unstable
system one that will be difficult to test, one whose quality cannot be assessed until the last
stage.

6.2. DATA FLOW DIAGRAMS

A data flow diagram is graphical tool used to describe and analyse movement of data
through a system. These are the central tool and the basis from which the other components are
developed. The transformation of data from input to output, through processed, may be
described logically and independently of physical components associated with the system. These
are known as the logical data flow diagrams. The physical data flow diagrams show the actual
implements and movement of data between people, departments and workstations which plays
vital role in studying the current system. The process in the context level diagram is exploded
into other process at the first level DFD.

48
6.3 DFD SYMBOLS:

In the DFD, there are four symbols

1. A square defines a source(originator) or destination of system data

2. An arrow identifies data flow. It is the pipeline through which the information flows
3. A circle or a bubble represents a process that transforms incoming data flow into outgoing
data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of data

Process that transforms data flow.

Source or Destination of data

Data flow

Data Store

CONSTRUCTING A DFD:

Several rules of thumb are used in drawing DFDS:

49
1. Process should be named and numbered for an easy reference. Each name should be
representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data traditionally flow
from source to the destination although they may flow back to the source. One way to
indicate this is to draw long flow line back to a source. An alternative way is to repeat the
source symbol as a destination.
3. The names of data stores and destinations are written in capital letters. Process and dataflow
names have the first letter of each work capitalized

Use case diagram for user 6.1

Use case diagram for user 6.1

Precondition

User must have a valid username and password.

50
Description

This user case describe how a user login the system.

Basis flow

1. Admin can open run the project.

2. Admin enter his user name and password clicks on the login button.
3. If the user is validated by the system he is shown main from depending on his privilege
level.
4. The user is ready for doing the work (reservation for cars).

User case diagram for admin 6.2

Precondition

Admin must have a valid username and password.

Description

This use case describe how an Admin login the system.

51
Basis flow

1. Admin can open run the project.

2. Admin enter his user name and password clicks on the login button.
3. The user is ready for doing the work (reservation for cars).Admin can add cars
4. Admin Can manage cars information
5. Admin can generate slip of payment
6. The user is ready for doing the work (reservation for cars).

Use case diagram For Admin 6.3

Precondition

Admin the system as an administrator.

52
Description

This use case describe how an Admin login the system and doing many type of their work
related

Basis flow

1. Admin can open run the project.

2. Admin enter his user name and password clicks on the login button.
3. The user is ready for doing the work (reservation for cars).Admin can add cars
4. Admin Can manage cars information
5. Admin can view the record.
6. Admin can edit the record.
7. Admin can delete the record.
8. Admin can update the record.
9. After do this required work.
10. Click the logout button and get out from the system.

Sequence diagram user registration fig: 6.4

53
Precondition

User make registration request to access the system.

Description

This sequence diagram describe how a user registered to access the system.

Basis flow

1. User first make request for register by press signup button.

2. Enter the required field with required information.
3. Information check by the admin.
4. All information according to demand.
5. Message shown to user successfully registered.

54
 Sequence diagram user registration with error fig:6.5
Precondition

User failed registration by entering invalid fields.

Description

This describe how a user cannot login the system.

Basis flow

1. User first make request for register.

2. Enter user name and password clicks on the login button after request pass.
3. Gives invalid inputs.
4. Admin checks information
5. Request cancelled due to invalid inputs.
6. User switch from system.

Sequence diagram user Login fig: 6.5

55
Precondition

User login in to system.

Description

This describe how a user login the system.

Basis flow

1. User first fill the inputs fields.

2. Enter user name and password clicks on the login button.
3. Gives valid inputs.
4. Admin checks information match inputs.
5. Message show you have successfully login.
6. User move on index page.

56
 Sequence diagram car reservation fig: 6.5

Precondition

User make reservation request by step of conditions.

Description

This describe how a user login the system and make reservations.

Basis flow

1. User first make request for register.

2. Enter user name and password clicks on the login button after request pass.
3. Request for reservation.
4. Admin checks information
5. Car allocated to user.
6. If information not relevant then request cancelled.
7. User logout from system.

57
 Chapter 7
Languages Overview

58
7.0 PHP (Server-Side Scripting Language)

PHP is a server-side scripting language designed primarily for web development but also
used as a general-purpose programming language. Originally created by Rasmus
Lerdorf in 1994, the PHP reference implementation is now produced by The PHP
Development Team. PHP originally stood for Personal Home Page, but it now stands for
the recursive acronym PHP: Hypertext Preprocessor.

PHP code may be embedded into HTML or HTML5 markup, or it can be used in
combination with various web template systems, web content management
systems and web frameworks. PHP code is usually processed by a
PHP interpreter implemented as a module in the web server or as a Common Gateway
Interface (CGI) executable. The web server software combines the results of the
interpreted and executed PHP code, which may be any type of data, including images,
with the generated web page. PHP code may also be executed with a command-line
interface (CLI) and can be used to implement standalone graphical applications.

The standard PHP interpreter, powered by the Zend Engine, is free software released
under the PHP License. PHP has been widely ported and can be deployed on most web
servers on almost every operating system and platform, free of charge.

The PHP language evolved without a written formal specification or standard until 2014,
leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has gone
on to create a formal PHP specification.

7.1 Feature of PHP Robust

Support for object-Oriented Programming. The PHP Data Objects extension which defines a
lightweight and consistent interface for accessing databases.

Performance enhancements taking advantage of the new engine.

Better support for MYSQL through a completely rewritten extension.
Data integrators.

Error handling through exception

59
7.1.1 PHP Applications

PHP is mainly focused on server-side scripting, so you can do anything any other CGI program can do,
such as collect form data, generate dynamic page content, or send and receive cookies. But PHP can do
much more. There are three main fields where PHP scripts are used.

Server-side scripting. This is the most traditional and main target field for PHP. You need three
things to make this work. The PHP parser (CGI or server module), a web server and a web
browser. You need to run the web server, with a connected PHP installation. You can access the
PHP program output with a web browser, viewing the PHP page through the server.
Command line scripting. You can make a PHP script to run it without any server or browser.
You only need the PHP parser to use it this way. This type of usage is ideal for scripts regularly
executed using cron (on *nix or Linux) or Task Scheduler (on Windows). These scripts can also
be used for simple text processing tasks.
Writing Client-Side GUI Applications: PHP is probably not the very best language to write
windowing applications, but if you know PHP very well, and would like to use some advanced
PHP features in your client-side applications you can also use PHP-GTK to write such programs.
You also have the ability to write cross-platform applications this way. PHP-GTK is an extension
to PHP, not available in the main distribution.

PHP can be used on all major operating systems, including Linux, many UNIX variants,
Microsoft Windows, Mac OS, and probably others.
PHP has also support for most of the web servers today. This includes Apache, Microsoft Internet
Information Server, Personal Web Server, Netscape and planet servers for the majority of the
servers PHP has a module, with PHP, and you have the freedom of choosing an operating system
and a web server.

60
7.2 Hypertext Mark-up Language (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 webserver or from local storage and
render them 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 forms, may be embedded into the rendered
page. It 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 <img

/> and <input /> introduce content into the page directly. Others such

as <p>...</p> surround and provide information about document text and may include

other tags as sub-elements. 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
affect the behavior and content of web pages. Inclusion of CSS defines the look and
layout 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.

7.1.3 Apache Server:

Introduction:

61
Often referred to as simply Apache, a public-domain open source Web server developed by a
loosely-knit group of programmers. The first version of Apache, based on the NCSA http Web
server was developed in 1995.

The original version of Apache was written for UNIX, but there are new versions that run under
OS/2, Windows and other platforms.

The name is a tribute to the Native American Apache Indian tribe, a tribe well known for its
endurance and skill in warfare. A common misunderstanding is that it was called the name a
patchy server, or Apache server.

7.1.4 What is phpMyAdmin?

PhpMy Admin is a tool written in PHP intended to handle the administration of MySQL over the
Internet. Currently it can create and drop databases, create/drop/alter tables, and delete/edit/add
fields, execute any SQL statement, and manage keys on fields

7.3 Introduction of database

A database is a collection of information in a structure way. We can say that it is a collection of a

group of facts. Your personal address book is a database of names you like to keep track of such
as member of family and friends. Database is a collection of organized data for one or more uses,
typically in digital form. One way of classifying database involves the type of their contents for
bibliographic, document-text statistical etc.
What is database system?

A database is a collection of information organized into interrelated tables of data and

specification of data objects, It is a kind of electronic filing cabinet. It is also known as
computerized data files. The database system is essentially a computerized record keeping
system. The database itself can be regard.

1.3.1 SQL SERVER/DATABASE MANAGEMENT SYSTEM

62
A database management, or DBMS, gives the user access to their data and helps them transform
the data into information. Such database management systems include dBase, paradox, IMS,
SQL Server and SQL Server. These systems allow users to create, update and extract
information from their database.
A database is a structured collection of data. Data refers to the characteristics of people, things
and events. SQL Server stores each data item in its own fields. In SQL Server, the fields
relating to a particular person, thing or event are bundled together to form a single complete unit
of data, called a record (it can also be referred to as raw or an occurrence). Each record is made
up of a number of fields. No two fields in a record can have the same field name.

Posing of data retrieval queries in a standard manner.

Retrieval of queries results efficiently.
Concurrent use of the system by a large number of users in a consistent manner.

DATA

Data is information that has been categorized for a predetermined purpose. The term data is often
used to distinguish between binary machine readable information from textual human readable
information.

7.2.3 SQL SERVER TABLES

SQL Server stores records relating to each other in a table. Different tables are created for the
various groups of information. Related tables are grouped together to form a database.
PRIMARY KEY
Every table in SQL Server has a field or a combination of fields that uniquely identifies each
record in the table. The Unique identifier is called the Primary Key, or simply the Key. The
primary key provides the means to distinguish one record from all other in a table. It allows the
user and the database system to identify, locate and refer to one particular record in the database.
RELATIONAL DATABASE
Sometimes all the information of interest to a business operation can be stored in one table. SQL
Server makes it very easy to link the data in multiple tables. Matching an employee to the

63
department in which they work is one example. It stores data in two or more tables and enables
you to define relationships between the tables and enables you to define relationships between
the tables.
FOREIGN KEY
When a field is one table matches the primary key of another field is referred to as a foreign key.
A foreign key is a field or a group of fields in one table whose values match those of the primary
key of another table.
REFERENTIAL INTEGRITY
Not only does SQL Server allow you to link multiple tables, it also maintains consistency
between them. Ensuring that the data among related tables is correctly matched is referred to as
maintaining referential integrity.
DATA ABSTRACTION
A major purpose of a database system is to provide users with an abstract view of the data. This
system hides certain details of how the data is stored and maintained. Data abstraction is divided
into three levels.
Physical level:
This is the lowest level of abstraction at which one describes how the data are actually stored.
Conceptual Level:
At this level of database abstraction all the attributed and what data are actually stored is
described and entries and relationship among them.
View level:
This is the highest level of abstraction at which one describes only part of the database.

7.2.4 ADVANTAGES OF RDBMS

Redundancy can be avoided

Inconsistency can be eliminated
Data can be Shared
Standards can be enforced
Security restrictions can be applied

64
 Integrity can be maintained
Conflicting requirements can be balanced
Data independence can be achieved.

7.2.5 DISADVANTAGES OF DBMS

A significant disadvantage of the DBMS system is cost. In addition to the cost of
purchasing of developing the software, the hardware has to be upgraded to allow for the
extensive programs and the workspace required for their execution and storage.

ENTERPRISE WIDE DATA SHARING

The unrivalled portability and connectivity of the SQL SERVER DBMS enables all the systems
in the organization to be linked into a singular, integrated computing resource.
PORTABILITY
SQL SERVER is fully portable to more than 80 distinct hardware and operating systems
platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary platforms.
This portability gives complete freedom to choose the database server platform that meets the
system requirements..
DISTRIBUTED DATA SHARING
SQL Servers networking and distributed database capabilities to access data stored on remote
server with the same ease as if the information was stored on a single local computer. A single
SQL statement can access data at multiple sites. You can store data where system requirements
such as performance, security or availability dictate.

65
Chapter 8

Screen Shots

66
Fig 8.1 Sign up interface

67
Fig 8.2 Sign in interface

68
69
Fig 8.3 Homepage interface with menu and footer

70
Fig 8.4 Profile after login interface

71
Fig 8.5 Add User interface

72
Fig 8.6 Add Car interface invalid input alert

73
8.7 Add client inputs fields Edit Record

74
Fig 8.8 Add User interface with Alerts

75
 Fig 8.9 Manage User interface

Fig 6.10 Manage User Feedback interface

76
Fig 8.11 Add Car interface

77
Fig 8.12 Manage Project interface

78
Fig 8.13 Car Booking User interface

79
Fig 8.14 Manage Booked car interface

80
Fig 8.15 Manage Add Car interface

81
Fig 8.16 rent a car interface

82
Fig 8.17 View and delete alert interface

Fig 8.18 Manage rent a car interface

83
Fig 8.18 Record deleted interface alert

Fig 8.19 update Record interface alert

84
Fig 8.19 View Update Record interface

85
Fig 8.19 payment slip interface

86
Fig 8.20 payment slip interface

87
Chapter: 09
Code Snippet

88
Introduction

This chapter is defines the some code of line which is use in a Project building.

9.1 Code Lines

Shot 9.1 Database connection

Sign in

Shot 9.2 User Session Start and destroy

89
Shot 9.3 session start for login

Shot 9.4 Update User Reservation

90
Shot 9.5 Delete User

Shot 9.6 View User

91
Shot 9.7 Distinct Used to get images of vehicles on front end.

92
Shot 9.8 Add Car Booking

Shot 9.9 Add Car Booking Payment Slip

93
Appendix: List of Tools:

Microsoft Windows 8

HTML

. Bootstrap

JS

CSS

Adobe Photo Shop CS6

Microsoft Paint

Adobe Dreamweaver CS6

MySQL as relational database

XAMPP 3.2.1

PHP My Admin

94
Chapter 11

Conclusion

95
Limitations
BAHAWALPUR RENTALS AND MOTERS is a Web application and it is restricted to only
limited type of users. In this application, Different types of Users have been given access rights
and they are restricted up to their functionalities, so that the data is maintained securely and
redundant data is prevented. As the Data is stored electronically, it is necessary to have a
Computer and Network connection to access the Application.

Future Enhancements
Every Edition of a book comes with new topics and modifications if any errors are present. In the
similar way, in near future, our application will overcome the flaws if occurred, and attains new
features offered online payment system verification of user connect through Nadra database to
overcome the crime and fraud situation in Pakistan cities. I turn this system further property and
others sales purchase systems. With this features we are able to make the compete with ubers
careem by giving user more the Flexible and easy Transportation. Following are the
Enhancements to the application.

Providing Good User few clicks Interface.

Providing access permissions to the Users

Try to Implement the GPS system in the Fleets.

Online payment systems

96
Chapter 12

References

97
 REFERENCES

Wikipedia

[1] Wikipedia is a free encyclopaedia, written collaboratively by the people who use it. It is a

special type of website designed to make collaboration easy, called a wiki.

http://en.wikipedia.org

Microsoft

[2] The Microsoft Developer Network (MSDN) is the portion of Microsoft responsible for

managing the firm's relationship with developers and testers, such as: software developers

standing on the various OS platforms or using the API languages of applications.

http://msdn.microsoft.com

W3Schools

[3] W3Schools is a web developers site, with tutorials and references on web development

languages such as HTML, CSS, JavaScript, PHP, SQL, W3.CSS, and Bootstrap, covering most

aspects of web programming.

https://www.w3schools.com

98
Tutorials Point[4] The tutorials point is an absolutely FREE website which has been created

to provide quality online education to the people who are enthusiastic to study different technical

and non-technical subjects in "Simply Easy Learning" way.http://www.tutorialspoint.com

Google

[6] The Google is a large corporative website. We can study anything and learn many things

from this website. We can search data free on Google.

http://www.google.com

THE END

99