ENROLLMENT NO.

PROJECT TITLE

CHAPTER 1
INTRODUTION

1.1 Project Summary

Application help us to customer to find a worker nearest their and also help to them book online
from the application. It will save time and find a perfect worker as per the needs. Worker can
also update their work details and they will earn more money with this concept. Worker can also
buy product and repair the customer problem. This Platform help customer and worker to
complete the task as per the requirements on tap.

1.2 PURPOSE

Main purpose of the Application is user can find Workers from the Application. Worker can also
View the Booking details and after there are this Booking Except/Reject Booking. This App
main Review are the multi Field Workers can provide to this Application and then after any
Field in Many workers are provided to User. This Application Main Purpose are the Few Time
in user Work can Completed in your Time.

1.3 Scope

The platform helps customers hire trusted professionals for services like salon at home, cleaning,
plumbing, carpentry, etc.

“Worker Finder” is a app-based marketplace for hiring trusted home and local services. The
Company's vision is to use technology and smart processes to structure the highly unorganized
services market in India and emerging markets.

Using “Worker Finder” customer can book their services at any time & any place. Customer
can see various service categories. Customer can see worker’s details. Customer can see ratings
& feedback.

SEMESTER V(DEPARTMENT NAME) Page 1

ENROLLMENT NO. PROJECT TITLE

CHAPTER 2
LITERATURE REVIEW

SEMESTER V(DEPARTMENT NAME) Page 2

ENROLLMENT NO. PROJECT TITLE

Limitation of Existing program:-

 The customers does not get proper workers.

 The customers need to go to various places to get services.

 The customers find difficult to get services they are in need of.

 It is also time consuming.

SEMESTER V(DEPARTMENT NAME) Page 3

ENROLLMENT NO. PROJECT TITLE

CHAPTER 3

System Requirement Specification

3.1 USER CHARACTERISTIC (MODULE DETAILS):-

ADMIN LOGIN
 Admin will able to logged into the system using given email and password.
 Admin can manage the whole admin panel and other process of the application.
 Admin can also able to change password and reset password.
ADMIN
 Manage user:
o Admin can manage the user who has register into app.
 Manage categories:
o Admin can manage the category like Home Service, Office Service.
 Manage localities:
o Admin can manage the locations of Ahmedabad city.
 Manage workers:
o Admin can manage the worker who has register into app and also can verify his
personal detail over a call.
o Admin can also verify the workers.
 Assign workers to the user:

o Admin can also assign booking if customer not selecting any workers.

USER
 Registration to the app:
o User can create his account using mobile no and password.
 Login the app:
o User can login using mobile no and password.
 Search workers according to various categories:
o User can search various workers on basis of category and area.
o User can view the workers profile and other detail.

SEMESTER V(DEPARTMENT NAME) Page 4

ENROLLMENT NO. PROJECT TITLE

 Book worker by users need:

o User can select his workers and also can specify the Date and Time for Service
booking.
 Feedback:
o User can also give a feedback to the application.
 Faq:

o User can view the frequently asked question.

WORKER
 Login into app
o Worker can create his account and admin will accept / reject account.
 Profile:
o Worker can update his profile details.
 View booking details:
o Worker can view booking details.
 Update status:
o Once user has complete work he can update the status.
o Worker can view Users locations
o Workers can view user location for services.

PLACEMENT
 Admin can also assign worker for placement
 Worker can also hire for someone which task will Given by the admin.

WORKER COMPER
 User can compare with another worker in application.

SEMESTER V(DEPARTMENT NAME) Page 5

ENROLLMENT NO. PROJECT TITLE

3.2 SOFTWARE REQUIREMENT

Net Beans: -

Net Beans IDE is a free, open source, integrated development environment (IDE)
that enables you to develop desktop, mobile and web applications. The IDE supports
application development in various languages, including Java, HTML5, PHP and C+
+. The IDE provides integrated support for the complete development cycle, from
project creation through debugging, profiling and deployment. The IDE runs on
Windows, Linux, Mac OS X, and other UNIX-based systems.

The IDE provides comprehensive support for JDK 8 technologies and the most
recent Java enhancements. It is the first IDE that provides support for JDK 8, Java
EE 7, and JavaFX 2. The IDE fully supports Java EE using the latest standards for
Java, XML, Web services, and SQL and fully supports the Glass Fish Server, the
reference implementation of Java EE.

