"Share The Ride": Project Report O

Project Report On
“SHARE THE RIDE”
BACHELOR OF ENGINEERING
In
COMPUTER ENGINEERING
Submitted By:
Mr. Yuvrajsinh Jadeja (140540107053)
Under the guidance of
Prof. Arjun V. Bala
Department of Computer Engineering

Darshan Institute of Engineering & Technology
At Hadala, Rajkot– 363 650
2017-2018
Dedicated Faculty Committed Education
Darshan
Institute of Engineering & Technology
Certificate
This is to certify that
Mr. Yuvrajsinh Jadeja Enrolment No. 140540107053 Branch Computer
Engineering Semester 7th has satisfactory completed the course in the Subject
Project-I (2170001) in this institute.
Submission Date: 28 / 09 / 2017
Staff in Charge Head of Dept.

GUJARAT TECHNOLOGICAL UNIVERSITY
CERTIFICATE FOR COMPLETION OF ALL ACTIVITIES AT ONLINE PROJECT PORTAL
B.E. SEMESTER VII, ACADEMIC YEAR 2017-2018
Date of certificate generation : 10 October 2017 (19:03:17)
This is to certify that, Jadeja Yuvrajsinh Naimishsinh ( Enrolment Number -

140540107053 ) working on project entitled with Share The Ride from
Computer Engineering department of DARSHAN INSTITUTE OF
ENGINEERING & TECHNOLOGY, RAJKOT-MORBI HIGHWAY, HADALA
had submitted following details at online project portal.
Periodic Progress Reports (PPR) Completed
Design Engineering Canvas (DEC) Completed
Patent Search and Analysis Report (PSAR) Completed
Final Plagiarism Report Completed
Final Project Report Completed
Name of Student : Jadeja Yuvrajsinh Name of Guide : Mr.Bala Arjun Virjibhai

Naimishsinh
Signature of Student : _____________ *Signature of Guide : ________________
Disclaimer :
This is a computer generated copy and does not indicate that your data has been evaluated. This is the receipt that GTU
has received a copy of the data that you have uploaded and submitted as your project work.
*Guide has to sign the certificate, Only if all above activities has been Completed.
ACKNOWLEDGEMENT
I take this opportunity to express my deepest gratitude and appreciation to all those
people who made this project work easier with words of encouragement, motivation and helped
me towards the successful completion of this project work.
First I would like to express my sincere gratitude to my Project Guide and Professor,
Department of Computer Engineering, Prof. Arjun V. Bala, Darshan Institute of Engineering &
Technology, At Hadala, Rajkot-363650 for his insightful advice, motivating suggestions,
invaluable guidance, help and lots of moral support in successful completion of this Project and
also for his constant encouragement and advice throughout my B.E. (Computer Engineering)
programme.
I would like to thank all other teaching staff for their valuable teaching and constant
advice which made me to finish this program successfully.
Finally my deepest gratitude goes to my parents who have given me much needed
comfort, support, encouragement and inspiration for completing this project.
Date: 28 / 9 / 2017 Yuvrajsinh Jadeja (140540107053)

ABSTRACT
ShareTheRide is a web application which creates an online management platform for
handling carpooling service that connects vehicle owners and co-travelers to share a vehicle
and travel low cost. Different parameters of the journey like the date of the journey, Pick-up
and Drop-off points, owner of the vehicle, type of the vehicle, the cost of the ride, type of the
ride, etc. will be captured. People who want to travel can search for a ride, book the ride,
negotiate the cost and communicate with owner & others who are sharing the ride. Also,
vehicle owners who want to find people for their journey can offer a ride with details of
journey, the availability of seats and Pick-up & Drop-off points.
TABLE OF CONTENTS
Chapter Topic Page No.

1 Introduction 1
1.1 Project Summary 1
1.2 Purpose 1
1.3 Scope 2
1.4 Objective 2
1.5 Technology and Literature Review 2
2 Project management 4
2.1 Project Planning 4
2.2 Project Scheduling 9
2.3 Risk Management 9
3 System Requirements Study 13
3.1 User Characteristics 13
3.2 Hardware and Software Requirement 15
3.3 Constraints 15
3.4 Assumptions and Dependencies 16
4 System Analysis 17
4.1 Study of Current System 17
4.2 Problems and Weaknesses of Current system 17
4.3 Requirements of New System 17
4.4 Feasibility Study 18
4.5 Features of new system 19
4.6 Requirements Validation 19
4.7 DFD Diagrams 21
4.7.1 DFD Level-0 Diagrams 21
4.7.2 DFD Level-1 Diagrams 22
5 System Design 23
5.1 Interface Design (Screen Design) 23
5.2 ER Diagram 28
5.3 Database Design 29
i
6 Implementation Planning 31
6.1 Implementation Environment 31
7 Conclusion and Discussion 32
7.1 Summary of Project work 32
References 33
Appendix-A
PPR 34
Appendix-B
Canvas Report 38
Appendix-C
PSAR 42
Appendix-D
Plagiarism Report 57
ii
CHAPTER 1
INTRODUCTION
1.1 Project Summary

1.2 Purpose
1.3 Scope
1.4 Objective
1.5 Technology and Literature Review
7609 INTRODUCTION
1. INTRODUCTION
'Share The Ride' is a web application which creates an online management platform
for handling carpooling service that connects vehicle owners and co-travelers to share a
vehicle and travel low cost. Different people who want to travel to any destination can search
for car-owners going in their way and request to join their ride by traveling together. The
same phenomena applies for car owners who want to find people for their journey can offer a
ride with details of journey.
1.1 PROJECT SUMMARY
‘Share The Ride’ is a web based application which simply provides an interface for
people to connect to each other for ride-sharing. It is a simple website in which people can
find their traveling or commuting solutions. People with vehicles simply offer ride by
providing origin & destination, date & time of journey, type of ride like one-time or
everyday, details of their vehicle like model, available seats, etc. And people who want to
travel or commute to a place on regular basis can login to the website and search for ride
matching with their needs with the use different filter options. When they find a ride of
their choice they can simply book it or even communicate with vehicle owner for more
details.
1.2 PURPOSE
The purpose behind this project is to make people use this type of software solutions
for day-to-day problems which we as general people face. This type of software solutions
can really help towards betterment of tomorrow and enrichment of Green World.
Carpooling solutions leads to not only low cost but also in saving a lot of fuel which can
help in sustaining of green earth.
1
7609 INTRODUCTION
1.3 SCOPE
The web based application ‘Share The Ride’ is used for creating and maintain entries
of rides offered by vehicle owners on the platform and for searching and updating the details
of ride entries when other users search and book a ride of their choice.
It manages all the user details like name, contact number, email, etc. and vehicle
details like model, license plate number, available seats, etc. and ride details like origin-
destination, date-time, ride type, occupancy, associated vehicle, etc. This kind of
documentation will make it easy to maintain which ride is on which date, which people
booked it and other details of the processes carried out.
1.4 OBJECTIVES
The main objective is to provide a reliable and easy to use online management
platform for ride-sharing purpose for both vehicle owners and co-travelers or commuters.
1.5 TECHNOLOGY AND LITERATURE REVIEW
 Technology used:
 PHP, PHPMyAdmin, MySQL
 Literature reviewed:
 Referred PHP from W3Schools online tutorials and Tutorials Point.

 Referred the data type of SQL Server from
