ONLINE SHOPPING SYSTEM

A PROJECT REPORT
Submitted by
JOSHI JAY (170260107008)
SHAH JAINAM (170260107048)

OZA SHREY (170260107013)

In fulfilment for the award of the degree

Of

BACHELOR OF ENGINEERING
In
COMPUTER ENGINEERING

KIRC, KALOL

Department of Computer Engineering

Gujarat Technical University, Ahmedabad 2019-20.

1
 Kalol Institute of Technology & Research Center

COMPUTER ENGINEERING DEPARTMENT

2019-20

CERTIFICATE

This is to certify that the dissertation entitled “Online Shopping System” has been carried
out by JOSHI JAY , SHAH JAINAM , OZA SHREY under my guidance in fulfilment of the
degree of Bachelor of Engineering in Computer Engineering (6th semester) of Gujarat
Technological University, Ahmedabad during the academic year 2019-20.

Internal Guide Head Of The Department

Prof: JUI KHAMAR Prof: SHILPA SERASIYA

2
 ACKNOWLEDGEMENT

I take this opportunity to humbly express our thankfulness to all those concerned
with my project.

First of all I am thankful to KITRC for undertaking this project. I am sincerely

indebted to Mrs. JUI KHAMAR for giving me the opportunity to work on this
project. Her continuous guidance and help have proved to be a key to my success
in overcoming the challenges that I have faced during my project work. Her support
made the project a pleasantly memorable one .Without her help at all stages in spite
of her own work load; the completion of the project would not have been possible.

I express my sincere gratitude to Prof. SHILPA SERASIYA for his valuable

guidance and positive feedback.

There are so many persons without whose help I would never have conceived and
learnt , to whom I would like to express my gratitude – my friends , colleagues,
and of course CE Department of KITRC.

Last but not least I am thankful to almighty GOD and my PARENTS for giving me
such a good atmosphere to work hard and to succeed.

With regards,

JOSHI JAY (170260107008)

SHAH JAINAM (170260107048)
OZA SHREY (170260107013)

3
 Abstract
• This project is a web based shopping system for an existing shop. The project
objective is to deliver the online shopping application into android platform.

• This project is an attempt to provide the advantages of online shopping to

customers of a real shop. It helps buying the products in the shop anywhere
through internet by using an android device. Thus the customer will get the
service of online shopping and home delivery from his favorite shop. This
system can be implemented to any shop in the locality or to multinational
branded shops having retail outlet chains.

• If shops are providing an online portal where their customers can enjoy easy
shopping from anywhere, the shops won’t be losing any more customers to
the trending online shops such as flipcart or ebay. Since the application is
available in the Smartphone it is easily accessible and always available.

4
 INDEX
1. Introduction ................................................................................ (6)
1.1 Project Profile
1.2Project Summary
1.3Project Purpose
1.4Project Goals
1.5Project Scope

2. Project Management ........................................................................... (9-14)

2.1 Project Planning & Scheduling

2.2Risk Management
3. System requirement study. ........................................................... (15)

3.1 User characteristics 3.2Hardware Requirements

3.2 Software Requirements

4. Tools and technology ................................................................... (16)

4.1 Software 4.2 Hardware

5. Functional & behavioural Design o System ............................... (17-28)

5.1 Use Case diagram 5.5 Class Diagram, Object Diagram 5.9 Deployment Diagram
5.2E-R Diagram 5.6 Sequence Diagram
5.3Context Diagram 5.7 Activity Diagram
5.4Data-Flow Diagram 5.8 Component Diagram
6. Testing......................................................................................... (29-31)
6.1 Testing Plan
6.2 Testing Strategy
6.3 Testing Method
7. Prototype ............................................. (32-34)

8.Conclusion… ..............................................................................(35)

9.Bibliography ............................................................................... (36)

5
1. INTRODUCTION

1.1 PROJECT PROFILE

PROJECT TITLE Online Shopping System

ORGANIZATION Kalol Institute Of Technology And Research Center

TOOLS Hardware

• Quad Core Processor

• 8 GB RAM
• 1 TB Hard disk space

Software

Operating System : Windows

Development tool : PHP : Hypertext Preprocessor,

JavaScript, Ajax

Data Base : MySQL

SIZE 3 person

6
TEAM MEMBERS JOSHI JAY

SHAH JAINAM

OZA SHREY

GUIDED BY MRS. JUI KHAMAR

Submitted To: KALOL INSTITUTE OF TECHNOLOGY AND

RESEARCH CENTER,KALOL

1.2 PROJECT SUMMARY

• Project Title
Online Shopping System

• Development Tools
PHP : Hypertext Preprocessor, JavaScript, Ajax

• Project Guide
Mrs.Nidhi Joshi

7
 • Submitted By
