0% found this document useful (0 votes)
8 views

documentation

Uploaded by

anishproject8
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)
8 views

documentation

Uploaded by

anishproject8
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/ 44

Project Title:

“ONLINE CHAMPS WEAR”

(By SEMESTER-V of III Year M.Sc (CA&IT) 2022-23)


Submitted By:
1. POORV NAGAR

2. KHUSHBU NAYI

3. KHUSHI NIKHAL

Group ID: 28
Name of Company: A.V. Sports
Date of Submission:

Submitted To:
K.S. School of Business Management
M.Sc. Computer Applications and Information Technology.

1
2
3
4
5
6
7
ACKNOWLEDGEMENT

We are very thankful to everyone who supported us for this Project and gave their guidance to
computer and thesis work effectively and moreover on time.
We are equally grateful to our faculty Mr. Hitesh Parmar, who gave us moral support and
guided us in different matters and solutions regarding the topic.
We feel immensely proud in extending our heartiest thanks to Mr. B.S. Agrawal, Director of
K.S. School of Business Management, for providing us a platform to improve in various fields.
They have been a source of inspiration for us and their experience and knowledge have helped
us in learning and giving this project the shape it has assumed.

With Regards:

8
INDEX

No. Title Page No.

1 Introduction 11

1.1 Organization Profile 11

1.2 System Details 11

1.2.1 Existing System 11

1.2.2 Proposed System 12

1.3 Scope of System 12

1.4 Objectives 12

2 Proposed system requirement gathering 13

2.1 Stakeholder Of System 13

2.2 Requirement Gathering Techniques Used 13

2.3 Consolidated List of Requirements 18

2.4 Project Definition 18

3 System Management And Planning 19

3.1 Feasibility Study 19

3.1.1 Technical Feasibility 19

3.1.2 Economical Feasibility 19

3.1.3 Operational Feasibility 19

3.2 Hardware-Software Requirement 20

3.3 System Planning 21

3.3.1 Work Breakdown Structure 21

3.3.2 Gantt Chart 22

9
3.4 Process Model 22

4 System analysis and Design 24

4.1 UML(Unified Modelling Language) 24

4.2 System Flow Diagram 31

4.3 Data Dictionary 34

4.4 User Interface 38

4.5 System Navigation 44

10
Chapter 1: Introduction
Currently we are developing a web application called “ONLINE CHAMPS WEAR” using
PHP. Let’s try to understand, how it will actually work.

1.1 ORGANIZATION PROFILE


Company Name : A.V. SPORTS
Address : 108, Rudra Business Park, Opp. Kashinath Park, Vastral, Ahmedabad,
Gujarat 382418
Contact No : +91-9558139477
About us : WE PROVIDE SPORTS STUFF FOR ALL TYPE OF SPORTS
GAMES LIKE BASKETBALL,CRICKET,TENNIS,FOOTBALL,
BADMINTON ETC.

1.2 SYSTEM DETAILS

1.2.1 EXISTING SYSTEM:


The present scenario for shopping is to visit the shops and market manually and then
from the available product list one needs to choose the item he or she wants and then pay
for the same item mainly in cash mode is done, as not every society is well educated and
aware to use net banking or card modes or wallets etc.
This system is not much user-friendly as one needs to go to the market physically and
then select items only from the available list. So mostly it is difficult to get the product
as per our desire. Description About the products is less available and are mostly verbal
only. For this type of shopping, one needs to have an ample amount of free time.
Also, not really good markets exist everywhere, so many times good markets become out
of reach for certain people. These obsolete system slows down functionality of the workers
and also for company.

11
1.2.2 PROPOSED SYSTEM:
In the proposed system customers need not go to the shops for purchasing the products.
He/she can order the product he/she wishes to buy through the use of this system. The
shop owner can be the admin of the system.
The shop owner can appoint officials particularly to handle this, who will help the owner
in managing the customers and product orders. The system also endorses a home
delivery system for delivering the purchased products.
The main purposed system is essentially to automate entire operation and information of
sports store application at the particular given point of time. So the customers and users
get the best and fast information about the sports stuff at the given point of time.

1.2 SCOPE OF SYSTEM