http://www.connectionstrings.com & http://dotnetguts.blogspot.in
 Referred the DBMS Query from Teach Yourself SQL in 21 Days
 Referred UML Diagram from Object Oriented Modeling and Design by
James R. Rumbaugh.
2
7609 INTRODUCTION
 Referred ER Diagram from Database Management System by Henry

Korth
 Referred Crystal Report Details and advantages from Crystal Reports
.Net Programming by Brian Bischof.
 Referred Software Engineering book by Pressman.
3
CHAPTER 2
PROJECT MANAGEMENT
2.1 Project Planning

2.2 Project Scheduling
2.3 Risk Management
7609 PROJECT MANAGEMENT
2. PROJECT MANAGEMENT
Software Project Management is an umbrella activity within software engineering.

This chapter provides how to plan, track and estimates this application by managing various
phases. It encompasses Project Development Approach’s justification, Schedules, risk
analysis, cost and effort estimation.
2.1 PROJECT PLANNING

Project Planning is concerned with identifying and measuring the activities,
milestones and deliverables produced by the project. Project planning is undertaken and
completed sometimes even before any development activity starts. Project planning consists
of following essential activities:
 Scheduling manpower and other resources needed to develop the system.
 Staff organization and staffing plans.
 Risk identification, analysis, and accurate planning.
 Estimating some of the basic attributes of the project like cost, duration and
efforts. The effectiveness of the subsequent planning activities is based on the
accuracy of these estimations.
 Miscellaneous plans like quality assurance plan, configuration management plan,
etc.
Project management involves planning, monitoring and control of the people, process, and
the events that occurs as the software evolves from a preliminary concept to an operational
implementation. Cost estimation is a relative activity that is concerned with the resources
required to accomplish the project plan.
2.1.1 Project Development Approach and Justification

A Software process model is a simplified abstract representation of a software
process, which is presented from a particular perspective. A process model for software
engineering is chosen based on the nature of the project and application, the methods and
tools to be used, and the controls and deliverables that are required. All software
4
development can be characterized as a problem-solving loop which in four distinct stages is

encountered:
 Requirement analysis
 Problem definition
 Technical development
 Integration and Testing
Throw-away prototyping: - Throw-away prototyping where the object of the evolutionary
development process is to understand the customer’s requirement and hence develop a better
requirements definition for the system. This approach is good when requirements are poorly
understood in beginning.
PIMS follows the Throw-away prototyping type of Evolutionary Development Model

software process model. This model is based on the idea of developing an initial
implementation, exposing this to user comment and reining through many versions until an
adequate system has been developed (Fig 2.1). After preliminary requirements gathering is
accomplished, a simple working model of the system is constructed to visually show the
users what their requirements may look like when they are implemented into a finished
system.
5
Fig 2.1 Evolutionary Development Model

 Strengths: -
 This approach is more effective to software development is often more
effective than the waterfall approach in producing system that meet the
immediate needs of customers.
 Specification can be developed incrementally.
 As user develops a better understanding of their problem, this can be
reflected in the software system.
 Problems:-
 The process is not visible.
 Documents producing for measuring the progress in this model will not be
cost-effective as system is going to be changed any time in terms of
requirements or interface, structure.
 Systems are often poorly structured.
 As in this model requirements and though system changes any time, will
leads to corruptness of the structure of the system.
 Problems become acute for large, complex, long-lifetime systems.
 Sometimes using this approach makes difficult to establish a stable system
architecture.
 Justification:
The most obvious reason for using Throwaway Prototyping is that it can be
done quickly. If the users can get quick feedback on their requirements, they may be able to
refine them early in the development of the software. Making changes early in the
development lifecycle is extremely cost effective since there is nothing at that point to redo.
If a project is changed after a considerable work has been done then small changes could
require large efforts to implement since software systems have many dependencies. We were
not provided with all the requirements in the beginning of the project and also the
requirements were subjected to changes. The throw-away prototype model delivers an
operational quality product at each stage which can then be examined by the clients for
further changes and provides feedback. Hence, we followed Evolutionary Development
model approach for system development.
6
2.1.2 Project plan

The software project management process begins with the set of activities that are
collectively called project planning. The objective of software project planning is to provide
a framework that enables the administrator to make reasonable estimates of resources, cost
and schedule.
Task From Date To Date

Functionality 17/07/2017 17/07/2017
Functionality Description 18/07/2017 18/07/2017
Screen Shots 17/08/2017 22/08/2017
Screen Shots 23/08/2017 25/08/2017
Data Dictionary 26/08/2017 27/08/2017
UML Diagram 29/08/2017 30/08/2017
UML Diagram & E-R Diagram 31/08/2017 02/09/2017
Final Report 17/09/2017 23/09/2017
Table 2.1 Project Planning
2.1.3 Milestones and Deliverables

Management needs information. As software is tangible, this information can only be
provided as documents that describe the state of the software being developed without this
information it is impossible to judge progress at different phases and therefore schedules can
not be determined or updated. Milestone is an end point of the software process activity. At
each milestone there should be formal output such as report that can be represented to the
management
 Milestones are the completion of the outputs for each activity.
 Deliverables are the requirements definition and the requirements specification.
 Milestone represents the end of the distinct, logical stage in the project.
 Milestone may be internal project results that are used by the project manager to
check progress.
7
 Deliverables are usually Milestones but reverse need not be true.

 We have divided the software process into activities for the following milestone
that should be achieved.
Software Process Activity Milestone