The two base products, the Net Beans IDE and Net Beans Platform, are free for
commercial and non-commercial use. The source code to both is available to anyone
to reuse as they see fit.

In June 2000, Net Beans was made open source by Sun Microsystems, which
remained the project sponsor until January 2010 when Sun Microsystems became a
subsidiary of Oracle.

ADVANTAGES:-

1. Works Out of the Box

Simply download and install the Net Beans IDE and you are good to go. Installation
is a breeze with its small download size. All IDE tools and features are

SEMESTER V(DEPARTMENT NAME) Page 6

ENROLLMENT NO. PROJECT TITLE

fully integrated no need to hunt for plug-ins and they work together when you launch
the IDE.

2. Free and Open Source

When you use the Net Beans IDE, you join a vibrant, open-source community of
thousands of users ready to help and contribute. There are discussions on the Net
Beans mailing lists, blogs on PlaneNetBeans, and helpful FAQs.

3. Connected Developer

The Net Beans IDE is the tool of choice for teams working in a collaborative
environment. You can create and manage java.net-hosted projects, for example; file
issue tracking reports using both Jira and Bugzilla, and collaborate with like- minded
developers—all directly from within the familiar interface of the IDE.

4. Powerful GUI Builder

The GUI Builder (formerly known as Project Matisse) supports a sophisticated yet
simplified Swing Application Framework and Beans Binding. Now you can build
GUIs in a natural way.

5. Support for Java Standards and Platforms

The IDE provides end-to-end solutions for all Java development platforms including
the latest Java standards.
 Java Mobility Support:

Java Mobility Support Complete environment to create, test, and run applications for
mobile devices. With pre-processor blocks, you can readily handle fragmentation
issues. Support for Java Mobility development is the best among all Java
development tools.

 Java Enterprise Edition (EE) 6 support: The first free, open-source IDE
to support Java EE 6 specifications.

SEMESTER V(DEPARTMENT NAME) Page 7

ENROLLMENT NO. PROJECT TITLE

 Java Standard Edition (SE) Support: You can develop applications

using the latest Java SE standards.

SEMESTER V(DEPARTMENT NAME) Page 8

ENROLLMENT NO. PROJECT TITLE

Net Beans Screenshot

DATABASE

MYSQL: - MySQL is a fast, easy-to-use RDBMS being used for many small and
big businesses. MySQL is developed, marketed and supported by MySQL AB,
which is a Swedish company. MySQL is becoming so popular because of many good
reasons −

 MySQL is released under an open-source license. So you have nothing to

pay to use it.

 MySQL is a very powerful program in its own right. It handles a large

subset of the functionality of the most expensive and powerful database packages.

 MySQL uses a standard form of the well-known SQL data language.

 MySQL works on many operating systems and with many languages

including PHP, PERL, C, C++, JAVA, etc.

SEMESTER V(DEPARTMENT NAME) Page 9

ENROLLMENT NO. PROJECT TITLE

 MySQL works very quickly and works well even with large data sets.

 MySQL is very friendly to PHP, the most appreciated language for web
development.

 MySQL supports large databases, up to 50 million rows or more in a table.

The default file size limit for a table is 4GB, but you can increase this (if your
operating system can handle it) to a theoretical limit of 8 million terabytes (TB).

 MySQL is customizable. The open-source GPL license allows

programmers to modify the MySQL software to fit their own specific environments.

MySQL Screenshot

SEMESTER V(DEPARTMENT NAME) Page 10

ENROLLMENT NO. PROJECT TITLE

3.2 SOFTWARE REQUIRMENT:

Language iOS

IDE

Platform

Database MySQL

Documentation Tools

3.3 HARDWARE REQUIREMENT

Hard Disk

RAM

Processor

3.4 PROJECT DEVELOPMENT APPROACH

Software development life cycle (SDLC) is a series of phase that provide a common
understanding of the software building process. Traditionally, the Systems
Development Lifecycle (SDLC) and Project Management (PM) methodologies have
followed a waterfall or gated approach. Depending upon the project and project
organization, the methodologies may be adapted using waterfall, iterative,
incremental, spiral or agile approaches. In our project we are using Spiral model for
showing our project development approach.

The spiral model is similar to the incremental model, with more emphasis placed on
risk analysis. The spiral model has four phases: Planning, Risk Analysis,
Engineering and Evaluation.

