Rkpatel 123

An UDP Project Report On
Dérive Ahmedabad
Prepared by
Rucha Patel
(Enrollment No:140024107002)
Shivani Raval
Parshwa Shah
Guided By:
Prof. Chintan Nagrecha
(Assistant Professor, CE Department)
DEPARTMENT
OF COMPUTER
ENGINEERING
AHMEDABAD INSTITUTE OF TECHNOLOGY
GUJARAT TECHNOLOGICAL UNIVERSITY

Winter-2018
AHMEDABAD INSTITUTE OF TECHNOLOGY
Gota-Ognaj Road, Ahmedabad, Gujarat 380060
CERTIFICATE
The report entitled “derive ahmedabad” prepared by rucha patel, Shivani raval,
parshwa shah for Project Phase-I (Semester - 7) for the partial fulfilment of degree of
Bachelor of Engineering (Computer Engineering), has been carried out under my
supervision in Department of Computer Engineering, AHMEDABAD INSTITUTE
OF TECHNOLOGY. Her present work has been found satisfactory.
Date of Submission:
Guided By:
Prof. Chintan nagrecha Prof. Ajay Upadhyaya
Assistant Prof, CE Dept Head of CE & IT Dept
AIT AIT
Acknowledgement
No task can be accomplished without proper support, guidance and appraisal. We are highly
thankful to many people who contributed either directly or indirectly for this project and
provided their invaluable cooperation to us to complete it.
We would like to thank our Head of Department, Prof. Ajay .N. Upadhyaya and our
faculty members of Computer Engineering for constantly guiding and showing us the
correct way to reach towards the desired goal.
Then we would like to thank our Internal guide Asst. Prof. Chintan Nagrecha who has
helped us out in every phase of the project and without their support and guidance the project
would not have been completed successfully.
The wholehearted help and co-operation by our friends are gratefully acknowledged.
Rucha Patel
Shivani Raval
Parshwa Shah
Plagiarism certificate
UNDERTAKING ABOUT ORIGINALITY OF WORK
We hereby certify that we are the sole authors of this IDP/UDP project report and that
neither any part of this IDP/UDP project report nor the whole of the IDP/UDP Project report
has been submitted for a degree by other student(s) to any other University or Institution.
We certify that, to the best of our knowledge, the current IDP/UDP Project report
does not infringe upon anyone’s copyright nor violate any proprietary rights and that any
ideas, techniques, quotations or any other material from the work of other people included in
our IDP/UDP Project report, published or otherwise, are fully acknowledged in accordance
with the standard referencing practices. Furthermore, to the extent that we have included
copyrighted material that surpasses the boundary of fair dealing within the meaning of the
Indian Copyright (Amendment) Act 2012, we certify that we have obtained a written
permission from the copyright owner(s) to include such material(s) in the current IDP/UDP
Project report and have included copies of such copyright clearances to our appendix.
We have checked the write up of the present IDP/UDP Project report using anti-
plagiarism database and it is in the allowable limit. In case of any complaints pertaining to
plagiarism, we certify that we shall be solely responsible for the same and we understand that
as per norms, University can even revoke BE degree conferred upon the student(s) submitting
this IDP/UDP Project report, in case it is found to be plagiarized.
Team:
Enrollment Number Name Signature
140024107002 Rucha Patel
150024107009 Shivani Raval
150024107021 Parshwa Shah
Place:
Date:
Guide Name: Asst. Prof. Chintan Nagrecha

Signature of Guide: _______________
TABLE OF CONTENTS
Abstract I
Tables II
1. List of figures
Chapter: 1 Introduction 1
1.1 Project Summary 2
1.2 Project Purpose 2
1.3 Project Scope 2
1.4 Project Objectives 3
1.5 Technology Review 3
1.6 Literature Review 3
Chapter: 2 Project Management 5
2.1 Project Planning 6
2.2 Project Scheduling 8
2.3 Risk Management 8
2.4 Canvas Designing 9
2.4.1 AEIOU Summary
2.4.1.1 Activities
2.4.1.2 Environment
2.4.1.3 Interactions
2.4.1.4 Objects
2.4.1.5 Users
2.4.2 Empathy Summary
2.4.3 Ideation
2.4.4 Product Development
Chapter: 3 System Requirements Study 12

3.1 User Characteristics 13
3.2 Hardware and Software Requirements 13
3.3 Specific Requirements 13
3.3.1 Functionality
3.3.2 Usability
3.3.3 Reliability
3.3.4 Performance
3.3.5 Supportability
3.3.6 Design Constraints
3.4 Assumptions and Dependencies 14
Chapter: 4 System Analysis 15