Project Plan Project schedule
Requirement Collection User requirements, System Requirements
Design System Design Document
1. Database design
2. User Interface design
Implementation
1. Code for giving security Access Rights
2. Code for reports Reports Generation
Testing Setting validations and error messages
Table 2.2 Milestones and Deliverables
2.1.4 Roles and Responsibilities

This phase defines the role and responsibilities of each and every member involved in
developing the system. To develop this system there was only one group with two members
working on the whole application. Each member was responsible for each and every part of
developing the system. Each of the group members has sufficient knowledge in several
programming languages. Our team structure is of mixed control team organization as it
consists of both democratic and chief programmer organization. The democratic arrangement
at the senior engineer’s level is used to decompose the problem into small parts.
8
2.2 PROJECT SCHEDULING

The following table outlines the tasks that need to be completed for each phase and the
students who are responsible for those tasks
Task List Members

Planning Yuvrajsinh
Plan for the implementation Yuvrajsinh
Implementation Yuvrajsinh
Design Functionality on paper Yuvrajsinh
Made Functionality in doc Yuvrajsinh
Design Functionality Description Yuvrajsinh
Made Functionality Description in doc Yuvrajsinh
Design Screen Shots on paper Yuvrajsinh
Made Screen Shots in html & Visual Yuvrajsinh
Studio
Design Data Dictionary on Paper Yuvrajsinh
Made Data Dictionary in doc Yuvrajsinh
Design UML & E-R Diagram on paper Yuvrajsinh
Made UML & E-R Diagram in Yuvrajsinh
gliffy.com & diagram.ly
Implementation Validation Yuvrajsinh
Implementation Correction Yuvrajsinh
Table 2.4 Scheduling
2.3 RISK MANAGEMENT

Risk management consists of a series of steps that help a software development team
to understood and manage uncertain problems that may arise during the course of software
development and can plague a software project. Risks are the dangerous conditions or
9
potential problems for the system which may damage the system functionalities to very high
level which would not be acceptable at any cost. so in order to make our system stable and
give its 100% performance we must have identify those risks, analyze their occurrences and
effects on our system and must prevent them to occur .
2.3.1 Risk Identification

All possible risks of ICP are:
Risk Type Description Possible Risks
Technology Risk, which derived The database used in the system cannot
from software or process as many transactions as per second
hardware technology, expected.
which are being used Software components which should be
as part of system reused contain defects which limit their
being developed. functionality.
People Risks, which are Key staffs are ill and unavailable at critical
associated with the times.
people in development Leaking an important data, Failure of the
team. administration, Lack of knowledge, Lack
of clear product vision, Technical staff
conflict and Poor communication between
people.
Organization Risk which derived The organization is restructured so that
from the different managements are responsible for
organizational the projects.
environment where Organizational financial problems force
the software is being reduction in project budget.
developed.
Requirements Risk which derived Changes to the requirements which require
from changes to the major design rework are proposed.
customer requirements Customer fails to understand the impact of
and process of requirements changes.
10
managing requirement
changes.
Estimation Risk which derived The time required to develop the software
from management is underestimated.
estimates of the The rate of defect repair is underestimated.
system characteristics The size of the software is underestimated.
and resources required
to build the system.
Table 2.5 Risk Identification
2.3.2 Risk Analysis

In this process each identified risk is considered in turn and a judgment made about
the probability and the seriousness of the risk.
 The probability of the risk might be assessed as very low (less than 10%), low (10-
25%), moderate (25-50%), high (50-75%) or very high (greater than 75%).
 The effects of the risk might be assessed as catastrophic, serious, tolerable or
insignificant.
Risk Risk Type Probability Effect

Software components which Technology Very Low Tolerable
should be reused contain
defects which limit their
functionality.
The database used in the Technology Moderate Serious
system cannot process as many
transactions per second as
expected.
Organization financial problem Organization Very Low Catastrophic
11
force reduction in the project

budget.
It is impossible to recruit staff Organization Low Tolerable
with the skill required for the
project.
Customer fails to understand Requirements High Tolerable
the impact of requirement
change.
Changes to requirements which Requirements Moderate Serious
require major design rework (Project Risk)
are proposed.
The time required to develop Estimation Low Serious
the software is underestimated.
The size of software is Estimation Low Tolerable
underestimated.
Table 2.6 Risk Analysis
2.3.3 Risk Planning

Risk Type Remedies/Plans
Hardware Failure Back up must be taken at each specific interval.
Schedule Slippage Reorganize team so that there is proper
understanding of the project and services and
people therefore understand each other’s job.
Rapidly Change in requirements For this risk we must have to analyze new
requirements and according to that proper changes
made.
Table 2.7 Risk Planning
12
CHAPTER 3
SYSTEM REQUIREMENTS STUDY
3.1 User Characteristics

3.2 Hardware and Software Requirement
3.3 Constraints
3.4 Assumptions and Dependencies
7609 SYSTEM REQUIREMENT STUDY
3. SYSTEM REQUIREMENT STUDY
This section identifies and lists the users of the application. Also describe their rights
in this project. ShareTheRide mainly deals with two types of users. Now functions of the user
are given below according to their rights and facilities.
3.1 USER CHARACTERISTIC

Two types of users interact with the system:
1. General user
General user can access homepage, general information, register itself and can search
for rides using filters.
1.1 General Information

In this functionality user can view general information.
 How It Works
Information regarding general phenomena of ride-sharing.
 About Us
Contains information about ShareTheRide online platform.
 Contact Us
Provides communication facility to contact to ShareTheRide developer team..
1.2 Search Rides

In this functionality user can search various rides offerd by other people with vehicles
and can use different filter options.
 Search Functionality
In this user can simply search by providing various search parameters.
 Filtering Functionality
It provides various filters for search results
13
1.3 Registration
General user can simply register his/herself on the website to become authorized user
and in order to use full functionalities of website.
2. Authorized user
Authorized user can access all the functionality which general user can access and they
can also access the following functionality.
 Login
They can log in to the website using unique username and password.
 Offer Ride
Here user can offer a ride by providing various parameters of the journey like
the date & time of the journey, Pick-up and Drop-off points, type of the ride,
type of the vehicle, the cost of the ride, type of the ride, etc.
 Book a ride
User can book a ride of choice that he/she found using the search functionality
if the ride chosen is available for booking.
 Communicate with Vehicle owner
In this user can communicate with owner by requesting the owner’s contact
details (if it is private) or exchanging contact numbers or emails.
 Feedback
