Service System

A PROJECT REPORT

Submitted by

Kamil Patel(186400316076)
Vaibhav Patel(186400316085)
Yash Patel(186400316088)
Raj Patel(186400316080)

In partial fulfillment for the award of the

DIPLOMA ENGINEERING
in

Information Technology Department

R. C. Technical Institute, Ahmedabad

Gujarat Technological University, Ahmedabad

April, 2021
 R. C. TECHNICAL INSTITUTE
Opposite Gujarat High Court, S. G. Highway, Sola,
Ahmedabad-380060
DEPARTMENT OF INFORMATION TECHNOLOGY
2021

CERTIFICATE
This is to certify that Kamil Patel(186400316076), Vaibhav Patel(186400316085), Yash
Patel(186400316088) and Raj Patel(186400316080) has satisfactorily completed the project
work entitled Service System assigned as UDP in partial fulfilment of Project-1 (3351605)
during 5th semester of academic year 2020-21.

Internal guide, Head of Department

Mr. Akhilesh Ladha Mr. Manoj P. Parmar
Lecturer in IT Department IT Department
Service System

Acknowledgement

We are pleased to present “Service System” project and take this opportunity to
express our profound gratitude to all those people who helped us in completion of this project.

We thank our college for providing us with excellent facilities that helped us to
complete and present this project. We would also like to thank the staff members and lab
assistants for permitting us to use computers in the lab as and when required.

We express our deepest gratitude towards our project guide for her valuable and timely
advice during the various phases in our project. We would also like to thank her for providing
us with all proper facilities and support as the project co-coordinator. We would like to thank
her for support, patience and faith in our capabilities and for giving us flexibility in terms of
working and reporting schedules.

We would like to thank all our friends for their smiles and friendship making the college
life enjoyable and memorable and family members who always stood beside us and provided
the utmost important moral support. Finally we would like to thank everyone who has helped
us directly or indirectly in our project. We also thankful to Mr. Shwetang Patel(Neighbour of
Kamil) who helped a lot in making our project successful.

Information Technology, RCTI i

Service System

Abstract
 Today the world is moving towards automation and simplification of various processes
that generally needed human intervention and decision making with the help of the
advanced technology that we have at our disposal today. One such attempt to automate
tedious processes is the advent of “Service applications” these applications are used by the
user to avail services as and when need arise, this concept is getting increasingly popular
and has found its use in many service domains, such as hotels booking, food ordering, taxi
booking etc. The proposed system is also an on demand application for availing housing
services by the users. This will significantly reduce the time and effort required to scout
and hire professionals who provides services such as cooking, cleaning, babysitting, driver
and other such services required in daily life. As in many applications the goal will be to
provide the required service on the user’s.

Information Technology, RCTI ii

 Service System

List of Figures

Sr. No. Name of figures Page No.

1 Working of PHP processor 2

2 Iterative Waterfall model 4
3 Urban Clap 12
4 Use case of Admin 14
5 Use case of Service Provider 15
6 Use case of Customer 16
7 E-R Diagram 17
8 Context Diagram (0 Level) 20
9 Data Flow Diagram (1 Level) 21

Information Technology, RCTI iii

 Service System

List of Table

Sr. No. Name of table Page No.

1 Gantt chart 7
2 Effort Estimation 9
3 Data Dictionary of User login 17
4 Data Dictionary of Customer data 18
5 Data Dictionary of Providers 18
6 Data Dictionary of Offers 18
7 Data Dictionary of Bookings 19
8 Data Dictionary of Invoice 19
9 Data Dictionary of Services 20
10 Data Dictionary of Transaction 20

Information Technology, RCTI iv

Service System

Table of Contents