Our designed online shopping system provides a 24×7 service , that is customers can
surf the website, place orders anytime they wish to. Also, the delivery system works
24×7 hours a week. Some of the features that can be modified and added to this system
in the future involve its implementation by local shopkeepers, where shops will be
providing an online interface to customers for shopping and placing orders.
Then some delivery persons can perform their work. This will be adding on
benefit for the customers as it will save their time, plus it adds on for the shopkeepers
also, as people will continue to shop from local shops rather than preferring to
supermarkets every time.
As, we are providing 360 degree view to your customer for the proper view of
the product so it is easy for customer to choose the product. Also, we had all types of
brand co-ordination so customer can find all types of brand from our website.

1.3 OBJECTIVES

The main objective of this system is to make the long and time consuming buying process much
easier, time saving and faster for customer to purchase items of the sports in an existing
shop. In order to build such an application complete web support need to be provided. A
complete and efficient web application which can provide the online shopping experience
is the basic objective of the project. The web application can be implemented in the form
of a web application with web view.

12
Chapter 2: PROPOSED SYSTEM REQUIREMENT GATHERING

2.1 STAKEHOLDER OF SYSTEM


STAKEHOLDERS:-

• ADMIN
• CUSTOMER
• VISITOR

➔ ADMIN
• The administrator is the super user of this application. Only admin have access into this admin
page. Admin may be the owner of the shop. The administrator has all the information about all
the users and about all products.
• Manage product
• Manage order
• Manage user
• Manage security of data
• Manage complains o Approve OR Disapprove user/owner

➔ CUSTOMER
• Register ID
• View product
• Edit Profile
• Search product
• Add to cart
• Purchase product

➔ VISITOR
• Visitors are the general people who visit the website but are not registered.
• They can view just products, product details, product preview, log-in/sign-up page and terms &
conditions.

2.2 REQUIREMENT GATHERING TECHNIQUE USED

Requirements Gathering is a fundamental part of any software development project.


These are things like “User wants to do X. How is this achieved?” In effect, Requirements
Gathering is the process of generating a list of requirements from all the stakeholders that
will be used as the basis for the formal definition of what the project is. For this there are
multiple techniques like:

13
1. INTERVEIW:-
Interviews of stakeholders and users are critical to creating the great software. Without
understanding the goals and expectations of the users and stakeholders, we are very unlikely
to satisfy them. We also have to recognize the perspective of each interviewee, so that, we
can properly weigh and address their inputs. Listening is the skill that helps a great analyst to
get more value from an interview than an average analyst. The most common technique for
the gathering requirements is to sit down with the end users and ask them what they need.
The discussion should be planned out ahead of time based on the type of requirements you
are looking for.

2. GROUP INTERVIEWS:-
A focus group is a gathering of people who are representative of the users or customers of a
product to get feedback. The feedback can be gathered about needs/opportunities/ problems
to identify requirements, or can be gathered to validate and refine already elicited
requirements. Group interviews are similar to one-to-one interview, except that more the one
person is being interviewed usually two to four. These interviews work well when everyone
is at the same level or has the same role.

3. QUESTIONNAIRES:-
Questions for the buyers:-
Q1. Have you purchased any sports product from online site?
➔ YES
➔ NO

Q2. How often do you use the web to find product information?
➔ EVERYDAY
➔ SEVERAL TIMES A WEEK
➔ ABOUT ONCE A WEEK
➔ SEVERAL TIMES A MONTH

Q3. HOW SATISFIED ARE YOU QUALITY OF PRODUCT?


➔ SATISFIED
➔ NEUTRAL
➔ NOT SATISFIED
➔ VERY DISSATIDFIED

Q4. HOW SAFE DID YOU FEEL WHILE SHARING YOUR DETAILS?
➔ VERY UNSAFE
➔ NOT SAFE
➔ NEUTRAL
➔ SAFE

14
➔ VERY SAFE

Q5. WOULD YOU LIKE TO ENROLL IN PAID SERVICES TO GET PRODUCT


EARLIER?
➔ YES
➔ NO
➔ MAYBE LATER

Q6. HOW HELPFUL WAS THE CUSTOMER SUPPORT STAFF?


➔ NOT AT ALL HELPFUL
➔ SLIGHTLY HELPFUL
➔ MODERATELY HELPFUL
➔ VERY HELPFUL
➔ EXTREMELY HELPFUL