Users which have traveled in past in ride offered by other people on the
website can simply review it and can give feedback of the ride in public or
private.
14
3.2 HARDWARE AND SOFTWARE REQUIREMENT SECIFICATION

This shows minimum requirements to carry-on to run this system efficiently.
3.2.1 Hardware
 Any hardware system capable of running an operating system and a web browser.
(Desktops, Laptops, Mobile Phones, Smart Phones, Tablets, etc.)
3.2.2 Software
 Operating System: Any computer or mobile or tablet based operating system
(Windows 95/98/2000/XP/NT/Vista/7/8, Mac OS, iOS, Android)
 Tool: Any Web Browser (compatible with HTML4 or above)
(To access the website)
3.3 CONSTRAINTS
3.3.1 Hardware Constraints

Any hardware system capable of running an operating system and a web browser. The
Graphics User Interface is best viewed in 1366*768 Resolution.
3.3.2 Reliability Constraints

Validation is the main reliability requirement that is used in the system. Without proper
validation, system does not allow to enter the value in the database.
3.3.3 Safety and Security Considerations

Safety:
If the use of this system is done by someone who is unauthorized but can able access this
system using valid authentication then he or she could able to change any important data
from the database.
15
Security:
If someone steals the password of the administrator or any regular user then he can able
to change the database or misuse the system and can enter in restricted area so for this
purpose system will provide encrypted password storage format in the database. When the
first time administrator or any regular user gives the password then the system will ask for
entering one key and on the basis of that key the password will be encrypted and then
onwards anyone who try to access that password then he will get it in encrypted form and for
decrypting that password he must have that key so without that key he can’t able to decrypt
that password.
3.4 ASSUMPTION AND DEPENDENCIES

 Assumptions
We will provide a friendly interface so that any user can easily navigate through the
system, but he/she should be capable of providing login name and password that has been
provided to them by website. The server used for data storing is always secured.
 Dependencies
Every new User has to register on the website for getting new Login Id to access the
system. All the normal users of the system will be assigned a specific set of roles. According
to these roles each and every user will be allowed access to a predefined set of features. The
features that are assigned to each user will be decided by administrator of the website.
16
CHAPTER 4
SYSTEM ANALYSIS
4.1 Study of Current Study

4.2 Problems and Weaknesses of Current System
4.3 Requirements of New System
4.4 Feasibility Study
4.5 Features of new system
4.6 Requirements Validation
4.7 DFD Diagram
4.7.1 DFD Level-0
4.7.2 DFD Level-1
7609 SYSTEM ANALYSIS
4. SYSTEM ANALYSIS
4.1 STUDY OF CURRENT SYSTEM
 First thing in the Analysis model is Study of Existing System, which is

available. Without Study of Existing System Analysis Model cannot proceed.
 Here, current system is conventional system. In conventional system there are
only two options available to people.
 Either they can travel on their own with full cost on his/herself or they may be
some people that they know would want to travel to the same place but
probability of finding someone that a person know and also want to travel at
same place or direction is very low.
 And in this conventional system tasks have to be done by vehicle owner like
searching for companions in relatives or known persons or job to find
unknown persons willing to come and join the journey is very much tough.
4.2 PROBLEMS AND WEAKNESSES OF CURRENT SYSTEM
 Cost of the ride do not get efficiently distributed

 Tedious task to find known persons to accompany the journey
 Very hard to find unknown persons to join the journey``16t
 No reliability
 No Effectiveness
4.3 REQUIREMENTS OF NEW SYSTEM

For developing a new system some requirements were provided by the user.
As per the specified requirements, it could be categorized in two different ways:
 User Requirement
 System Requirement
17
4.3.1 User Requirements
 Admin can create all constraints of the system and assign rights to the other
users and can modify those details also.
 The login rights as well as login information of all users is saved to database
in respective formats for ease.
 User can change password.
 User should be able to offer ride by providing various important details.
 User should be able to search for ride by using various filter options.
 Authenticated user should be able to book ride by confirmation of owner.
 User should be able to review and give feedback to the past traveled rides.
4.3.2 System Requirements
 Whatever user is selected on the basis of that the whole view should be loaded
and all the information related to the user should be saved in database.
 And on the basis of logged on user system will further react means it allows
only those group of function for which that user is authenticated. Only
authenticated user will be able to book ride offered by vehicle owners.
 There will be various ways of retrieving data & details and it takes less time.
4.4 FEASIBILITY STUDY
 Economic feasibility:
It does not require any other equipment and extra expenses in software so it is
economical.
 Technical feasibility:
Software needs any editor and PHPMyAdmin MySQL
 Operational feasibility:
Website should work properly according to administration of website.
 Schedule feasibility:
Website must be completed within one year.
18
4.5 FEATURES OF NEW SYSTEM

The project “Share The Ride” includes features mentioned below:
 Login
 Registration
 Search Rides
 Offer Ride
 Book Ride
 Manage user profile
Description:
Login
This feature allows user to log into the website to use full features provided by
website.
Registration
General User can view general information and search for rides offered by other
people and if general user may want to book a ride then they will be asked to log-in with
their account or sign up by providing details in order to book ride and use full features of the
website.
Search Rides
This feature allows user to search among various rides offered by vehicle owners.
They can also use different filter options too.
Book Ride
This feature allows users to become a co-traveler of any ride offered by others if seats
are available.
Manage User Profile
It can show user’s profile. Here user can edit profile details, change avatar and change
password.
4.6 REQUIREMENTS VALIDATION
19
 A requirements validation is concerned with showing that the requirements actually

define the system, which the customer wants.
 Requirements validation is important because errors in a requirements document can
lead to extensive rework costs when they are subsequently discovered.
4.6.1 Requirement Validation Checks
We have done below validation checks
 Validity checks: Check whether the information entered is in valid format.

 Consistency checks: Requirements in a document is not conflicting.
 Completeness checks: The requirements document includes requirement, which
define all functions, and constraints intended by the system user.
 Realism checks: Using knowledge of existing technology, the requirements are
checked to ensure that they could actually be implemented.
 Verifiability: The requirements are given in verifiable manner (e.g.: Using
quantifiable measures) to reduce disputes between client and developer.
4.6.2 Requirement Validation Techniques
 This section is concerned with showing that the requirements actually define the
system, which the customer wants.
 In addition to that, the system also has to provide security to the registered user
such as administrator or simple user. And our system has to fulfill both the above-
mentioned requirements and it has done it effectively.
 Requirement validation examines the specification to ensure that all system