Acknowledgement i
Abstract ii
List of Figures iii
List of Tables iv
List of Abbreviations v
Table of Contents vi
Chapter : 1 Introduction to Project
1.1. Project Summary 1
1.2. Purpose 1
1.3. Scope 1
1.4. Technology Review (Introduction to software/technology) 2
Chapter : 2 Project Management
2.1. Project Planning & Schedule 4
2.1.1 Project Development Approach 4
2.1.2 Project Plan 6
2.1.3 Milestones and Deliverables 6
2.1.4 Schedule representation 7
2.2. Risk Management 7
2.2.1 Risk Identification 7
2.2.2 Risk Analysis 9
2.3. Estimation 9
2.3.1 Effort Estimation 9
Chapter : 3 System Requirement Study 10
3.1. User Characteristics 10
3.2. Hardware and Software characteristics 11
Chapter : 4 System Analysis and Designing 12
4.1. Study of current system 12
4.2. Problems & weakness of current system 12
4.3. Requirement of new system 12

Information Technology, RCTI v

Service System

4.4. Feasibility study 13

4.5. Function of the system 14
4.5.1 Use case diagram 14
4.6. Data Modelling 17
4.6.1 E-R Diagram 17
4.6.2 Data Dictionary 17
4.7. Functional & Behavioral Modeling 20
4.7.1 Context diagram (0 level) 20
4.7.2 Data Flow Diagram (1 level) 21
4.8. Main Modules of new system 21
Screenshots (if any) 22

Conclusion 23

Information Technology, RCTI vi

Service System

CHAP TER 1 : I NTRODUCT ION

1.1. Project Summary

Project Name: Service System

Service System is a project to automate the “Process of scouting and hiring professionals
who provide Industrial, commercial and residential services” by developing system that is efficient
and user-friendly. The main idea of the project is to maintain and handle all domains involved,
from cooking, cab, automotive and many other domains.

There is a need to automate this sector because till now it is managed manually. So, by
making a proper system for this process, the overall process can be done efficiently and utilization
of resources can be done. It will also aim to providing a clear picture of hoe the entire process is
taking place stepwise so that the chances of frauds and errors can be minimized. SS will fulfil the
purpose of providing easy accessibility to its customers.

In this project, there are many domains included in it, so customers basically have to
choose his/her domain in which he/she is interest to get the service and after that we will show
a list of service providers on the basis of availability and rating (high to low) to the customers
and after his/her interest he/she select one of them.

In this project, there is also a feature of the ratings for the customer which will be
assigned by us depending on the service provider’s feedback.

There is a feature of service system safety and also there are measures for customer
security and hygiene. SS is the need of the hour in today’s rapidly growing world. Also, this
will increase employment opportunity within the country.

1.2. Purpose
To develop this type of Platform for services of Industrial, Commercial and Residential. The
process is easy and convenient for Consumer/User, Service Provider.

1.3. Scope
1. In this system Admin will able to track the activity of service ordered by the
consumer/user.
2. Service Provider should be able to upload their information after login through the
service provider webpage.
3. Consumer/User should be able to upload their information and request service after login
through consumer webpage.

Information Technology, RCTI P a g e 1 | 41

Service System

1.4. Technology Review

Front End: PHP, CSS

Back End: MySQL

PHP: It is a widely-used open source general-purpose scripting language that is especially

suited for web development and can be embedded into Html. The best things in using PHP are
that it is extremely simple for a newcomer, but offers many advanced features for a professional
programmer.

PHP is an HTML-embedded Web scripting language. This means PHP code can be inserted
into the HTML of a Web page. When a PHP page is accessed, the PHP code is read or "parsed"
by the server the page resides on. The output from the PHP functions on the page is typically
returned as HTML code, which can be read by the browser.

Because the PHP code is transformed into HTML before the page is loaded, users cannot view
the PHP code on a page. This make PHP pages secure enough to access databases and other
secure information

Figure 1.1 Working of PHP processor

CSS: Stands for "Cascading Style Sheet." Cascading style sheets are used to format the layout
of Web pages. They can be used to define text styles table sizes, and other aspects of Web
pages that previously could only be defined in a HTML pages. CSS helps Web developers
create a uniform look across several pages of a Web site. Instead of defining the style of each
table and each block of text within a page's HTML, commonly used styles need to be defined
only once in a CSS document. Once the style is defined in cascading style sheet, it can be used
by any page that references the CSS file. Plus, CSS makes it easy to change styles across
several pages at once.

Information Technology, RCTI P a g e 2 | 41

Service System

