Final Year Service Provider Website

An
Industrial Training Report
Submitted to
UKA TARSADIA UNIVERSITY
in partial fulfillment of the requirements for the degree of
Bachelor of Technology
in
Computer Engineering
By
Surbhi P. Thummar (201303100910015)
Pooja V. Pancholi (201303100910036)
Under the Guidance

of
Ms. Shraddha Kothiya
Department of Computer Engineering & Information Technology

Chhotubhai Gopalbhai Patel Institute of Technology
Uka Tarsadia University
Bardoli - 394350
May 2017
CERTIFICATE
This is to certify that project work embodied in this report entitled Industrial
Training as carried out by Surbhi P. Thummar (201303100910015), Pooja V. Pancholi
(201303100910036) under my guidance in partial fulfilment of the degree of Bachelor of
Technology in Computer Engineering, Chhotubhai Gopalbhai Patel Institute of
Technology, UTU, Bardoli during the academic year 2016-2017.
Date:
Place:
Guided By:
_________________ ___________________
Ms. Shraddha Kothiya Ms. Purvi Tandel
Assistant Professor Head of the Dept.,
Department of CE & IT Department of CE & IT
CGPIT, UTU, Bardoli. CGPIT, UTU, Bardoli.
_________________________
Signature of Examiner
Chhotubhai Gopalbhai Patel Institute of Technology

Uka Tarsadia University
Bardoli – 394350
ACKNOWLEDGEMENTS
The satisfaction that accompanies the successful completion of this project would
be incomplete without mentioning the people who made it possible, without whose
constant guidance and encouragement would have made eforts go in vain. I consider
myself privileged to express gratitude and respect towards all those who has guided
through the completion of projects.
I convey thanks to my project guide Ms. Shraddha Kothiya, Computer Engineering
and Information Technology department, CGPIT for providing encouragement, constant
support and guidance which was of a great help to complete this project work
successfully.
I am grateful to my external guide Mr. Prafulla Jagtap, Senior Software Engineer
in SecuremetaSysInfotech Pvt. Ltd. for giving me the support and encouragement that was
necessary for the completion of this project.
I am grateful to Ms. Purvi Tandel, Head of the Department, Computer Engineering
and Information Technology, CGPIT for giving us the support and encouragement that was
necessary for the completion of this project.
I would also like to express my gratitude to Dr. N.C. Shah, Director, Chhotubhai
Gopalbhai Patel Institute of Technology for providing us congenial environment to work
in.
I would like to thank all the faculty members for their patience, understanding and
guidance that gave me strength and will power to work through the long tedious hours
for developing a project and preparing the report.
Last but not the least, I would also like to thank my colleagues, who have co-
operated during the preparation of our report and without them this project has not been
possible. Their ideas helped me a lot to improve my project report.
Surbhi P. Thummar(201303100910015)
Pooja V. Pancholi (201303100910036)
vii
ABSTRACT
GoList is a service provider web application which provides a connection medium or

pathway between users and service providers/sellers without any hassle.The system
allows users to search for the desired services or classifieds relevant to their choices. It
even allows user to post their services or classifieds to be displayed to other users.To
validatory users, it also allows in-app chatting and searching the items based on entered
zip code.To make the process trustful for users in case of hiring a service, user can write
review along with the pictures of that durationaboutthe service on the based of his/her
experience during the service execution. User can also request for certain service
alongwith entering the zip code of the region in which the service is required. The web
application has an administartor portion where the administrator can manage all the of
sections that are executed as a part of front-end. Administrator has rights to manage
service providers, sellers, users, requests, service, classifieds, categories, headings and
titles displayed on front-end, site configurations and admin account.
viii
Table of Contents
Acknowledgements............................................................................................................ vii
Abstract ............................................................................................................................. viii
List of Figures ...................................................................................................................... xi
List of Tables ..................................................................................................................... xiv
Chapter 1 Introduction ................................................................................................... 1
1.1 Overview ............................................................................................................... 1
1.2 Problem Definition ................................................................................................ 1
1.3 Application ............................................................................................................ 1
Chapter 2 Training Activities........................................................................................... 2
2.1 Environmental Setup ............................................................................................. 2
2.2 Version Control System Training ........................................................................... 2
2.3 Core PHP Training.................................................................................................. 2
2.4 PHP Framework Training ....................................................................................... 2
Chapter 3 System Planning ............................................................................................. 3
3.1 Project Development Approach ............................................................................ 3
3.2 System Modules .................................................................................................... 5
3.2.1 Back-end Development.................................................................................. 5
3.2.2 Front-end Development ................................................................................ 5
3.2.3 User Development ......................................................................................... 5
3.3 Functional Requirements ...................................................................................... 6
3.4 Non Functional Requirements .............................................................................. 8
3.5 Timeline Chart ....................................................................................................... 9
Chapter 4 System Design .............................................................................................. 11
4.1 Use Case Diagram................................................................................................ 11