4.1 Requirements of New System 16
4.2 Feasibility Study 16
4.3 Requirements Validation 17
4.4 Features Of New System 17
4.5 For Conventional Approach 18
4.5.1 Process Flow Diagram
4.5.2 Context Diagram
4.5.3 Data Flow Diagram
4.5.4 E-R Diagram
Chapter: 5 System Design 25

5.1 Database Design 26
5.2 Input-Output Design(if applicable) 26
Chapter: 6 Limitation and Future Enhancement 28

6.1 Limitation 29
6.2 Future Enhancement 29
Chapter: 7 Conclusion and Discussion 30

7.1 Self Analysis of Project Viabilities 31
7.2 Problem Encountered and Possible Solutions 31
7.3 Summary of Project work 31
Chapter: 8 References 32
Appendix 1: Periodic Progress Report 34

Appendix 2: Design Engineering Canvas 46
Appendix 3: PSAR Report 50
Abstract
Derive Ahmedabad is a web site gives information about Ahmedabad City,
Family tours, City tours, Events. This Web site will definitely be a boon for people
who want to explore something new in the city, productive within their area of
interest, no matter what genre it would be. we offer tour and travel services including
tour booking , hotel reservations, holiday tour packages. we offer everything related
to travelling Ahmedabad city services under one roof.
Team_id: 9411 ABSTRACT
Figure No. Name of the figure Page No.

Figure 4.5.1 Process Flow Diagram 30
Figure 4.5.2 Context Diagram 31
Figure 4.5.3 Data Flow Diagram 32
Figure 4.5.4.1 Data Flow Diagram Level 33
Figure 4.5.5 ER Diagram 34
C.E. DEPARTMENT | AIT 2

Team_id: 9411 PROJECT MANAGEMENT
CHAPTER 1: INTRODUCTION

1.1 Project summary:
Derive Ahmedabad will be the most hyped and highly trending web-site
In Our web-page The Act Of Purchasing Services Over The Internet. Event booking
Has Grown In Popularity Over The Years, Mainly Because People Find It Convenient
And Easy To buy tickets From The Comfort Of Their Home Or Office.
1.2 Project purpose:
 Derive Ahmedabad will be the most hyped and highly trending web-site
 In Our web-page The Act Of Purchasing Services Over The Internet. Event booking
GrownIn Popularity Over The Years, Mainly Because People Find It Convenient And
Easy To buy tickets From The Comfort Of Their Home Or Office.
1.3 Project scope:
The web-site is allow to book tours and services over the internet without the need
of going physically to the market. User can book package and also book events
online from anywhere in the world .
 Proper services and resources will be provided to the users.
 Users can ask for service if they don't find it in the given options.
 Users can share their location to the service providers for service at their location.
 Users are allowed to pay for their services with cash or by other payment
gateways like paytm, upi, google pay.
 Users can select any of the available nearby shops whichever suites them.
 Our services values for money & batter services.

1.4 Project objective:
 The successful implementation of the new system will purely upon the involvement of the
officers working in that department. The officers will be imparted the necessary training
on the new technology.
 The education of the end user start after the implementation and testing is over.
When the system is found to be more difficult to under stand and complex, more
effort is put to educate the end used to make them aware of the system, giving them
lectures about the new system and providing them necessary documents and
materials about how the system can do this.
1.5 Technology review:
Technology:
What is PHP?
 PHP stands for “PHP stands for Hypertext Preprocessor”. PHP is a server side
scripting language for making logic driven website. Ever wonder how they made that
“contact us” from on their site, which sends out emails? Well they used PHP. Or how
they made that image upload tool? Well they used PHP. PHP written scripts can use
database to keep track of your customer’s and visitor activities on your site, send out
periodically newsletters to your subscribers, upload file or images and the drive the
content on your site dynamically. The possibilities are endless, Most of the social
networking websites you visit are writing in PHP. Yep! PHP is that powerful.
 Learning the basic of PHP will help you webpage development of a PHP website in
your browser, your browser sends out a request to the web server. The web server
then calls the PHP scripts on that page. The PHP module executes the scripts, which
tends sends out the result in the form of diagram which illustrate the process.

PHP Stands for:
 PHP stands for Hypertext Preprocessor.

 PHP Scripts run inside Apache server.
 PHP and Apache server are free.
 PHP is the most user server side scripting language.
 PHP files contain PHP scripts and HTML.
 PHP files have the extension “php”, “php3”, “php4” or “html”.