MySQL: Microsoft SQL server is a full-featured relational data base management system
(RDBMS) that offers a variety of administrative tools to ease the burdens of database
development, maintain and administration.
It is based on the structure query language (SQL), which is used for adding, removing, and
modifying information in the database. Standard SQL commands, such as ADD, DROP,
INSERT, and UPDATE can be used with MySQL.
MySQL can be used for a variety of applications, but is most commonly found on Web servers.
A website that uses MySQL may include Web pages that access information from a database.
These pages are often referred to as "dynamic" meaning the content of each page is generated
from a database as the page loads.

Information Technology, RCTI P a g e 3 | 41

Service System

CHAP TER 2: P ROJ ECT M ANAGE MENT

2.1. Project Planning & Schedule

2.1.1. Project Development and Approach
 How to choose the right approach for a project is a large topic. The methodology you
choose can depend on many things, including the structure and location of the project
team, the technologies being used on the project, and the degree to which collaboration
is a part of the company’s culture.

 The project is done based on the decided development life cycle model. We decide the
Iterative Waterfall Model for our application

Iterative Waterfall Model

In a practical software development project, the Classical Waterfall Model is hard to

use. So, the Iterative waterfall model can be thought of as incorporating the necessary
changes to the classical waterfall model to make it usable in practical software
development projects. It is almost same as the classical waterfall model except some
changes are made to increase the efficiency of software development.

“The iterative waterfall model provides feedback paths from every phase to its preceding
phases, which is the main difference from the classical waterfall model.”
Feedback paths introduced by the iterative waterfall model are shown in the figure below.

Figure 1.2 Interactive Waterfall

Information Technology, RCTI P a g e 4 | 41

Service System

When errors are detected at some later phase, these feedback paths allow correcting
errors committed by programmers during some phase. The feedback paths allow the
phase to be reworked in which errors are committed and these changes are reflected in
the later phases. But, there is no feedback path to the stage – feasibility study, because
once a project has been taken, it does not give up project easily.
It is good to detect errors in the same phase in which they are committed. It reduces the
effort and time required to correct the errors.

Phase Containment of errors: The principle of detecting errors as close to their points
of commitment as possible is known as Phase Containment of errors.

Advantages of Interactive Waterfall Model

 Feedback Path: In the classic waterfall model, there are no feedback paths, so
there is no mechanism for error correction. But in iterative waterfall model
feedback path from one phase to its preceding phase allows correcting the errors
that are committed and these changes are reflected in the later phases.
 Simple: The Iterative waterfall model is very simple to understand and use.
That’s why it is one of the most widely used software development models.

Drawback of Interactive Waterfall Model

 Difficult to incorporate change requests: The major drawback of the iterative
waterfall model is that all the requirements must be clearly stated before starting
the development phase. Customer may change requirements after some time but
the iterative waterfall model does not leave any scope to incorporate change
requests that are made after development phase starts.
 Incremental delivery not supported: In the iterative waterfall model, the full
software is completely developed and tested before delivery to the customer.
There is no scope for any intermediate delivery. So, customers have to wait long
for getting the software.
 Overlapping of phases not supported: Iterative waterfall model assumes that
one phase can start after completion of the previous phase But in real projects,
phases may overlap to reduce the effort and time needed to complete the project.
 Risk Handling not supported: Projects may suffer from various types of risks.
But, the Iterative waterfall model has no mechanism for risk handling.
 Limited customer interactions: Customer interaction occurs at the start of the
project at the time of requirement gathering and at project completion at the
time of software delivery. These fewer interactions with the customers may lead
to many problems as the finally developed software may differ from the
customers’ actual requirements.

Information Technology, RCTI P a g e 5 | 41

Service System

2.1.2. Project Plan

 Project planning is one of the major tasks that are performed during the
development of the project. Using project planning, the task of finding the size
of the project is done and with that total amount of time and cost required for
the project is calculated.
 The approach to developing the software system should follow some systematic
way i.e. Software Development Life Cycle. Using the upper-level analysis and
the environment of the project, which lifecycle model would fit properly for this
project was judged. After deciding the proper software development lifecycle
model, the development of this project according to the model was done.