ix
4.2 Sequence Diagram .............................................................................................. 14
4.3 Activity Diagram .................................................................................................. 17
4.4 Class Diagram ...................................................................................................... 22
4.5 Database Schema ................................................................................................ 23
4.6 Data Flow Diagram .............................................................................................. 38
4.7 ER Diagram .......................................................................................................... 45
Chapter 5 Implementation and Testing........................................................................ 46
5.1 Hardware and Software Requirements .............................................................. 46
5.2 Snapshots ............................................................................................................ 47
5.3 Test Cases ............................................................................................................ 81
Chapter 6 Conclusion and Future Scope ...................................................................... 86
Chapter 7 References ................................................................................................... 87
x
LIST OF FIGURES
Figure 3-1 Agile development model .................................................................................. 3
Table 3.3 Functional requirements ...................................................................................... 6
Figure 3-5-1 Timeline chart (January - February) ............................................................... 9
Figure 3-5-2 Timeline chart (February - April) ................................................................... 9
Figure 3-5-3 Timeline chart (April) ................................................................................... 10
Figure 4-1-1 Use case - authentication .............................................................................. 11
Figure 4-1-2 Use case – admin panel ................................................................................. 12
Figure 4-1-3 Use case – guest user .................................................................................... 12
Figure 4-1-4 Use case – registered user ............................................................................. 13
Figure 4-2-1 Sequence diagram – authentication .............................................................. 14
Figure 4-2-2 Sequence diagram – service provider ........................................................... 15
Figure 4-2-3 Sequence diagram – seller ............................................................................ 15
Figure 4-2-4 Sequence diagram – manage accounts.......................................................... 16
Figure 4-3-1 Activity diagram – authentication................................................................. 17
Figure 4-3-2 Activity diagram – manage accounts ............................................................ 18
Figure 4-3-3 Activity diagram – service provider ............................................................. 19
Figure 4-3-4 Activity diagram – seller............................................................................... 20
Figure 4-3-5 Activity diagram – admin side ...................................................................... 21
Figure 4-4 Class diagram ................................................................................................... 22
Figure 4-6-1 Data flow diagram – level 0 .......................................................................... 39
Figure 4-6-2 Data flow diagram – level 1 .......................................................................... 39
Figure 4-6-3 Data flow diagram – level 2( process 1) ....................................................... 40
Figure 4-6-4 Data flow diagram – level 2(process 2 ) ....................................................... 41
Figure 4-6-5 Data flow diagram – level 2(process 3) ........................................................ 42
Figure 4-7 ER diagram....................................................................................................... 45
Figure 5-2-1 Home page - header ...................................................................................... 47
Figure 5-2-2 Home page - listing ....................................................................................... 47
Figure 5-2-3 Home page - footer ....................................................................................... 48
Figure 5-2-4 Zip code ........................................................................................................ 48
xi
Figure 5-2-5 Registration page .......................................................................................... 49
Figure 5-2-6 Login page .................................................................................................... 49
Figure 5-2-7 After login ..................................................................................................... 50
Figure 5-2-8 Activation email ............................................................................................ 50
Figure 5-2-9 Forgot password ............................................................................................ 51
Figure 5-2-10 Email format for forgot password ............................................................... 51
Figure 5-2-11 My account - status and email changing ..................................................... 52
Figure 5-2-12 My account - changing password ............................................................... 52
Figure 5-2-13 My account - activation/deactivation of account ........................................ 53
Figure 5-2-14 Service creation - adding contact details .................................................... 53
Figure 5-2-15 Service creation - choosing travel method .................................................. 54
Figure 5-2-16 Service creation - adding business details .................................................. 55
Figure 5-2-17 Service creation - describing service in details ........................................... 56
Figure 5-2-18 Service creation - uploading service media ................................................ 57
Figure 5-2-19 Service creation - categorize service .......................................................... 58
Figure 5-2-20 Service creation - selected service .............................................................. 59
Figure 5-2-21 Service creation - setting up the social links............................................... 59
Figure 5-2-22 Service details page .................................................................................... 60
Figure 5-2-23 Rating .......................................................................................................... 61
Figure 5-2-24 Reflection of user ratings ............................................................................ 62
Figure 5-2-25 Classified creation - price and product details ............................................ 63
Figure 5-2-26 Classified creation - uploading service media ............................................ 64
Figure 5-2-27 Classified creation - adding contact details ................................................ 65
Figure 5-2-28 Classified listing ......................................................................................... 65
Figure 5-2-29 Deletion of a post ........................................................................................ 66
Figure 5-2-30 Suggesting a friend ..................................................................................... 66
Figure 5-2-31 Chatting - user A ......................................................................................... 67
Figure 5-2-32 Chatting - user B ......................................................................................... 67
Figure 5-2-33 Selecting a favourite classified ................................................................... 68
Figure 5-2-34 Listing of favourite classified ..................................................................... 68
Figure 5-2-35 Entering desired service and zipcode.......................................................... 69
Figure 5-2-36 Entering advanced service description ....................................................... 69
Figure 5-2-37 Requests listing ........................................................................................... 70
xii
Figure 5-2-38 Admin login ................................................................................................ 70
Figure 5-2-39 Admin home ............................................................................................... 71
Figure 5-2-40 Admin site settings...................................................................................... 71
Figure 5-2-41 Admin home content ................................................................................... 72
Figure 5-2-42 Admin social site setting ............................................................................. 72
Figure 5-2-43 Listing users ................................................................................................ 73
Figure 5-2-44 Viewing users ............................................................................................. 73
Figure 5-2-45 Deleting users ............................................................................................ 73
Figure 5-2-46 After deletion of users................................................................................. 74
Figure 5-2-47 Listing categories ........................................................................................ 74
Figure 5-2-48 Viewing categories ..................................................................................... 74
Figure 5-2-49 Editing categories ....................................................................................... 75
Figure 5-2-50 After edition of categories .......................................................................... 75
Figure 5-2-51 Deleting categories ..................................................................................... 76
Figure 5-2-52 After deletion categories ............................................................................. 76
Figure 5-2-53 Listing requests ........................................................................................... 76
Figure 5-2-54 Viewing requests......................................................................................... 77
Figure 5-2-55 Deleting requests......................................................................................... 77
Figure 5-2-57 Listing FAQs............................................................................................... 78
Figure 5-2-58 Viewing FAQs ............................................................................................ 78
Figure 5-2-59 Editing FAQs .............................................................................................. 78
Figure 5-2-60 After edition of FAQs ................................................................................. 79
Figure 5-2-61 Deleting FAQs ............................................................................................ 79
Figure 5-2-62 After deletion of FAQs ............................................................................... 79
Figure 5-2-63 Listing emails .............................................................................................. 80
Figure 5-2-64 Editing emails ............................................................................................. 80
xiii
LIST OF TABLES
Table 3.3 Functional requirements ...................................................................................... 6
Table 4.5.1 Categories table............................................................................................... 23
Table 4.5.2 Cities table ...................................................................................................... 23
Table 4.5.3 Cometchat table .............................................................................................. 24
Table 4.5.4 Cometchat_golist_mapping table ................................................................... 24
Table 4.5.5 Cometchat_users table .................................................................................... 25
Table 4.5.6 Contents table ................................................................................................. 25
Table 4.5.7 Email_layouts table......................................................................................... 26
Table 4.5.8 Email_templates table ..................................................................................... 26
Table 4.5.9 Favorites table ................................................................................................. 26
Table 4.5.10 Posts table ..................................................................................................... 27
Table 4.5.11 Post_delete_reasons table ............................................................................. 29
Table 4.5.12 Post_images table ......................................................................................... 29
Table 4.5.13 Provider_ratings table ................................................................................... 29
Table 4.5.14 Provider_rating_images table ....................................................................... 30
Table 4.5.15 Provider_reviews table ................................................................................. 31
Table 4.5.16 Requests table ............................................................................................... 31
Table 4.5.17 Service_provider_images table ..................................................................... 32
Table 4.5.18 Service_providers table................................................................................. 33
Table 4.5.19 Service_provider_categories_list table ......................................................... 36
Table 4.5.20 Site_settings table ......................................................................................... 36
Table 4.5.21 Users table..................................................................................................... 37
Table 4.5.22 User_deactivate_reasons table ...................................................................... 38
Table 5-3 Test cases ........................................................................................................... 81
xiv
CHAPTER 1 INTRODUCTION
1.1 Overview
GoList is a service provider web application which provides a medium for the buyers and
sellers of a specific type of product to get into communication. It acts as a pathway for
communication between the two parties.It also allows a verified user to post services
which includes posting videos and images of the service they want to provide. For
example,if User A owns a car washing company, he can promote his services through
images and videos. User B, who wants his car washed can have featured access to chat
online with the service provider or can contact him directly using certain communication
medium such as email , contact number or his business address, in order to fulfill the deed.
1.2 Problem Definition