What is the difference between the PHP an HTML?
 HTML files are requested by browsers and return by server.

 PHP files are request by browser, and executes by the server to output a plain HTML
that is returned to the browsers.
When to use PHP?
 Creating web pages that contain dynamic contents.

 Responding to html forms.
 Accessing database.
What make PHP a choice among the other scripting language?
 PHP is free.
 PHP can run on windows and UNIX servers.
 PHP is very fast and easy to learn.
What is MYSQL?
 Open source database system.

 Like most modern database management system is based on the relational model
RDBMS.
 Free.
 Run on Linux, Windows, Netware, and IOS and so on.
 Easily accessible through programming language like PHP.

Why MYSQL Choose:
 Open source database.

 Consistent fast performance and high reliability.
 Ease of use.
 High availability.
 Comprehensive application development.
 Management Easy.
 Lowest total cost of ownership.
1.6 Literature review
 Derive Ahmedabad is a web site gives information about Ahmedabad City, Family
tours, City tours, Events. This Web site will definitely be a boon for people who want
to explore something new in the city, productive within their area of interest, no
matter what genre it would be.
 we offer tour and travel services including tour booking , hotel reservations, holiday
tour packages.
 Study of Current Existing System:
GOOGLE.COM
 Wikipedia.COM
 This site provides location of any accommodation is available in our area.

 Accommodation (a Gtu project on php)
 This web site is providing the with photo and review feature of any service.
 Provides services form verified and trust for the tours.Available only in
Ahmedabad.This website is give a a to z information about the tours.

CHAPTER 2: PROJECT MANAGEMENT

Team_id:9411 PROJECT MANAGEMENT
2.1 Project planning
2.1.1 Project Development Approach:
Spiral Model:
 Spiral Model is a combination of a waterfall model and iterative model. Each phase in
spiral model begins with a design goal and ends with the client reviewing the
progress. The spiral model was first mentioned by Barry Boehm in his 1986 paper.
 The development team in Spiral-SDLC model starts with a small set of requirement
and goes through each development phase for those set of requirements. The software
engineering team adds functionality for the additional requirement in every-increasing
spirals until the application is ready for the production phase.
Phase of This Model:
Planning:
 It includes estimating the cost, schedule and resources for the iteration. It also
involves understanding the system requirements for continuous between the between
the system analyst and the customer.
Risk Analysis:
 Identification of potential risk is done while risk mitigation strategy is planned and
finalized.
Engineering:
 It includes testing, coding and deploying software at the customer site
Evolution:
 Evaluation of software by the customer. Also, includes identifying and monitoring

risks such as schedule slippage and cost overrun

When to use Spiral Methodology?
 When project is large

 When releases are required to be frequent
 When creation of a prototype is applicable
 When risk and costs evaluation is important
 For medium to high-risk projects
 When requirements are unclear and complex
 When changes may require at any time
 When long term project commitment is not feasible due to changes in economic
priorities
Figure 1 spiral Model

Application:
 It used to large scale project.
2.1.2 Milestones and deliverable:
 When planning a project, a series of milestone should be established. The milestone is

in 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. It is logical step in
project progress but which are not delivered to the customer. The completion of each
phase of SDLC is milestone in linear sequential model. Each completing phase raises
the project work 10-15% towards last end product expected.
2.1.3 Roles and Responsibilities:
 We are 2 members in the development of this project. Our system was decomposed into
different modules and we are the only responsible person for analysis, design and
implementation, documentation along with the testing.
Table 1 Roles & Responsibilities

Activities rucha shivani parshwa
Understanding Existing   
System
Project Definition Study   
Requirements Gathering &   
Analysis
Project Planning   
Project Scheduling   
Database Design   
UML Diagrams   
Documentation   
2.1.4 Group Dependencies:

 The team structure depends on the management style of the organization, the number
of people in the team, their skill levels and the problem difficulty. Considering all
these points our Team organization was Democratic Decentralized. In which there is
no team leader. Decision on the problems was made by group consensus.
Communication among the team members was horizontal.
2.2 Project scheduling:
2.3 Risk management

 Risk management is concerned with identifying risks and drawing up plans to

minimize their effect on a project. A risk is a probability that some adverse
circumstance will occur. Project risks affect schedule or resources. Product risks
affect the quality or performance of the software being developed. Business risks
affect the organization developing or producing the software.
The risk management process includes the following:
 Risk Identification
 Risk Analysis
 Risk Planning
2.3.1 Risk Identification:
 Risk Identification is concerned with discovering possible risk to project. It identifies

project, product and business risks. Following is the list of potential risk identified
which might leads to the failure of the project.
 Table 3 Risk Identification