SEMESTER V(DEPARTMENT NAME) Page 11

ENROLLMENT NO. PROJECT TITLE

A software project repeatedly passes through these phases in iterations (called

Spirals in this model). The baseline spiral, starting in the planning phase,
requirements are gathered and risk is assessed. Each subsequent spirals builds on the
baseline spiral. It‘s one of the software development models like Waterfall, Agile,
and V-Model.

 Planning Phase:-

Requirements are gathered during the planning phase. Requirements like ‗BRS‘ that
is ‗Business Requirement Specifications‘ and ‗SRS‘ that is ‗System Requirement
specifications‘.

 Risk Analysis:-

In the risk analysis phase, a process is undertaken to identify risk and alternate
solutions. A prototype is produced at the end of the risk analysis phase. If any risk is
found during the risk analysis then alternate solutions are suggested and
implemented.

 Engineering Phase:-

In this phase software is developed, along with testing at the end of the phase. Hence
in this phase the development and testing is done.

 Evaluation phase:

This phase allows the customer to evaluate the output of the project to date before
the project continues to the next spiral.

SEMESTER V(DEPARTMENT NAME) Page 12

ENROLLMENT NO. PROJECT TITLE

SPIRAL MODEL DIAGRAM

ADVANTAGES OF SPIRAL MODEL

 High amount of risk analysis hence, avoidance of Risk is enhanced.

 Good for large and mission-critical projects.
 Strong approval and documentation control.
 Additional Functionality can be added at a later date.
 Software is produced early in the software life cycle.

DISADVANTAGES OF SPIRAL MODEL

 Can be a costly model to use.

 Risk analysis requires highly specific expertise.
 Project‘s success is highly dependent on the risk analysis phase.
 Doesn‘t work well for smaller projects.

WHEN TO USE SPIRAL MODEL

 When costs and risk evaluation is important

 For medium to high-risk projects
 Long-term project commitment unwise because of potential changes to
economic priorities
 Users are unsure of their needs
SEMESTER V(DEPARTMENT NAME) Page 13
ENROLLMENT NO. PROJECT TITLE

 Requirements are complex

 New product line
 Significant changes are expected (research and exploration)

SEMESTER V(DEPARTMENT NAME) Page 14

ENROLLMENT NO. PROJECT TITLE

3.5 SCHEDULE REPRESENTSTION

SEMESTER V(DEPARTMENT NAME) Page 15

ENROLLMENT NO. PROJECT TITLE

CHAPTER 4
ANALYSIS & DESIGN

4.1 Feasibility Study

4.4.1 Technical Feasibility:-

COCOMO MODEL: - The constructive cost model as a model for estimating

effort, cost, and schedule for software projects. It drew on a study of 63 projects at
TRW Aerospace where Boehm was Director of Software Research and Technology.
The study examined projects ranging in size from 2,000 to 100,000 lines of code,
and programming languages ranging from assembly to PL/I. These projects were
based on the waterfall model of software development which was the prevalent
software development process in 1981.

References to this model typically call it COCOMO 81. In 1995 COCOMO II was
developed and finally published in 2000 in the book Software Cost Estimation with
COCOMO II. COCOMO II is the successor of COCOMO 81 and is claimed to be
better suited for estimating modern software development projects; providing
support for more recent software development processes and was tuned using a
larger database of 161 projects. The need for the new model came as software
development technology moved from mainframe and overnight batch processing to
desktop development, code reusability, and the use of off-the-shelf software
components. This article refers to COCOMO 81.

COCOMO consists of a hierarchy of three increasingly detailed and accurate forms.

The first level, Basic COCOMO is good for quick, early, rough order of magnitude
estimates of software costs, but its accuracy is limited due to its lack of factors to
account for the difference in project attributes (Cost Drivers). Intermediate
COCOMO takes these Cost Drivers into account and Detailed COCOMO
additionally accounts for the influence of individual project phases.

SEMESTER V(DEPARTMENT NAME) Page 16

ENROLLMENT NO. PROJECT TITLE

A.BASIC COCOMO MODEL

Basic COCOMO computes software development effort (and cost) as a function of

program size. Program size is expressed in estimated thousands of source lines of
code (SLOC, KLOC). COCOMO applies to three classes of software projects:-
 Organic projects –"Small" teams with "good" experience working with
"less than rigid" requirements.
 Semi-detached projects –"Medium" teams with mixed experience