2.1.3. Milestones and Deliverables

 Milestones
 Our first milestone was understanding of project definition.
 We determined all the segments of our project definition and carried
out different complexity by doing feasibility study.
 After searching all the factors and knowing project definition we
gathered project specification, it’s requirements and features.
 We analysed all the specifications and requirements with taken care of
every possible ways and all the loop holes.
 We planned our project according to project requirements, we divided
whole project in small segments, and we convert those segments into
sprints and based on that we started working on our project.
 After requirement gathering, analysing and planning we started
designing our project modules in which we created user interface
according to wire frames.
 Deliverables
 Project Objective
 Scope of Project
 Data Dictionary/Database
 User Pages (UI)
 Provider Pages (UI)

Information Technology, RCTI P a g e 6 | 41

 Service System

2.1.4. Schedule representation

A Scheduling a project identifies deadlines and interdependent tasks and assigns dates
to required resources. As such, a schedule is an important tool for completing projects
on time and budget.

The project schedule should be based on a Work Breakdown Structure (WBS), which
lists all of the tasks and goals of the project. The schedule places these tasks into a
sequence of linked events with dates/weeks.

The Project schedule create a model for entire project to guide the work being done and
to measure progress against fixed time table.

Month June July August September October November December February March April

Week 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

Problem
Selection

Solution
Discussion

Documenta
tion

Designing

Coding

Testing &
Correction

Once the original schedule has been established, you'll need to confirm that the
required resources are available on their required dates. If they aren't available, you'll
need to reschedule those tasks or find replacement resources. This can happen
throughout a project's life cycle. People get sick and supplies often arrive late. This is
why you should always view a schedule as a living document that's updated as needed
until the project has been completed.

2.2. Risk Management

2.2.1. Risk Identification

Risk is an inevitable concept of the softer project and it mainly concerns future
happenings. We want to produce a well working system; therefore, we must consider
all the possible defects and unexpected conditions.

Information Technology, RCTI P a g e 7 | 41

Service System

Following the possible risk of our project…

1. Schedule Risks
Project schedule get slip when project tasks and schedule release risks are not addressed
properly. Schedule risks mainly affect a project and finally on company economy may
lead to project failure.

Schedule Risk occurs due to following reasons.

a. Wrong time estimation
b. Resources are not tracked properly. All Resources like staff, systems, skills of
individuals.
c. Failure to identify complex functionalities and time required to develop those
functionalities.
d. Unexpected project scope expansions.
e. Sometimes, if bad situation such as traffic or vehicle accident may cause time delay
in making service efficient.

2. Budget Risks
a. Wrong budget estimation
b. Cost overruns
c. Project scope expansion
d. Lack of funds to operate properly
e. Difficult to pay enough money to service provider and admin

3. Operational Risks
Risk of loss due to improper process implementation failed system or some external
event risk.

Causes of operational risk:

a. Failure to address priority conflicts
b. Failure to resolve the responsibilities
c. Insufficient resources
d. No proper subject training
e. No resource planning
f. No communication in the team
g. Require staff who has superior knowledge in PHP Language
h. In future, it might requires shifting of base language because PHP is not a good
option for long-term

Information Technology, RCTI P a g e 8 | 41

Service System

4. Technical Risks
Technical risks generally lead to failure of functionality and performance.

Causes of Technical risks are:

a. Continuous changing requirements
b. The product is complex to implement.
c. Difficult project modules integration.
d. If sometime server will down for maintenance, it will affect all the users who
are currently accessing the system or who are trying to access the system.
e. The whole system under Admin. So, when the admin is not available, then it is
difficult to approve a job post, provider account upgrade requests and feature
requests.

5. Programmatic Risks
These are the external risks beyond the operational limits. These are all uncertain risks
are outside the control of the program.

These external events can be:

a. Running out of the fund.
b. Changing user product strategy and priority

2.2.2. Risk Analysis

Risk analysis is the important aspect of the system planning whenever planning the
Application, programmer always should consider the risk of system which he might
face in the Website. Risks are of two types…

1. Protective Risks
a. Proactive risk management attempts to reduce the tendency of any accident
happening in future by identifying the boundaries of activities, where a
breach of the boundary can lead to an accident.
b. Proactive risk management combines a mixed method of past, present and
future prediction before finding solutions to avoid risks.