Q7. WOULD YOU LIKE TO KNOW MORE ABOUT YOUR MEMBERSHIP BENEFITS?
➔ YES ➔ NO

Q8. DID YOU RECEVIED THE PRODUCT AT THE SHIPPING ADDRESS?


➔ YES
➔ NO

Q9. DO YOU GENERALLY FIND VARIOUS ALTERNATIES FOR SAME PRODUCTS?


➔ YES ➔ NO

Q10. WHICH FEATURES DO YOU LIKE MOST ABOUT A SPORTING GOODS OF


YOUR STORE?
➔ THE SIZE OF THE STORE
➔ THE VARIETY OF ITEMS
➔ THE BRANDS OF THE ITEMS SOLD
➔ THE FRIENDLY SERVICES

Q11. HOW WOULD YOU RATE YOUR SPORTING GOODS QUANTITY OF ITEMS?(1
BEING TERRIBLE TO 5 BEING AMAZING)
➔1
➔2
➔3
➔4
➔5

Q12. HOW MANY TIMES DO YOU SHOP ONLINE IN A MONTH?

15
➔ ONCE
➔ TWICE
➔ THRICE
➔ MORE THAN THRICE

Q13. WHICH PAYMENT METHOD DO YOU PERFER FOR ONLINE SHOPPING? ➔


PAYMENT GATEWAY
➔ USSD
➔ BANK TRANSFER

Q14. HOW WOULD YOU RATE YOUR OVERALL ONLINE SHOPPING


EXPERIENCE?
➔ EXCELLENT
➔ AVERAGE
➔ POOR

Q15. HOW LIKELY ARE YOU TO RETURN TO THIS WEBPAGE FOR YOUR ONLINE
SHOPPING?
➔ VERY LIKELY
➔ SOMEWHAT LIKELY
➔ HIGHLY UNLIKELY

Q16. WHAT IS YOUR GENDER?


➔ MALE
➔ FEMALE
➔ PERFER NOT TO SAY

Q17. HOW OFTEN DO YOU SHOP ON THIS WEBSITE?


➔ VERY OFTEN
➔ SELDOM
➔ NOT OFTEN

Q18. CHOOSE 2 PRODUCT YOU OFTEN BUYING FROM OUR WEBSITE?


➔ ACCESSORIES
➔ CLOTHING
➔ SKINCARE PRODUCT

Q19. WHAT IS THE BIGGEST CHALLENGE YOU FACE WITH ONLINE SHOPPING?
➔ SLOW CHECKOUT TIME
➔ LACK OF THE PRODUCT I WANT
➔ SLOW WEBPAGE RESPONSE TIME
16
Q20. HOW LIKELY ARE YOU TO RECOMMEND THIS SITE TO OTHER ONLINE
SHOPPERS?
➔ VERY LIKELY
➔ SOMEWHAT LIKELY
➔ VERY UNLIKELY

Q21.WHAT IS THE BIGGEST SHOPPING CONCERN ABOUT ONLINE SHOPPING?


➔ BREACH OF PERSONAL INFORMATION
➔ BREACH OF PAYMENT DETIALS
➔ POOR INTERNET CONNECTION

Q22. HOW DO YOU SPENT ON ONLINE SHOPPING EVERY MONTH?


➔ LESS THAN RS.5000
➔ RS.1000-RS.5000
➔ RS.500-RS.1000
➔ MORE THAN RS 5000

Q23. DO YOU ALWAYS SHOP ON YOUR WEBSITE?


➔ SURE
➔ NOT AT ALL

Q24. DID YOU ENJOY ONLINE SHOPPING EXPERIENCE ON YOUR WEBSITE?


➔ YES
➔ NO

Q25. WHAT IS YOUR FAVORITE SPORTS?


➔ BASKETBALL
➔ VOLLEYBALL
➔ FOOTBALL
➔ SOFTBALL
➔ CIRCKET
➔ BASEBALL

Q26. WOULD YOU RATHER HAVE EXPENSIVE TOP OF THE LINE EQUIPMENT
OR LOW PRICE EQUIPMENT?
➔ EXPENSIVE TOP LEVEL
➔ CHEAP BASIC LEVEL

Q27. WOULD YOU LIKE TO ENROLL IN PAID SERVICE TO GET PRODUCT


EARLY?