working with a mix of rigid and less than rigid requirements.
 Embedded projects – Embedded projects developed within a set of
"tight" constraints. It is also a combination of organic and semi-detached projects.
(hardware, software, operational,…).The basic COCOMO equations take the form:
Effort Applied (E) = ab (KLOC) bb [man-months]

Development Time (D) = cb (Effort Applied) db

[months]

People required (P) = Effort Applied / Development Time [count]

where KLOC is the estimated number of delivered lines (expressed in thousands) of

code for the project. The coefficients ab, bb, cb and db are given in the following
table.

Soft Ab Bb Cb Db
ware
proje
ct
Organic 2.4 1.05 2.5 0.38

Semi- 3.0 1.12 2.5 0.35

detached
Embedded 3.6 1.20 2.5 0.32

Basic COCOMO is good for a quick estimate of software costs. However, it does not
account for differences in hardware constraints, personnel quality and experience,
use of modern tools and techniques, and so on.

B. INTERMEDIATE COCOMO MODEL:-

SEMESTER V(DEPARTMENT NAME) Page 17
ENROLLMENT NO. PROJECT TITLE

Intermediate COCOMO computes software development effort as a function of

program size and a set of "cost drivers" that include subjective assessment of the
product,hardware, personnel and project attributes. This extension considers a set of
four "cost drivers", each with a number of subsidiary attributes:-

 Product attributes
 Hardware attribute
 Personnel attribute
 Project attribute

The Intermediate Cocomo formula now takes the

form: E=ai (KLoC) (bi) (EAF)

Where E is the effort applied in person-months, KLoC is the estimated number of

thousands of delivered lines of code for the project, and EAF is the factor calculated
above. The coefficient ai and the exponent bi are given in the next table:-

Software project Ai Bi

Organic 3.2 1.05

Semi-detached 3.0 1.12

Embedded 2.8 1.20

The Development time D calculation uses E in the same way as in the Basic COCOMO.

C. DETAILED COCOMO MODEL

Detailed COCOMO incorporates all characteristics of the intermediate version with

an assessment of the cost driver's impact on each step (analysis, design, etc.) of the
software engineering process.

The detailed model uses different effort multipliers for each cost driver attribute.
These Phase Sensitive effort multipliers are each to determine the amount of effort
required to complete each phase. In detailed cocomo, the whole software is divided
SEMESTER V(DEPARTMENT NAME) Page 18
ENROLLMENT NO. PROJECT TITLE

into different modules and then we apply COCOMO in different modules to estimate
effort and then sum the effort.

The effort is calculated as a function of program size and a set of cost drivers are
given according to each phase of the software life cycle.

A Detailed project schedule is never static. The Six phases of detailed COCOMO are:-

 planning and requirements

 system design
 detailed design
 module code and test
 integration and test
 Cost constructive model

4.1.2 Economical Feasibility:-

Economic feasibility analysis is the most commonly used method for determining
the efficiency of a new project. It is also known as cost analysis. It helps in
identifying profit against investment expected from a project. Cost and time are the
most essential factors involved in this field of study.

Generally, it means whether a business or a project is feasible cost wise and

logistically. Economists calculate economic feasibility by analysing the costs and
revenues a business would incur by undertaking a certain project.

Economic feasibility analysis is the most commonly used method for determining
the efficiency of a new project. It is also known as cost analysis. It helps in
identifying profit against investment expected from a project. Cost and time are the
most essential factors involved in this field of study.

These include:

 Economic feasibility cash flow.

 Estimated total project cost.
 Estimated total earnings.
 Risk factors.
 Cost benefits.

SEMESTER V(DEPARTMENT NAME) Page 19

ENROLLMENT NO. PROJECT TITLE

4.1.3 Optional Feasibility:-

 Operational feasibility refers to the measure of solving problems with

the help of a new proposed system. It helps in taking advantage of the opportunities
and fulfils the requirements as identified during the development of the project. It
takes care that the management and the users support the project.
 After analyzing the technical, economic, and scheduling feasibility
studies, next would come the operational analysis. In order to determine if the
redesign of the workspace environment would work, an example of an operational
feasibility study would follow this path based on six elements:
 Process –Input and analysis from everyone the new redesign will
affect along with a data matrix on ideas and suggestions from the original plans.
 Evaluation –Determinations from the process suggestions; will the
