Vous êtes sur la page 1sur 63

Table of Content

Sr.No Topic Page.No


1. 1. Introduction 3
1.1. Project Summary 4
1.2. Objective 4
1.3. Scope 4
1.4. Technology Used 5
1.5. Hardware-Software used 6
2. System Analysis 8
2.1. Study of current System 9
2.2. Problem and weakness of Current System 9
2.3. Requirement of New System 9
2.4. Feasibility Study 10
3. Project Management 11
3.1. Project Planning and Scheduling 12
3.1.1. Project Development Approach 12
3.1.2. Project Plan 13
3.1.3. Schedule Representation 14
3.1.4. Roles and Responsibilities 15
3.2. Risk Management 16
3.2.1. Risk Identification 16
3.2.2. Risk analysis 17
3.2.3. Risk planning 17
4. System Modeling 18
4.1. Dataflow diagrams 19
4.1.1. Context Level Diagram 20
4.1.2. Level - 1 DFD 21
4.1.3. Level 2 DFD 22
4.2. Use case diagrams 25
4.3. Activity Diagrams 28
4.4. Sequence diagrams 32
4.5. State Transition Diagrams 35
4.6. Class Diagrams 36
4.7. System Architecture 37
5. Data modeling and design 39
5.1. Data dictionary 40
5.2. Database Relationship Diagram 48

5.3. Input/output and Interface Design 48


5.3.1. Samples of Forms, Reports and Interface 49
5.3.2. Access Control and Security
6. Limitation and Future Enhancement 50
7. Conclusion 52

1
8. Bibliography and References 55

Introduction

1.1. Project Summary


1.2. Objective

2
1.3. Scope
1.4. Technology Used
1.5. Hardware-Software used

1.1. Project Summary

This is a personal website.This Project is designed so as to be used by Car booking


business specializing in renting cars to customers. it is an Online System through which
customers can view available cars, register, view Profile and book car. The advancement in
information technology and internet technology has greatly enhanced various business
process and communication between services Provider.This website use for all educated
candidates.

1.2. Objective

To Prodece a web-based system that allow customer to register and book car online
and for the admin to effectively manage their car booking business.
customers task whenever they need to rent a car.
The tea2taxi Provide complete functionality of listing And booking car.
In this system ,tourism and travelling facilities also Provide.

1.3. Scope

3
This Project traverses a lot of areas ranging from business concept to computing field,
and required to perform several researches to achieve the project objectives.
Tea2taxi System solution is fully functional and flexible.
It is very easy to used
It save a lot of time ,money and labour.
Web-platform means that the system will be available for 24/7 except when there is a
temporary server issue which is expected to be minimal.
It increases the efficiency of the management at quality service to the customer.

1.4 . Technology Used


PHP
PHP stands for PHP: Hypertext Preprocessor
PHP is a server-side scripting language, like ASP
PHP scripts are executed on the server
PHP supports many databases (MySQL, Informix, Oracle, Sybase,
Solid, PostgreSQL, Generic ODBC, etc.)
PHP is an open source software
PHP is free to download and use

Web server(Apache web Server)


My Sql
MySQL is a relational database management system (RDBMS),
and ships with no GU tools to administer MySQL databases or
manage data contained within the databases.
Users may use the included command line tools, or use MySQL
"front-ends", desktop software and web applications that create and
manage MySQL databases, build database structures, back up data,
inspect status, and work with data records.
The official set of MySQL front-end tools, MySQL Workbench is
actively developed by Oracle, and is freely available for use.
Facts
MySQL is the largest growing relational database out on the
market.
MySQL mainly runs on UNIX-based environments.
MySQL acts as a DBMS.
MySQL is one of the most used open source databases in the
world.
Can use Enhanced MySQL.
Capacity to handle 50,000,000+ records.
Very fast command execution, perhaps the fastest to be found
on the market.
Easy and efficient user privilege system.

4
Benefits of MYSQL
Able to handle large databases that can be accessed over the
Web.
Flexible and secure password system to protect your data -
powerful security system.
Fast, reliable, easy to use, and affordable.
Relational database management system.
Stability
On-line help facility
MySQL meets the ANSI SQL92 regulations
1.5 . Hardware-Software used
Hardware Requirement

Server Side:

RAM 4 GB RAM Recommended


Processer Dual Core or More 2.0 GHZ Processor
HardDisk At least 10 GB Free Disk Space for Req
Software and Data Storage

Client Side:

RAM 2 GB RAM Recommended