2. Reactive Risks
a. Reactive risk management attempts to reduce the tendency of the same or
similar accidents which happened in past being repeated in future.
b. Reactive risk management solely depends on past accidental analysis and
response.

Information Technology, RCTI P a g e 9 | 41

Service System

2.3. Estimation
2.3.1. Effort Estimation
Task name Estimated time Starting time Ending time Status
Project 1 Week 1 August 7 August Completed
definition
Requirement 4 Weeks 7 August 7 September Completed
gathering
Analysis 2 Weeks 8 September 21 September Completed
Planning 2 Days 21 September 22 September Completed
Data 2 Weeks 23 September 6 October Completed
dictionary
Designing 8 Weeks 7 October 4 December Completed
Frontend 8 Weeks 7 December 5 March Completed
Backend 4 Weeks 8 March 2 April Completed
Testing 2 Week 5 April 16 April Completed

Information Technology, RCTI P a g e 10 | 41

Service System

CHAP TER 3: SYS TEM RE QUI RE ME NT ST UDY

3.1. User Characteristics

User characteristics are useful source of information that helps designers to faster such as
understanding of target users and the product in development. When designing for a specific
user group, the ‘user characteristics’ helps you to better understand the target group and predict
usability problems in practice.

We define characteristics of each user below…

1. Admin

 Admin can do Login.

 Admin can login-in and may also access/search any Information put up by User and
Service Provider.
 Admin can also see Service Provider Bookings.
 Admin can manage the System.
 Admin can manage commission system.
 Admin can change pay-out settings.
 Admin can also see invoice generated by Service Provider.
 Admin can see total number of Providers and Customers.
 Admin can also ban User and Service Provider if they are going against our Policy.

2. User

 User can do Registration.

 User can do Login.
 User can Hire/Book Service Provider available in location.
 User can do rating to service provider.
 User can do Post Job to hire Providers.

3. Service Provider

 Service Provider can do Registration.

 Service Provider can do Login.
 Service Provider can set the availability and unavailability time.
 Service Provider can set service area to provide a service.
 Service Provider can accept the User request of the Service.
 Service Provider can also see schedule and bookings.
 Service Provider can set our profile.

Information Technology, RCTI P a g e 11 | 41

Service System

 Service Provider can set Business Hours.

 Service Provider can set the Services.
 Service Provider can also add team member.
 Service Provider can generate invoice for customer.
 Service Provider can also upgrade their account to use more facility.
 Service Provider can also check their whole day schedule.

3.2. Hardware and Software characteristics

 Hardware Requirements
o Minimum 1.18 GHz processor
o Minimum 2GB of RAM
o 100 GB Free storage in Hard disk Storage

 Software Requirements
o Web Browser: Google Chrome, Mozilla Firefox, Safari, Opera Mini, etc.
o Operating System: Linux, Unix, Windows
o Database: MySQL 5.1 or above, Maria DB 10.0 or above, Microsoft SQL Server
2005 or above
o PHP Version: PHP 5.4 or above with PHP XML extension enable.

Information Technology, RCTI P a g e 12 | 41

Service System

CHAP TER 4: SYS TEM ANAL YSI S AND DE SI GNI NG

4.1. Study of current system

 Urban Clap
Urban Clap is also an On Demand Service Application which provide users with
services of various different nature from Salon, Spa to Electronics Repair, Cleaning, and
Plumbing etc., all on the same platform. Urban Clap does not provide a platform for hiring
professionals such as maids, cooks, drivers and developer etc.

Figure – 1 Urban Clap

4.2. Problem & weakness of current system

 Internet is required to run the system
 Skilled manpower is required
 Vehicle is required
 This company only provide a housekeeping services.

4.3. Requirement of new system

 User, Service provider and admin both require a smart phone or a laptop/desktop computer
with high speed internet.
 User, Service Provider and Admin both have to update their devices to the latest version of
software. So that, they can smoothly run the system without barrier.
 Patience is required for the User to get the best service.

Information Technology, RCTI P a g e 13 | 41