requirements have been stated unambiguously; those inconsistencies, errors have
been detected and corrected and the system is tested successfully and the work
products confirm to the standard.
 Primary requirements validation mechanism is Formal Technical Review. Most of
the questions (conducted in FTR) answers Related to Investment Casting Process
are summarized in following statements:
 Source of the requirements are identified.
20
 Final statement of requirements has been examined by original source.

 Requirements are testable.
 Requirements related to main requirements are found.
 All sources of requirements are covered to get maximum requirement.
 All methods of finding requirements are applied.
 Requirements are not duplicated and each of them gives distinct idea of
processes within project.
 Requirements do not violate any domain constraints.
 Requirements associated with system performance, behavior and
operational characteristics are clearly stated and understood.
4.7 DFD DIAGRAMS
4.7.1 Data Flow Diagram level 0
21
4.7.2 Data Flow Diagram level 1
22
CHAPTER 5
SYSTEM DESIGN
5.1 Interface Design (Screen Design)

5.2 ER Diagram
5.3 Database Design
7609 SYSTEM DESIGN
5. SYSTEM DESIGN
5.1 INTERFACE DESIGN
 Login Form :
Login Form is used for to Authenticate the User. This module will process on user
name and password and authenticate user based on his role. Verification of the
Username and Password against the Database.
 Username : Provide facility to access website based on the User Name.

 Password : Password is used for security of particular user. Password will be
case sensitive.
 Sign in : The User has to enter the valid username and password and click the
Login Button to redirect user into main screen.
23
7609 SYSTEM DESIGN
 Registration:
This form captures the information about new user.
 Full Name : Full name of new user

 Mobile Number : Mobile Number of user
 Email : Email id of user
 Password : new Password for security of user
.
24
7609 SYSTEM DESIGN
 Search Rides:
Using this form user can search for rides offered by other people.
 Origin : Place or City from where user want to travel.

 Destination : Place or City to where user want to travel.
 Stopover : Contains points of places or cities from where journey will pass
through.
 Date & Time : Date and time of the journey.
 One-way/Roundtrip : Specifying whether journey is one-way or roundtrip.
 Type of vehicle : Specifies which type of vehicle is used for journey.
25
7609 SYSTEM DESIGN
 Offer Ride:
Using this form vehicle owner can offer a ride by providing ride details.
26
7609 SYSTEM DESIGN
 Origin : Place or City from where user want to travel.

 Destination : Place or City to where user want to travel.
 Stopover : Contains points of places or cities from where journey will pass
through.
 Date & Time : Date and time of the journey.
 One-way/Roundtrip : Specifying whether journey is one-way or roundtrip.
 Type of vehicle : Specifies which type of vehicle is used for journey.
 Model : Specifies the model of vehicle.
 License Plate Number : Specifies the license plate number of the vehicle which is
mandatory for all vehicle by rules of government.
 Available Seats : The no. of seats available in the vehicle for co-travelers.
 Type of Ride : It Specifies whether the ride is One-time or Everyday-ride.
 User Profile:
In this user can manage their profile details.
 Name : It specifies the name of user.

 Gender : Specifies the gender of the user.
 Address : Specifies the residential address of the user.
 Email : Specifies the email address of the user.
 Mobile No. : Specifies the contact number of the user.
27
7609 SYSTEM DESIGN
5.2 ER-DIAGRAM
28
7609 SYSTEM DESIGN
5.3 DATABASE DESIGN
List of Tables:
Serial Table Name

No.
1 user
2 userdetails
3 vehicle
4 ride
1) user :
2) userdetails :
29
7609 SYSTEM DESIGN
3) vehicle :
4) ride:
30
CHAPTER 6
IMPLEMENTATON PLANNING
6.1 Implementation Environment

7609 IMPLEMENTATION PLANNING
6. IMPLEMENTATION PLANNING
6.1 IMPLEMENTATION ENVIRONMENT

Challenges identified for successful design and implementation of this project are
dominated by: complexity, reliability/availability, transparent data access while respecting
security.
The project was a result of a group consensus. The team was having only one
member. The team was guided by internal guide.
This software is basically GUI related Data Access System. There is well-structured
navigation bar and icons has been provided for user. User can easily work through this
system. It has user friendly interface.
 Program/Module Specification
 This system is developed to automate and ease the work of people. System GUI must
be as simple and user friendly as anyone can use it. At front side we implemented
various forms for accessing the system.
 We create a various forms to insert and search records from data base. Different types
of user controls are used in this system so it will become very attractive and easy to
understand the process of that control. There is also a restriction given to this system
which prevents the system from garbage data and also prevent system from generating
run time error.
31
CHAPTER 7
CONCLUSION
7.1 Summary of Project work

7609 CONCLUSION AND DISCUSSION
7. CONCLUSION AND DISCUSSION
 We have developed a web based application which can work as online

management platform by connecting vehicle owners to co-travelers on one-
time or regular basis. In this project we have provided following major
functionalities needed in ride-sharing system:
 People who want to travel can search rides
 Vehicle owners can offer ride by providing details.
 People who were able to find ride of their choice can book it by
confirmation.
 Conventional ride-sharing system does not work on software solution. In
conventional, people have to find others on their own with no reliability or
effectiveness. Because of this people face so many problem in ride-sharing.
So this project will help them to find co-travelers effectively and in very
proper manner.
 We have provided two users Authorized and General so that general user can
not book ride which is necessary for security. We have made web forms for
adding ride, searching rides & user details.
32
REFERENCES
Books:
 Object Oriented Modeling and Design by James R. Rumbaugh.
 Software Engineering by Pressman.
 Database Management System by Henry Korth.
Websites:
 http://www.diagram.ly
 http://www.gliffy.com
 http://www.connectionstrings.com
 http://www.csharpcorner.com
 http://www.codeproject.com
 http://www.msdnmicrosoft.com
33
10/10/2017 Periodic Progress Report (PPR) Details
Print Back
DARSHAN INSTITUTE OF ENGINEERING & TECHNOLOGY, RAJKOT-MORBI

College :
HIGHWAY, HADALA
StudentName : Jadeja Yuvrajsinh Naimishsinh
EnrollmentNo : 140540107053 Department : Computer Engineering
MobileNo : 9033114999 Discipline : BE
Email : yuvrajjadeja7997@gmail.com Semester : Semester 7
PPR Details
Periodic Progess Report : First PPR