JOSHI JAY (170260107008)
JAINAM SHAH (170260107048)
OZA SHREY (170260107013)

• Submitted To
Kalol Institute of Technology and Research Centre

1.3 PROJECT PURPOSE:-

• This project is an attempt to provide the advantages of online
shopping to customers of a real shop.
• It helps buying the products in the shop anywhere through internet

1.4 PROJECT GOALS:-

• Improve customer satisfaction through better service.
• Integrate with other systems; meet security, performance and
scalability requirements

1.5 PROJECT SCOPE:-

• The document is the one that describes the requirements along with
interfaces for the system. It is meant for use by the developers and will be the
basis for validating the final delivered system.
• surveying users before and after a redesign on how well they understand the
new product or service (brands) or cause (non-profits).

8
 2. Project management

2.1 PROJECT PLANNING AND SCHEDULING

• Project Development Approach and Justification:-

➢ The system development approach that we select is to deliver

software a bit at a time (Incrementally), repeating parts of the
development process for each delivery (iteration).

➢ Project Activities :-

• The major activity in the project includes the following tasks:

• To determine the methodology for the construction of the project.
• To determine the model of the software through which the project will
be identified.
• Determining the first face goals from the aim of the project.
• Designing the software development life cycle for the project.
• Identify the number of phases in the software development life cycle of
the project.

➢ Project Management:-

9
 • Online Shopping System

➢ Planning, scheduling and tracking of project:

• The project planning consists of:

• Selection of Suitable software development model.
• Risk Management Plan, which involves the risk identification and risk
assessments.

➢ Project Scheduling:
• Generalized project scheduling tools and technique can be applied with
little modification to software projects.
• Program evolution and review techniques (PERT) and critical path
method (CPM) are two project scheduling method that can be applied
to software development. Both techniques are driven by information
already developed in earlier project planning activities:

• Estimate of effort.
• A decomposition of the product function.
• The selection of appropriate process model and task set.
• Decomposition of tasks.

1
2.2. Risk Managemant
Creating a Task Management System is a difficult undertaking. Lots of things
can go wrong and frankly, many often do. It’s for this reason that being prepared
understanding the risks and taking proactive measure to avoid or manage them is a
key element of good software project management.
Recognizing what can go wrong is the first step called Risk Identification. Next each
risk is analyzed to determine the likelihood that it will occur and the damage that it
will do if it does occur. Once this information is established, risks are ranked, by
probability and impact. Finally a plan is developed to manage those risks with high
probability.

1
Risk Probability Effect

Software components which

should be reused contain Moderate Serious
defects limit their
functionality

Change of requirements High Serious

which require proposal of Moderate Serious
major design rework

Scheduling slippage: The

time required for the High Serious
development of software is
underestimated, so schedule
slippage will occur

The size of software is High Tolerable

underestimated

1
 Power
High Tolerable
Failure

Risk Identification:-
The followings are the possible risks, which is associated with project. We have
identified mainly technical and project risks.

Technical Risks:-

• Our software doesn’t work on all operating system.

• It cannot work if proper system is not installed.

Project Risks:-
• Scope might have been wrongly defined and the project might go in the wrong
direction.
• The time limits might not have been properly calculated as per the scope. If
the project was not properly scheduled, or if the scope was ill defined, it might
not be possible to finish the project at the right time.
• Scope creep could occur. The expectations and requirements have increased
or may be changed.
• Certain technical problems have remained unsolved.

1
Risk Analysis and Planning:-
To handle the risks we have prioritized it. The damaging risks can be handled
first and then most likely risks. Since the risk related to the schedule slippage
arise primarily due to the intangible nature of the software, so we had to do
the visibility of software requirements documentation and reviewing the
relevant documents during the developments. Every phase can be broken into
the reasonably sized tasks and milestones can be scheduled for these tasks.

1
 3. System requirement study

3.1 User Characteristics

There are 3 kinds of users for the proposed system.
• Administrators :
Administrators are the ones who adds or administers the categories for the products,
and administers the Vendors.
• Vendors/Sellers:
Vendors/Sellers will add their products to the products to the database,which will be
seen in the website to the end users or say customers who can buy the products by
selecting the one they need.Vendors will have the special privileges than the end
users,and have ability to manage the products added by them.
• End Users/Customers:
The end user will be the one who visits the website and buys products online from
the ones added by the Vendors/Sellers.
3.2 SOFTWARE REQUIREMENT

• Operating System : Unix, Linux, Mac, Windows etc..

• Development tool : PHP : Hypertext Preprocessor,
JavaScript, Ajax
• Data Base : MySQL

3.3 HARDWARE REQUIREMENT

• OS : 4.0 or Higher.
• RAM : 512mb or Higher.

1
 4. Tools & Technology

4.1 SOFTWARE

• We have selected PHP application development tool for