Processer Laptop/PC/Mobile with Any Processor th
execute browser
Harddisk At least 10 GB Free Disk Space for Requ
Software and data Storage

Software Requirement

Server Side:-

Linux/Windows Server OS
LAMP/WAMP/XAMPP Server
(Apache / MySQL)

Client Side

Any Browser

5
System Analysis
2.1.Study of current System

2.2. Problem and weakness of Current System

2.3. Requirement of New System

2.4. Feasibility Study

6
2.1. Study of current System

People to get around even when they do not have access to their owen personal
vehical or dont own a vehical at all.
In Car booking Current System
Can be provided manually All work in Paper work.
The All User Has to Go to office where get the All information About the Car, Car
rent and Booking the Car.
In the Current System user can not Provided feedback or complain for the Admin.

2.2. Problem and weakness of Current System

Time consuming:-

The All User Has to Go to office where get the All information About the Car, Car rent
and Booking the Car.

West Money, labour:-

The all user need a car then user go to particular place for booking a car whenever
user go to booking a car then user used Private vehicle , taxi and Auto so in this case user
waste a money and labour

2.3. Requirement of New System

In tea2taxi System can be totally computerized System .


This system provides tourism, Event and travelling facilities
It is an online System through Which Customer can view available cars, View Profile
And Book the Car.
New System can be Provided User different features like saving time, Easily Get all
information about the car and Driver detail.
User can Provided easily Feedback and complain for Admin.
Admin Provided by complain for Solution User can easily Get solution for Admin.

2.4. Feasibility Study

At this stage, the analyst estimates the urgency of the project and estimates the development

7
cost.In Feasibility analysis, we have to study the following:-

Technical Feasibility:

Technical Feasibility is concerned with the availability of Hardware and software required for
the development of the system, to see compatibility.

Maturity of the technology proposed to be used and to see the availability of the required
technical manpower to develop the system.

After the study we came to conclusion that we further with the tools and development
environment chosen by use. this was important in our case as we were working on two
various phases of the department that will need to be integrated in future to make extended
system.

Operation feasibility:

Operation feasibility is all about problem that may arise during operations.

There are two aspect related with this issue:

what is the Probability that the solution development m,ay not be put to use
or may not work?
What is the inclination of the management and end users towards the
solution? through, there is very least possibility of management being avarse
to the solution, there is very least possibility of management being averse to
the solution, there is a significant probability that the end user may not be
interested in using the solution due to lack of training, inside etc.
Economic Feasibility:

It is the measure profit cost effectiveness of the project. the economic feasibility is nothing
but judging the possible benefit of solving the problem is worthwhile of not. art the
feasibility study level, it is impossible to estimate the cost because members requirement
and alternative solution have not been identified, the analyst weight the cost and benefits of
all solution have been identified, the analyst weight the cost and benefit of all solution, this is
called "cost benefit analysis.

8
Project Management
3.1. Project Planning and Scheduling

3.1.2. Project Plan

3.1.3.Schedule Representation

3.1.4. Roles and Responsibilities

3.2.Risk Management

3.2.1. Risk Identification

3.2.2. Risk analysis

3.2.3. Risk planning

3.1. Project Planning and Scheduling

When planning a project, a series of milestone should be established. The milestone is in

9
end-points of the software process activity. All projects have important event called
milestones that marks significant point in their development as they represent difficult
handles to passed or critical task that must be completed on time.
At each milestone, there is formal output, as a report. Milestone report needs not to be large
Documents. They may be short report of achievements in a project activity.

3.1.1. Project Development Approach

Software Engineering paradigm: Spiral Model


The spiral model is a risk-driven process model generator for software projects.
Based on the unique risk patterns of a given project, the spiral model guides a team to
adopt elements of one or more process models, such as incremental, waterfall, or
evolutionary prototyping.

