Sal Institute of technology & Engineering Research

Department of Computer science & Engineering

2022-23

Gujarat Technological University, Ahmedabad

Project Desk
A
REPORT

For
Design Engineering, II A (3150001)
Submitted By: -
SHAH PARVA S. (210670131504)
ADESHARA ZALAK J. (210670131509)
KESHARIYA PARINA H. (210670131511)

Guided by Head of Department

Prof. Neha Minocha Prof. Sudha Patel

Academic Year
2022-23
Sal Institute of technology & Engineering Research
Department of Computer science & Engineering
2022-23

CERTIFICATE
Date:

This is to certify that the SHAH PARVA SURESHKUMAR

Enrolment No: 210670131504 of Semester 5th, Department of
Computer Science & Engineering has satisfactorily completed the
work under the “PROJECT DESK” in Design Engineering II A
(3150001) course with in the four walls of the Institute.

Internal Guide Head of Department

Prof. Neha Minocha Prof. Sudha Patel

Department of Computer Science & Engineering

Sal Institute of technology & Engineering Research
Department of Computer science & Engineering
2022-23

CERTIFICATE
Date:

This is to certify that the ADESHARA ZALAK JATINBHAI

Enrollment No: 210670131509 of Semester 5th, Department of
Computer Science & Engineering has satisfactorily completed the
work under the “PROJECT DESK” in Design Engineering II A
(3150001) course with in the four walls of the Institute.

Internal Guide Head of Department

Prof. Neha Minocha Prof. Sudha Patel
Department of Computer Science & Engineering
Sal Institute of technology & Engineering Research
Department of Computer science & Engineering
2022-23

CERTIFICATE
Date:

This is to certify that the KESHARIYA PARINA HARSUKHBHAI

Enrollment No: 210670131511 of Semester 5th, Department of
Computer Science & Engineering has satisfactorily completed the
work under the “PROJECT DESK” in Design Engineering II A
(3150001) course with in the four walls of the Institute.

Internal Guide Head of Department

Prof. Neha Minocha Prof. Sudha Patel
Department of Computer Science & Engineering
 ACKNOWLEDGEMENT

When we reach the completion of the project giving credit becomes a must, as
without the support of the other so many peoples’ help and guidance this project
could not be completed successfully.
We would like to thank Prof. NEHA MINOCHA for guiding us and showing
their views on the project for framing the realistic picture of the requirement and
involved needed in this project. They were always there with their great ideas and
suggestions whenever we needed. They took a great deal of interest in our work
and encouraged us to outperform ourselves They believed in us and were a pillar
of strength for us.
We would like to thank to help us prepare this project. We would also appreciate
their guidance and technical knowledge they gave us regarding this project.
Last but not least, our heartfelt appreciation goes to all those not named here, but
who have rendered their co-operation, little or more, directly or indirectly in the
course of development of this Decolorization of Dye waste water by Adsorption
on Alumina Adsorbent.
Thanking All.
YOUR TRULY,
PARVA SHAH
ZALAK ADESHARA
PARINA KESHARIYA
 ABSTRACT

An abstract is the concise description of the Project “PROJECT DESK”

Contains the following activity.
Form this website
 A network is a set of linear features that are interconnected in PD.
 Provide developer a platform a source of income.
 This website help customer to make project of their business.
 TABLE OF CONTENT

Chapter Page
Chapter Title
No. No.
Chapter 1 Introduction

1.1 Need for the new system 1

1.2 Detailed problem definition 2
1.3 Viability of the system 3
1.4 Presently available system for the same 4
1.5 Future prospect
Chapter 2 Project Canvas
2.1 AEIOU Canvas 5
2.2 Mind Map Canvas 7
2.3 Empathy Canvas 8
2.4 Ideation Canvas 11
Chapter 3 Possible Solution
3.1 Product Development Canvas 13
3.2 Prototyping 15
3.3 LNM Canvas 16

Chapter 4 System Modeling

4.1 Database design 17
 Chapter 1
Introduction
1.1 Need For The New System

 The proposed system is used to develop the “freelance” that means the
system that will connect user and developer directly.
 This system will be designed that it can satisfy all the requirement of the
user.
 This system will provide online projects for small as well as big platforms.
 Freelance itself indicate that the platform where the person works for
themselves or being hired to accomplish the assignment for different
companies.
 Our system will provide such kind of platform for them.

1.2 Detailed Problem Definition

 As we know that India is still the country were many unemployed people
do not get their job or work under a company.
 There are many platforms were people are less paid or not according to
work they have done.
 Users are directly not connected by the developer. They are connected with the
client in between where they tell their requirement to the client and then client
tell the developer what the user want.
 Their systems have a dedicated plan to purchase.
 The purchased product is for temporary based for two or three months.

1.3 Viability Of The System

 Our system will provide a direct connection between developer and user.
 Our system will deliver the product on time and also according to the user.
 Our system will hire the people who are willing to work to be self employed.
 Our system will work for small as well as big platforms also.
 Our system will provide assignments to the people who are willing to be