RISK ID DESCRIPTION TYPE

RID 1 Domain Knowledge risk Project
RID 2 Project Scheduling risk Project
RID 3 Communication risk Project
RID 4 Organization risk Project
RID 5 Project Size Estimation risk Project
RID 6 Requirement Change risk Project
RID 7 Staff Turnover Project
Risk can be primarily categorized as:
 Product risk
 Project risk
 Business risk
Risk assessment:
 Involves identifying sources of potential harm, assessing the likelihood that harm will
occur and consequence if harm does occur. For this project it might be System Crash.

Risk Communication:
 Involves an interactive dialogue between stakeholders and risk assessors and risk
managers which actively informs the other processes. Steps taken for risk
communication are as under:
 Probability of certain risk is negotiated with client.
 All the possible risks are listed out during communication and project is
developed taking care of that risks.
2.3.2 Risk Analysis:
 Risk analysis is concerned with identifying each risk and judgments are made about
the probability and seriousness of risk.
Probability can be:

 Very low
 Low
 Moderate
 High
 Very high
And risk Impact can have values:

 Catastrophic
 Serious
 Tolerable
 Insignificant
2.3.3 Risk Planning:
Risk planning identifies strategies to manage risk. The various mitigation plan and
precautions were taken to minimize the risk involved.
 Lack of domain knowledge could be potential risk to the project. So study for domain
knowledge was given utmost important and more time was allocated to the analysis
phase to properly understand the system. Also, suggestion from the experts and online
chatting were done to overcome the risk.

 To meet client’s deadline, the whole project was divided on hourly basis so as to
reduce the possibility of moving away from scheduled time.
 Project is built on 3-tire technology, so that easy modification is possible and hence it
can cope up with future enhancements.
 As project is being developed on Apache, XAMMP & MySql should be installed on
the server computer. This is major risk associated but it can easily be solved.
 All the above tools which are require to be installed on the server side, no need to
install them on client

2.4 Canvas designing:
2.4.1 AEIOU summary:
2.4.1.1 Activities
 Reading, Writing, Eating, Room sharing, Shopping.
2.4.1.2 Environment:
 It describes the environment of the Paying guest that we have visited like Hot
air, Rainy weather, Dusty air, Cloudy weather.
2.4.1.3 Interactions:
 Interaction between Manager to Customer, Student to Student, Manager to
Parents, Watchmen to PG member, Watchmen to Manager.

2.4.1.4 Objects:
 Various object used like CCTV, Wi-Fi, Mobile, TV, Pc/Laptops, Beds, Food,
Water.
2.4.1.5 Users:
 Various users are Students, Citizen, Villagers, and Managers.

2.4.2 Empathy summary:
This canvas includes users and stack holders and their activities with experience with
two happy and sad stories.
2.4.2.1. Users:
 Various users like Villagers, Citizen, Managers, Employee, For

book Tours, For book events.

2.4.2.2. Stack holder:
 Visitors, Managers, Guest Members.
2.4.2.3. Activities:
 Search Location, Booking, Communication.
2.4.2.4 Story boarding:
 Two stories of paying guest members felt better after using this
system and other two story where people are facing problem
without the system

2.4.3 Ideation:
In ideation canvas, we have carried out which type of activities is related to our
project and people. What is the situation and location regarding to activities.
2.4.3.1 People:
 Students, Workers, Watchmen, Visitors, Parents.
2.4.3.2 Activities:
 Customers management, Manage event, Manage Tours, History.
2.4.3.3 Situation/context/Location:
 Historic Locations, Hotels, Restaurant.
2.4.3.4 Props/possible solutions:

 Internet, Manage database, Computer, CCTV, GPS maps.

2.4.4 Product development:
In this canvas following things are done.

2.4.4.1 Purpose:
 To save cost, time saving, minimize effort.
2.4.4.2 People:
 Managers, Customers, Citizen, Visitors.
2.4.4.3 Product experience:

 Help anywhere, More attractive, Better performance, Provide Integrity.
2.4.4.4 Product Functions:

 Provide Security, Provide online information of Places, Useful for finding
places in the city.

2.4.4.5 Product Features:

 Search History, Book Hotels, Book Events, Book Tours
2.4.4.6 Components:
 Laptop, GPS maps, Mobile, Wi-Fi/Routers.
2.4.4.7 Customer revalidation:

 Customer Validation, Security validation, comparatively costly.
2.4.4.8 Reject, Redesign, And Retain:

 Easy Booking option, more secure, User interactive.

CHAPTER 3: SYSTEM REQUIREMENT STUDY