Nowadays, if you want to get a product online, you don’t trust online shopping really
easily. You might have a fear whether the product you are going to buy is identical or
would be fake. The main motive of the project is to ensure trust and originality amongst
buyers by having them view the video of the product they are going to buy. In this case
they can have clear idea about what kind of product they are going to buy. Also it provides
a common platform for people to have access to contact of different kinds of service
providers providingday-to-day services house cleaning, gardening, security, car washing
etc. and services like makeover, party rentals, pet grooming etc.that are existing in your
nearby regions.
1.3 Application
The motive of this project is to bring up the small scale companies who requires promotion
of their services and wants a medium to promote them. It also provides seekers with a
user friendly experience in order to seek the identicalservice they are looking for.
1
CHAPTER 2 TRAINING ACTIVITIES
2.1 Environmental Setup

It is necessary that we adapt Ubuntu-Linux environment. So we installed lamp stack to our
system for web development and php storm and sublime text editor. We also have to
work on our company’s local repository so we also installed git into our system.[1] It is
also necessary that we upload our work to company’s demo server so we have also
installed FTP Client in to our system.[2]
2.2 Version Control System Training

When working with a team, it is very necessary for all the team members to stay on the
same page in order to avoid conflicts and issues. In context of that, we use Apache
Subversion, to keep all the developers in a team up-to-date with the project’s working
copies.[3] In case of conflicts or issues we can revert the last change / commit.
2.3 Core PHP Training

In order to work with and understand the flow of different frameworks that we learn in
the company, initially we had learnt different core concepts that could help us go along
with the future projects. Amongst such concepts, we learnt:
 Session / Cookie Management [4]

 Ajax and jSon Parsing [4]
 cUrl [4]
 MySql Database handling and Email sending [4]
 Bootstrap integration [5]
2.4 PHP Framework Training

In order to adapt RAD behavior of our company we learned two versions of CakePhp (2
and 3) which were based on MVC architecture. In this period of training we learnt different
aspects like naming conventions, authentication, validation, bootstrap integration,
plugins and helpers, generating jSon response and framework related syntax. [6]
2
CHAPTER 3 SYSTEM PLANNING
3.1 Project Development Approach

GoList uses agile development model. Agile model believes that every modules needs to
be handled differently and the existing methods need to be tailored to best suit the
project requirements. In Agile, the tasks are divided to time boxes (small time frames) to
deliver specific features for a release. Iterative approach is taken and working software
build is delivered after each iteration. Each build is incremental in terms of features; the
final build holds all the features required by the client. Here is the graphical representation
of agile development model.
Figure 3-1 Agile development model
Agile model is based on the adaptive software development methods, whereas the
traditional SDLC models like the waterfall model is based on a predictive approach.
Predictive teams in the traditional SDLC models usually work with detailed planning and
have a complete forecast of the exact tasks and features to be delivered in the next few
months or during the product life cycle.
3
Predictive methods entirely depend on the requirement analysis and planning done in the
beginning of cycle. Any changes to be incorporated go through a strict change control
management and prioritization.
Agile uses an adaptive approach where there is no detailed planning and there is clarity
on future tasks only in respect of what features need to be developed. There is feature
driven development and the team adapts to the changing product requirements
dynamically. The product is tested very frequently, through the release iterations,
minimizing the risk of any major failures in future. Customer Interaction is the backbone
of this Agile methodology, and open communication with minimum documentation are
the typical features of Agile development environment. The agile teams work in close
collaboration with each other and are most often located in the same geographical
location.
Agile methods are being widely accepted in the software world recently. However, this
method may not always be suitable for all products. Here are some pros and cons of the
Agile model.
The advantages of the Agile Model are as follows −
 Is a very realistic approach to software development.
 Promotes teamwork and cross training.
 Functionality can be developed rapidly and demonstrated.
 Resource requirements are minimum.
 Suitable for fixed or changing requirements
 Good model for environments that change steadily.
 Minimal rules, documentation easily employed.
 Enables concurrent development and delivery within an overall planned context.
 Little or no planning required.
 Easy to manage.
 Gives flexibility to developers.
4
3.2 System Modules

There are three modules in GoList web application. They are divided on the basis of the
project’s User Interface flow as follows:
 Back-end Development
 Front-end Development
 User Development
3.2.1 Back-end Development
The user who logs in to the web application as an administrator gets access to the back-
end of it. The back-end of GoList gives the administrator the priviledges to have acces to
all the content that has been shown on the front-end user interface. Only administrator
has the right to edit the content that has been posted by any of the users that have
registered themselves with the GoList.
The social site configurations and the application related API keys can also be changes
only by the administrator. The categories that have been viewed on the front-end can be
modified by the administrator. If a service provider or seller do not get a specific category
to post their classifieds, they can contact using the support email and the administrator
can add their relevant categories and it will get reflected on the front-end.
3.2.2 Front-end Development
The visitor who visits the web application has access to the front-end guest user
functionalities. He comes across a modal popup which will ask him to enter the regional
zip code. After entering the zip code, the visitor can have featured listings of the services
and classifieds with nearest distances and highest rankings. The front-end also includes
categorized search of classifieds and different services with categories likely to be
searched.
3.2.3 User Development
The user development manages three aspects. It categorizes user into three: Visitor/Guest
user, Service provider and seller. The guest user as per the name do not need to be a
registered user to have access to the web application. i.e such user will be the seeker of
service or product. He has the right to view the product and contact the seller of the
5
product. He also has the right to view different services over the web application and
contact their providers. The communication medium can be email, contact number or
through online chatting (in-app feature).He can also review the service which he had
experienced to make it easy for other users to know the quality of the service. User as
service provider has been provided three facilities where he can create a single service
through which he can serve several users, he can respond the customer reviews and on
the basis of request list he can provide services to the seeker. User as seller has been
provided the facility to post his classified with videos and images and also has the right to
chose whether he wants to sell the product or not.
3.3 Functional Requirements