Project : Share The Ride
Status : Reviewed
1. What Progress you have made in the Project ?
Requirement gathering and analysis done. Based on the analysis, decided modules.
2. What challenge you have faced ?
Based on analysis, which are the important modules and which are not was difficult to find out.
3. What support you need ?
By taking support from faculties, decided the modules which are useful for the project.
4. Which literature you have referred ?
Existing software, books, material related to my project.
Comments
Comment by Internal Guide :

None
Comment by External Guide :
None
Comment by HOD :
None
Comment by Principal :
None
Comment by University Admin :
None
1/1
Print Back

College :
HIGHWAY, HADALA
PPR Details
Periodic Progess Report : Second PPR

Status : Reviewed
1) Finalized analysis of the project.. 2) Working on database design and data dictionary.
1) As analysis was done properly, I didn’t face any difficulty.
1) By taking support from faculties, decided the database tables which are useful for the project.
1) Existing software, books, material related to my project.
Comments

None
None
Comment by HOD :
None
None
None
1/1
Print Back

College :
HIGHWAY, HADALA
PPR Details
Periodic Progess Report : Third PPR

Status : Reviewed
1) Finalized database design and data dictionary.
1) Taken support from faculties in finalizing data dictionary.
Comments

None
None
Comment by HOD :
None
None
None
1/1
Print Back

College :
HIGHWAY, HADALA
PPR Details
Periodic Progess Report : Forth PPR

Status : Reviewed
1) Working on various UML and other necessary diagrams.
1) Taken support from faculties in finalizing diagrams.
Comments

None
None
Comment by HOD :
None
None
None
1/1
Canvas Report
AEIOU Summary
Empathy Mapping Canvas
Ideation Canvas
Product Development Canvas
(GTU)
INNOVATION COUNCIL (GIC)
Patent Search & Analysis Report
(PSAR)
Date of Submission : 31/08/2017
Dear Jadeja Yuvrajsinh Naimishsinh,
Studied Patent Number for generation of PSAR : 17BE7_140540107053_1
PART 1: PATENT SEARCH DATABASE USED
1. Patent Search Database used : Free Patents Online
Web link of database : http://www.freepatentsonline.com/
2. Keywords Used for Search : carpool,-,-
3. Search String Used : carpool
4. Number of Results/Hits getting : 2151
PART 2: BASIC DATA OF PATENTED INVENTION /BIBLIOGRAPHIC DATA
5. Category/ Field of Invention :
6. Invention is Related to/Class of Invention : carpool
6 (a) : IPC class of the studied patent : G01C21/3438
7. Title of Invention : Dynamic real-time carpool matching
8. Patent No. :
9. Application Number : US14543949
9 (a) : Web link of the studied patent : https://patents.google.com/patent/US20160138928A1
10. Date of Filing/Application (DD/MM/YYYY) : 11/18/2014
11. Priority Date (DD/MM/YYYY) :
12. Publication/Journal Number :
13. Publication Date (DD/MM/YYYY) :
14. First Filled Country : Albania :
Page 1
15. Also Published as
Sr.No Country Where Filled Application No./Patent No.
16. Inventor/s Details.
Sr.No Name of Inventor Address/City/Country of Inventor
1 Shang Q NY(US)
17. Applicant/Assignee Details.
Sr.No Name of Applicant/Assignee Address/City/Country of Applicant
1 International Business Machines Cor NY(US)
18. Applicant for Patent is : Company
PART 3: TECHNICAL PART OF PATENTED INVENTION
19. Limitation of Prior Technology / Art

N/A
20. Specific Problem Solved / Objective of Invention

N/A
21. Brief about Invention

According to one exemplary embodiment, a method for real-time carpool matching is provided. The method may include receiving a plurality of
carpool requests having a plurality of carpool route segments. The method may include determining at least one carpool match in real-time
based on the plurality of carpool route segments. The method may include assigning each carpool match a viability value. The method may then
include assigning a selected carpool match automatically for a user associated with the determined at least one carpool match, based on the
assigned viability value associated with each carpool match within the at least one carpool match. The method may further include choosing a
driver from a plurality of carpool participants, whereby the plurality of carpool participants is based on the selected carpool match. The method
may also include sending the selected carpool match to the plurality of carpool participants
22. Key learning Points

N/A
23. Summary of Invention

According to one exemplary embodiment, a method for real-time carpool matching is provided. The method may include receiving a plurality of
carpool requests having a plurality of carpool route segments. The method may include determining at least one carpool match in real-time
based on the plurality of carpool route segments. The method may include assigning each carpool match a viability value. The method may then
include assigning a selected carpool match automatically for a user associated with the determined at least one carpool match, based on the
assigned viability value associated with each carpool match within the at least one carpool match. The method may further include choosing a
driver from a plurality of carpool participants, whereby the plurality of carpool participants is based on the selected carpool match. The method
may also include sending the selected carpool match to the plurality of carpool participants
24. Number of Claims : 20
25. Patent Status : Applied Patent
26. How much this invention is related with your IDP/UDP?

< 70 %
27. Do you have any idea to do anything around the said invention to improve it? (Give short note in not more than 500
words)
Page 2
No
Page 3
(GTU)
(PSAR)
6. Invention is Related to/Class of Invention : carpooling solution
6 (a) : IPC class of the studied patent : G05B19/418
7. Title of Invention : System and method of wireless carpool scheduling
8. Patent No. :
Page 1
1 Mark Sohm Guelph(CA)
2 Kathryn Wilhelm Guelph(CA)
3 Larry Vettor Guelph(CA)
1 BlackBerry Ltd Guelph(CA)

N/A

N/A

A system and method of wireless carpool scheduling for notifying a carpool schedule change instantly is disclosed. The method comprises the
steps of opening up a carpool schedule web page from a carpool application, submitting a carpool schedule change, updating the carpool
schedule web page, sending an email notification to the group of carpoolers, pushing a wireless notification to a plurality of mobile devices
owned by the group of carpoolers. The system comprises a plurality of mobile devices for loading a carpool schedule web page corresponding
to a carpool group from a carpool application and submitting a carpool schedule change, a wireless network, wireless carpool scheduling server
for storing and providing carpool data related to one or more group of carpoolers, receiving the submitted carpool schedule change and sending
an email notification and pushing a wireless notification with respect to the submitted carpool schedule change.

N/A

