Presentation for Online Shopping Software Project. For Project source code & report mail at prakhartated@gmail.com

1. “ONLINE SHOPPING MANAGEMENT
SYSTEM”
1. PRAKHAR TATED
2. MANSIMRAN KAUR
3. ANUJ SONI
4. PREETI SONI
by
Prof. RICHA MISHRA
SHRI BALAJI INSTITUTE OF TECHNOLOGY & MANAGEMENT BETUL (M.P.)
Department of Computer Science & Engineering

2. 1. INTRODUCTION
2. LITERATURE SURVEY
3. SYSTEM ANALYSIS AND DESIGN
4. RESULS/OUTPUTS
5. CONCLUSION /RECOMMENDATION
6. . REFERENCES

3. Problem definition
 “On-Line Shopping System” is a web-based project which is made for remote-
shopping or shopping through Internet. As the technology is being advanced the
way of life is changing accordance. Now a day’s we can place the order for
anything from our home. There is no need to go the shop of the things we want.
The order can be placed online through Internet. The payment, the confirmation of
purchasing; we can do everything we want. Now we can think that how the days
have been changed with time. People had to stand in rows to wait there terms to
buy a particular thing from a popular shop. But what is happening now a day’s; we
can extremely surprise that those things can be available on the door-step in few
hours.
 People had to suffer the rush of the market when they went for shopping. They
used to think hundred times to buy anything having the sufficient money for
shopping. The problem was the rush; the quarrel at the time of buying the things.
But the advancement of technology brought the new way for shopping. The way of
shopping was completely changed with the coming of Internet Technology. People
have to fill a simple form on the internet to place their order on any popular shop
or shopping-mall for the thing they want to buy. Now they can place their order
from the home.
 This project entitled “On-Line Shopping” is an implementation of the above
description. It means, it implements the E-shopping or in other word shopping
through Internet. It lets the user to place their order online for any article.

4. Project overview/specifications
 The central concept of the application is to allow the customer to
shop virtually using the Internet and allow customers to buy the
items and articles of their desire from the store. The information
pertaining to the products are stores on an RDBMS at the server
side (store). The Server process the customers and the items are
shipped to the address submitted by them.
 The application was designed into two modules first Os for the
customers who wish to buy the articles. Second is for the
storekeepers who maintains and updates the information
pertaining to the articles and those of the customers?
 The end user of this product is a departmental store where the
application is hosted on the web and the administrator maintains
the database. The application which is deployed at the customer
database, the details of the items are brought forward from the
database for the customer view based on the selection through
the menu and the database of all the products are updated at the
end of each transaction.
 Data entry into the application can be done through various
screens designed for various levels of users. Once the
authorized personnel feed the relevant data into the system,
several reports could be generated as per the security.

5. hardware software specification
 Hardware Requirement:-
 Processor :Pentium Processor ISA 32 Family, Intel Core or
above
 Secondary Storage :80 GB HDD
 Memory :512 MB or above
 Others :17" Color Monitor, Printer, Scanner,
 Keyboard, Mouse.

 Software Requirement

 Operating System : Windows 7/8/10 or Linux
 User Interface : HTML, CSS
 Client-side Scripting : JavaScript, JSP
 Programming Language : Java
 Web Applications : JDBC, Servlets, JSP
 IDE/Workbench : NetBeans 8.2
 Database : SQL
 Server Deployment : Tomcat 8.x

6. Exiting system
 In the existing system all transactions, dealings of products,
purchasing of products were done manually which is time
consuming.
 Reports are prepared manually as and when needed. Maintaining
of reports is very tedious task.
 To buy any product user has to collect information about it either
by visiting the shop or asking people which is the better one.
 There is no computer system for handling payments. All
calculations are performed manually which may not be accurate
always. Maintaining the record is really a tedious task.
 Any internet user can use this existing website to search for any
kind of products, select particular products from a wide range of
products.
 Once they make of their mind to purchase any particular thing
they can place an order and make a payment throw various
available payment option.

7.  Proposed system
 The development of this new system contains the following activities,