Service System

4.4. Feasibility study

Feasibility study is carried out when there is a complex problem or opportunity. It is considered as the
primary investigation which emphasizes on “look before You Loop” approach to any project.

A feasibility study is undertaken to determine the possibility of either improving the existing system
or developing a completely new system.

 In feasibility study there three type of study takes place:-

1. Technical Feasibility study

2. Economical Feasibility study
3. Operational Feasibility study

1. Technical Feasibility study

o In this type of study the current technology in used in an organization such as

the existing software, hardware, and personnel staff to determine whether it will
work for the proposed system or completely new once is to be used.
o The technology that was important in developing a new system such as
development tools, block-end database system were available from within the
organization.
o The proposed system is capable of adding, changing, enhancing the
functionality, features etc. the proposed system is capable large storage of data.
o The back-end front-end technology has greater important for providing an
accurate, error-free, frequencies of data to be used.

2. Economical Feasibility study

o For proving that system development is economical, the feasibility study takes
place to check the cost of developing a system against the benefits that it
provides. If the costs are less and benefits are than we can define our system
to be economical developed.
o The registration processing is speedier than the registered manually.
o The saving of papers as all data are stored computerized.
o The record is of free of human error as there is less chance of mistakes.
o The above benefits are in terms of saving time, minimize error and provide
efficiency in work done.

3. Operational Feasibility study

o The operational feasibility is concerned with the operability of the system after
it has been installed. That is some programmer may not like changes in their
routing method of work of has fear that they will lose their peer group.
o The following areas will have the operational feasibility in proposed project.

Information Technology, RCTI P a g e 14 | 41

Service System

o The organization has approved this system as their working system.

o The user of the System has accepted the proposed system as their new
working system and realized the benefits of it.
o The system will work in a proper way after it has been installed and the
installation process is easy to use.

4.5. Function of the system

4.5.1. Use Case Diagram
Use Case Diagram of Admin

Information Technology, RCTI P a g e 15 | 41

Service System

Use Case Diagram of Service Provider

Information Technology, RCTI P a g e 16 | 41

Service System

Use Case Diagram of Customer

Information Technology, RCTI P a g e 17 | 41

Service System

4.6. Data Modelling

4.6.1. E-R Diagram

4.6.2. Data Dictionary

 Data Dictionary of User login

Field Name Data type Data Size Constrains

ID Bigint 20 Primary Key
user_login Varchar 60 Foreign Key
user_pass Varchar 255 Not Null
user_name Varchar 50 Foreign Key
user_email Varchar 100 Foreign Key
user_registered Datetime --- Not Null
display_name Varchar 250 Not Null

Information Technology, RCTI P a g e 18 | 41

Service System

 Data Dictionary of Customer Data

Field Name Data type Data size Constrains

Id Int 10 Primary Key
user_id Bigint 20 Foreign Key
Name Varchar 255 Not Null
Phone Number 10 Not Null
Phone 2 Number 10 Not Null
Email Varchar 255 Not Null
Address Varchar 255 Not Null
Apt Varchar 255 Not Null
City Varchar 255 Not Null
State Varchar 255 Not Null
Country Varchar 255 Not Null
Zip code Number 10 Not Null
Region Varchar 255 Not Null

 Data Dictionary of Providers

Field Name Data type Data size Constrains

id Int 10 Primary key
avatar_id Int 10 Not Null
admin_moderation Varchar 128 Not Null
status Varchar 128 Not Null
gender Varchar 128 Not Null
identity Varchar 128 Not Null
company_name Varchar 128 Not Null
rating Decimal 10, 2 Not Null
full_name Varchar 128 Not Null
tagline Text ----- Not Null
bio Text ----- Not Null
email Varchar 128 Not Null
phone_no Varchar 128 Not Null
mobile_no Varchar 128 Not Null
fax_no Varchar 128 Not Null
website Varchar 128 Not Null
category_id Varchar 128 Not Null
address Text ----- Not Null

 Data Dictionary of offers

Field Name Data type Data size Constrains

