Final Project Report

On
Quick Book(Taxi Booking)

Prepared By
Rao Atif Mahmood (BSSE-E2-21-25)

Roll no 85

Supervised By
Mr. Waqar
Computer Sciences Department
UOS
Jan, 2018

University of Sahiwal, Sahiwal.

Project Report
 ACKNOWLEDGEMENT

Praise to Allah Almighty, Lord of the worlds, the Merciful and the Beneficent, who gave us
strength, thoughts and co-operative people to enabled us to accomplish this goal and fulfill
the required functionalities.
This was all not possible without the guidance, continuous appreciation and moral support
by Mr. Waqar Ahmad. He was always there whenever we need his help and ideas. We are
really thankful to him who made our concepts clearer.
At last, we would like to acknowledge all of the assistance and contributions of University of
Sahiwal for supporting us with all that is needed starting from the books, and ending with
the full care that it is providing us with, to help us to be professionals in the field of
Information Technology.
DECLARATION

We hereby declare that we have developed this application and accompanied report entirely on the basis of
our personal efforts. Not any of the portion of the application work presented has been submitted of any
application for any other qualification or degree of this or any other university or institute of learning.

CERTIFICATE OF APPROVAL

It is to certify that the final year project of BSSE “Quick Book (Cab Booking Flutter App)” was
developed by Student Name, Team Me

mber2, Team Member3, Team Member4 under the supervision of “Mr. Waqar
Ahmad” and that in his opinion, it is in scope, fully adequacy and quality of the degree of Master of Science
in Computer Sciences.

Supervisor External Examiner

Mr. Waqar Ahmad

Lecturer
Department of Computer Science
University of Sahiwal
Head of Department

Dr. Shafiq Hussain

Department of Computer Science
 ABSTRACT

Quick Book is a cutting-edge ride-hailing mobile application developed using Flutter, offering a user-
friendly and efficient platform for on-demand transportation. Designed with a focus on swiftness and
seamlessness, Quick Book connects passengers with a wide network of verified drivers in real-time.

Key features include:

 Instant Booking: Effortless booking with real-time tracking of driver location and estimated arrival
time.
 Diverse Ride Options: Choose from a variety of ride options to suit your needs and budget,
including economy, premium, and bike rides.

 TABLE OF CONTENTS
 1 INTRODUCTION 13
 1.1 Introduction & history 14
 1.2 Clear statement of the problem 14
 1.3 Introduction to the software tools 15
 1.4 Objectives 15
 1.5 Proposed solution 15
 1.6 Motivation 16
 1.7 Scope of proposed solution 16
 1.8 Relevance to courses 16
 1.8.1 Introduction to Computer Programming (CSC103) 16
 1.8.2 Object Oriented Programming (CSC241) 16
 1.8.3 Software Engineering (CSC291 & CSC392) 16
 1.8.4 Database Systems (CSC271) 17
 1.8.5 Computer Communication and Networking (CSC339) 17
 1.9 Tools & techniques 17
 1.9.1 Hardware details 17
 1.9.2 Software details 17
 2 STATE OF THE ART 18
 2.1 What is RTOMS? 19
 2.2 Implementation 19
 2.3 Existing applications 19
 2.4 Drawbacks of existing applications 19
  2.5 The Necessity 20
 2.5.1 Accurate records 20
 2.5.2 Better communication20
 2.7 Proposed application architecture 20
 2.6.1 Chosen application architecture 20
 3 METHODOLOGY & WORKPLAN 21
 3.1 Existing methodology 22
 3.1.1 Incremental model 23
 3.2 Adopted methodology 23
 3.3 Roles & responsibilities 24
 4 SYSTEM ANALYSIS & DESIGN 25
 4.1 Requirements gathering techniques 26
 4.2 Requirement analysis 26
 4.2.1 Functional requirements 27
 4.2.2 Non-functional requirements 28
 4.2.3 Application quality attribute 28
 4.2.3.1 Availability 28
 4.2.3.2 Maintainability 29
 4.2.3.3 Consistency 29
 4.2.3.4 Portability 29
 4.2.4 Database requirements 29
 4.3 Use cases 29
 4.3.1 UC1: Login 30
 4.3.2 UC2: Register member 31
 4.3.3 UC3: Administrator 32
 4.3.4 UC4: Change password 33
 4.3.5 UC5: Waiter 35
 4.3.6 UC6: Log out 36
 4.3.7 UC7: Customer functionalities 37
 4.3.8 UC8: Manager functionalities38
 4.4 Planning & scheduling 39
 4.4.1 Gantt chart 39
 4.5 Sequence diagram 41
 4.5.1 SQ1: User 42
 4.6 Data flow diagram 43
 4.7 Entity relationship diagram 44
  5 SYSTEM IMPLEMENTATION 45
 5.1 Introduction 46
 5.2 Screenshots 47
 6 SYSTEM TESTING 57
 6.1 Introduction 58
 6.2 Testing plan 58
 6.2.1 Unit testing 59
 6.2.2 System testing 59
 6.2.3 Integration testing 59
 6.2.4 User acceptance testing 59
 6.3 Test cases 60
 6.4 Testing results 61
 7 CONCLUSION & FUTURE WORK 62
 7.1 Conclusion 63
 7.2 Future work 63
 REFERENCES 64