3.1 User characteristics:
User characteristics include type of user dealing with the system such as:
 Manager
 Customers
 Administrators
3.2 Hardware and Software Requirement:
 Hardware requirement:
o Intel I3(processor)
o 4GB Ram
o 512KB Cache Memory
o Hard Disk 10GB
 Software requirement:
 Frontend:
o HTML,HTML5
o CSS,CSS3
o JavaScript, Jquery
o Bootstrap
 Backend:
o PHP
o Database
o mysql
 Tools:
o Sublime
o Notepad++

3.3. Specific requirement:
3.3.1 Functionality
 Login of admin
 Change password of admin
 Login of user
 Change password of user
 Change personal contact detail of admin
 Change personal contact detail of user
3.3.2 Usability:
 This Web site describes the tours and events. In addition to usability, customer send
inquiry, register for event, services, trust were used as predictors with intention and
decision to book tours.
 This web Application describes the development and empirical validation of a new
scale for measuring usability in book events and tours.
 A regression analysis of booking intention shows that usability has the greatest impact
on booking system intention, followed by the book your tour system.
3.3.3 Reliability:
 The system can work all the time without failures apart from network failure. The
Customer can have the faith on the system. The admin will keep the privacy of all
Customers in a proper manner. Web Application must be available 24 Hours 7 days .It
may be used at any time. Due to wireless connectivity.

3.3.4 Performance:
 Should run on 500 GHz, 64MB machine.

 Should have a proper internet connection.
 The response time for occurs a change will be no more than 4 seconds.
 The response time for access the database will be no more than 5 seconds
Supportability.
3.3.5 Supportability:
 The successful implementation of the new system will purely upon the involvement of
the officers working in that department. The officers will be imparted the necessary
training on the new technology.
 The education of the end user start after the implementation and testing is over. When
the system is found to be more difficult to understand and complex, more effort is
put to educate the end used to make them aware of the system, giving them lectures
about the new system and providing them necessary documents and materials about
how the system can do this.
3.3.6 Design Constraints:
 Data should not become corrupted in case of network failure, system crash or power
failure.
 Security
 This system is provisioned to be built on core php which is highly flexible. Decision
regarding which database to use should be taken considering the fact that data being
exchanged or stored is large, and the appropriate data management system will yield
efficient performance.
3.4 Assumption and Dependencies:
 Every User has mobile.

 The system database will be accessible in real time.

 The customer and manager don’t submit any fake report to the system
CHAPTER 4: SYSTEM ANALYSIS

4.1 Requirement of new system:
Behind any concerted effort to build, launch or maintain a web site is probably
an idea or concept of what the site’s a leadership or company executives want
done. Behind any rational web effort should be a formal structure and
methodology known as a project plan.
There are following requirement of new system.
s
1. User Requirement:
User requirements typically describe the needs, goals, and tasks of the user. I
strongly recommend that any user requirements document define and describe the
end-user, and that any measurements of quality or success be taken with respect to
that end-user.
2. System Requirement:
The term system requirements have two meanings. First, it can refer to the
requirements that describe the capabilities of the system with which, through
which, and on which the product will function.
4.2 Feasibility study:
The important of the preliminary investigation is the determination of the whether the
system requested is feasible or not. There are three aspects of feasibility study which should
be checked in preliminary investigation.
There are three feasibility studies:
1) Technical feasibility
2) Economic feasibility

3) Operational feasibility
 Technical Feasibility:
 The technical feasibility in the proposed system deals with the technology used in
the system. It deals with the hardware and software used in the system whether
they are of latest technology or not. It happens that after a system is prepared a
new technology arises and the user wants the system based on that technology.
Thus it is important to check the system to be technically feasible.
 The minimum memory requirement is 256MB of RAM while 1GB is better to
have for better performance. Hard Disk of 35 GB is required. As far as
software is concerned, SQL Server 2005 and Core PHP should be installed on
the server. According to the project requirement, we have the hardware with
the proper input.
 Economical Feasibility:
 According to the concept of Economical Feasibility, the system should be

completed with minimum cost. This is one of the most important factors for
any system. The proposed system is cost-effectiveness. This system is in range
of which is assumed for developing it. So, it is economically feasible. In this
bud the cost of hardware and software for the class of application is being
considered.
 Operational Feasibility:
 The system should be easy to operate by the user. The user should be given operating
manual about the system. Proposed projects are beneficial only if they can be turn into
information systems that will meet the organization’s operating requirements. The new
system is very efficient regarding to its operations on data. There is sufficient support for
the system from management and users. Users welcome these systems accept it without
any resistance