Table 3.3 Functional requirements
Sr. No Title and Description
FR #0 Title: Registration
Description:To have access to the GOLIST functionalities, you must register

yourself.After registration you will be provided with a verification link in your email
which will verify you as a legitimate user. You can thereafter have access to the web
application.
FR #1 Title: Login
Description:For having access to the in-app features, user must enter the credentials
that the sign in form ask for. Once authenticated, user can have access to web
application’s features.
FR #2 Title: Email
Description:To send verification emails. When user forgets password. When user
wants to change the email. When sending link to a friend. When new category gets
added.
6
FR #3 Title: Video / Image Upload
Description:This function is used by the web application in the following cases:

1. While creating a service.
2. While creating a classified.
FR #4 Title: Google Map API
Description:This function is used by the web application in the following cases:

1. Entering the zip code for location of user.
2. During creation of service (when user has to address business address).
FR #5 Title: Chat
Description:This function is used by the web application when a user who is logged
in wants to chat with a service provider or seller.
FR #6 Title: Admin
Description:A user who logs ino the system as admin has the following priviledges:
1. He can manage users, cities, categories, services, posts, requests.
2. He also has right to change how few things on the front end will be displayed.
3. He can set the API settings for different plugins used.
4. He can change the format of the emails sent.
FR #7 Title: Searching
Description: A user can search for a classified through the searching functionality
provided on the front end header section. On the basis of search value inserted, the
resultant classifieds will be listed.
FR #8 Title: Location
Description: User's current location will always be tracked when user enters the zip
code and accordinglythe classified featured listing will be done on front end page
along with mile calculation of the relevant post.
FR #9 Title: Manage Account
7
Description: In Manage Accountsettings section, user will able to change email

address or password, select online status or deactivate/activate account.
FR #10 Title: Requesting
Description : If a user does not want to search manually all the categories area
wise, user can request using the header page’s “Get your things done” section.
FR #11 Title: Favourites listing
Description:If a user wants to save a video with intention of viewing in future, user
can add the video to favourites list.
FR #12 Title: Logout
Description: If a user wants to make his web application account inaccesible by

intruders , he is required to logout from the web application.
3.4 Non Functional Requirements

PORTABILITY: This is a responsive and cross platform web service. Different users can
easily communicate and exchange messages. In any case of urgencies if user has any
web browser he/she can access or use this web service.
PERFORMANCE: This web service uses minimum page load time. If internet speed is
good, then audio and video quality will be better.
RELIABILITY: The web service works very well depending on the speed of the internet
and it functions properly as per its scope.
8
3.5 Timeline Chart
Figure 3-5-1 Timeline chart (January - February)
Figure 3-5-2 Timeline chart (February - April)
9
Figure 3-5-3 Timeline chart (April)
10
CHAPTER 4 SYSTEM DESIGN
4.1 Use Case Diagram
Figure 4-1-1 Use case - authentication
Figure 4-1-1 depicts the use case interaction between the visior and the web application.
For registering with the web application, user must fill the necessary details that are valid
according to the format. After filling the details, user will recieve a verification email on
the registered email. User must click on the verification link to activate the registered
account. After the verification link is clicked, user information is added to the database.
For logging into the account, user must enter the credentials that he filled during the
registeration process. After the credentials match with the database record values, user
can access the account. In case user does not remember the password, user is required to
enter the registered email. User will recieve a random generated password using which
user can have access to the account.
11
Figure 4-1-2 Use case – admin panel
Figure 4-1-2 depicts the usecase interaction of administrator. Administrator can perform
necessary add/update/delete operations in order to manage users, categories, cities,
service providers, email templates, site configurations, front-end content and requests.
Figure 4-1-3 Use case – guest user
Figure 4-1-3 depicts the usecase interaction of a guest user. Guest user can view or search
the classifieds displayed on the front-end.
12
Figure 4-1-4 Use case – registered user
Figure 4-1-4 depicts the use case interaction of a registered user. Registered user can be
classifed as either service provider or seller. A service provider can either create a service
or manage his account. User needs to enter details such as contact number, address,
service description, upload image/video, categories of service and social links for creating
a service.
13
4.2 Sequence Diagram
Figure 4-2-1 Sequence diagram – authentication
Figure 4-2-1 shows the sequence diagram for Authentication in which user needs to fill
required details and verify by clicking on a link received through email. User will then
redirect to started page. If user is alreasy registered then user has to login by entering
email and password which will be check with original details and then redirect to started
page. If user forgot the password, then user needs to enter email and on that email user
will receive random generated password from server.
14
Figure 4-2-2 Sequence diagram – service provider
Figure 4-2-2 shows the sequence diagram for Service Provider in which for creating a
service user has to enter details such as contact, address, product description, upload
image/video, category by service and social group links. For viewing service info, user has
to click on service provider button which redirects user to service information page.
Figure 4-2-3 Sequence diagram – seller
Figure 4-2-3 shows the sequence diagram for Seller in which for creating a classified user
needs to enter product details, upload image/video, contact details which will send on the
server and product details will be added to the database. By clicking on classified button
user will be able to view classified info.
15
Figure 4-2-4 Sequence diagram – manage accounts
Figure 4-2-4 shows the sequence diagram for Manage Accounts in which user can change
password, change email and also deactivate the account.
16
4.3 Activity Diagram

Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system.So the
control flow is drawn from one operation to another. This flow can be sequential,
branched or concurrent. Activity diagrams deals with all type of flow control by using
different elements like fork, join etc.
Figure 4-3-1 Activity diagram – authentication
Figure 4-3-1 shows the activity diagram for Authentication in which if user is registered
then user needs to login with valid credentials and will logged in to the application. If not
registered, then user has to register first. For forgot password user needs to enter email
on which user will receive random generated password.
17
Figure 4-3-2 Activity diagram – manage accounts
Figure 4-3-2 shows the activity diagram for Manage Accounts. After login into the system,
user clicks on setting option and after that user can change the password, email and
deactivate the account.
18
Figure 4-3-3 Activity diagram – service provider
Figure 4-3-3 shows the activity diagram for Service Provider in which after doing login, if
user has already created the service then user can get access to service information page
else user has to create a new service by filling required details.
19
Figure 4-3-4 Activity diagram – seller
Figure 4-3-4 shows the activity diagram for Seller. User as seller can create a new product
classified by entering details for creation and if already created then user can get access
to product listing page.
20
Figure 4-3-5 Activity diagram – admin side
Figure 4-3-5 shows the activity diagram for Admin. Admin manages users,categories,
clients, service providers, email templates, site configs, front end content, classified posts
and requests by doing insertion, updation and deletion, also admin can display records.
21
4.4 Class Diagram
Figure 4-4 Class diagram
Figure 4-2-3 shows the class diagram for GoList. Figure shows the interaction amongst
different classes such as users, service providers ratings, service providers images, service
providers categories, post images, cometchat, cometchat golist mapping, categories and
favourites, their relations, attributes and operations.
22
4.5 Database Schema