CHAPTER # 1
INTRODUCTION
1. INTRODUCTION
In this chapter, we will introduce this application, software tools, problem statement, objectives, scope of
this application, proposed application, motivation of this proposed solution, relevance to courses and tools
& techniques which are used to implement this application.

1. Introduction & history

2. The transportation sector is undergoing a significant transformation with the rise of on-demand services.
3. Traditional taxi services are being challenged by innovative mobile applications that offer greater
convenience, efficiency, and affordability.
4. "Quick Book" aims to capitalize on this trend by providing a user-friendly and reliable platform for both
passengers and drivers.

History:

5. Briefly discuss the evolution of ride-hailing services, mentioning key players like Uber and Lyft.
6. Highlight the growing demand for such services in urban areas and the increasing reliance on mobile
technology for everyday tasks.
1. Clear statement of the problem
Inefficiencies in Traditional Taxi Services:

7. Difficulty in finding available taxis, especially during peak hours.

8. Unpredictable pricing and potential for overcharging.
9. Safety concerns for passengers, including lack of driver background checks and inadequate tracking mechanisms.
10. Limited payment options, often restricted to cash.
11. Lack of transparency and accountability for drivers.

1. Introduction to the software tools

 Android Studio is the official Integrated Development Environment (IDE) for Android app development,
based on Flutter

Flutter (Dart)

 Android Studio(component design, prototype design)

 User Interface
 Database Connectivity(cloud based Database)

2. Objectives
Develop a user-friendly and efficient mobile application for on-demand cab booking.
Provide a reliable and safe platform for both passengers and drivers.
Offer competitive pricing and a variety of ride options to cater to diverse user needs.
Integrate secure payment gateways for convenient and hassle-free transactions.
Ensure the application is scalable and adaptable to future growth and new features.

3. Proposed solution
"Quick Book" will be a mobile application built using Flutter, offering the following key features:

12. Real-time ride requests and driver tracking.

13. Multiple ride options (economy, premium, etc.)
14. Secure payment gateways (credit/debit cards, mobile wallets).
15. Driver verification and background checks.
16. In-app communication between passengers and drivers.
17. Emergency assistance features (panic button, share ride details).
18. User-friendly interface with intuitive navigation.
1. Motivation
 Motivating your staff to provide outstanding services.
 Encourage customers to Share their Experiences During their Stay
 Make Everybody Happy!

1. Scope of proposed solution

Focus on urban areas.
Initial version will include core features like ride booking, driver tracking, and basic payment
options.
Future iterations may include features like ride-sharing, corporate solutions, and integration with
public transportation.

2. Relevance to courses
1. Introduction to Computer Programming (CSC103)
We have studied the basics of programming in this course. Using the concepts of C++, we implemented this
project.

2. Object Oriented Programming (CSC241)

Using the concepts of OOP approach in programming pattern and coding design we implemented our
project.

3. Software Engineering (CSC291 & CSC392)

This course helped us to evaluate our development methodologies which are used in our project.

4. Database Systems (CSC271)

In this project, we develop relational database system for efficient working of the project by using the
concepts of database systems.

5. Computer Communication and Networking (CSC339)

Communication to different ends will be done using the knowledge learned from this course.

9. Tools & techniques

Restaurant Table Order Management System android application consists of software tool.

1. Hardware details
 High Speed Internet Connection

2. Software detail
 Adobe Photoshop (background, design, logo, button and other graphics)
 Android Studio (component design, prototype design)
 User Interface
  Database Connectivity (cloud based Database)

3.

CHAPTER # 2
STATE OF THE ART
2. STATE OF THE ART
In this chapter, we will discuss Cab Booking? How we’ll implement this application? Why we need it, if
other applications exist? What is the pros and cons of existing applications and proposed application?

1. What is Quick Book?

Quick Book is a cutting-edge ride-hailing mobile application developed using Flutter, offering a user-
friendly and efficient platform for on-demand transportation. Designed with a focus on swiftness and
seamlessness, Quick Book connects passengers with a wide network of verified drivers in real-time.

Key features include:

3. Instant Booking: Effortless booking with real-time tracking of driver location and estimated arrival
time.
4. Diverse Ride Options: Choose from a variety of ride options to suit your needs and budget,
including economy, premium, and bike rides.

1. Implementation
Implementation is the stage of the project when the theoretical design is turned out into a working system.
Thus it can be considered to be the most critical stage in achieving a successful new system and in giving
the user, confidence that the new system will work and be effective.
The implementation stage involves careful planning, investigation of the existing system and it’s constraints
on implementation, designing of methods to achieve changeover and evaluation of changeover methods.