10
`

3.1.2. Project Plan

The project milestone can be identified during the development of the project. This
milestones and milestone deliverables are shown bellows as weekly progress. Scheduling of a
software project does not differ greatly from scheduling of any multi task engineering effort.

Software project place can be viewed as the following:-


1.Within the Organaization:

11
How the project is to be implemented?
What are various constraints(time,cost,staff)?What is market strategy?
2.with respect to the Customer:-
Customer feedback is also taken and further modification and easily give complain to admin.
the admin can be also give solution of the complain.
For a successful software project ,the following step can be followed.
Select a Project
Identifying Projects aims and objective
Understanding requirements and specification
Methods of analysis, design and implementation
Testing techniques
Budget allocation
Project estimation
Cost
Time
Size of code
Duration
Resource allocation
Hardware
Software
Previous relevant project information
Risk Management
Risk avoidance
Risk Detection

3.1.3. Schedule Representation

An elementary Gantt chart or Timeline chart for the development Plan is given below. The
Plan explain the tasks verus the time(in week).they will take to complete.

Gantt chart:
GANTT CHART
Jul- Aug- Sep Oct- Nov-
15 15 -15 15 15

Sr Task name Durati 10/7 4/8 1/9 29/9

12
No on to to to to
25/7 24/8 15/9 7/10
1 Informati- 15
on days
Gathering
2 Informatio 20
n Analysis days

3 Project 15
planning Day
4 Designing 8Day
5 Coding
6 Implement
ation
7 Testing

3.1.4. Roles and Responsibilities

This is web based application, so it will be available for General Users and Admin. Our
system will be used by three main types of users.

Admin
Traveller
Provider

Admin module :-

Manage Different services(Like Driver,Car, Advertisers)


manage cities &location
manage car
manage rate/fare(Per kilometer for various car)
Manage Advertisement Rates
Manage Provider Rates
Get Request from Traveller
Assign Journey to Provider
Manage Payment

13
view feedback
Complain & Solution

Provider Module:-

Register
Send Request for New Car
Request for Service Like Only Driver/Only Car/Taxi etc.
Get Confirmation
Get Journey
Change Journey Status

Traveller Module:-

Register
Search Cars
Request for Booking
Get Confirmation
Get Car/Driver Details
Calculate Fare
Payment online or offline
Feedback&Complain
Get Solution

3.2. Risk Management

Risk management is the identification, assessment, and prioritization of risks followed by


coordinated and economical application of resources to minimize, monitor, and control the
probability and/or impact of unfortunate events or to maximize the realization of
opportunities. Risk managements objective is to assure uncertainty does not deflect the
Lndeavour from the business goals.

3.2.1. Risk Identification

14
Managing risk is to identify potential risks. Risks are about events that, when triggered, cause
problems or benefits. The identification methods are formed by templates or the development
of templates for identifying source, problem or event.

List of risk identification:-

unavailability of Internet
literacy level of driver
large amount of order cancelation.

3.2.2. Risk analysis

risk identification can start with the source of our problems and those of our competitors
(benefit), or with the problem itself.

Source analysis :-

Risk sources may be internal or external to the system that is the target of risk
management (use mitigation instead of management since by its own definition risk
deals with factors of decision-making that cannot be managed).

Examples of risk sources are: stakeholders of a project

Problem analysis :-

Risks are related to identified threats. For example: the threat of losing money, the
threat of abuse of confidential information or the threat of human errors, accidents and
casualties. The threats may exist with various entities, most important with
shareholders, customers and legislative bodies such as the government.

3.2. 3. Risk planning

A risk management plan is a document that a project manager prepares to foresee risks,
estimate impacts, and define responses to issues. It also contains a risk assessment matrix.

15
risk management plans include a risk strategy. Broadly, there are four potential strategies,
with numerous variations. Projects may choose to:-

Different Plan step:-


limited this service to urben area only
to used more graphics for easy operation.
To make cancelation process is more harder.

System Modeling

4.1 Dataflow diagrams

4.1.2 Level - 1 DFD

4.1.3 Level 2 DFD

4.2 Use case diagrams

4.3 Activity Diagrams

4.4 Sequence diagrams

4.5 State Transition Diagrams

16
4.6 Class Diagrams

4.7 System Architecture

4.1. Dataflow diagrams.

The system model is termed as dataflow diagram (DFD). A full disruption of a

system actually consist set of data flow diagrams.

Dataflow diagram is a graphical or pictorial tool used to describe the movement

of data through system. It consists of flows, processes, sources, destinations and

stores all described through the use of easily understood symbols.

An entire system can be described from the viewpoint of the data; it processes

with only four symbols. The symbols, which mention bellow.

Symbols:-

Data Flow

Process

Entity

17
Data Store

4.1.1. Context Level Diagram

18
4.1.2. Level - 1 DFD

19
4.1.3. Level 2 DFD

20
2nd level Authentication

2nd Level Request Management

21
2nd Level Search Management

22
4.2. Use case diagrams

Use case diagrams show business use cases, actors, and the relationships between them.
The relationships between actors and business use cases state that an actor can use a
certain functionality of the business system.
Symbols:-

23
Actor

Relation Flow

Usecase

Admin:-

24
25
Provider & Traveller

26
4.3. Activity Diagrams [Swimlane]

Activity diagrams are as simple to make as an ordinary flowchart.Each symbol has a meaning
and context where its use is appropriate.
Symbol:-

Symbol Describe
The start symbol represents the beginning of
a process or workflow in an activity diagram.
It can be used by itself or with a note symbol
that explains the starting point.
The activity symbol is the main component
of an activity diagram. These shapes indicate
the activities that make up a modeled
process.
The connector symbol is represented by
arrowed lines that show the directional flow,
or control flow, of the activity. An incoming
arrow
starts a step of an activity; once the step is
completed, the flow continues with the
outgoing arrow.
The join symbol, or synchronization bar, is
a thick vertical or horizontal line. It combines
two concurrent activities and re-introduces
them
to a flow where only one activity occurs at a
time.

A fork is symbolized with multiple arrowed


lines from a join. It splits a single activity
flow into two concurrent activities.

The decision symbol is a diamond shape; it


represents the branching or merging of
various flows with the symbol acting as a
frame or
container.
The end symbol represents the completion
of a process or workflow.

27
Activity for Admin:-

28
Provider

29
Traveller

30
4.4. Sequence diagrams
Sequence for Admin:-

31
Sequence diagram for Provider:-

32
Sequence diagram for Traveller:-

33
4.5. State Transition Diagrams

System States
Events and Actions

1:login
Whenever user enter the credential then it check for authentication or the valid userid
and password if data is entered correctly then open the home page of particular user.

2:Logout
After successfully work is finish all the session and cookies is destroyed and again
redirect to login page.

3:when we once entered all data it allows as to perform specific operation as per
requirement of user.

34
4.6. Class Diagrams

35
`