which try to develop on-line application by keeping the entire process in
the view of database integration approach.
 Secure registration and profile management facilities for Customers.
 Browsing through the e-Mall to see the items that are there in each
category of products like Apparel, Kitchen accessories, Bath accessories,
Food items etc.
 Creating a Shopping cart so that customer can Shoppe ‘n’ no. of items
and checkout finally with the entire shopping cart
 Customers should be able to mail the Shop about the items they would
like to see in the Shop
 Secured mechanism for checking out from the Shop( Credit card
verification mechanism )
 Updates to customers about the Recent Items in the Shop.
 Uploading ‘Most Purchased’ Items in each category of products in the
Shop like Apparel, Kitchen accessories, Bath accessories, Food items etc.

8.  Feasibility study
 Feasibility is the determination of whether or not a project is worth doing. The
process followed in making this determination is called a feasibility study. This
type of study determines if a project can and should be taken. Once it has been
determined that a project is feasible, the analyst can go ahead and prepare the
project specification which finalizes project requirements.

 Different Type of Feasibility Study:-
 In the conduct of the feasibility study, the analyst will usually consider seven
distinct, but inter- related types of feasibility. They are
 Technical Feasibility
 Operational Feasibility
 Economic Feasibility
 Social Feasibility
 Management Feasibility
 Legal Feasibility
 Time Feasibility

9.  This is concerned with specifying equipment and software that
will successfully satisfy the user requirement; the technical needs
of the system may vary considerably, but might include:
 The facility to produce outputs in a given time:
 Response time under certain conditions.
 Ability to process a certain volume of transaction at a
 Particular speed.
 Facility to communicate data to distant location.

 In examine technical feasibility; configuration of the system is
given more importance than the actual make of hardware. The
configuration should give the complete picture about the
system’s requirement: How many workstations are required, how
these units are interconnected so that they could operate and
communicate smoothly. What speeds of input and output should
be achieved at particular quality of printing. This can be used as
a basis for the tender document.

10.  It is mainly related to human organization and
political aspects. The points to be considered are:
 What changes will be brought with the system?
 What organizational structures are distributed?
 What new skills will be required? Do the existing
staff members have these skills? If not, can they
be trained in due course of time?
 Generally project will not be rejected simply
because of operational infallibility but such
considerations are likely to critically affect the
nature and scope of the eventual
recommendations.

11. Economic analysis is the most frequently used
technique for evaluating the effectiveness of a
proposed system. More frequently known as cost /
benefit analysis; the procedure is to determine the
benefits and saving that are expected from a
proposed system and compare them with costs. If
benefits outweigh costs, a decision is taken to
design and implement the system. Otherwise,
further justification or alternative in the proposed
system will have to be made if it is to have a
change of being approved. This is an ongoing
effort that improves in accuracy at each phase of
the system life cycle.

12. Social feasibility is a determination of whether
a proposed project will be acceptable to the
people or not. This determination typically
examines the probability of the project
accepted by the group directly affected by the
proposed system change.

13. It is a determination of whether a proposed
project will be acceptable to management .if
does not accept a project or gives a negligible
support to it; the analyst will tend to view the
project as a non-feasible one.

14. Legal feasibility is a determination of whether a
proposed project infringes on known Acts
Statutes, as well as any pending legislation.
Although in some instances the project might
appear sound, on closer investigation it may be
found to infringe on several legal areas.

15. Time feasibility is a determination of whether a
proposed project can be implemented fully
within a stipulated time frame. If a project
takes too much time it is likely to be rejected.

16.  Requirement specification
 It is quite difficult and time consuming task to find the
information as well as maintaining information manually. If
all these information are to be kept at a single place it is
also not possible in the manual system. Computerized
system will upgrade and manage information very easily.
 As it is a web-based application so it uses Internet
technologies and its hardware/software requirement will
also be more comprehensive than Desktop application
system. Some Network devices will be required like
modems, switches, Internet connection.
 Software required for the system is also different from a
normal desktop system. First of all a server software will
be mandatory. A browser is also needed as a client
process on the user side.

17.  Flow charts /DFDs/E-RDs
 A data flow diagram is a primary graphic tool for the analysis phase of