creating our system as it is very much student friendly as
the developer can do designing.
• And for Data-Base , we select MYSQL because of its great
advantages in data base management field. It is very well
easy to use.

4.2 HARDWARE

• We have used the hardware that which is the basic

requirement for using the javascript , php, mysql etc.
properly.
• We have used the hardware specification so that we could
get the optimized performance.

1
 5. Functional and behavioral design of system
5.1 USE CASES FOR ONLINE SHOPPING SYSEM

Use Case Diagram

1
 5.2 E-R DIAGRAM for ONLINE SHOPPING SYSEM

1
5.3 CONTEXT DIAGRAM

1
5.4 DATA FLOW DIAGRAM

Data Flow Diagram 0 level

2
Data Flow Diagram 1 level for Admin

2
Data Flow Diagram 1 level for User

2
5.5 Class Diagram, Object Diagram:

2
5.6 Sequence Diagram:

2
5.7 Activity Diagram:

Activity diagram user-side

2
Activity diagram Admin-side

2
5.8 Component Diagram

2
5.9 Deployment Diagram

2
6. Testing
6.1 TESTING PLAN:-

• Development of a complex client/server three tier application requires that a

methodology be developed for more effective application or software testing
and quality assurance. Testing is made to find errors in the application. The
strategy adopted for the testing in our application.

6.2 TESTING STRATEGY:-

“Testing cannot show the absence of defect. It can only show that software

errors are present.”

• Testing is the process of executing a program with the explicit intention of

finding errors that is, making the program fail. Testing is very crucial and
most expensive phase of the software development. Before delivering the
system, the process of rigorous testing is done to check that software works
as it is expected and meets its specifications. For that two testing strategies
are there Code Testing & Specification Testing. We have used both of them
at different levels of code development.

➢ TESTING (WHITE BOX TESTING)

The code-testing strategy examines the logic of the program. To follow this
testing method, test cases should be developed that result in executing every
instruction in the program or module; that is, every path through the program

2
 is tested. A path is a specific combination of conditions that is handled by the
program.
This testing is used at initial stage of the development, as code volume is very
less at this stage. It checks only the aspects are implemented correctly or not.

But this strategy does not indicate the code meets its specifications nor does
it determine weather all aspects are even implemented. So with this, another
strategy is also used.

➢ SPECIFICATION TESTING (BLACK BOX TESTING)

• In this strategy, the specifications stating what the program should do and
how it should perform under various conditions are examined. Test cases
are developed for each condition or combination of conditions
• The analyst does not look into the program to study the code and is not
concerned about weather every instruction or path through the program is
tested. This is more efficient method, since it focuses on the way software
is expected to be used.

6.3 TESTING METHODS:-

• Different types of testing method are used,

➢ UNIT TESTING:-

• In it analyst tests the program making up a system. The software units in a

system are the modules and routines that are assembled and integrated to
perform a specific function.

3
• It focuses on modules, independently of one another, to locate errors. This
enables the tester to detect errors in coding and logic that are contained
within the module alone.
➢ Bottom-Up Unit Testing:-
• It can be performed from the bottom up, starting with the smallest and
lowest-level modules and proceeding one at a time. For each module in
bottom-up testing, a short program executes the module and provides the
needed data, so that the module is asked to perform the way it will when
embedded within the larger system.
➢ Top-Down Unit Testing:-
• As the name implies, begins with the upper-level modules. However, since
the detailed activities usually performed in lower-level routines are not
provided, stubs are written. A sub is a module can be called by the upper-
level module and that, when reached properly, will return a message to the
calling module, indicating a proper interaction occurred.
➢ SYSTEM TESTING:-
• System testing does not test the software per se but rather the integration
of each module in the system. It also tests o find discrepancies between
the system and its original objective, current specifications and system
documentation.
• The primary concern is the compatibility of individual modules.
Analysts are trying to find areas where modules have been designed
with different specifications.

3
7. Prototype

1. Login page

3
2. Home page

3
3. Categories page

3
8. CONCLUSION:
• The project entitled Online shopping system was completed successfully.

• The system has been developed with much care and free of errors and at the
same time it is efficient and less time consuming. The purpose of this project
was to develop a web application and an android application for purchasing
items from a shop.

• This project helped us in gaining valuable information and practical knowledge

on several topics like designing web pages using html & css, usage of
responsive templates, designing of android applications, and management of
database using mysql .

• The entire system is secured. Also the project helped us understanding about
the development phases of a project and software development life cycle. We
learned how to test different features of a project.

• This project has given us great satisfaction in having designed an application

which can be implemented to any nearby shops or branded shops selling
various kinds of products by simple modifications.

3
 9. Bibliography
Reference Websites:-
• www.google.com
• www.w3school.com
• www.wikipedia.com