Table 4.5.1 Categories table
Column Name Data Type Size Constraint Description
Id INT 11 Primary Key ID No.
Name VARCHAR 255 Foreign Key Category name
Type VARCHAR 50 Foreign Key Category type
keyword TEXT - - Category

keyword
parent_id INT 11 - Belongs to
show_home TINYINT 1 - Shown on main

page or not
order_rank INT 11 - Rank of

category
active TINYINT 1 - Status
Table 4.5.2 Cities table
City VARCHAR 200 - City name
zipcode VARCHAR 5 - Zipcode
23
Table 4.5.3 Cometchat table
Form INT 10 Foreign Key From name
To INT 10 Foreign Key To name
message TEXT - - Message detail
sent INT 10 Foreign Key Sent on
read TINYINT 1 Foreign Key Read or not
is_deleted INT 1 - Deleted or not
Table 4.5.4 Cometchat_golist_mapping table
type ENUM - - Mapping type
user_id INT 40 - User ID
reference_user_id INT 40 - Opposite user

ID
chat_id INT 40 - Chat ID
created DATETIME - - Created on
updated DATETIME - - Updated on
24
Table 4.5.5 Cometchat_users table
userid INT 11 Primary Key User ID
username VARCHAR 100 Foreign Key User name
displayname VARCHAR 100 - Display name
password VARCHAR 100 - Password
avatar VARCHAR 200 - Image path
link VARCHAR 200 - Link to chat
grp VARCHAR 25 - Belongs to

group
friends TEXT - - Friend id
Table 4.5.6 Contents table
page_name VARCHAR 255 - Front end page

name
page_heading VARCHAR 255 - Front end page

heading
content TEXT - - Front end page

content
25
Table 4.5.7 Email_layouts table
id INT 11 Primary Key ID No.
name VARCHAR 255 Foreign Key Name of email
body TEXT - - Body of email
status ENUM - - Statcu
Table 4.5.8 Email_templates table
name VARCHAR 255 - Name of email

template
subject VARCHAR 255 - Subject of

template
content TEXT - - Content
Table 4.5.9 Favorites table
26
service_id INT 11 - Service ID
Type ENUM - - Type of service
Table 4.5.10 Posts table
category_id INT 11 - Category ID
provider_id INT 11 - Provider ID
date_of_post DATETIME - Date of posting

classified
city VARCHAR 255 - City
state VARCHAR 255 - State
zipcode VARCHAR 50 - Zipcode
title VARCHAR 255 - Title of

classified
description TEXT - - Description of

classified
email VARCHAR 255 - Email address
phone VARCHAR 255 - Contact no
contact_name VARCHAR 255 - Name
27
contact_address TEXT - - Address
price DOUBLE - - Price
image1 VARCHAR 255 - Image path
video TEXT - - Video path
video_type VARCHAR 25 - Type of video
video_thumb VARCHAR 255 - Wideo

thumbnail
is_sold TINYINT 1 - Sold or not
end_date DATE - - End date of

selling
for_sale TINYINT 1 - Type of post
is_personal TINYINT 1 - Type of post
is_housing TINYINT 1 - Type of post
is_job TINYINT 1 - Type of post
is_active TINYINT 1 - Status
spam INT 11 - Fake or not
latitude VARCHAR 700 - Location
longitude VARCHAR 700 - Location
28
video_upload_at DATETIME - - Uploaded at
updated DATETIME - - Updated at
Table 4.5.11 Post_delete_reasons table
post_id INT 40 - Post ID
question TEXT - - Question value
answer TEXT - - Answer value
Table 4.5.12 Post_images table
post_id INT 11 - Post ID
image VARCHAR 255 - Image path
Table 4.5.13 Provider_ratings table
ip_address VARCHAR 255 - IP address
29
score INT 11 - Score of rating

total
quality INT 11 - Quality rate
speed INT 11 - Speed rate
price INT 11 - Price rate
avg_rate DOUBLE - - Average rate
date DATE - - Date
name TEXT - - Name of rater
comment TEXT - - Comment

detail
reply_content TEXT - - Content of

reply
reply_date DATETIME - - Replied on
Table 4.5.14 Provider_rating_images table
service_provider_id INT 11 - Provider ID
30
provider_rating_id INT 11 - Provider

rating ID
Table 4.5.15 Provider_reviews table
ip_address VARCHAR 255 - IP address
title VARCHAR 60 - Title
review VARCHAR 200 - Review

description
Table 4.5.16 Requests table
category_id INT 11 - Category ID
zip_code VARCHAR 50 - Zipcode
31
longitude VARCHAR 50 - Location
state VARCHAR 200 - Location
city VARCHAR 200 - Location
contact_address TEXT - - Address
contact_name VARCHAR 700 - Name
phone VARCHAR 255 - Contact
email VARCHAR 255 - Email address
description TEXT - - Description
is_active INT 1 - Status
is_send INT 1 - Sent or not
Table 4.5.17 Service_provider_images table
is_primary_image TINYINT 4 - Image ID
32
Table 4.5.18 Service_providers table
first_name VARCHAR 255 - First name
last_name VARCHAR 255 - Last name
email VARCHAR 255 - Email

address
password VARCHAR 255 - password
business_name VARCHAR 255 - Business

name
customer_travel TINYINT 4 - Travel option
service_provider_travel TINYINT 4 - Travel option
street_address TEXT - - Address
state VARCHAR 255 - State
city VARCHAR 255 - City
zip_code VARCHAR 50 - Zipcode
phone VARCHAR 255 - contact
travel_distance INT 11 - Distance
longitude VARCHAR 50 - location
33
reg_date DATETIME - - Registered