36
4.7. System Architecture

Symbols:-
Indicates Terminator.

4. Indicates Process.

Indicates Decision.

Indicates Data.

Indicates Flow.

37
38
Data modeling and designs
5.1 Data dictionary

5.2 Database Relationship Diagram

5.3. Input/output and Interface Design

5.3.1. Samples of Forms, Reports and Interface

5.3.2. Access Control and Security

39
5.1. Data dictionary

What is a Data Dictionary ?

A data dictionary is a catalog-a repository-of the elements in a system. As the name suggests,
these elements are structured around data in a way to meet the user and the organization
requirements. A data dictionary is a list of elements that composes all the data flow process
through a system. It stores details and description of the data flows, data stores and processes.

If analyst wants to know by what other names is a table or a data item referenced in a system,
or where it is being used the answers are properly developed in data dictionary.

The dictionary is developed during data flow analysis and assists the analysts involved in
determining system requirements. However its content is used during system design as well.

Why is a Data Dictionary Important?


Analyst use data dictionary for five important reasons.
To manage the details in large systems.
To communicate a common meaning for all system elements.
To facilitate analysis in order to determine where the changes are
To be made.
To locate errors and omissions in the system.

Tables

40
Log_in

No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION


1 Login_id Int 4 Primary key It is store Users id
2 Email_id Varchar 30 Not null It is store Users E-
mail id
3 Password Varchar 15 Not null It is store Users
Password
4 User_type Varchar 10 Not null It is store Users
type

Provider
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Provider_id Int 4 Primary key It is store Providers
id
2 Login_id Int 4 F.K(Log_in) It is references to
Login_id from
Login
3 First_name Varchar 15 Not null It is store Providers
first name
4 Last_name Varchar 15 Not null It is store Providers
last name
5 Area_id Int 4 F.K(Area) It is references to
area_id from area
6 Address Varchar 40 Not null It is store Providers
Address
7 Mobile_no Varchar 15 Not null It is store Providers
mobile number
8 RegisterDate Datetime Not null It is store Providers
Registration Date
9 ProviderPhoto Varchar 50 Not null It is store Providers
photo
10 Status Varchar 50 Not null It is store Providers
Status

41
Traveller
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Traveller_id Int 4 Primary key It is store
Travellers id
2 Login_id Int 4 F.K(Log_in) It is references to
Login_id from
Login
3 First_name Varchar 15 Not null It is store
Travellers first
name
4 Last_name Varchar 15 Not null It is store
Travellers last
name
5 Gender Varchar 10 Not null It is store
Travellers Gender
6 Birth_Date Datetime Not null It is store
Travellers
BirthDate
7 Address Varchar 40 Not null It is store
Travellers Address
8 Area_id Int 4 F.K(Area) It is references to
area_id from area
9 RegisterDate Datetime Not null It is store
Travellers
Registration Date