4.3 Requirements validation:
BOOK REDBUS find tour

MAKE MY
MY [Current package on one
TRIP
SHOW existing click
Specifications [Current
[Current system]
existing
existing
system]
system]
No
Services for packages No No Yes
Vault for Documents No No Yes Yes

Service at your location Yes Yes Yes Yes
Yes
Payment method Yes Yes Yes
Travel Insurance Yes Yes No No

Pick and drop facility Yes Yes Yes Yes
Requires booking Yes Yes Yes No
24*7 availability No No Yes Yes
 Requirement validation is ensuring that the project which we build for client is
having all necessary requirement of client and unnecessary requirement is not
accomplished. So we have gathered all requirements of client and ensure that all
requirements are meeting the needs of our project. And we also validate all
requirement of client.

4.4 Features of New system:
 Customer can have access to the web page, so they can find nearest hotel easily.
 Customer can easily book the tours and events.
 User account: The application allows the user to create their accounts in the system
and provide features of updating and viewing profiles.
 Search: search is simply local search engine based on key words.
 Discussion Forum: Provides users with a platform to discuss and help each other with
their problems.

4.5 For CONVENTIONAL approach:
4.5.1 Process Flow Diagram:

START
YES
REGISTERED ? LOGIN
NO
REGISTRATION FORM AUTHENTICATION
REGISTRATION
SUCCESFULL
SEARCH PLACE VIEW PLACE
SEARCH BOOK PACKAGE

PACKAGE
SEARCH EVENT
BOOK EVENT
MANAGE
VIEW PROFILE
PROFILE
VIEW HISTORY
FEEDBACK
END
4.5.2 Context Diagram:

REGISTRATION
LOGIN
LOGIN
MANAGE USER
MANAGE PROFILE
ADD PACKAGE
BOOK PACKAGE
SUCESSFULLY ADDED
BOOKING RECEIPT
BOOK EVENT DÉRIVE AHMEDABAD ADD EVENT
USER BOOKING RECEIPT SUCESSFULLY ADDED ADMIN
SEARCH HISTORY MANAGE BOOKING
RESPONCE MANAGE PROFILE
VIEW HISTORY MANAGE HOTELS
VIEW PROFILE VIEW FEEDBACK
FEEDBACK
4.5.3 Data Flow Diagram :
LEVEL-0
REGISTRATION
LOGIN
LOGIN
MANAGE USER
MANAGE PROFILE
MANAGE PLACE
SEARCH PLACE MANAGE PACKAGE
SEARCH PACKAGE DÉRIVE AHMEDABAD MANAGE EVENT

USER MANAGE PROFILE ADMIN
BOOK PACKAGE
SEARCH EVENT MANAGE BOOKING
BOOK EVENT MANAGE HISTORY
VIEW HISTORY VIEW FEEDBACK
VIEW PROFILE MANAGE HOTEL
FEEDBACK
4.5.3.1 DFD Level - 1 booking event:

BOOK
BOOKING ACCEPT BOOK EVENT

USER
CALL NUMBER
4.5.3.2 DFD Login -1 login side:
USER ID ADMIN ID
PASSWORD LOGIN PASSWORD

USER ADMIN
4.5.3.3 DFD Login -1 Manage Hotel:
ADD HOTEL
ADD HOTEL ADDRESS MANAGE HOTEL

ADMIN
MANAGE HOTEL BOOKING
4.5.3.4 DFD Login -1 Manage Profile:

CHANGE USER_ID CHANGE ADMIN_ID
CHANGE ADDRESS MANAGE PROFILE CHANGE PASSWORD

USER ADMIN
CHANGE PASSWORD
4.5.3.5 DFD Login -1 Search Place:
VIEW NAME
VIEW E-MAIL ID VIEW PROFILE

USER
VIEW ADDRESS
4.5.4 ER Diagram:

TOUR BOOKING HOTEL BOOKING

TOUR
EVENT
FEEDBACK / ADMIN_ID PASSWORD
COMPLAINTS
EVENT
REGISTRATION HISTORY MANAGE
MANAGE MANAGE_USER
PROFILE
USER ADMIN_ID
CONTACT
USER_NAME DO HAS ADMIN
Input Input
CONTACT E-MAIL ID
Output Output
PASSWORD
FORGOT
PASSWORD
CHANGE
PASSWORD
SEQURITY
QUESTION QUESTION
DO DO
USER_ID
BIRTH_DATE ANSWER
USER_NAME USER_ID
FIRST_NAME SEQURITY
QUESTION
LOGIN
LAST_NAME REGISTRATION
PASSWORD
EMAIL_ID
EMAIL_ID PASSWORD
ADDRESS
GENDER LAST_NAME
CONTACT
MALE STATE
CITY
FEMALE
COUNTRY