on
about TEXT - - description
website1 TEXT - - Website path
website8 TEXT - Website path
image VARCHAR 255 - Image
image2 VARCHAR 150 - Image
image3 VARCHAR 150 - Image
video TEXT - - Video path
video_type VARCHAR 100 - Video

extension
video_thumb TEXT - - Thumbnail

path
categories TEXT - - List of

categories
34
avg_rating DOUBLE - - Rating

average
total_reviews INT 11 - Review total
is_active TINYINT 1 - Status
spam INT 11 - Fake or not
show_admin TINYINT 1 - Admin

viewed or
not
username VARCHAR 255 - Username
score_rating DOUBLE - - Score rate
speed_rating DOUBLE - - Speed rate
price_rating DOUBLE - - Price rate
quality_rating DOUBLE - - Quality rate
rate1_total INT 10 - Total rating

individually

individually

individually

individually

individually
35
video_upload_at DATETIME - - Video

uploaded on
Table 4.5.19 Service_provider_categories_list table
categorie_id INT 11 - Category ID
Status TINYINT 4 - Status
Table 4.5.20 Site_settings table
paypal_email VARCHAR 100 - Api setting
admin_email VARCHAR 100 - Admin email
phone VARCHAR 18 - Phone no
address TEXT - - Address
longitude VARCHAR 50 - Longitude
36
support_email VARCHAR 50 - Support Email
cat_allowed INT 11 - Max category

allowed
default_lang VARCHAR 2 - Language
site_logo TEXT - - Logo image
maximum_request INT 44 - Max request

allowed
Table 4.5.21 Users table
service_provider_id INT 11 - Service ID
first_name VARCHAR 255 - First name
last_name VARCHAR 255 - Last name
email VARCHAR 255 - Email
username VARCHAR 255 - Username
password VARCHAR 255 - Password
is_active INT 1 - For status
is_admin TINYINT 1 - For role
is_online ENUM - - For account
facebook_id VARCHAR 255 - social signup
facebook_access_token TEXT - - social signup
37
google_id VARCHAR 255 - social signup
google_access_token TEXT - - social signup
new_email VARCHAR 700 - Change email
Table 4.5.22 User_deactivate_reasons table
user_id INT 40 - User ID No.
question TEXT - - Question value
answer TEXT - - Answer value
take_action VARCHAR 700 - Action to take
created DATETIME Created on
4.6 Data Flow Diagram
Data Flow Diagrams (DFDs) model that perspective of the system that is most readily
understood by users – the flow of information around the system and the activities that
process this information.
Data Flow Diagrams provide a graphical representation of the system, which aims to be
accessible to computer specialist and non-specialist users alike. The models enable
analysts and users to work together effectively, during the analysis and specification of
requirements.
38
Figure 4-6-1 Data flow diagram – level 0
Figure 4-6-1 shows the Context level or 0 level Data Flow Diagram in which user browse
for the services and service provider/seller will provide the service and post.
Figure 4-6-2 Data flow diagram – level 1
39
Figure 4-6-2 shows the 1st level DFD. Here it is shown that how user interacts with the
whole system for fulfilling particular tasks or process.
Figure 4-6-3 Data flow diagram – level 2( process 1)
Figure 4-6-3 shows the DFD for process 1.0 - Signup. Here user will enter details, will
received an activation link on email and by clicking on that email will be verified, gets
redirected to the started page.
40
Figure 4-6-4 Data flow diagram – level 2(process 2 )
Figure 4-6-4 shows the DFD for process 2.0 – Sign in. Here, user needs to enter email and
password which will verified with database details. If user forgots the password, user is
required to enter the email id on which user will receive random password.
41
Figure 4-6-5 Data flow diagram – level 2(process 3)
Figure 4-6-5 shows the DFD for process 3.0 – Browse the Service. Here user can search the
service based on zipcode or categories.
42
43
Figure 4-6-6 shows the DFD for process 4.0 – Become Service Provider/Seller. In this user
can add service provider details with asked details and also can add classified details with
required fields asked.
Figure 4-6-7 shows the DFD for process 5.0 – Communication. In this user can
communicate with other user through chat plugin and data will get store into the
database.
44
4.7 ER Diagram
Figure 4-7 ER diagram
Figure 4-7 shows the Entity Relationship diagram in which there are entities such as users,
service, posts, favourites, categories and commetchat session. Here user can creates
services, posts, add videos to favourites, chat using commetchat and searched categories
according to requirement.
45
CHAPTER 5 IMPLEMENTATION AND TESTING
5.1 Hardware and Software Requirements
SOFTWARE REQUIREMENTS
 Operating Systems like windows and linux

 Network
 Web Browsers like google chrome and mozilla firefox
 PHP extensions and settings
HARDWARE REQUIREMENTS
 Recommended higher resolution monitor for display

 Recommended minimum CPU – Pentium 4,3.2 GHz
46
5.2 Snapshots
 Home Page
Figure 5-2-1 Home page - header
 Figure 5-2-1 Provides functionality to the list your video classifieds and search a service
using zip code.
Figure 5-2-2 Home page - listing
 Figure 5-2-2 provides list of featured classifieds and services.
47
Figure 5-2-3 Home page - footer
 Figure 5-2-3 provides help Videos to understand the GoList concept.
 Zip Code
Figure 5-2-4 Zip code
 Figure 5-2-4 allows user to identify where exactly the service relies from the zip code
location.
48
 Registration Page
Figure 5-2-5 Registration page
 Figure 5-2-5 allows visitor to become legitimate user of the web application.
 Login Page
Figure 5-2-6 Login page
 Figure 5-2-6 allows user to have access to the in-app facilities.
49
 After Login
Figure 5-2-7 After login
 In Figure 5-2-7 user will be redirected to the getting stared page where you can chose
between selling or service providing and Figure 5-2-8 shows email received by the visitor.
 Activation Mail
Figure 5-2-8 Activation email
50
 Forgot Password
Figure 5-2-9 Forgot password
 In Figure 5-2-9 user has to enter his email address , in case of forgotten password.
 Random Password Send through Email
Figure 5-2-10 Email format for forgot password
 In Figure 5-2-10 User will recieve an email with new password (random generated).
51
 My Account
Figure 5-2-11 My account - status and email changing
Figure 5-2-12 My account - changing password
52
Figure 5-2-13 My account - activation/deactivation of account
 In My account section, user can set online status, change email address , change