A system and method of wireless carpool scheduling for notifying a carpool schedule change instantly is disclosed. The method comprises the
steps of opening up a carpool schedule web page from a carpool application, submitting a carpool schedule change, updating the carpool
schedule web page, sending an email notification to the group of carpoolers, pushing a wireless notification to a plurality of mobile devices
owned by the group of carpoolers. The system comprises a plurality of mobile devices for loading a carpool schedule web page corresponding
to a carpool group from a carpool application and submitting a carpool schedule change, a wireless network, wireless carpool scheduling server
for storing and providing carpool data related to one or more group of carpoolers, receiving the submitted carpool schedule change and sending
an email notification and pushing a wireless notification with respect to the submitted carpool schedule change.
25. Patent Status : Failed to maintain the Patent
Page 2
71 to 90%
words)
No
Page 3
(GTU)
(PSAR)
6. Invention is Related to/Class of Invention : carpool service
6 (a) : IPC class of the studied patent : G06Q10/06; G01C21/34; G06Q50/30
7. Title of Invention : Carpool service providing method and carpool server using the
same
8. Patent No. :
Page 1
1 Huang Shihchia Taipei City(TW)
2 Jiau Mingkai Taipei City(TW)
1 National Taipei University of Technology Taipei City(TW)
18. Applicant for Patent is : University

N/A

N/A

The invention discloses a carpool service providing method and a carpool server using the same. The method includes the following steps:
generating a carpool population matrix according to a plurality of carpool requests received from a plurality of passengers and drivers;
generating a first carpool matching result and a second carpool matching result according to the carpool population matrix; performing a routing
procedure to each of the first and second segments; respectively comparing the segment fitness value of one of the second segments with the
segment fitness value of the corresponding first segment and updating the second carpool matching result by replacing the one of the second
segments with the corresponding first segment if the segment fitness value of the one of the second segments is worse than the segment fitness
value of the corresponding first segment; updating the carpool population matrix according to the updated second carpool matching result

N/A

The invention discloses a carpool service providing method and a carpool server using the same. The method includes the following steps:
generating a carpool population matrix according to a plurality of carpool requests received from a plurality of passengers and drivers;
generating a first carpool matching result and a second carpool matching result according to the carpool population matrix; performing a routing
procedure to each of the first and second segments; respectively comparing the segment fitness value of one of the second segments with the
segment fitness value of the corresponding first segment and updating the second carpool matching result by replacing the one of the second
segments with the corresponding first segment if the segment fitness value of the one of the second segments is worse than the segment fitness
value of the corresponding first segment; updating the carpool population matrix according to the updated second carpool matching result
25. Patent Status : Granted Patent & In-force Patent

< 70 %
Page 2
words)
No
Page 3
(GTU)
(PSAR)
2. Keywords Used for Search : share,the,ride
3. Search String Used : share the ride
6. Invention is Related to/Class of Invention : carpooling solution
6 (a) : IPC class of the studied patent : G06Q50/30; G01C21/34; G06Q30/02; G06Q30/06; G07B15/00
7. Title of Invention : RIDE-SHARING RANGE CONTOURS
8. Patent No. :
Page 1
1 Liu Yimin Ann Arbor
2 Macneille Perry Robinson MI (US )
3 Yang Jinjing Lathrup Village
1 Ford Global Technologies LLC Dearborn, MI (US )

N/A

N/A

A ride-sharing server may identify a set of ride-sharing users within a range contour indicative of a threshold of at least one of cost, and time and
the number of occupants surrounding a driver route; send a set of ride-sharing options to a driver device, the ride-sharing options indicating the
ride-sharing users; send a set of ride-sharing options to a rider device; and receive, from the driver device, a selection of one of the ride-sharing
options to pick up one of the ride-sharing users; receive, from the ride device, a selection of one of the ride-sharing options to reserve one of the
ride-sharing drivers or cancellation of a selection. A mobile device may receive, from the ride-sharing server, the set of ride-sharing options;
display a user interface including the ride-sharing options; receive a selection of one of the ride-sharing options to pick up one of the ride-sharing
users; and send the selection to the ride-sharing server.

N/A

A ride-sharing server may identify a set of ride-sharing users within a range contour indicative of a threshold of at least one of cost, and time and
the number of occupants surrounding a driver route; send a set of ride-sharing options to a driver device, the ride-sharing options indicating the
ride-sharing users; send a set of ride-sharing options to a rider device; and receive, from the driver device, a selection of one of the ride-sharing
options to pick up one of the ride-sharing users; receive, from the ride device, a selection of one of the ride-sharing options to reserve one of the
ride-sharing drivers or cancellation of a selection. A mobile device may receive, from the ride-sharing server, the set of ride-sharing options;
display a user interface including the ride-sharing options; receive a selection of one of the ride-sharing options to pick up one of the ride-sharing
users; and send the selection to the ride-sharing server.
25. Patent Status : Applied Patent
Page 2
< 70 %
words)
No
Page 3
(GTU)
(PSAR)
2. Keywords Used for Search : share,the,ride
3. Search String Used : share the ride
6. Invention is Related to/Class of Invention : ride sharing service
6 (a) : IPC class of the studied patent : G06Q99/00
7. Title of Invention : RIDE-SHARE SERVICE
8. Patent No. :
Page 1
1 Mccall Clark E Ann Arbor
2 Lazar II Walter M MI (US)
1 GM GLOBAL TECHNOLOGY OPERATIONS LLC Detroit,MI (US)

N/A

N/A

Implementing a ride share service includes determining a route for an operator of the vehicle and accessing user preferences of the operator,
the user preferences including characteristics of a ride share event and prospective ride share individuals. The ride share service also includes
comparing the user preferences with information provided by individuals seeking transportation, each of the individuals providing a request for
the transportation. The ride share service further includes identifying qualified candidates for the ride share event from the comparing by
determining a threshold level of characteristics matching information provided by the individuals. In response to receiving a selection of a
qualified candidate from the qualified candidates, the ride share service includes transmitting a communication to the selected qualified
candidate accepting the request

N/A

Implementing a ride share service includes determining a route for an operator of the vehicle and accessing user preferences of the operator,
the user preferences including characteristics of a ride share event and prospective ride share individuals. The ride share service also includes
comparing the user preferences with information provided by individuals seeking transportation, each of the individuals providing a request for
the transportation. The ride share service further includes identifying qualified candidates for the ride share event from the comparing by
determining a threshold level of characteristics matching information provided by the individuals. In response to receiving a selection of a
qualified candidate from the qualified candidates, the ride share service includes transmitting a communication to the selected qualified
candidate accepting the request
25. Patent Status : Granted Patent & In-force Patent