CHAPTER 5: SYSTEM DESIGN
5.1 Database Design:

 Database is an integrated collection of data and provides a centralized access to the

data and makes possible to treat data as a separate resource. Usually centralized data
managing software is called a Relational Database Management System (RDBMS).
The most significant different between RDBMS and other type of Data Management
is the separation of data as seen by the program and data as store of on the direct
access storage device. This is the difference between logical and physical data.
5.2 Database Design – Data Dictionary:
5.2.1 Registration Table :
Field
Field Name Data Type Length Constraints Description
Name Varchar 2 30 Not Null Full name of user
Username Varchar 2 30 Primary Key Unique id of user
E-mail_ID Varchar 2 30 Not Null E-mail ID of the user
Password Varchar 2 30 Not Null Password of the user
5.2.2 Admin Login Table :
Field Name Data Type Field Length Constraints Description

Admin_id Varchar 2 30 Primary Key Admin id
Password Varchar 2 30 Not Null Password of the admin
5.2.3 Search Events Table :

Admin_id Varchar 2 30 Foreign Key Admin id
Event_id Integer 10 Not Null Unique id of the event
Event_name Varchar 2 30 Not Null Name of the event
Event_info Varchar 2 30 Not Null Information of the event
5.2.4 Feedback Table :

Name Varchar 2 30 Not Null Name of the user

Date Date and Time 10 Not Null Date

Email_id Varchar 2 30 Not Null E-mail of the user
User_ID Varchar 2 30 Foreign Key Id of the user
Subject Varchar 2 50 Not Null Subject of the feed back
Description Varchar 2 150 Not Null Detail description about feedback
5.2.4 Change Password Table :

User_ID Varchar 2 30 Foreign Key User id
Old_Password Varchar 2 30 Not Null Old password of the user
New_Password Varchar 2 30 Not Null New password of the user
Confirm_Password Varchar 2 30 Not Null Confirmation of the new password

CHAPTER 6: LIMITATION AND FUTURE ENHANCEMENT
1. Limitation:

 This application would be useful among the people who use Smartphone and internet
on regular basis. For illiterate people and who do not use Smartphone reduce the
efficiency of application.
 It Is Available From Only Mobiles And Laptops.
 Needs a lot of manual work.
 Takes more time.
 location based system needs to be improve by accuracy
2. Future enhancement:
 More locations and tours can be added in our database which indicates more
availability of service providers.
 Expanding our services in other regions can help more users.
 With every updates we'll expand our services as per the feedbacks we receive from
the users.
 We’ll try to make our system automatic so that user can directly know of the nearby
event providers instead of someone guiding them, which will minimize the work for
humans at some point and also the work time for finding services will also be
improved..

CHAPTER 7: CONCLUSION AND DISCUSSON

7.1 Self-analysis of project viabilities
 The project is fulfilling all the requirements given by organization. According to

organization requirement, the design is made very much user friendly. Each part of
user authentication is made very carefully to avoid maximum unauthorized access to
website. No one can directly use the website. He must require authenticating himself
to use website. We can say that our project work is satisfying all the viabilities of the
project required by organization.
7.2 Problem encountered and possible solutions
 During project development, we have found many errors. Many of them were due to
somewhat misspelling of variables or due to misunderstanding of database paths. The
errors are as follows.
 There are many small Errors like misspell variable name or applied wrong
logic.
Solutions: I’ve used e-book to solve the errors related to PHP.
 Database server is not responding or it may be crash.
Solutions: Restart the server.
 Table not found.
Solutions: In this case, we can check the table name and enter the valid table
name.
 Syntax errors.
Solutions: I’ve used W3Schools to solve the syntax errors related to PHP.
7.3 Summary of project work:
 Currently there are various live systems like bookmyshow.com, redbus.com,

tourism.gov.in etc. That provides details to have event booking, tour booking,
history. But there are not any systems to dedicate to “DERIVE
AHMEDABAD”. Our deriveahmedabad web portal system that allows to users
to search tours, events, history, hotel booking online without go anywhere.

 User can search events by as areas as he/she required as well as. User can book
events as well as and send their quires online on the portal. User can see the
photos of events and get the information of that event. User can book the event
tickets.