password, or deactivate account.
 Creating a Service (Contact Details)
Figure 5-2-14 Service creation - adding contact details
 Figure 5-2-14 depicts step 1 of creating a service where user is required to enter contact
details.
53
 Creating a Service (Servicing Type)
Figure 5-2-15 Service creation - choosing travel method
 Figure 5-2-15 depicts the second step of creating a service where user has to choose the
alternative in order to provide service accordingly.
54
 Creating a Service (Map Integration)
Figure 5-2-16 Service creation - adding business details
 Figure 5-2-16 depicts the thirs step of creating a service where if user chooses "I travel
to my customers" in the previous step, in that case only the miles section will appear.
55
 Creating a Service (Service Details)
Figure 5-2-17 Service creation - describing service in details
 Figure 5-2-17 depicts the fourth step of creating a service where user is required to
describe the service in detail.
56
 Creating a Service (Image and Video Upload)
Figure 5-2-18 Service creation - uploading service media
 Figure 5-2-18 depicts the fifth step of creating a service where user is required to
upload images and videos relevant to the service provided.
57
 Creating a Service (Category Selection)
Figure 5-2-19 Service creation - categorize service
 Figure 5-2-19 and 5-2-20 depicts the sixth step of creating a service where user is
required to select the categories relevant to the service provided.
58
Figure 5-2-20 Service creation - selected service
 Creating a Service (Social Link Setting)
Figure 5-2-21 Service creation - setting up the social links
 Figure 5-2-21 depicts the sixth step of creating a service where user can add social
pages of the service (if any).
59
 Creating a Service (Resulting Detail Page)
Figure 5-2-22 Service details page
 According to Figure 5-2-22user after creating a service will have access to the service
dashboard.
 The service dashboard contains two main units:
o It will display other user ratings and reviews on the service
o It will display the categories under which the service falls
60
 Rating Management
Figure 5-2-23 Rating
 Other legitimate users or guest users can rateto a service on the basis of four
parameters: speed, quality, service and value along with service experinece images.
61
Figure 5-2-24 Reflection of user ratings
 The ratings and reviews will get affected as shown in the Figure 5-2-24.
62
 Creating a product(Category Description)
Figure 5-2-25 Classified creation - price and product details
 Figure5-2-25 depicts the first step of creation of product classified where user is
required to fill all details in order to categorize the product.
 On the basis of this category selection, user will be able to add the product classified
in front end categorized search.
63
 Creating a Product(Image and Video Upload)
Figure 5-2-26 Classified creation - uploading service media
 Figure 5-2-26 depicts the second step of creation of product classified where user is
required to upload images and videos relevant to the product.
 A user can upload a maximum of 12 images and a video.
64
 Creating a Service (Contact Details)
Figure 5-2-27 Classified creation - adding contact details
 Figure 5-2-27 depicts the third step of creation of product classified where user is
required to enter contact details. On completion user’s classified will be created and
listed as shown in Figure 5-2-28.
Figure 5-2-28 Classified listing
65
 Deleting the Post
Figure 5-2-29 Deletion of a post
 User is required to fill the details while deleting the product.
 Send to friend(Details of receiver)
Figure 5-2-30 Suggesting a friend
 User can suggest another user to view the product by sending the product/service link
to his email.
66
 Chat Module( User A )
Figure 5-2-31 Chatting - user A
 Chat Module( User B )
Figure 5-2-32 Chatting - user B
 Legitimate users can chat with other users over the GoList web application platform.
67
 Favourites Listing
Figure 5-2-33 Selecting a favourite classified
 User can add certain posts to favourites list with intention to view it in future.
Figure 5-2-34 Listing of favourite classified
 Figure 5-2-34 shows the listing after adding a service / product classified to favourites.
68
 Request List
Figure 5-2-35 Entering desired service and zipcode
Figure 5-2-36 Entering advanced service description
69
Figure 5-2-37 Requests listing
 Figure 5-2-37 will display the request done by the user.
 Admin Login
Figure 5-2-38 Admin login
70
 Admin Settings
Figure 5-2-39 Admin home
 The admin can access andchange the site settings as per Figure 5-2-40.
 Site Settings
Figure 5-2-40 Admin site settings
71
 Home Page Content Settings
Figure 5-2-41 Admin home content
 Social Site Settings
Figure 5-2-42 Admin social site setting
 The admin can set the API keys required for different social sites as per Figure 5-2-42
and can change the home page heading and footer contents as per Figure 5-2-41.
72
 User Management
Figure 5-2-43 Listing users
Figure 5-2-44 Viewing users
Figure 5-2-45 Deleting users
73
Figure 5-2-46 After deletion of users
Category management
Figure 5-2-47 Listing categories
Figure 5-2-48 Viewing categories
74
Figure 5-2-49 Editing categories
Figure 5-2-50 After edition of categories
75
Figure 5-2-51 Deleting categories
Figure 5-2-52 After deletion categories
Request Management
Figure 5-2-53 Listing requests
76
Figure 5-2-54 Viewing requests
Figure 5-2-55 Deleting requests
Figure 5-2-56 After deletion of requests
77
Frequently Asked Questions Management
Figure 5-2-57 Listing FAQs
Figure 5-2-58 Viewing FAQs
Figure 5-2-59 Editing FAQs
78
Figure 5-2-60 After edition of FAQs
Figure 5-2-61 Deleting FAQs
Figure 5-2-62 After deletion of FAQs
79
Email Management
Figure 5-2-63 Listing emails
Figure 5-2-64 Editing emails
80
5.3 Test Cases

Table 5-3 Test cases
Test Case Test Data Expected Result Actual Result Pass/Fail

ID
1 Login - Login ID If Login ID and If Login ID and Pass
- Password password is password is
empty or empty or invalid,
invalid, then then display error
display error message
message otherwise
otherwise Login successfully
Login
successfully
2 Register - Username If all details If all details Pass
- Password entered are entered are valid
- email valid with with database
- confirm database format format add user
email add user to to database
database
3 Video / Add video Uploaded Video Uploaded Video Pass
Image audio and image and image format
upload format only accept video
only accept files of .mp4 or
video files of .mov extension.
.mp4 or .mov For image only
extension. accept jpg or png
For image it files.
only accepts jpg
or png files.
81
4 Forgot Email Id If Email Id is valid Password is reset Pass