redesign benefit everyone? Who is left behind? Who feels threatened?
 Implementation –Identify resources both inside and out that will work
on the redesign. How will the redesign construction interfere with current work?
 Resistance –What areas and individuals will be most resistant?
Develop a change resistance plan.
 Strategies – How will the organization deal with the changed or
structures need to be reviewed or implemented in order for the redesign to be
effective?
 Adapt & Review –How much time does the organization need to
adapt to the new redesign? How will it be reviewed and monitored? What will
happen if, through a monitoring process, additional changes must be made?

A) RISK ANALYSIS:-

Risk analysis is the review of the risks associated with a particular event or action. It
is applied to projects, information technology, security issues and any action where
risks may be analysed on a quantitative and qualitative basis. Risk analysis is a
component of risk management.

Risks are part of every project and business endeavour. As such, risk analysis should
occur on a recurring basis and be updated to accommodate new potential threats.
Strategic risk analysis minimizes future risk probability and damage.

SEMESTER V(DEPARTMENT NAME) Page 20

ENROLLMENT NO. PROJECT TITLE

The risk management process involves a few key steps. First, potential threats are
identified. For example, risks are associated with individuals using a computer either
incorrectly or inappropriately, which creates security risks. Risks are also related to
projects that are not completed in a timely manner, resulting in significant costs.

Next, quantitative and/or qualitative risk analysis is applied to study identified risks.
Quantitative risk analysis measures expected risk probability to forecast estimated
financial losses from potential risks. Qualitative risk analysis does not use numbers
but reviews threats and determines and establishes risk mitigation methods and
solutions.

A contingency plan may be used during risk analysis. If a risk is presented,

contingency plans help minimize damage.

SEMESTER V(DEPARTMENT NAME) Page 21

ENROLLMENT NO. PROJECT TITLE

4.2 Function of System:-

4.2.1 Use Case Diagram For Admin:-

SikllHub Authenti
cation
Login Exte
nd
City
Managem
Area
ent
Managem
Category
ent
Managem
Subcatego
ent
ry
Managem
Search
ent
Admin Worker
View
Worker
View
Booking
View
Rating
Change
Password
Forgot
Password
Logout

SEMESTER V(DEPARTMENT NAME) Page 22

ENROLLMENT NO. PROJECT TITLE

Use Case Diagram For User:-

SillHub
Registratio de
Verific
ation
n Inclu
Authenti
Login cation
Extend
View City
View Area
View
Category
View
Subcategor
y
Search
User Worker
View
Worker
Booking
Managem
ent
Rating
Change
Password
Forgot
Password
Logout

SEMESTER V(DEPARTMENT NAME) Page 23

ENROLLMENT NO. PROJECT TITLE

Use Case Diagram For Worker:-

SikllHub
Registratio d e
Verific
ation
n Inclu
Authenti
Login
Extend cation
View City
View Area
View
View
Category
Subcategor
Manage
y
Profile
Upload
Worker Photos
View
Booking
Update
Booking
View
Status
Rating
Change
Password
Forgot
Password
Logout

SEMESTER V(DEPARTMENT NAME) Page 24

ENROLLMENT NO. PROJECT TITLE

4.3 Data Modeling:-

4.3.1 Class Diagram:-

Depe Depe
nd on nd on
Subca One
Categ
tegor Worker
ory
y One Rating
1
.
*

1
One Worker .
Many Photos*

Manage
Worker
Manage
Rating 1
Worker .
Photo *

De
pen
d
on
Use
r

SEMESTER V(DEPARTMENT NAME) Page 25

ENROLLMENT NO. PROJECT TITLE

4.3.2 ER Diagram:-

SEMESTER V(DEPARTMENT NAME) Page 26

ENROLLMENT NO. PROJECT TITLE

4.3.3 Activity Diagram

• Activity Diagram For Admin

Log
in N
[Authentica o
ted..?]
Y
es
Sub
Cat
Are cat
City ego Sea Vie Cha For
a ego Vie Vie
Ma ry rch w nge got
Ma ry w w
nag Ma Wo Boo Pas Pas
nag Ma Wor Rati
em nag rke kin sw sw
em nag ker ng
ent em r g ord ord
ent em
ent
ent

Log
out

SEMESTER V(DEPARTMENT NAME) Page 27

ENROLLMENT NO. PROJECT TITLE