CHAPTER 8: REFERENCES

 Websites:ss
 https://en.wikipedia.org/wiki/PHP
 https://www.tutorialspoint.com/uml/uml_process_flow_diagram.htm
 https://www.tutorialspoint.com/uml/uml_dataflow_diagram.htm
 https://www.tutorialspoint.com/uml/uml_context_diagram.htm
 https://www.lucidchart.com/pages/uml-e-r-diagram
 BOOKMYSHOW.COM
 http://redbus.com
 https://makemytrip.com
 Books:
 PHP and MySQL Development
-Luke Welling.
 HTMLAnd CSS Design
-Jon Duckett

APPENDIX 1: Periodic Progress Report
( 1 ) PPR 1
( 2 ) PPR 2
( 3 ) PPR 3
( 4 ) PPR 4

PPR OF MEMBER 1
PPR 1

PPR -2

PPR-3

PPR 4

PPR OF MEMBER 2
PPR 1
PPR 2


PPR 3

PPR 4


PPR OF MEMBER 3
PPR 1

PPR 2

PPR 3

PPR 4

APPENDIX 2 : DESIGN ENGINEERING CANVAS

1: AEIOU CANVAS
2: IDETION CANVAS
3: PRODUCT DEVLPOEMENT CANVAS
4: ENPATHY CANVAS

1: AEIOU CANVAS

2: IDEATION CANVAS
3: PRODUCT DEVELOPMENT CANVAS

4: EMPATHY CANVAS


APENDIX 3 : PSAR REPORT
1: PSAR 1
2: PSAR 2
3: PSAR 3
4:PSAR 4
5: PSAR 5
PSAR OF MEMBER 1
PSAR 1



PSAR 2

PSAR 3


PSAR 4



PSAR 5

PSAR OF MEMBER 2
PSAR 1



PSAR 2


PSAR 3


PSAR 4


PSAR 5


PSAR OF MEMBER 3
PSAR 1


PSAR 2


PSAR 3


PSAR 4


PSAR 5



C.E. DEPARTMENT | AIT

100

Rkpatel 123

Caricato da

Informazioni sul documento

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

Rkpatel 123

Caricato da

Copyright:

Formati disponibili

An UDP Project Report On

AHMEDABAD INSTITUTE OF TECHNOLOGY

GUJARAT TECHNOLOGICAL UNIVERSITY

Bachelor of Engineering (Computer Engineering), has been carried out under my

supervision in Department of Computer Engineering, AHMEDABAD INSTITUTE

OF TECHNOLOGY. Her present work has been found satisfactory.

Guide Name: Asst. Prof. Chintan Nagrecha

Chapter: 3 System Requirements Study 12

Chapter: 4 System Analysis 15

Chapter: 5 System Design 25

Chapter: 6 Limitation and Future Enhancement 28

Chapter: 7 Conclusion and Discussion 30

Appendix 1: Periodic Progress Report 34

Figure No. Name of the figure Page No.

C.E. DEPARTMENT | AIT 2

C.E. DEPARTMENT | AIT 3

1.1 Project summary:

1.2 Project purpose:

1.3 Project scope:

C.E. DEPARTMENT | AIT 4

1.4 Project objective:

1.5 Technology review:

C.E. DEPARTMENT | AIT 5

PHP Stands for:

 PHP stands for Hypertext Preprocessor.

What is the difference between the PHP an HTML?

 HTML files are requested by browsers and return by server.

When to use PHP?

 Creating web pages that contain dynamic contents.

What make PHP a choice among the other scripting language?

 Open source database system.

C.E. DEPARTMENT | AIT 6

Why MYSQL Choose:

 Open source database.

1.6 Literature review

 Study of Current Existing System:

 This site provides location of any accommodation is available in our area.

C.E. DEPARTMENT | AIT 7

CHAPTER 2: PROJECT MANAGEMENT

C.E. DEPARTMENT | AIT 8

2.1 Project planning

2.1.1 Project Development Approach:

Phase of This Model:

 It includes testing, coding and deploying software at the customer site

 Evaluation of software by the customer. Also, includes identifying and monitoring

C.E. DEPARTMENT | AIT 9

When to use Spiral Methodology?

 When project is large

Figure 1 spiral Model

C.E. DEPARTMENT | AIT 10

 It used to large scale project.

2.1.2 Milestones and deliverable:

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

2.1.3 Roles and Responsibilities:

Table 1 Roles & Responsibilities

2.1.4 Group Dependencies:

C.E. DEPARTMENT | AIT 11

2.2 Project scheduling:

2.3 Risk management

C.E. DEPARTMENT | AIT 12

 Risk management is concerned with identifying risks and drawing up plans to

2.3.1 Risk Identification:

 Risk Identification is concerned with discovering possible risk to project. It identifies