the system development life cycle. Analysts to show what happens to
data items, as they flow through the system use it.
 An information moves through software, it is modified by a series of
transformations. Data flow diagram is a graphical technique that depicts
information flow and the transforms the are as data move from input to
output. The basic form of a DFD is also known as data flow graph or a
bubble chart. The DFD serve two purposes:
 (i) To provide and indication of how data are transform as they move
through the system.
 (ii) To depict the functions that transforms that data flow.
 The DFD provides additional information that is used during the analysis
of information domain and serve as a basis for the modeling of function.

18. Basic notations, which used to create DFD, are as
follows:
 RECTANGLE
It is used to represent an external entity or another
system element that produces information for
transformation or receive information.
 CIRCLE
It used to represent any process or transform
which applied on data
 ARROW
Arrow represents one or more data items or data
objects.
 PARALLEL LINES
The parallel line used to represent any database.

23.  Process: Software process as a framework for the tasks that are required to build high quality
software. Or we can say that process defines the approach that is taken as software is
engineered.
Process model used by us:
 Spiral model: The Spiral model originally proposed by Boehm , is an evolutionary software
process model that couples the iterative nature of prototyping with the controlled & systematic
aspects of the linear sequential model . It provides the potential for rapid development of
incremental version of the software.
 Using the spiral model software is developed in a series of incremental releases.
 A spiral model is divided into a number of framework activities also called task regions. A
spiral model contains six task regions:
 Customer Communication: Tasks required to establish effective communication between
developer & customer.
 Planning: Tasks required to define resources, timeline & other project related information.
 Risk analysis: Task required to access.
 Engineering: Tasks required to build one or more representation of the application.
 Construction & release: Task required to construct, test, install & provide user support (e.g.,
documentation & Training)
 Customer evaluation: Tasks required to obtain customer feedback based on evolution of the
software representation created during the engineering stage & implemented during the
installation stage.

24.  Step 1 : Initialization Username and Password.
 Step 2 : Check the Username and Password. If Invalid Username and
Password then Go To Step 1 otherwise Go To Step 3.
 Step 3 : Check Enter Operator is Admin or User. If Admin Go To
Step 4 otherwise Go To Step 8.
 Step 4 : If create a new user Go To step 5 otherwise Go To Step 6.
 Step 5 : Fill up the information in registration form and create a
Username and Password and fill up other information of this
new User. Go To Step 9.
 Step 6: Written detail of following in the User table.
Username, password, Firstname, Lastname, Gender, Address,
City, State,Zip- code , Contact no, Email id and ISAdmin
 Step 7 : If Request Issue then Update user ISAdmin or not information
 and entry in the User table. Go To Step 9.
 Step 8 : Go To Step 6.
 Step 9 : End.

26.  Design and Test steps/ criteria
Database is collection of data that can be
treated as single unit. This Single or individual
unit is called table. In relational database
system table is combination of rows and
columns which show records and fields
respectively. After great efforts we determine
the main entities, there attribute and
relationship among them. After determining all
these entities, we design the table structure as
follows:

27. Field Type Null Key Default Extra
Id Int No Pri Null auto_incre
ment
Category_n
ame
Varchar Yes Null
Descriptio
n
Varchar Yes Null

28. Field Type Null Key Default Extra
Id_history Int No Pri Null auto_increme
nt
User_id Int Yes Mul Null
Product_id Int Yes Mul Null
Time_of_orde
r
Timestamp Yes Null
Quantity Int Yes Null
Amount Double Yes Null

29. Field Type Null Key Default Extra
Product_co
de
Int No Pri Null auto_incre
ment
Id Int Yes Mul Null
Product_na
me
Varchar Yes Null
Image Varchar Yes Null
Amount Double Yes Null
Manufactur
er
Varchar Yes Null
Informatio
n
Varchar Yes Null

30. Field Type Null Key Default Extra
User_id Int No Pri Null auto_incre
ment
Username Varchar No Null
Password Varchar No Null
Date_of_bi
rth
Date Yes Null
Sex Varchar Yes Null
Email Varchar Yes Null
Mobile_no Varchar Yes Null
Address Varchar Yes Null
Role Varchar Yes Null

