documentation
documentation
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
1 Introduction 11
1.4 Objectives 12
9
3.4 Process Model 22
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.
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.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
• 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.
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
Q4. HOW SAFE DID YOU FEEL WHILE SHARING YOUR DETAILS?
➔ VERY UNSAFE
➔ NOT SAFE
➔ NEUTRAL
➔ SAFE
14
➔ VERY SAFE
Q7. WOULD YOU LIKE TO KNOW MORE ABOUT YOUR MEMBERSHIP BENEFITS?
➔ YES ➔ NO
Q11. HOW WOULD YOU RATE YOUR SPORTING GOODS QUANTITY OF ITEMS?(1
BEING TERRIBLE TO 5 BEING AMAZING)
➔1
➔2
➔3
➔4
➔5
15
➔ ONCE
➔ TWICE
➔ THRICE
➔ MORE THAN THRICE
Q15. HOW LIKELY ARE YOU TO RETURN TO THIS WEBPAGE FOR YOUR ONLINE
SHOPPING?
➔ VERY LIKELY
➔ SOMEWHAT LIKELY
➔ HIGHLY UNLIKELY
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
Q26. WOULD YOU RATHER HAVE EXPENSIVE TOP OF THE LINE EQUIPMENT
OR LOW PRICE EQUIPMENT?
➔ EXPENSIVE TOP LEVEL
➔ CHEAP BASIC LEVEL
17
➔ YES
➔ NO
➔ MAYBE LATER
Q29. WHICH FEATURES DO YOU LIKE THE MOST ABOUT SPORTS SHOPPING
STORE?
➔ THE VARIETY OF ITEMS
➔ FRIENDLY SERVICES
➔ 360 DEGREE VIEW
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
• 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.
• 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.
• 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
❖ Software requirement
20
3.3 SYSTEM PLANNING:-
21
3.3.2 GANTT CHART
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.
• 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
24
CUSTOMER USE CASE DIAGRAM
25
• ACTIVITY DIAGRAM
26
CUSTOMER ACTIVITY DIAGRAM
27
\
• 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
• CUSTOMER TABLE
34
• CATEGORY TABLE
FIELD CONSTRAINT
DATA TYPE SIZE
NAME
Category_id Int 5 Primary Key
• PRODUCT TABLE
35
• CART TABLE
DATA
FIELD NAME SIZE CONSTRAINT
TYPE
Cart_id Int 5 Primary Key
• FEEDBACK
TABLE
36
• ORDER TABLE
• WISHLIST TABLE
DATA
FIELD NAME SIZE CONSTRAINT
TYPE
Wishlist_id Int 5 Primary 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
AV SPORTS
42
• CHANGE PASSWORD PAGE
AV SPORTS
43
4.5 SYSTEM NAVIGATION
44