71 to 90%
Page 2
words)
No
Page 3
86% Unique
Total 34440 chars (2000 limit exceeded) , 312 words, 13 unique sentence(s).
Essay Writing Service - Paper writing service you can trust. Your assignment is our priority! Papers ready in 3 hours!
Proficient writing: top academic writers at your service 24/7! Receive a premium level paper!
Results Query Domains (original links)
trb.org dartmouth.edu slideshare.net fao.org

virginia.edu freebsd.org msdn.microsoft.com
1,470,000 results CHAPTER 1 INTRODUCTION
technet.microsoft.com technet.microsoft.com
youtube.com
111,000 results 1 Project Summary Get Free Access
2,460,000 results 2 Purpose Get Free Access
2,190,000 results 3 Scope Get Free Access
531,000 results 4 Objective Get Free Access
Unique 5 Technology and Literature Review 7609 INTRODUCTION 1 -
Unique 7609 INTRODUCTION 2 -
8 results 3 SCOPE The web based application ‘Share The Ride’ is used Get Free Access
Unique for handling carpooling service that connects vehicle owners and co-travelers to share a vehicle and -
Unique Different people who want to travel to any destination can search for car-owners going -
Unique The same phenomena applies for car owners who want to find people for their -
Unique 1 PROJECT SUMMARY ‘Share The Ride’ is a web based application which simply provides an -
Unique It is a simple website in which people can find their traveling or commuting -
Unique of journey, type of ride like one-time or everyday, details of their vehicle like model, -
Unique can login to the website and search for ride matching with their needs with the -
Unique When they find a ride of their choice they can simply book it or -
Unique 2 PURPOSE The purpose behind this project is to make people use this type of -
Unique This type of software solutions can really help towards betterment of tomorrow and enrichment -
Unique Carpooling solutions leads to not only low cost but also in saving a lot -
Top plagiarizing domains: technet.microsoft.com (2 matches); msdn.microsoft.com (1 matches); youtube.com (1 matches); freebsd.org (1 matches); virginia.edu (1 matches);
dartmouth.edu (1 matches); slideshare.net (1 matches); fao.org (1 matches); trb.org (1 matches);
Create a FREE account to continue.

CHAPTER 1 INTRODUCTION 1.1 Project Summary 1.2 Purpose 1.3 Scope 1.4 Objective 1.5 Technology and Literature Review 7609 INTRODUCTION 1 1. INTRODUCTION Share
The Ride is a web application which creates an online management platform for handling carpooling service that connects vehicle owners and co-travelers to share a vehicle
and travel low cost. Different people who want to travel to any destination can search for car-owners going in their way and request to join their ride by traveling together. The
same phenomena applies for car owners who want to find people for their journey can offer a ride with details of journey. 1.1 PROJECT SUMMARY ‘Share The Ride’ is a web
based application which simply provides an interface for people to connect to each other for ride-sharing. It is a simple website in which people can find their traveling or
commuting solutions. People with vehicles simply offer ride by providing origin & destination, date & time of journey, type of ride like one-time or everyday, details of their
vehicle like model, available seats, etc. And people who want to travel or commute to a place on regular basis can login to the website and search for ride matching with their
needs with the use different filter options. When they find a ride of their choice they can simply book it or even communicate with vehicle owner for more details. 1.2 PURPOSE
The purpose behind this project is to make people use this type of software solutions for day-to-day problems which we as general people face. This type of software solutions
can really help towards betterment of tomorrow and enrichment of Green World. Carpooling solutions leads to not only low cost but also in saving a lot of fuel which can help in
sustaining of green earth. 7609 INTRODUCTION 2 1.3 SCOPE The web based application ‘Share The Ride’ is used

"Share The Ride": Project Report O

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

"Share The Ride": Project Report O

Caricato da

Copyright:

Formati disponibili

Project Report On

“SHARE THE RIDE”

Under the guidance of

Prof. Arjun V. Bala

Department of Computer Engineering

This is to certify that

Mr. Yuvrajsinh Jadeja Enrolment No. 140540107053 Branch Computer

Project-I (2170001) in this institute.

Submission Date: 28 / 09 / 2017

Staff in Charge Head of Dept.

This is to certify that, Jadeja Yuvrajsinh Naimishsinh ( Enrolment Number -

Periodic Progress Reports (PPR) Completed

Design Engineering Canvas (DEC) Completed

Patent Search and Analysis Report (PSAR) Completed

Final Plagiarism Report Completed

Final Project Report Completed

Name of Student : Jadeja Yuvrajsinh Name of Guide : Mr.Bala Arjun Virjibhai

Signature of Student : _____________ *Signature of Guide : ________________

Date: 28 / 9 / 2017 Yuvrajsinh Jadeja (140540107053)

Chapter Topic Page No.

1.1 Project Summary

1.1 PROJECT SUMMARY

1.5 TECHNOLOGY AND LITERATURE REVIEW

 PHP, PHPMyAdmin, MySQL

 Referred PHP from W3Schools online tutorials and Tutorials Point.

 Referred ER Diagram from Database Management System by Henry

2.1 Project Planning

Software Project Management is an umbrella activity within software engineering.

2.1 PROJECT PLANNING

2.1.1 Project Development Approach and Justification

development can be characterized as a problem-solving loop which in four distinct stages is

PIMS follows the Throw-away prototyping type of Evolutionary Development Model

Fig 2.1 Evolutionary Development Model

2.1.2 Project plan

Task From Date To Date

Table 2.1 Project Planning

2.1.3 Milestones and Deliverables

 Deliverables are usually Milestones but reverse need not be true.

Software Process Activity Milestone

Table 2.2 Milestones and Deliverables

2.1.4 Roles and Responsibilities

2.2 PROJECT SCHEDULING

Task List Members

Table 2.4 Scheduling

2.3 RISK MANAGEMENT

2.3.1 Risk Identification

Table 2.5 Risk Identification

2.3.2 Risk Analysis

Risk Risk Type Probability Effect

force reduction in the project

Table 2.6 Risk Analysis

2.3.3 Risk Planning

Table 2.7 Risk Planning

3.1 User Characteristics

3. SYSTEM REQUIREMENT STUDY

3.1 USER CHARACTERISTIC

1.1 General Information

1.2 Search Rides

3.2 HARDWARE AND SOFTWARE REQUIREMENT SECIFICATION

3.3.1 Hardware Constraints

3.3.2 Reliability Constraints

3.3.3 Safety and Security Considerations

Signature of Student : _ *Signature of Guide : ____