City
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 City_id Int 4 Primary key It is store City id
2 City_name Varchar 15 Not null It is store City name

Area
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Area_id Int 4 Primary key It is store Area id
2 Area_name Varchar 20 Not null It is store Area
name
3 City_id Int 4 F.K(City) It is references to
city_id from city

42
Cars
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Car_id Int 4 Primary key It is store Car id
2 RTOReg_No Varchar 15 Not null It is store Car s
RTOReg_No
3 Provider_id Int 4 F.K(Provider) It is references to
Provider_id from
Provider
4 CarType_id Int 4 F.K(Provider) It is references to
CarType _id from
CarType
5 Company_Name Varchar 15 Not null It is store cars
Company Name
6 RTORegister_Date DateTime Not null It is store Cars
RTO
RegistrationDate
7 DriverName Varchar 15 Not null It is store cars
Driver Name
8 DriverLicence_No Varchar 20 Not null It is store cars
Driver Licence
Number
9 DriverPhoto Varchar 40 Not null It is store cars
Driver Photo
10 AvailableFromTime DateTime Not null It is store cars
Available From
Time
11 AvailableToTime DateTime Not null It is store cars
Available To Time
12 Car_Image Varchar 40 Not null It is store
Car_Image
13 Status Varchar 50 Not null It is store Status

Confirmation
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Confirm_id Int 4 Primary key It is store Confirm_id
2 Request_id Int 4 F.K(Request) It is references to
Request_id from
Request
3 Car_id Int 4 F.K(Car) It is references to
Car_id from Car
4 Cofirm_Date Date/Time Date/Time It is store
sCofirm_Date

43
CarTypes
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 CarType_id Int 4 Primary key It is store CarType
id
2 CarType Varchar 20 Not null It is store Car Type

Feedback
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Feedback_id Int 4 Primary key It is store Users
feedback id
2 Title Varchar 20 Not null It is store feedback
Title
3 Content Varchar 20 Not null It is store feedback
Content
4 FullName Varchar 30 Not null It is store users
FullName
5 ContactNo Varchar 15 Not null It is store Users
ContactNo
6 Email Varchar 20 Not null It is store Uses
Email
7 Feedback_Date Date/time Not null It is store Feedback
date

Complain
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Complain_id Int 4 Primary key It is store Users
Complain_ id
2 Traveller_id Int 4 F.K(Traveller) It is references to
Traveller_id from
Traveller
3 Car_id Int 4 F.K(Car) It is references to
Car_id from Car
4 Title Varchar 25 Not null It is store Users
Complain title
5 Details Varchar 50 Not null It is store Users
Complain Details
6 ComplainDate Date/time Not null It is store Users
Complain Date
7 Status Varchar 40 Not null It is store Users
Complain Status

44
FareDetails
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Fare_id Int 4 Primary key It is store Fare_ID
2 CarType_id Int 4 F.K(CartypeS) It is references to
Cartype_id from
Cartype
3 MinKM Int 15 Not null It is store MinKM
4 MaxKM Int 15 Not null It is store MaxKM
5 Amount Decimal 20 Not null It is store Amount

Advertisers
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Advertiser_id Int 4 Primary key It is store
Advertiser_ID
2 FullName Varchar 20 Not null It is store Advertiser
full name
3 MobileNo Varchar 10 Not null It is store Advertiser
MobileNo
4 Address Varchar 30 Not null It is store Advertiser
Address
5 Email Varchar 20 Not null It is store Advertiser
Email

Advertisements
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Advertisement_id Int 4 Primary key It is store
Advertisement_ID
2 Advertiser_id Int 4 F.K(Advertiser) It is references to
Advertiser_ID from
Advertiser
3 Start_Date Date/time Not null It is store
Advertisements
Start_Date

4 End_Date Date/time Not null It is store


Advertisements
Start_Date

45
AdvOnCar
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 AdOnCar_id Int 4 Primary key It is store
AdOnCar_ID
2 Advertisement_i Int 4 F.K(Advertisement) It is references to
d Advertisement_ID
from
Advertisement
3 Car_id Int 4 It is references to
Car_id from car
4 FromDate Date/time It is store AdOnCar
FromDate
5 ToDate Date/time It is store AdOnCar
ToDate