self-employed.

1|P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 1.4 Presently Available System For The Same

 www.freelancer.in

 In this system the user need to purchase the dedicated plan.

 This system do not connect user to developer directly.

1.5 Future Prospect

 Track Project
 Chat System

2|P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 Chapter 2
Project Canvas
2.1 AEIOU Summary: -

Description:
1 Environment: -
 Data connection
 User Friendly
2 Interaction: -
 Developer
 Customer
3 Objects: -
 Programminng language

3|P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
  Mobile phone
 Desktop
 Tablet
4 Activities: -
 Request project
 Project listing
 Project rejection
 Project accepting
 Completed projects

5 User: -
 Customers
 Admin
 Developers

4|P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 2.2 Mind Map: -

5|P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 2.3 Empathy Canvas: -

1 User: -
 Admin
 Customers
 Developers

6|P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 2 Stake Holders: -
 Admin
 Project Manger
 HR
 Technical Staff

3 Activities: -
 Analysis
 Testing
 Developer Profile
 Customer Profile
 Progress Report

STORY BORDING: -
HAPPY: -
Once a while my friend want to start the new start up but got stuck because he
does not have a platform to start from then I suggested him to upload details
regarding the start up where the developer codes the website and this way my
friend got the platform to start his business and this was the happy moment.
HAPPY: -
Two months ago, my uncle has the business of home crocries as he has the old
Ideology as he does not believe in online platforms. Me and my all the cousins
secretly ordered the project on the site “PROJECT DESK”. After couple of
Weeks we received our project. We gave this project as a surprise to my uncle.
He got shocked after seeing the project and analytics, there was a vast growth
seen in the business. This was the happy moment.
SAD: -
A year ago, my friend Yash wants to make a project but he has the low budget as
he was new in the market to settle the business. He had suffered a lot to search
the perfect developer for his project. If he got the developer then the cost was
high and if the cost is low he didn't get the developer having experience. So my
friend told me his problem after this incident i developed the website those who
suffer from this problems, to make project more cost effective.

7|P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 SAD: -
20 days ago, there was a requirement of specialized project at effective rate. But
at the same time my team was enable to find that developer. If I got the developer
then the demand was high to make a project. So due to this problem my team
unfortunately rejected the project. This was the sad moment.

8|P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 2.4 Ideation Canvas: -

1. People: -
 Admin
 Customer
 Developer

2. Activities: -
 Request Project
 Project Listing
 Project Rejection
 Project Accepting
 Completed Projects

9|P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 3. Situation/Context/Location: -
 User Friendly
 Web application
 Cost effective
 Easy to use

4. Props/Tools/Objects/Equipment: -
 Analyse
 Development Engineering
 Authentic

10 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 Chapter 3
Possible Solution
3.1 Product development canvas: -

1. Purpose: -
 User Friendly
 Help Customer
 Employement
 Budget Friendly

2. People: -
 Admin
 Developer
 Customer

3. Product Experience: -
 Quick Responsive
 Attractive
 Better Performance

11 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 4. Product Function: -
 Dashboard Management
 Cloud Service

5. Product Features: -
 Upload Requirement Information
 Manage Project Records
 Search Project
 Better Earning

6. Component: -
 Operating System
 Server
 Client Machine

7. Customer Validation: -
 Feedback
 Authentication
 Verification

8. Reject, Redesign, Retain: -

 Maintenance

12 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 3.2 Prototype Model: -

13 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 3.3 Learning Need Matrix (LNM): -

14 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 Chapter 4
SYSTEM MODELING
4.1 Data Dictionary

A data dictionary is a collection of descriptions of the data objects or items in a

data model for the benefit of programmers and others who need to refer to
them. A first step in analyzing a system of objects with which users interact is
to identify each object and its relationship to other objects. This process is
called data modeling and results in a picture of object relationships. After
each data object or item is given a descriptive name, its relationship is
described (or it becomes part of some structure that implicitly describes
relationship), the type of data (such as text or image or binary value) is
described, possible predefined values are listed, and a brief textual
description is provided. This collection can be organized for reference into
a book called a data dictionary.

When developing programs that use the data model, a data dictionary can be
consulted to understand where a data item fits in the structure, what
values it may contain, and basically what the data item means in real-
world terms. For example, a bank or group of banks could model the data
objects involved in consumer banking. They could then provide a data
dictionary for a bank's programmers. The data dictionary would describe
each of the data items in its data model for consumer banking (for
example, "Account holder" and ""Available credit").

15 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 16 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 17 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 18 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 19 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING
 Refrence:

1 https://www.w3schools.com

2 https://www.freelancer.in

3 https://www.upwork.com

4 https://www.fiverr.com

20 | P a g e
SAL INSTITUTE OF TECHNOLOGY & ENGINEERING