0% found this document useful (0 votes)
6 views38 pages

Workbok 2

Uploaded by

hetumungara1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views38 pages

Workbok 2

Uploaded by

hetumungara1
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 38

Project definition

 Reason for choose this definition:


• We choose this definition because it easily can be purchasing online
Watch and also save user’s time and efforts.

 Purpose:
• This project offers where users can view various type of watches
and can buy it online easily.

 General Introduction:
• Customer can save their time and order book online.
• Online system makes customer management easier and more
efficient.
• Customer can see our watches and buy it on online platform.

 Benefits of online Purchase the Product:


1. Easy returns and delivery process
2. More information about the product
3. More variety
4. Great marketing channel for business
5. People stay in touch with each other
6. Awareness and activism

Page | 1
ANALYSIS

 There are two kinds of analysis in this project:

1. User side analysis


2. Admin side analysis

1. User side analysis:


• In our project, we put some menu like, Home, Registration, Login,
Cart, Profile etc.

 Registration:
• When user want to use this website or buy the product, He/she will
submit their details in the form.

 Login:
• If user has already register in this website, then they can easily
login.

 Cart:
• User can add their likely products in the cart and then buy it
anytime.

 Feedback:
• User can share their feedback and experience in the feedback form.

 Contact us:
• If users have any type of query or issues, they can contact and solve
their problems.

 Product:
• Users can find out their necessary product through the different types of
categories.

Page | 2
 Category & subcategory:
• User can see categories and its subcategories.

 About us:
• User can know all the details about the website.

2. Admin side analysis:

• Only admin can login in this page.

 Manage customer:
• Admin can view customer and delete it.

 Manage product:
• Admin can manage entire product list.

 Manage database:
• Admin can manage entire database.

 Manage feedback:
• Admin can view and delete the feedback.

 Manage cart:
• Admin can manage user’s cart.

 Manage category & subcategory:


• Admin can add, update, and delete category and subcategory.

 Manage orderlist:
• Admin can manage user’s order.

Page | 3
FEASIBILITY STUDY

Feasibility when starting off a project you would need to look at if it is possible to
create this project.

1. Technical Feasibility:

Hardware Requirement
RAM Minimum 1 GB
Hard Disk 256 GB
Processor I5

Software Requirement
Operating System Windows 10
Front End HTML, CSS, PHP, JavaScript
Back End MySQL
Web Server Apache(XAMPP)
Web Browser Google Chrome, Microsoft Edge

2. Operational Feasibility:

• For people, our project is easy to use as it just requires some


knowledge of computer and technology.
• Easy to maintain.

3. Economical Feasibility:

• Hardware and software are free.


• Does not need any cost in future.
• Our template is totally free.
• Hence it is economically feasible.

4. Time feasibility:

 Our project will take three months to its completion, so it will be also
timely feasible.
Page | 4
E-R DIAGRAM

• Entity relationship diagram helps to explain the logical structure of


database.
• E-R diagram uses some basic symbols.

 RECTANGLE:

• A rectangle to denote an entity set.

 DIAMOND:

• A Diamond to denote a relationship between


two entity.

 OVAL:

• An oval to denote attribute.

 LINE:
• A line which links attributes to an entity.

Page | 5
Page | 6
DATA FLOW DIAGRAM

 A data flow diagram is a graphical Representation of the flow of data


through a system. A DFD model uses following primitive symbols.

• it represents external entities with which system communicate.

• A process is represented as a rectangle with rounded age.

• It is used to model a collection of data packet at rest.

• Represents of data.

Page | 7
DATA FLOW DIAGRAM

DFD-context Level Diagram: -

Page | 8
Level-0: DFD For User Side:-

Page | 9
Level-1: DFD For User Side:-

Page | 10
Level-2: DFD For User Side:-

Page | 11
Level-3: DFD For User Side:-

Page | 12
Level-0: DFD For Admin side: -

Page | 13
Level-1: DFD For Admin Side: -

Level-1: DFD For Admin Side: -

Page | 14
Level-1: DFD For Admin Side: -

Level-1: DFD For Admin Side: -