17
➔ YES
➔ NO
➔ MAYBE LATER

Q28. WHAT IS YOUR BRAND?


➔ NIKE
➔ PUMA
➔ ADIDAS
➔ CAMPUS

Q29. WHICH FEATURES DO YOU LIKE THE MOST ABOUT SPORTS SHOPPING
STORE?
➔ THE VARIETY OF ITEMS
➔ FRIENDLY SERVICES
➔ 360 DEGREE VIEW

Q30. WHAT IS YOUR AGE?


➔ LESS THAN 18
➔ 18+

2.3 CONSOLIDATED LIST OF REQUIREMENT

➔ System must be user friendly.


➔ System must be interactive.
➔ System must have security.
➔ User’s account and data should be maintained.

2.4 PROJECT DEFINITION

The title of our project “ONLINE CHAMPS WEAR”.

Online Sports store is an e-commerce based web application where the user can view the product
related to sports and can buy the product online. Admin or shop owners can add the product according to the
product category or product type.

This project contains all the common features of a web application like CRUD operation ADD
product, Delete product, Edit, and Update Product, Dummy payment page, Cart option to view the project,
or select product.

18
CHAPTER - 3: SYSTEM MANAGEMENT AND PLANNING

3.1 FEASIBILITY STUDY:-

• Feasibility is study of impact, which happens in organization by the development of the system.
• The impact can be either positive or negative. When the positive nominate the negatives, then the
system is considered feasible.

3.1.1 TECHNICAL STUDY:-

• Technical feasibility analysis is an attempt to study the project basically from a technician's
angle.
• There are number of features which are included into this system the main technologies and
the tools which are connected with this system is:

• HTML/CSS
• PHP
• MYSQL
• BOOTSTRAP

• It is a web based user interface. Thus it provides an easy access to the users.
• To access the system, internet connectivity is must require, because it is web Based web
application.
• From these, it is clear that current system developed is technically feasible.

3.1.2 ECONOMICAL STUDY:-

• An economic feasibility analysis should be performed to identity the financial risk


associated with the project.
• The cost of hardware and software for the class of application being considered. • The
benefits in the form of reduced costs of fewer costly errors.
• The cost if nothing change (i.e. the proposed system is not developed).
• We are using the open source platform to build our system.
• Thus, the project is economically feasible for both client and us.

3.1.3 OPERATIONAL STUDY:-

• Operational feasibility determines if the human resources are available to operate the system
once it has been installed.
• By doing so there is no need for the company either to recruit some special individual to run
the system or spend a huge amount to train some individual.
• Thus, the project is operationally individual. • This project well-planned design would
ensure the optimal utilization of the resources and would help in the improvement of
performance status.

19
3.2 HARDWARE – SOFTWARE REQUIREMENT:-

❖ Hardware requirement

• Server side requirement


Processor: 3.0 GHz
RAM: 4 GB
Hard disk: 1 TB

• Clients side requirement


Processor: 1.7 GHz
RAM: 500 MB

❖ Software requirement

Operating system: windows


Web server: IIS 8.0
Back – end tool: SQL server

❖ Client side requirement

Operating system: windows xp, vista, linux


Browser: internet explorer, Mozilla, chrome

20
3.3 SYSTEM PLANNING:-

3.3.1 WORK BREAKDOWN

21
3.3.2 GANTT CHART

3.4 PROCESS MODEL

Waterfall Model

• This model is also called as the classic life cycle model as it suggests a systematic sequential
approach to software development.

22
5 Phases of Waterfall Model:

1. Communication
2. Planning
3. Modelling
4. Construction
5. Deployment

1. Communication

In communication phase the major task performed is requirement gathering which helps
in finding out exact need of customer. Once all the needs of the customer are gathered the
next step is planning.

2. Planning

In planning major activities like planning for schedule, keeping tracks on the processes
and the estimation related to the project are done. Planning is even used to find the types
of risks involved throughout the projects. Planning describes how technical tasks are
going to take place and what resources are needed and how to use them.

3. Modelling

This is one the important phases as the architecture of the system is designed in this
phase. Analysis is carried out and depending on the analysis a software model is
designed. Different models for developing software are created depending on the
requirements gathered in the first phase and the planning done in the second phase.

4. Construction