2. Existing applications
 3. CHAPTER # 3
4. METHODOLOGY & WORKPLAN
2. METHODOLOGY & WORKPLAN
In this chapter, we will discuss that what are the existing methodologies and which one we have chosen for
implementation of this project in an effective way, also we will discuss advantages of adopted methodology.

What is methodology and why we need it?

Whenever a small or large project have started to develop, first thing all of programmers required is
methodology. Methodology is a way of developing a project, in which all of the programmers gather the
user’s requirements, design the project, implement it, and after all this testing and maintenance of the
project, in a satisfaction of user and according to the project requirements.

1. Existing methodology
There are several existing methodologies that can be used to develop this application using software
development processes.

1. Incremental model
To overcome the incremental model is used. In incremental model, the product is developed in increments
and partitioned into smaller pieces. These smaller pieces, then built and delivered to client in increments.
Quick response from clients. Each module is smaller than compare to whole module.
 Figure1: Incremental Model

2. Adopted methodology
Incremental model is used to develop this project, in which we divided our work in multiple modules. All
these modules are further divided into more easily managed modules which made up the actual
implementation of the requirements.

Reason behind using this model is:

 It is easy to test and debug the product during iterations.
 Software released in increments over time is more likely to satisfy changing user requirements than
if it were planned as a single overall release at the end of the same period.

Taxi service UML Model

Introduction:

The online taxi service allows users to book their taxi online . The platform offers administration
interface where the taxi company can manage the content and access all bookings and
customer information.

The taxi service should provide the following functionalities to the user:

 Provide the functionality to make your own bookings.

 Give your customers the facility to make payments and deposits online.
 Generate invoices.
 Update your web site without the need to get a web designer involved.
 Provide the customer with taxi availability.
 Track your customers.
 Engage your customers.

The basic flow of the taxi service can be followed by the use case diagram.

 User books the taxi by providing the details of source and destination.
 Booking clerk checks the database.
 If successful the user books the cab.
 Use Case Diagram

TAXI BOOKING SYSTEM

SOURCE/DESTINATION

DATE/TIME

TYPE OF TAXI

FARE/KM &
TOTAL FARE

PAYMENT
OPTION

ADMINISTRATOR USER

User Details

REPORT
 Class diagram:

Cab
Generate Report
Cab_no
Fare
Source :
Destination 1
Deptr_time
Cab Terminal Arri_time Transport Dept
Class_type
Cab_no Service prov_name
Terminal_no Get_cab_detail(); Service_city
Deptr_time Show_cabdetail() Service_state
Add_cab(); Service_country
Show 1..*
Delete_cab();
Driver_detail(); Get_service_detail();
Show_service_detail(

Login

1 Ticket
2
Customer cancelled

Cust_name Login
Cust_age
1 Cust_gender User_id
Cust_phn _no Psswd
Cust_id
Bill Cab_no Sign_in();
Grp_discount
Bill_id
Bill_price
Get_c_detail();
Show_bill(); Show_c_detail();
Generate_bill(); Add_cust();
Delete_cust();
..*
1
Generate report
1 1 1 1
Reservation
PrintTkt Report
Cab_no Cancellation
Cust_name Genrate_Report();
Date_ofjourney Print_Ticket(); Cab_no
Fare Date_of_cancel
Get_details(); Cancel_charge
Show_detail();
Show_details();
Show_ticket();
Cnfrm_cancel();
Refund_charge();
Sequence diagram: The sequence diagrams below shows the interaction between the different
processes. It shows the object interactions in time sequence.

Maintains Taxi Information

Administrator Taxi Menu Taxi Driver Database

Display Menu

Enter Taxi no

Entered

Enter Src & Dest

Entered

Enter Dept &

Arrival Time
Entered Get Details
Submit Details

Verify Details
Add/Del/ Modify
Taxi
Error or
Success
Message
Add/Del/ Modify

Update Cab Details

Sequence diagram:

Reserving the Taxi

Reservation
User Menu Database

Display Menu

Enter Details Submit Details

Entered
Verify Data
Success/Error Msg Dsp
Reserve Taxi

Do Payment
Make Payment Update Reservation
info
Display Taxi & Rsv
Sequence diagram:

Cancellation
State Diagram: The state diagram below describes the different operations of the uml model.

Check for
If available Taxi Dept
Reservation
Send
Check Request
minimum
level

If unavailable
Reserve Taxi

Cancel
Maintain
database

Book Taxi

Do Payments
Activity Diagram: The activity diagram below shows the stepwise graphical representation with support
for choice, iteration and concurrency.
Collaboration Diagram:

The collaboration diagram provides an overall view of the collaborating objects within the real time
environment of the system.

Conclusion:

Hence the above model can be used to successfully develop a software for online taxi service.