Page | 15
Level-1: DFD For Admin Side: -

Level-1: DFD For Admin Side: -

Page | 16
USE CASE DIAGRAM: -

Page | 17
Page | 18
DATA DICTIONARY

DATABASE NAME: - Watchgallery

TABLE NAME: - registration

DESCRIPTION: - All the details of users are stored in this table.

TABLE NAME: - category

DESCRIPTION: - All the details of category are stored in this table.

Page | 19
TABLE NAME: - subcategory

DESCRIPTION: - Users who have subcategory, their details are stored in this
table.

TABLE NAME: - feedback

DESCRIPTION: - If users give feedback, it is stored in this table.

Page | 20
TABLE NAME: - product

DESCRIPTION: - All the products of this website are stored in this table.

Page | 21
TABLE NAME: - cart

DESCRIPTION: - User can purchase the product about the website. And it is
stored in this table.

TABLE NAME: - bill

DESCRIPTION: - All the details about bill and price are stored in this table.

Page | 22
SCREEN LAYOUT

1. HOME PAGE: -

DESCRIPTION: -When user visit this site first time, this page will appear.

Page | 23
3. REGISTRATION: -

DESCRIPTION: - Users who want to purchase the Watch; he/she will submit
their detail in registration form.

Page | 24
3. Login: -

DESCRIPTION: - After Registration User can login in this website.

4. Product: -

DESCRIPTION: - Products are shown in this page.

Page | 25
5. Category & subcategory: -

DESCRIPTION: - Category and subcategory are shown in this format.

6. Cart: -

DESCRIPTION: - If user want to purchase the product, he/she can add the
product in their cart.

Page | 26
5. Contact & Feedback: -

DESCRIPTION: - This Table is used to maintain and stored the information


related to contact and feedback.

6. About Us: -

DESCRIPTION: - User can know the whole information about this site easily.

Page | 27
1. ADMIN LOGIN: -

DESCRIPTION: - Admin must be login to go to admin panel.

2. Add Product: -

DESCRIPTION: - Admin can purchase to the Add Product in this website.

Page | 28
3. Product: -

DESCRIPTION: -After admin view, update and delete the product in this website.

4. Add Category: -

DESCRIPTION: - Admin can add the Category in this website.

5. Category: -

DESCRIPTION: - Admin can view, update and delete the Category in this website.

Page | 29
6. Add Subcategory: -

DESCRIPTION: -Admin can add subcategory in this website.

7. Subcategory: -

DESCRIPTION: -Admin can view, update and delete the subcategory the in this website.

Page | 30
8. Customer List: -

DESCRIPTION: - Admin can view and delete the customers in this website.

9. Cart: -

DESCRIPTION: - Admin can view and delete the cart in this website.

10. Orderlist: -

DESCRIPTION: - Admin can view and delete the order in this website.

Page | 31
TEST CASE

Page | 32
Page | 33
GANTT CHART

Page | 34
LIMITATIONS

 A modern approach for order.

 Currently we don’t add location facility.

 Product search is not available.

FUTURE SCOPE

 Make system more users friendly.

 We will provide facility for online payment.

 We will provide wish list.

Page | 35
BIBLIOGRAPHY

 BOOKS: -

• PHP
• CSS WITH MYSQL SERVER

 WEBSITE:-

• www.w3school.com
• www.greeksforgeeks.com
• www.google.com

Page | 36
WORK EXPERIENCE

Our project guide Mr. Hardik Dave provided full support to us.
She always helped us just like a companion and not just as
professional guide; she also Provide the information required by us at
any time. She personally worked hard for our project. Also, the other
faculty members related to the computer department never refused to
help us. Also, the institute has provided the immense help by leap and
bounds.

We also learnt some designing techniques; so, we


heartily thankful to all who helped us in gradually climbing the steps
towards the completion of this project of Online appointment booking
system. Thank you, all faculty members, giving us such a great
opportunity.

Last but not the least the overall experience of developing


this project is as good as studying an entire new subject to fuelling up
the knowledge treasure.

Page | 37
Page | 38

You might also like