Activity Diagram for User

Logi
n N
[Authentica o
ted..?]

Y
es

Boo
Vie
Vie kin Cha For
Vie w Sea Vie
Vie w g nge got
w Sub rch w Rati
w Cat Ma Pas Pas
Are cat Wo Wor ng
City ego nag swo swo
a ego rker ker
ry em rd rd
ry
ent

Log
out

SEMESTER V(DEPARTMENT NAME) Page 28

ENROLLMENT NO. PROJECT TITLE

Activity Diagram for Worker

Log
in N
o
[Authentic
ated..?]

Y
e
s
Up
Vie Upl dat
Vie Ma Vie Cha For
Vie Vie w oa e Vie
w na w nge got
w w Su d Bo w
Cat ge Bo Pas Pas
Cit Ar ego bca Ph oki swo swo Rat
Pro oki
y ea ry teg oto ng rd rd ing
file ng
ory s Sta
tus

Log
out

SEMESTER V(DEPARTMENT NAME) Page 29

ENROLLMENT NO. PROJECT TITLE

4.3.4 Sequence Diagram:-

• Sequence Diagram for Admin

Doctor

Admi Docto
n r

SEMESTER V(DEPARTMENT NAME) Page 30

 y Vie w w nge ot at
Log w w h Ma at
: in : w : Are : Cat
: Sub : W : W : na : :
Pass : Pass : in
a
b
Req City ego ork wor wor
User a cate ork ge g as
ues
ENROLLMENT NO. ry er d
PROJECT d
TITLE
t Reque er me e
for st to nt
Authe
logi View
Success
nticat
n City
fully
Sequence
e Diagram
ViewedRequest to
for User
Succe
City View Area
ssful Successfully Viewed
Area
Request to View
Category
Successfully Viewed
Category
Request to View
Subcategory
Successfully Viewed
Subcategory
Request to Search
Worker
Successfully
Search Worker
Request to View
Worker
Successfully
View Worker
Request to Booking
Management
Successfully Booking
Managed
Request to Change
Password
Successfully Update change
password
Request to Forgot
Req Password
ues Successfully
t sent Password
for
Logge Request to Rating
dlog
out Successfully
out Rating
Succe
ssfull
y

SEMESTER V(DEPARTMENT NAME) Page 31

ENROLLMENT NO. PROJECT TITLE

Sequence Diagram for Worker

Up
Vi
dat D
Vie Ma Vie Cha Forg e
Vie Vie e at
Vie w nag w nge ot w
Log w w Bo
:
Req in
: w : Are : Cat : Sub : e : Bo : oki : Pas : Pass : R a
b
City ego Pro oki swo wor at
Worker
ues
Reque
a
ry
cate
file ng
ng
rd d in as
t Sta e
for st to g
Authe View tus
logi Success
nticat City
n fully
e
ViewedRequest to
Succe
City View Area
ssful Successfully Viewed
Area
Request to View
Category
Successfully Viewed
Category
Request to View
Subcategory
Successfully Viewed
Subcategory
Request to Manage
Profile
Successfully
Manage Profile
Request to View
Booking
Successfully
View Booking
Request to Update
Successfully
Booking Status
Updated Booking
StatusRequest to Change
Password
Successfully Update change
password
Request to Forgot
Req Password
ues Successfully
t sent Password
Request to View
Logge
for Rating
Successfully
dlog
out
out Viewed Rating
Succe
ssfull
y

SEMESTER V(DEPARTMENT NAME) Page 32

ENROLLMENT NO. PROJECT TITLE

4.4 Function And Behavioural Modeling:-

4.4.1 Data Flow
Diagram:- Data flow
Diagram (level 0)

SEMESTER V(DEPARTMENT NAME) Page 33

ENROLLMENT NO. PROJECT TITLE

Data flow diagram level(1)

SEMESTER V(DEPARTMENT NAME) Page 34

ENROLLMENT NO. PROJECT TITLE

4.4.2 Flow Chart:-

• System Flow Chart for Admin

Start

Login
N
Ye [ Authenticated o
s .? ]

Change Password
Forgot Password
City Management
Area Management
Category Management
Subcategory Management
Search Worker
View Worker
View Booking
View Rating

Logout

Stop

SEMESTER V(DEPARTMENT NAME) Page 35

 Start