31.  Software testing is a criterion of software quality assurance and
represents the ultimate review of specified designing and coding.
 System testing reveals the presence of errors in the software
developed.
 Testing is the process of executing a program with the intent of
finding an error.
 A good test is one that has a high probability for finding a yet
undiscovered error.
 A successful test is one that uncovers the hidden errors.
Characteristics of Testing:
 Testing begins at the module level and works outward and
towards the integration of the entire computer based system.
 Different testing techniques are appropriate at different level of
time.

33. This is the art of tying each individual
functional unit together into a system and
testing end-to-end. In the previous example, it
might mean creating a shopping basket of
various items (taxable and non-taxable), and
passing that basket object to the VAT
calculation engine. Once the VAT has been
calculated, pass the output to a payment
system and ensure the proper payment is
made. It's a 'day in the life' of a piece of data.

34. This is the activity of taking a new piece of
functionality and testing it deeply. It does not
involve testing data as it passes in and out of
this functionality. For instance, integration
testing a VAT calculation formula would involve
inputting various values and validating the
output.

35. is a level of software testing where individual units/
components of a software are tested. The purpose is to
validate that each unit of the software performs as
designed. A unit is the smallest testable part of any
software. It usually has one or a few inputs and usually
a single output. In procedural programming, a unit may
be an individual program, function, procedure, etc. In
object-oriented programming, the smallest unit is a
method, which may belong to a base/ super class,
abstract class or derived/ child class. (Some treat a
module of an application as a unit. This is to be
discouraged as there will probably be many individual
units within that module.) Unit testing frameworks,
drivers, stubs, and mock/ fake objects are used to
assist in unit testing.

36. 1)Validation is the process of evaluating software at the end of the development
process to determine whether software meets the customer expectations and
requirements.
2)Execution of code is comes under Validation.
3)Validation activity is carried out just after the Verification.
4)It determines whether the software is fit for use and satisfy the business need.
5)Includes all the dynamic testing techniques.
6)It is basically checking of developed program based on the requirement
specifications documents & files.
7)Following activities are involved in Validation: Testing like black box testing, white
box testing, gray box testing etc.
8)It is computer based execution of program.

37. Home Page

46.  After having detail study on Online Shopping one can see a great
change in the behavior of people in many manners like their
attitude, buying patterns. In earlier times people use to do
manual shopping but now as time changed people are becoming
busy and due to which technologies has brought a new
revolution i.e. “Online Shopping.”
 The central concept of the application is to allow the customer to
shop virtually using the Internet and allow customers to buy the
items and articles of their desire from the store. The information
pertaining to the products are stores on an RDBMS at the server
side (store). The Server process the customers and the items are
shipped to the address submitted by them.
 The application was designed into two modules first Os for the
customers who wish to buy the articles. Second is for the
storekeepers who maintains and updates the information
pertaining to the articles and those of the customers?

47.  The end user of this product is a departmental store
where the application is hosted on the web and the
administrator maintains the database. The
application which is deployed at the customer
database, the details of the items are brought
forward from the database for the customer view
based on the selection through the menu and the
database of all the products are updated at the end of
each transaction.
 Data entry into the application can be done through
various screens designed for various levels of users.
Once the authorized personnel feed the relevant data
into the system, several reports could be generated
as per the requirements.
 This system offers information relevant to the user
accessing the application thus avoiding unnecessary
overloading and at the same time maintaining the
security.

48.  We think that not a single project is ever considered
as complete forever because our mind is always
thinking new and our necessities also are growing.
 Our application Also, if you see at the first glance that
you find it to be complete but we want to make it still
mature and fully automatic.
 As system is flexible you can generate more report
and screen as and when required.
 The system is modified in future as per the owner
requirement.
 In this system we can add more reports about users
so more and more Information about achat.com

49.  www.kashipara.com
 www.scribd.com
 The Complete Reference of Java – Patricknaughton
 Analysis & Design of Information – James A. Senn
 Software Engineering – Fairly
 Software engineering by Roger s. Pressman