ProviderRates
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Prate_id Int 4 Primary key It is store Prate_id
2 CarType_id Int 4 F.K(CarType) It is references to
CarType_id from
carType
3 FromKM Int 4 Not null It is store Prate
FromKM
4 ToKM Int 4 Not null It is store Prate
ToKM
5 Rate Decimal 15 Not null It is store Prate

Requests
No FIELD DATA TYPE SIZE CONSTRAIN DISCRIPTION
1 Request_id Int 4 Primary key It is store Users
Request_id
2 Traveller_id Int 4 F.K(Traveller) It is references to
Traveller_id from
Traveller

46
3 CarType_id Int 4 F.K(CarType) It is references to
CarType_id from
carType
4 FromArea_id Int 4 It is store Users
5 ToArea_id Int 4
6 Request_Date Date/Time Not null It is store Users
Request_Date
7 TravelDateTime Date/Time Not null It is store Users
TravelDateTime
8 TotalPassangers Int 5 Not null It is store Users
totalpassanger
9 Address1 Varchar 20 Not null It is store Users
Address1
10 Address2 Varchar 20 Not null It is store Users
Address2
11 Status Varchar 20 Not null It is store Request
status

Payments
No FIELD DATATYPE SIZE CONSTRAIN DISCRIPTION
1 Payment_id Int 4 Primary key It is store
Payment_ID
2 Confirm_id Int 4 F.K(Confirmation) It is references to
Confirm_id from
Confirmation
3 TotalKM Int 4 Not null It is store TotalKM
4 TotalCharges Decimal 8 Not null It is store
TotalCharges
5 Tax Decimal 8 Not null It is store Tax
6 ExtraCharges Decimal 8 Not null It is store
ExtraCharges
7 ExtraChargeDetail Varchar 20 Not null It is store
s ExtraChargeDetails
6 Total Decimal 8 Not null It is store Payment
Total

Complains
No FIELD DATATYPE SIZE CONSTRAI DISCRIPTION
N
1 Complain_id Int 4 Primary key It is store
Complain_id
2 Traveller_id Int 4 F.K(Traveller) It is references to

47
Traveller_id from
Confirmation
3 Car_id Int 4 F.K(Car) It is It is references
to Car_id from Car
4 Title Varchar 20 Not null It is store Complain
Title
5 Details Varchar 40 Not null It is store Complain
Detail
6 Complain_Date Date/Time Not null It is store
Complain_Date
7 Status Varchar 20 Not null It is store Complain
Status

5.2. Database Relationship Diagram

An entity-relationship diagram is a data modeling technique that creates a


graphical representation of the entities, and the relationships between entities,
within an information system.

Features:-
Entity which specify distinct real-world items in an application.
Relationships which connect entities & represent meaningful dependencies
between them.
Attributes which specify properties of entities and relationships

Symbols:-
Entity

Relationship

Attribute

Entity flow

48
49
5.3. Input/output and Interface Design

5.3.1. Samples of Forms, Reports and Interface

Home Page

Admin HomePage:-

50
Cars

Service

51
About

Provider Registration

52
Traveller Registration

Feedback

53
Login

Traveller HomePage:-

54
Taxi Booking

Driver Booking

55
Provider Request:-

56
5.3.2. Access Control and Security

Security Requirement:

The Information should be Secure; there should not be any kind of malfunctioning.
System Information will not be changed by any person rather than the management. That is
as follows:

Administrator has the highest authority to edit/delete/create database.


Critical information like passwords should be transferred in encrypted form.
Passwords should be stored in encrypted form.
Password will not be mailed to the user in case user forgets password, instead either
temporary password or a password reset link will be sent.
The Data is secure because Authentication is always required for downloading and
uploading the data.

57
Limitation and Future Enhancement

58
Limitation:-

No driver side Android Application


Driver and Admin communication Offline.
The fixed location start and fixed location return of the rental car

Future Enhancement:-

Add new car is represent the car list.


The User payment for the current receipt of the payment.
Add the current project for booking easy.
Car selection
Service selection
Advertising

59
Conclusion

Conclusion:-

60
Tea2taxi system will improve the management of rentals and bookings of cars.This system
developed in order to overcome the problems faced using the manual ways. This System Can
be Totally Computerized System. System can Provide different Features like Fast & Safe,
Best Price , Package Delivery Safe and reliable way to travel at offered able prices.

61
Bibliography and References

Bibliography and References

www.google.com

62
www.w3school.com

www.w3campus.com

Beginning PHP, MySQL and Apache By Robin Nixon

www.toves.org

https://patents.google.com

63