ENROLLMENT NO. PROJECT TITLE
Is No Register
Regist
er ? Now
Ye
System Flow Chart for User s
Login
No
Ye [ Authenticated.?
s ]

Change Password
Forgot Password
View City
View Area
View Category
View Subcategory
Search Worker
View Worker
Booking Management
Rating

Logout

Stop

SEMESTER V(DEPARTMENT NAME) Page 36

 Start

Register No Is
ENROLLMENT NO. Now Regist PROJECT TITLE
er ?
Ye
s
System Flow Chart for Worker Is
No
Appro
ved ?
Ye
s
Login
No
Ye [ Authenticated.?
s ]

Change Password
Forgot Password
Manage Profile
Update Photos
View Booking
Update Booking Status
View Rating

Logout

Stop

SEMESTER V(DEPARTMENT NAME) Page 37

ENROLLMENT NO. PROJECT TITLE

CHAPTER 5

Data Structure
5.1 Database Schema Design:-

Admin
Description :- Represents Admin’s Details.

Constraint Field Name Data Type Description

Primary admin_id Int(11) Admin ID

Key

admin_name Varchar(200) Admin

Name

admin_email Varchar(200) Admin

Email

admin_password Varchar(200) Admin

Password

admin_profile_pic Varchar(200) Admin

Profile Pic

is_active Int(11) Active or

not

SEMESTER V(DEPARTMENT NAME) Page 38

ENROLLMENT NO. PROJECT TITLE

City
Description :- Represents city Details.

Constraint Field Data Type Description

Name

Primary city_id Int(11) City ID

Key

city_name Varchar(200) City Name

is_active Int(11) Active or not

SEMESTER V(DEPARTMENT NAME) Page 39

ENROLLMENT NO. PROJECT TITLE

Area
Description :- Represents Area’s Details.

Constraint Field Data Type Description

Name

Primary Key area_id Int(11) Area ID

area_name Varchar(200) Area Name

Foreign key city_id Int(11) City ID

is_active Int(11) Active or not

SEMESTER V(DEPARTMENT NAME) Page 40

ENROLLMENT NO. PROJECT TITLE

User Master
Description :- Represents User Details.

Constraint Field Name Data Type Description

Primary user_id Int(11) User ID

Key
user_name Varchar(200) User Name

user_gender varchar(10) User gender

user_mobile bigint(20) User Mobile

No.
user_email Varchar(200) User Email

user_password Varchar(200) User

Password

address Varchar(200) User

Address
Foreign city_id Int(11) City ID
key
Foreign area_id Int(11) Area ID
key
user_photo Varchar(200) User Photo

is_active Int(11) Active or not

SEMESTER V(DEPARTMENT NAME) Page 41

ENROLLMENT NO. PROJECT TITLE

Category Master
Description :- Represents Category’s Details.

Constraint Field Name Data Type Description

Primary Key category_id Int(11) Category ID

category_name Varchar(200) Category

Name

category_image Varchar(200) Category

Image

is_active Int(11) Active or

not

SEMESTER V(DEPARTMENT NAME) Page 42

ENROLLMENT NO. PROJECT TITLE

Sub Category
Description :- Represents Subcategory Details.

Constrain Field Name Data Type Descriptio

t n

Primary sub_category_id Int(11) Sub

Key Category
ID
sub_category_name Varchar(200 Sub
) Category
Name
Foreign category_id Int(11) Category
key ID

sub_category_imag Varchar(200 Sub

e ) Category
Image Path

is_active Int(11) Active or

not

SEMESTER V(DEPARTMENT NAME) Page 43

ENROLLMENT NO. PROJECT TITLE

Worker Master
Description :- Represents Worker’s Details.

Constra Field Name Data Type Description

int

Primary worker_id Int(11) Worker ID

Key

worker_nam Varchar(20 Worker Name

e 0)

worker_gend varchar(20 Worker Gender

er )

worker_dob date Worker DOB

email_id varchar(20 Worker Email ID
0)
mobile_no varchar(11 Worker Mobile No.
)

password varchar(11 Worker Password

)

worker_phot varchar(20 Worker Photo

o 0)

address varchar(20 Worker Address

0)

Foreign city_id int(11) City ID

key

SEMESTER V(DEPARTMENT NAME) Page 44

ENROLLMENT NO. PROJECT TITLE

Foreign sub_category int(11) Sub Category ID

key _id

Foreign area_id int(11) Area ID