The actual coding of the software is done in this phase. This coding is done on the basis
of the model designed in the modelling phase. So in this phase software is actually
developed and tested.

5. Deployment

In this last phase the product is actually rolled out or delivered & installed at customer’s
end and support is given if required. A feedback is taken from the customer to ensure the
quality of the product.

• When to use the waterfall model:

• This model is used only when the requirements are very well known, clear and fixed.
• Product definition is stable.
• Technology is understood.
• There are no ambiguous requirements
• Ample resources with required expertise are available freely
• The project is short

23
CHAPTER – 4 SYSTEM ANALYSIS AND PLANNING

4.1 UML (UNIFIED MODELING LANGUAGE)


• USE CASE DIAGRAM

ADMIN USE CASE DIAGRAM

24
CUSTOMER USE CASE DIAGRAM

25
• ACTIVITY DIAGRAM

ADMIN ACTIVITY DIAGRAM

26
CUSTOMER ACTIVITY DIAGRAM

27
\

• SEQUENCE DIAGRAM

ADMIN SEQUENCE DIAGRAM

28
CUSTOMER SEQUENCE DIAGRAM

29
• CLASS DIAGRAM

30
4.2 SYSTEM FLOW DIAGRAM

31
ADMIN SYSTEM FLOW DIAGRAM

32
CUSTOMER SYSTEM FLOW DIAGRAM

33
4.3 DATA DICTIONARY

• ADMIN TABLE

FIELD NAME DATA TYPE SIZE CONSTRAINT

Admin_id Int 5 Primary Key

Email_id Varchar 30 Not Null,Unique

Password Varchar 50 Not Null

• CUSTOMER TABLE

FIELD NAME DATA TYPE SIZE CONSTRAINT


Customer_id Int 5 Primary Key

Email_id Varchar 50 Not null,Unique

F_name Varchar 50 Not null

L_name Varchar 50 Not null

Mobile_no Varchar 15 Not null

Password Varchar 50 Not null

Address Varchar 100 Not null

Gender Varchar 1 Not null

Date of Birth Date - Not null

34
• CATEGORY TABLE

FIELD CONSTRAINT
DATA TYPE SIZE
NAME
Category_id Int 5 Primary Key

Category_name Varchar 20 Foreign Key

• PRODUCT TABLE

FIELD NAME DATA TYPE SIZE CONSTRAINT

Product_id Int 5 Primary Key

Category_id Int 5 Foreign Key

Product_Name Varchar 30 Not Null

Product_Brandname Varchar 30 Not Null

Product_description Varchar 100 Not Null

Product_Price Int 5 Not Null

Product_img Image path - Not Null

35
• CART TABLE

DATA
FIELD NAME SIZE CONSTRAINT
TYPE
Cart_id Int 5 Primary Key

Customer_id Int 5 Foreign Key

Product_id Int 5 Foreign Key

Product_Price Int 5 Not Null

Product_quantity Int 5 Not Null

Total_Price Int 10 Not Null

• FEEDBACK
TABLE

FIELD NAME DATA TYPE SIZE CONSTRAINT

Feedback_id Int 5 Primary Key

Customer_id Int 5 Foreign Key

36
• ORDER TABLE

FIELD NAME DATA TYPE SIZE CONSTRAINT

Order_id Int 5 Primary key

Customer_id Int 5 Foreign key

Cart_id Int 5 Foreign key

Payment_id Int 5 Foreign key

Order_status Varchar 20 Not Null

Ordercust_name Varchar 20 Not Null

Ordercust_address Varchar 20 Not Null

Ordercust_contact Varchar 20 Not Null

• WISHLIST TABLE

DATA
FIELD NAME SIZE CONSTRAINT
TYPE
Wishlist_id Int 5 Primary key

Product_id Int 5 Foreign key

Customer_id Int 5 Foreign key

37
4.4 USER INTERFACE

• HOME PAGE:-

38
• ADD TO CART:-

• ADMIN DASHBOARD:-

39
• INSERT PRODUCT:-

40
• USER PROFILE PAGE

AV SPORTS

41
• REGISTRATION PAGE:-

AV SPORTS

• FORGOT PASSWORD PAGE

AV SPORTS

42
• CHANGE PASSWORD PAGE

AV SPORTS

43
4.5 SYSTEM NAVIGATION

44

You might also like