id int 10 Primary key
offer_title varchar 128 Not Null
coupon_code varchar 128 Not Null
discount_value float ----- Not Null
discount_description text ----- Not Null
Information Technology, RCTI P a g e 19 | 41
Service System

 Data Dictionary of Bookings

Field Name Data Type Data Size Constrains

id int 10 Primary key
customer_id int 10 Not Null
booking_made_by varchar 100 Not Null
service_location varchar 100 Not Null
date date ----- Not Null
start_time time ----- Not Null
end_time time ----- Not Null
provider_id int 10 Not Null
services varchar 255 Not Null
type varchar 255 Not Null
booking_customer_id int 10 Not Null
status enum ------ Not Null
total decimal 10,2 Not Null
order_id int 10 Not Null
payment_type varchar 255 Not Null
txn_id varchar 255 Not Null

 Data Dictionary of Invoice

Field Name Data type Data size Constrains

id int 30 Primary key
reference_no varchar 100 Not Null
due_date date ---- Not Null
provider_id int 10 Not Null
customer_email varchar 128 Not Null
booking_id biginit 20 Not Null
services text ----- Not Null
description text ----- Not Null
total decimal 10, 2 Not Null
grand_total decimal 10, 2 Not Null
payment_mode varchar 255 Not Null
payment_type varchar 100 Not Null
txn_id varchar 255 Not Null

Information Technology, RCTI P a g e 20 | 41

Service System

 Data Dictionary of Transaction

Field Name Data type Data size Constrains

id Int 10 Primary key
provider_id Int 10 Not Null
payment_date Datetime ---- Not Null
txn_id Varchar 255 Not Null
payment_type Varchar 255 Not Null
payment_method Varchar 255 Not Null
payment_status Varchar 255 Not Null
amount Decimal 10, 2 Not Null

 Data Dictionary of Services

Field Name Data type Data size Constrains

id Int 10 Primary key
user_id BigInt 20 Not Null
provider_id Bigint ---- Not Null
service_name Varchar 255 Not Null
cost Decimal 10, 2 Not Null
offer Varchar 128 Not Null
offer_title Varchar 128 Not Null
copon_code Decimal 10, 2 Not Null
discount_value float ---- Not Null
discoutnt_description Text ---- Not Null

4.7. Functional & Behavioral Modeling

4.7.1. Context Diagram (0 Level)

Information Technology, RCTI P a g e 21 | 41

Service System

4.7.2. Data Flow Diagram(0 Level)

4.8. Main Modules of new system

This Project contains mainly three modules:

1. Admin
2. Customer
3. Service Provider

Information Technology, RCTI P a g e 22 | 41

Service System

SCREE NSH OT S

 Admin Panel

Information Technology, RCTI P a g e 23 | 41

Service System

Information Technology, RCTI P a g e 24 | 41

Service System

Information Technology, RCTI P a g e 25 | 41

Service System

Information Technology, RCTI P a g e 26 | 41

Service System

Information Technology, RCTI P a g e 27 | 41

Service System

 Provider

Information Technology, RCTI P a g e 28 | 41

Service System

Information Technology, RCTI P a g e 29 | 41

Service System

Information Technology, RCTI P a g e 30 | 41

Service System

Information Technology, RCTI P a g e 31 | 41

Service System

Information Technology, RCTI P a g e 32 | 41

Service System

 Customer

Information Technology, RCTI P a g e 33 | 41

Service System

Information Technology, RCTI P a g e 34 | 41

Service System

Information Technology, RCTI P a g e 35 | 41

Service System

 Home Page


Information Technology, RCTI P a g e 36 | 41

Service System

Information Technology, RCTI P a g e 37 | 41

Service System

Information Technology, RCTI P a g e 38 | 41

Service System

Information Technology, RCTI P a g e 39 | 41

Service System

Information Technology, RCTI P a g e 40 | 41

Service System

Conclusion
 Service system application will be able to solve various problems faced by the people
working day jobs or involved in other activities due to which are unable to spare time for
scouting and hiring housekeepers by providing a platform for the same.
 This application will also help in ensuring user satisfaction and reduce the stress of the
professionals who get hired through this platform and provide them with a platform which
will significantly increase their chances of getting hired.

Information Technology, RCTI P a g e 41 | 41