key

aadhar_card int(30) Worker

Aadhar
Card
No.
pan_card int(30) Worker
Pan
Card
No.
worker_charge int(11) Worker
Charge

about_details varchar(10 Worker

00) Details

experiance_detail varchar(20 Worker

0) Experie
nce
Details

business_name varchar(20 Worker

0) Business
Name
is_block int(11) Worker Is
Block Or Not

is_available int(11) Worker Is

Available Or
Not
is_online int(11) Worker Is
Online Or Not

is_verify int(11) Worker Is

Verify Or Not

SEMESTER V(DEPARTMENT NAME) Page 45

ENROLLMENT NO. PROJECT TITLE

is_active Int(11) Active or not

Booking_Master
Description :- Represents Booking Details.

Constraint Field Name Data Type Description

Primary booking_id Int(11) Booking ID

Key

booking_date Timestamp Booking

Date

Foreign worker_id Int(11) Worker ID

key

charge Int(11) Worker Charge

Foreign user_id Int(11) User ID

key

address varchar(200) Address of User

Foreign area_id Int(11) Area ID

key

is_complete Int(11) Service is

Complete or not

for_booking_time varchar(100) Time of Service

for_booking_date date Date of Service

SEMESTER V(DEPARTMENT NAME) Page 46

ENROLLMENT NO. PROJECT TITLE

is_active Int(11) Active or not

Worker Inquiry
Description :- Represents Worker inquiry Details.

Constraint Field Name Data Description

Type

Primary worker_inquiry_id Int(11) Worker

Key Inquiry ID
Foreign worker_id Int(11) Worker ID
key

Foreign user_id Int(11) User ID

key

worker_inquiry_date date Worker

Inquiry date
is_active Int(11) Active or not

SEMESTER V(DEPARTMENT NAME) Page 47

ENROLLMENT NO. PROJECT TITLE

Worker Review
Description :- Represents Worker’s Photo Details.

Constraint Field Name Data Type Description

Primary worker_review_id Int(11) Worker

Key Review ID

Foreign worker_id Int(11) Worker ID

key

rating float Worker

Ratings

review varchar(200) Worker

Reviews

Foreign booking_id Int(11) Booking ID

key

is_active Int(11) Active or not

SEMESTER V(DEPARTMENT NAME) Page 48

ENROLLMENT NO. PROJECT TITLE

Payment
Description :- Represents Payment Details.

Constraint Field Name Data Type Description

Primary payment_id Int(11) Payment ID

Key

payment_date date Payment

Date

Foreign booking_id Int(11) Booking ID

key

amount Int(11) Amount of

Payment

method varchar(200) Method of

Payment

is_active Int(11) Active or not

SEMESTER V(DEPARTMENT NAME) Page 49

ENROLLMENT NO. PROJECT TITLE

FAQ
Description :- Represents FAQ Details.

Constraint Field Name Data Type Description

Primary faq_id Int(11) FAQ ID

Key

faq_question Varchar(1000) FAQ

Question

faq_answer Varchar(1000) FAQ Answer

is_active Int(11) Active or not

SEMESTER V(DEPARTMENT NAME) Page 50

ENROLLMENT NO. PROJECT TITLE

CHAPTER 6

Project Layouts (Screen Shots of project)

You have to put Minimum 8 to 10 screen shots

SEMESTER V(DEPARTMENT NAME) Page 51

ENROLLMENT NO. PROJECT TITLE

CHAPTER 7

Testing

 Introduction about different testing methods

 Which method you applying on your project and specify
why

SEMESTER V(DEPARTMENT NAME) Page 52

ENROLLMENT NO. PROJECT TITLE

Conclusion

SEMESTER V(DEPARTMENT NAME) Page 53

ENROLLMENT NO. PROJECT TITLE

Future Enhancements

Enhancements and improvement is continuously ongoing process for the app’s lifetime, so to
enhance the functionality and make it more usable for the user.

Here are the some future enhancements which will be done on the app:
 By Extending the use of the Free time, suggest the user for best encounter options
according to the location of high priority contact and user
 Add multi language support for the application
 Add chat like functionality for the user to interact with the contact from the app itself.

SEMESTER V(DEPARTMENT NAME) Page 54

ENROLLMENT NO. PROJECT TITLE

BIBLIOGRAPHY

SEMESTER V(DEPARTMENT NAME) Page 55