password and authorized if the Email id is
then new authorized and
password is set valid
by received
email
5 Activation - Email If user clicks on User clicks on the Pass
link recieved the link in the link in email,
with link email, user's user's account is
account gets getting activated
activated
6 Create a - Enters If user enters all User enters all Pass
service contact details details according
classified - Enters according to to database
address database format and user's
- Enters format, user's classified gets
details classified will be created
- Enters created
links
7 Create a - Enters If user enters all User enters all Pass
product contact details details according
classified - Enters according to to database
price database format and user's
- Enters format, user's classified gets
details classified will be created
- Uploads created
video/imag
e
82
8 Change - Enters When user clicks User clicks on Pass

email email on verification verification link
link new email new email gets
must get added added to the
to the database database
9 Change - Enters old When user User enters the Pass
password password enters the password
- Enters password according to valid
new according to format and new
password valid format, password gets set
new password
gets set
10 Add to - Clicks When user clicks User clicks on the Pass
favourite button button, the button and
classified gets classified gets
added to the list added to the list
11 Request- - Enters When user User enters Pass

ing Service enters details details according
name according to to the valid
- enters zip valid format, format, email is
code email goes to recieved on the
the service service provider
providers with end
same or similar
service
12 Location - Enters zip When user User enters a zip Pass
based code enters zip code, code and
search the classifieds classifieds gets
gets listed with listed with
distance distance
83
13 Delete - Enters When user User enters Pass

product reason enters reason reason for
for deletion of deletion and the
product, product gets
product will not removed from
be displayed on front end
front end
14 Rate a - Chooses When a user User enters Pass
classified rating enters detail details according
- Enters according to to valid format
details valid format, and user's review
- Uploads users review and and rating gets
image rating will get affected on
affectedon provider's
provider's dashboard
dashboard
15 Deactivate - Enters User must enter User enters a Pass
account reason a reason and reason and clicks
click on confirm on the confirm
box to box, the account
deactivate gets deactivated
account
16 Activate - Enters User must enter User enters the Pass
account Reason a reason and reason and clicks
click on the on confirm box
confirm box to and user's
activate account account gets
activated
84
17 Chatting - Enters User must be User is able to Pass

message able to send and chat with other
recieve chat users
messages from
other users
18 Social - facebook If the oAuth The oAuth details Pass
signup email and details match matched with
password with the user user credentials
- gmail credentials, user and user is
email and is redirected successfully
password back to GoList redirected
home page
19 Contact us - name If all the details User enters valid Pass
- email are avlid and details and is
- phone match database added to the
number format, add the database
- subject details to
- message contacts table
20 Logout Select User should User get Logout Pass
Logout Logout of the of the application
application and and redirected to
redirected to Login page
Login page
85
CHAPTER 6 CONCLUSION AND FUTURE SCOPE
The project is completed according to its functionality requirement. It can be used

at an initial level as communication medium between the providers and the seekers. It
also provides admin side management for betterment of management of the web
application.
This project was implemented with less number of functionalities which are
chatting and video classifieds. This was built according to the initial requirements of the
client for the first release. For the next release, the project will include payment module,
push notification and email api setting.
86
CHAPTER 7 REFERENCES
Web References
[1] https://git-scm.com/documentation
[2] https://wiki.filezilla-project.org/Documentation
[3] http://www.tutorialspoint.com/svn/
[4] http://php.net/manual/en/index.php
[5] http://getbootstrap.com/components/
[6] https://book.cakephp.org/3.0/en/index.html
87

Final Year Service Provider Website

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Final Year Service Provider Website

Transféré par

Droits d'auteur :

Formats disponibles

An

Industrial Training Report

UKA TARSADIA UNIVERSITY

in partial fulfillment of the requirements for the degree of

Under the Guidance

Ms. Shraddha Kothiya

Department of Computer Engineering & Information Technology

Chhotubhai Gopalbhai Patel Institute of Technology

GoList is a service provider web application which provides a connection medium or

Abstract ............................................................................................................................. viii

List of Figures ...................................................................................................................... xi

List of Tables ..................................................................................................................... xiv

Chapter 1 Introduction ................................................................................................... 1

1.1 Overview ............................................................................................................... 1

1.2 Problem Definition ................................................................................................ 1

1.3 Application ............................................................................................................ 1

Chapter 2 Training Activities........................................................................................... 2

2.1 Environmental Setup ............................................................................................. 2

2.2 Version Control System Training ........................................................................... 2

2.3 Core PHP Training.................................................................................................. 2

2.4 PHP Framework Training ....................................................................................... 2

Chapter 3 System Planning ............................................................................................. 3

3.1 Project Development Approach ............................................................................ 3

3.2 System Modules .................................................................................................... 5

3.2.1 Back-end Development.................................................................................. 5

3.2.2 Front-end Development ................................................................................ 5

3.2.3 User Development ......................................................................................... 5

3.3 Functional Requirements ...................................................................................... 6

3.4 Non Functional Requirements .............................................................................. 8

3.5 Timeline Chart ....................................................................................................... 9

Chapter 4 System Design .............................................................................................. 11

4.1 Use Case Diagram................................................................................................ 11

4.3 Activity Diagram .................................................................................................. 17

4.4 Class Diagram ...................................................................................................... 22

4.5 Database Schema ................................................................................................ 23

4.6 Data Flow Diagram .............................................................................................. 38

4.7 ER Diagram .......................................................................................................... 45

Chapter 5 Implementation and Testing........................................................................ 46

5.1 Hardware and Software Requirements .............................................................. 46

5.2 Snapshots ............................................................................................................ 47

5.3 Test Cases ............................................................................................................ 81

Chapter 6 Conclusion and Future Scope ...................................................................... 86

Chapter 7 References ................................................................................................... 87

1.2 Problem Definition

CHAPTER 2 TRAINING ACTIVITIES

2.1 Environmental Setup

2.2 Version Control System Training

2.3 Core PHP Training

 Session / Cookie Management [4]

2.4 PHP Framework Training

CHAPTER 3 SYSTEM PLANNING

3.1 Project Development Approach

Figure 3-1 Agile development model

The advantages of the Agile Model are as follows −

 Is a very realistic approach to software development.

 Promotes teamwork and cross training.

 Functionality can be developed rapidly and demonstrated.

 Resource requirements are minimum.

 Suitable for fixed or changing requirements

 Good model for environments that change steadily.

 Minimal rules, documentation easily employed.

 Enables concurrent development and delivery within an overall planned context.

 Little or no planning required.