Online Shopping E Cart

A Major Project –II

Submitted in partial fulfillment of the requirement for the award of degree of Bachelor of
Technology in Computer Science and Engineering

Submitted to
RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA, BHOPAL

(M.P.)

Submitted by:

Ahmad Raza Ansari 0191CS191019

Nayan Tamrakar 0191CS191098

Prafull Singh Tomar 0191CS191110

Under the Guidance of:

Ms. MANJARI SINGH RATHORE

Dept. of CSE

DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

TECHNOCRATS INSTITUTE OF TECHNOLOGY (EXCELLENCE), BHOPAL

SESSION: 2021-22

TECHNOCRATS INSTITUTE OF TECHNOLOGY (EXCELLENCE), BHOPAL

 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

CERTIFICATE

This is to certify that the work embodies in this Major Project-II entitled “Online
Shopping E Cart” being submitted by Ahmad Raza Ansari (0191CS191019), Nayan
Tamrakar (0191CS191098), Prafull Singh Tomar (0191CS191110), () for partial
fulfillment of the requirement for the award of degree of “Bachelor of Technology in
Computer Science and Engineering” discipline to “RAJIV GANDHI PROUDYOGIKI
VISHWAVIDYALAYA, BHOPAL (M.P.)” during the academic year 2021-22 is a record of
real piece of work, carried out by her/him/them under my supervision and guidance in
the “Department of Computer Science and Engineering”, Technocrats Institute of
Technology (Excellence), Bhopal (M.P.).

SUPERVISED BY FORWARDED BY

Ms. MANJARI SINGH RATHORE Prof. (Dr.) Yogadhar

Pandey

Dept. of CSE Head, Dept. of CSE

APPROVED BY

Prof. (Dr.) K.K. Dwivedi

Director

TIT, Bhopal

TECHNOCRATS INSTITUTE OF TECHNOLOGY (EXCELLENCE), BHOPAL

 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

DECLARATION

We, Ahmad Raza Ansari (0191CS191019), Nayan Tamrakar (0191CS191098), Prafull

Singh Tomar (0191CS191110), () students of Bachelor of Technology in Department
of Computer Science and Engineering discipline, Session: 2021-22, Technocrats
Institute of Technology (Excellence), Bhopal (M.P.), hereby declare that the work
presented in this Major Project –II entitled “Online Shopping E Cart” is the outcome of
my/our own work, is real and correct to the best of my/our knowledge and this work has
been carried out taking care of Engineering Ethics. The work presented does not
infringe any patented work and has not been submitted to any other university or
anywhere else for the award of any degree or any professional diploma.

I also declare that “A check for plagiarism has been carried out on the Project
and is found within the acceptable limit and report of which is enclosed herewith”.

Date:

Ahmad Raza Ansari

0191CS191019

Nayan Tamrakar
0191CS191098

Prafull Singh Tomar

0191CS191110
 ACKNOWLEDGEMENT

We, Ahmad Raza Ansari, Nayan Tamrakar, Prafull Singh Tomar, take the opportunity to
express my/our cordial gratitude and deep sense of indebtedness to the management of
my/our college for providing me a platform for completion of my/our Major Project. I
express a deep sense of gratitude to my Guide Ms. MANJARI SINGH RATHORE, Dept of
CSE for the valuable guidance and inspirational guidance from the initial to the final level
that enabled me to develop an understanding of this Project work.

I would like to give my sincere thanks to Prof. (Dr.) Yogadhar Pandey, Head,
Dept of CSE, for their kind help, encouragement and co-operation throughout my
Project period I owe my special thanks to our Prof. (Dr.) K.K. Dwivedi, Director, TIT
(Excellence) for their guidance and suggestions during the Project work. I thank
profusely to all the lecturers and members of teaching and non-teaching staff in
Computer Science and Engineering Department who helped in many ways in
making my education journey pleasant and unforgettable.

Lastly, I want to thank my parents, friends and to all those people who had
contributed to my project directly or indirectly.

Ahmad Raza Ansari

0191CS191019

Nayan Tamrakar
0191CS191098

Prafull Singh Tomar

0191CS191110
 INTRODUCTION

The Project entitled "ONLINE SHOPPING CART" is a web-based application. Software

developed in JAVA LANGUAGE using Java as frontend and MySql as backend on
Windows Operating System.

The main aim of the project is to improve the services of Customers and vendors. It maintains
the details of customer payments, product receipts, addition of new customers, products and
also updating, deletion for the same. It also mails the details of users which have logged in
the shopping portal to the email id which they have given during the signup process.

The primary features of the project entitled are high accuracy,design flexibility and easy
availability. And also it uses database tables Representing entities and relationships between
entities.The site containing avery interesting feature sending a mail to the customer about
their registration process

Online shopping is the process whereby consumers directly buy goods, services etc. from a
seller interactively in real-time without an intermediary service over the internet. Online
shopping is the process of buying goods and services from merchants who sell on the
Internet. Since the emergence of the World Wide Web, merchants have sought to sell their
products to people who surf the Internet. Shoppers can visit web stores from the comfort of
their homes and shop as they sit in front of the computer. Consumers buy a variety of items
from online stores. In fact, people can purchase just about anything from companies that
provide their products online.

Books, clothing, household appliances, toys, hardware, software, and health insurance are
just some of the hundreds of products consumers can buy from an online store.
Many people choose to conduct shopping online because of the convenience. For example,
when a person shops at a brick-and- mortar store, she has to drive to the store, find a parking
place, and walk throughout the store until she locates the products she needs. After finding
the items she wants to purchase, she may often need to stand in long lines at the cash register.
Despite the convenience of online shopping, not everyone chooses to purchase items and
services online. Some people like the idea of physically going to a store and experiencing the
shopping process. They like to touch the merchandise, try on clothing, and be around other
people. Online shopping doesn't permit shoppers to touch products or
 1.OVERVIEW OF PROJECT

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)
which is maintained in My SQL. The Server process the customers and the items are shipped
to the address submitted by them.

The application was designed into two modules:-

I> Customers who wish to buy the articles.
II> 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.
 2. SYSTEM STUDY

Information systems projects’ originate from many reasons: to achieve greater speed in
processing data, better accuracy and improved consistency, faster information retrieval,
integration of business areas, reduced cost and better security. The sources also vary project
proposals originate with department managers, senior executives and systems analysis.

Sometimes the real origin is an outside source, such as a government agency which stipulates
a systems requirements the organisation must meet. When the request is made, the first
systems activity, the preliminary investigation, begins. The activity has three parts: request
clarification, feasibility study and request approval.

2.1 Existing System:

The existing system was an automated system. But It was found to be inefficient
in meeting the growing demands of population .

2.1.1 Drawbacks in the existing systems:

Disadvantage of the existing system:

 Time Consuming
 Expensive
 Needed an agent
 We have to out for that
 3.SYSTEM ANALYSIS

• This system is all about the converting the shopping system from manual to online.
• Customer can buy products online after login to the site.
• Administrator is adding product to database.
• Administrator can edit or delete the product from the database.
• After buying and making payment the products are send to customers address that he has
given.
• Customer can write feedback for the product or services.
• Admin can see daily sell and feedback given by customer.
• Administrator is adding the delivery report to the database.
• Both admin and customer can see the delivery report.

3.1 Purpose:
Online shopping tries to enhance access to care and improve the continuity
and efficiency of services. Depending on the specific setting and locale, case managers are
responsible for a variety of tasks, ranging from linking clients to services to actually
providing intensive shopping and delivery services themselves.

Main objective
• To shop wile in the comfort of your own home, without having to step out of the door.
• Sell at lower rate due to less over head.
• Provide home delivery free of cost.
• No wait to see the products if someone else is taking that.

3.2 Scope:

This product has great future scope. Online shopping Internet software developed on and for
the Windows and later versions environments and Linux OS. This project also provides
security with the use of Login-id and Password, so that any unauthorized users can not use
your account. The only Authorized that will have proper access authority can access the
software.

3.3 Need for the proposed system:

The online shopping (HOME SHOP) is an easy to maintain, ready to run, scalable,
affordable and reliable cost saving tool from Software Associates suited for small, medium,
and large shopping complex and shopping malls.
Features and Benefits:

 Providing security
 Low cost
 Basic computer knowledge required
 Configurable and extensible application UI design

The proposed system can be used even by the naïve users and it does not require
any educational level, experience, and technical expertise in computer field but it will be of
good use if the user has the good knowledge of how to operate a computer.

3.4 Feasibility study:

A feasibility study is a short, focused study, which aims to answer a

number of questions:
 Does the system contribute to the overall objectives of the organizations?
 Can the system be implemented using current technology and within given
cost and schedule constrains?
 Can the system be integrated with systems which are already in place?

3.4.1 Technical Feasibility:

 Is the project feasibility within the limits of current technology?

 Does the technology exist at all?
 Is it available within given resource constraints (i.e., budget schedule)?

3.4.2 Financial Feasibility:

 Is the project possible, given resource constraints?

 Are the benefits that will accrue from the new system worth
the costs?
 What are the savings that will result from the system, including tangible and
intangible ones?
 What are the development and operational costs?
3.4.3 Operational Feasibility:

Define the urgency of the problem and the acceptability of any solution; if the
system is developed, will it be used? Includes people-oriented and social issues: internal
issues, such as manpower problems, labour objections, manager resistance, organizational
conflicts and policies; also external issues, including social acceptability, legal aspects and
government regulations.
 4. SYSTEM REQUIREMENTS SPECIFICATIONS

System requirements are expressed in a software requirement document. The

Software requirement specification (SRS) is the official statement of what is required of the
system developers. This requirement document includes the requirements definition and the
requirement specification. The software requirement document is not a design document. It
should set out what the system should do without specifying how it should be done. The
requirement set out in this document is complete and consistent. The software specification
document satisfies the following:-

1. It specifies the external system behaviours.

2. It specifies constraints on the implementation.
3. It is easy to change.
4. It serves as reference tool for system maintainers.
5. It record forethought about the life cycle of the system.
6. It characterizes acceptable response to undesired events.

4.1 User Class and Characteristics:

There are 3 types of user of this software-

1. General public
2. Customers
3. Administrator

1. General public can use the system to see the product ,their prices and quantity available.
General user cannot buy the products.
2. Customers are using for viewing and buying the products. Customer can also write
feedbacks for products and services
3. Administrators can add, edit & delete products and provide services to the customer.
Administrator can see the daily sell. Can also see the feedback given by the customer.
Administrator maintaining the deliveries.

4.2 Functional Requirements:

The System must provide following functionalities—

 Keeping records of admission of customers.
 Keeping the records of products.
 Keeping the daily sell .
 Storing the feedback given by the customer.
 Keeping details about the product it is delivered
or not.etc.
 Storing the items selected by the customer in the temporary storage.

4.3 Performance Requirements:

In order to maintain an acceptable speed at maximum number of uploads allowed from a

particular customer will be any number of users can access the system at any time. Also
connections to the servers will be based on the criteria of attributes of the user like his
location, and server will be working whole 24X7 times.

4.4 Non Functional Requirements:

Following Non-functional requirements will be there in the

Insurance on internet:
i). Secure access of confidential data (customer’s details).
ii). 24 X 7 availability.
iii). Better component design to get better performance at peak time.
iv).Flexible service based architecture will be highly desirable for future extension. Non
functional requirements define system properties and constraints . It arise through user needs,
because of budget constraints or organizational policies, or due to the external factors such as
safety regulations, privacy registration and so on.

Various other Non-functional requirements are:

1. Security
2. Reliability
3. Maintainability
4. Portability
5. Extensibility
6. Reusability
7. Application Affinity/Compatibility
8. Resource Utilization

4.5 External Interface Requirements:

4.5.1 User Interface:

User of the system will be provided with the Graphical user interface, there is no command
line interface for any functions of the product. The user will get 2 pages:-
1. Login page followed by Password.
4.5.2 Hardware Interface:

Hardware requirements for Insurance on internet will be same for both the parties which are
follows:
Processor: - Pentium I or above.
RAM: - 128 MB or above.
HD: - 20 GB or above.
NIC: - For each party

4.5.3 Software Interface:-

Software required to make working of product is:-

1. Operating System: Windows XP/vista/7 or later version, Linux OS which supports
networking.
2. JAVA development tool kit.

4.5.4 Communication Interfaces:

The two parties should be connected through either by LAN or WAN for the communication.

4.6 General Constraints, Assumptions,

Dependencies, Guidelines:

4.6.1 General Constraints

The interface will be in English only. The system is working for single server.
Sender Receiver.
There is no maintainability or backup so availability will get affected.
The system is a single user system.
GUI features available.

4.6.2 Assumptions and Dependencies

The product does require back-end database server My SQL for storing the username and
password for different types of user of the system as well as various databases regarding
various insurance information.
Assumptions:

User must be trained for basic computer functionalities .User must have the basic knowledge
of English.The system must be able to respond to database software within reasonable time.

Front-end (user interaction):

 The product will require a computer with an application program or with any
other application program and an communication channel.
 The speed of the communication channel (if any) must be, at a minimum 28.8
kbps in order to support message transfer in reasonable time.

PROBLEM DEFINITION

To develop a web-based application to improve the service to the customers and shopkeeper
which in turn increases the sales and profit in "ONLINESHOPPING CART ".

As the customer can easily buy the products which are visible to him if the product is in the
stock of the shop.

GOAL OFTHE PROJECT

The system is capable of maintaining details of various customers, vendors, products and
storing all the day to day transactions such handling customers and product receipts by e-mail
,updating of stores.
MODEL / ARCHITECTURE OF SDLC WHICH WE HAVE
USED
HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE REQUIRED:

Processor: Intel P2 and above.

Hard Disk: 8.3GB and above
RAM: 64MB and above

SOFTWARE:

JDK 1.6.0_21
TOM-CAT SERVER 5.0 and above ,
My SQL SERVER .

OPERATING SYSTEM :

Windows NT and above

Macintosh
Linux
 5. SYSTEM DESIGN SPECIFICATION

5.1 ARCHITECTURAL DESIGN

5.1.1 DATA FLOW DIAGRAMS:

Data flow diagrams (DFD) was first developed by LARRY CONSTANTINE as way
representing system requirements in a graphical form; this lead to modular design. A DFD
describes what data flow (logical) rather than how they are processed, so it does not depend
on hardware, software, data structure or file organization. It is also known as ‘bubble chart’.A
Data Flow Diagrams is a structured analysis and design tool that can be used for flowcharting
in place of, or in association with, information-oriented and process-oriented systems flow
charts. A DFD is a network that describes the flow of data and the processes that change, or
transform, data throughout a system. This network is constructed by using a set of symbols
that do not imply a physical implementation. It has the purpose of clarifying system
requirements and identifying major transformations that will become programs in system
design.
So it is the starting point of the design phase that functionality decomposes the requirement
specifications down to the lowest level of detail.

The symbols used to prepare DFD do not imply a physical implementation, a DFD can be
considered to an abstract of the logic of an information-oriented or a process-oriented system
flow-chart. For these reasons DFDs are often referred to as logical data flow diagrams. The
four basic symbols used to construct data flow diagrams are shown below:

5.1. 2. DATABASE DESIGN:

A database design is a collection of stored data organized in such a way that the data
requirements are satisfied by the database. The general objective is to make information
access easy, quick, inexpensive and flexible for the user. There are also some specific
objectives like controlled redundancy from failure, privacy, security and performance. A
collection of relative records make up a table. To design and store data to the needed forms
database tables are prepared. Two essential settings for a database are:

 Primary key: - The field that is unique for all the record occurrences.
Foreign key: - The field used to set relation between tables. Normalization is a technique
to avoid redundancy in the tables.
 TABLES

Table Name: users

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
username varchar
password varchar
firstname varchar
middlename varchar
lastname varchar
photos blob
address varchar
city varchar
state varchar
pincode varchar
emailid varchar
phoneno varchar

Table Name: user_authentication

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
username varchar
password varchar
Table Name: user table area
------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
username varchar
price double
itemid int
itemtype varchar
status int
lot_no varchar
description varchar

Table Name: sales

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
username varchar
total_purchase double
purchase_date varchar

Table Name: book_info

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
isbn_no varchar
copies int
Table Name: book_table
------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
title varchar
author varchar
publication varchar
price double
edition varchar
category varchar
bookid int
isbn_no varchar

Table Name: book_temp_table

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
title varchar
author varchar
publication varchar
price double
edition varchar
category varchar
bookid int
isbn_no varchar

Table Name: cloth_info

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
lot_no varchar
total_times int
Table Name: cloth_table
------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
clothid int
type varchar
price double
lot_no varchar
size int
category varchar
company varchar

Table Name: cloth_temp_table

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
clothid int
type varchar
price double
lot_no varchar
size int
category varchar
company varchar

Table Name: electronic_info

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
lot_no varchar
total_times int
Table Name: electronic_table
------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
electronicid int
companyname varchar
category varchar
model varchar
price double
lot_no varchar
specification varchar

Table Name: electronic_temp_table

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
electronicid int
companyname varchar
category varchar
model varchar
price double
lot_no varchar
specification varchar
Table Name: other_info
------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
lot_no varchar
total_times int

Table Name: other_table

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
otherid int
category varchar
company varchar
price double
lot_no varchar
weight double

Table Name: other_temp_table

------------------------------------------------------------------------------------------------
Column Name Type
------------------------------------------------------------------------------------------------
otherid int
category varchar
company varchar
price double
lot_no varchar
weight double
5.1.3 USE CASE DIAGRAM:

Use case diagrams are used to model the functional interaction between
users and system.
 6. TESTING

Software Testing is an empirical investigation conducted to provide stakeholders

with information about the quality of the product or service under test, with respect to the
context in which it is intended to operate. Software Testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the risks
at implementation of the software. Test techniques include, but are not limited to, the process
of executing a program or application with the intent of finding software bugs. It can also be
stated as the process of validating and verifying that a software program/application/product
meets the business and technical requirements that guided its design and development, so that
it works as expected and can be implemented with the same characteristics.

Software Testing, depending on the testing method employed, can be implemented at

any time in the development process, however the most test effort is employed after the
requirements have been defined and coding process has been completed.

6.1 Unit Testing:

The primary goal of unit testing is to take the smallest piece of testable software
in the application, isolate it from the remainder of the code, and determine whether it behaves
exactly as you expect. Each unit is tested separately before integrating them into modules to
test the interfaces between modules. Unit testing has proven its value in that a large
percentage of defects are identified during its use.

Unit testing is a software verification and validation method where the

programmer gains confidence that individual units of source code are fit for use. A unit is the
smallest testable part of an application. In procedural programming a unit may be an
individual program, function, procedure, etc., while in object-oriented programming, the
smallest unit is a class, which may belong to a base/super class, abstract class or derived/child
class.
Ideally, each test case is independent from the others: substitutes like method
stubs, mock objects, fakes and test harnesses can be used to assist testing a module in
isolation. Unit tests are typically written and run by software developers to ensure that code
meets its design and behaves as intended. Its implementation can vary from being very
manual (pencil and paper) to being formalized as part of build automation.

6.2 Integration Testing

Integration testing, also known as integration and testing (I&T), is a software

development process which program units are combined and tested as groups in multiple
ways. In this context, a unit is defined as the smallest testable part of an application.
Integration testing can expose problems with the interfaces among program components
before trouble occurs in real-world program execution.
Integration testing is a component of Extreme Programming (XP), a pragmatic method of
software development that takes a meticulous approach to building a product by means of
continual testing and revision.

There are two major ways of carrying out an integration test, called the bottom-
up method and the top-down method. Bottom-up integration testing begins with unit testing,
followed by tests of progressively higher-level combinations of units called modules or
builds. In top-down integration testing, the highest-level modules are tested first and
progressively lower-level modules are tested after that. In a comprehensive software
development environment, bottom-up testing is usually done first, followed by top-down
testing.

6.3 Validation testing

: At the validation level, testing focuses on user visible actions and user recognizable
output from the system. Validations testing is said to be successful when software functions
in a manner that can be reasonably expected by the customer. Two types of validation testing

 Alpha testing is simulated or actual operational testing by potential users/customers or an

independent test team at the developers' site .Alpha testing is often employed for off-the-shelf
software as a form of internal acceptance testing, before the software goes to beta testing.

 Beta testing comes after alpha testing. Versions of the software, known as beta version,
are released to a limited audience outside of the programming team. The software is released
to groups of people so that further testing can ensure the product has few faults or bugs.
Sometimes, beta versions are made available to the open public to increase the feedback field
to a maximal number of future users.

 Gray box testing Grey box testing is the combination of black box and white box testing.
Intention of this testing is to find out defects related to bad design or bad implementation of
the system .it is used for web application.
 7. Software Quality Assurance Plan
Each development and maintenance project should have a Software Quality
Assurance Plan that specifies its goals, the SQA tasks to be performed, the standards against
which the development work is to be measured, and the procedures and organizational
structure.

The IEEE Standards for the Software Quality Assurance Plans states that the plan should
contain the following sections:

1. Purpose
2. Reference documents
3. Management
4. Documentation
5. Standards, practices and conventions
6. Reviews and Audits
7. Configuration Management
8. Problem reporting and corrective action
9. Tools, techniques and methodologies
10. Code Control
11. Media Control
12. Supplier Control
13. Records collection, maintenance and retention.

1. Purpose, Scope and Overview:

The purpose of this Software Quality Assurance (SQA) Plan is to establish the goals,
processes, and responsibilities required to implement effective quality assurance functions for
the ONLINE SHOPPING. The ONLINE SHOPPING Software Quality Assurance plan
provides the framework necessary to ensure a consistent approach to software quality
assurance throughout the project life cycle.

This plan establishes the SQA activities performed throughout the life
cycle of the ONLINE SHOPPING. Specifically, this SQA Plan will show that the SQA
function is in place for this project. It will show that the SQA group has a reporting channel
to senior management that is independent of the project manager, the project’s software
engineering group, and software related groups that include Software Configuration
Management (SCM), System and Software Test, and Logistics .The goal of the SQA program
is to verify that all software and documentation to be delivered meet all technical
requirements.
2. Reference documents:

Software Quality Assurance, Principles and Practice: Nina S God bole.

3. Management:
An IEEE standard lays down three aspects that should be covered in the Software Quality
Assurance Plan:

Organization:

The organization section includes the roles of the team members, their hierarchy etc. It is
important that the head of the Software Quality Assurance (SQA) function in the organization
has the adequate 37authority to be able to perform independent verification that the processes
are adhered to. The following describes the functional groups that influence and control
software quality.

a). Program Management/Line Management (Sponsor) is responsible for

the following items:

1. Identifying an individual or group independent from the Project to audit and report on the
project’s SQA function.
2. Identifying the quality factors to be implemented in the system and software.

b). Project Management is responsible for:

1. Resolving and following-up on any quality issues raised by SQA.

2. Identifying, developing and maintaining planning document. Such as the Program
Management Plan.

c). System Engineering is responsible for:

Implementing the engineering practices, processes, and procedures as defined in

program/project planning documents.

d). Software Design/Development is responsible for:

Identifying, implementing, and evaluating the quality factors to be

implemented in the software.

e). Software Test is responsible for:

Verifying, Implementing the software test practices, processes, and procedures as defined in
program/project planning documents.
f). System Test is responsible for:

Verifying the quality factors are implemented in the system (software and hardware).

g). Logistics is responsible for:

1. Reviewing and commenting on the “” SQA Plan.

2. Implementing the quality program in accord ONLINE SHOPPING
assurance with this SQA Plan.

h). Software Configuration Management (SCM) is responsible for:

Implementing the SCM practices, processes, and procedures as defined in reference and
other program/project planning documents.

i). Independent Verification and Validation (IV& V) is responsible for:

Implementing the practices, processes, and procedures as defined for IV&V in

program/project planning documents.

j). Systems Engineering Process Office (SEPO) is responsible for:

1. Maintaining the SQA Process.

2. Ensuring SQA training availability.

3. Providing assistance in software process engineering and software

process improvement.

a) Tasks:

An SQA task is performed in relationship to what software development activities

are taking place. One or more SQA tasks can be performed concurrently until a task
is completed The following are the tasks of SQA plan:

 Evaluate System Requirements Analysis Process

 Evaluate System Design Process
 Evaluate Software Requirements Analysis Process
 Evaluate Software Design Process
 Evaluate Software Tools
 Evaluate Software Implementation and Unit Testing Process
 Evaluate End-item delivery Process
 Evaluate Configuration Management Process
 b) Responsibilities:

The project manager and design/development teams have primary responsibility for
the quality controls applied during the development of the software project.

The quality manager will:

 Define the responsibilities of quality personnel in the form of quality assurance procedures
applicable to the project.
 Agree to the quality plan with the project manager.
 Approve the plan of the audits for the project which are to be carried out by quality
personnel.
 Resolve any disagreement between the project manager and quality personnel on matters
relating to quality.
 Review the activities performed by project personnel to ensure that the requirements of the
quality plan and quality procedures are being satisfied.

Quality personnel will:

 Carry out planned internal audits of the project to assess compliance with quality
objectives.
 Agree on corrective action with the project manager for any discrepancies, non-
conformities found and ensure that corrective action is taken.
 Evaluate defect trends and take appropriate action.

4. Documentation:

The basic purpose of the documentation section of the Software Quality Assurance Plan is to
describe the documentation to be produced and how it is to be reviewed. The documentation
section normally includes the following:
 Software Requirements Specification (SRS)
 Software Design Description
 Software Verification Plan
 Software Verification report
 Reference to Software Standards (ISO, CMM, IEEE etc) and procedures mentioned and
defined as in the Quality Manual and Quality Management System.
 User guides, operators and programmers manual
 Configuration Management Plan
 Software Quality Objectives.

5. Standards, practices and conventions:

To verify the delivery of a fully conforming, high-quality product, every individual assigned
to the project will participate in quality assurance. This section describes the procedures used
by SQA to verify that the quality assurance provisions of this SQA Plan and applicable
standards, practices, conventions, and metrics are met .The following measurements will be
made and used to determine the cost and schedule status of the SQA activities: SQA
milestone dates (planned)
a. SQA milestone dates (completed)
b. SQA work scheduled (planned)
c. SQA work completed (actual)
d. SQA effort expended (planned)
e. SQA effort expended (actual)
f. SQA funds expended (planned)

6. Reviews and Audits:

The review and audits sections of Software Quality Assurance Plan will state which technical
and managerial reviews will be undertaken and how they will be carried out. The ANSI
standard suggests that the following would be a minimum set of reviews:

 Software Requirements Specification Review: This review is held to approve the document
defining the software requirements specifications and it aims to check the adequacy of the
requirements.
 Primary Design Review: The purpose of this review is to approve formally, the software
top-level design document.
 Critical Design Review: The purpose of this review is to approve the software detailed
design document as a basis for further development work.
 Software Verification Review: The purpose of this review is to approve the test plan. It is
the evaluation of the adequacy and completeness of the methods described.
 Functional Audit: This is held to verify that all the requirements in the software
requirements specification have been met.
 Physical Audit: This is held to verify that the software and its documentation are internally
consistent prior to delivery to the user.
 In-Process Audit: In-Process audits of a sample design are held to verify the consistency of
the design.

7. Configuration Management:

This Configuration Management section of the Software Quality Assurance Plan

covers configuration identification, configuration control, configuration status accounting,
and configuration auditing.

8. Problem reporting and corrective action:

This section of the Software Quality Assurance plan describes the system, which
ensures that software problems are documented and resolved. It should be a closed-loop
system. All the problems should be promptly reported at appropriate level, acted upon and
resolved. Each problem should be analyzed problem must have severity level and a priority
number.
For each problem, some corrective action and a target completion date should be
identified. The appropriate level of management should be made aware of the problems and
adverse trends. The corrective action taken will be evaluated to ensure that it solved the
problem without introducing any new problems. Management should monitor the status of all
unresolved problems.
9. Tools, techniques and methodologies:

Tools - SQA software tools include, but are not limited to, operating system
utilities, debugging aids, documentation aids, checklists, structuring preprocessors, file
comparators, structure analyzers, code analyzers, standards auditors, simulators, execution
analyzers, performance monitors, statistical analysis packages, software development
folder/files, software traceability matrices, test drivers, test case generators, static or dynamic
test tools, and information engineering CASE tools.

Techniques - techniques include review of the use of standards, software

inspections, requirements tracing, requirements and design verification, reliability
measurements and assessments, and rigorous or formal logic analysis.

Methodologies - methodologies are an integrated set of the above tools and

techniques. The methodologies should be well documented for accomplishing the task or
activity and provide a description of the process to be used.

10. Code Control:

Code control includes the items listed below:

 Identifying, labelling, and cataloging the software to be controlled
 Identifying the physical location of the software under control
 Identifying the location, maintenance, and use of backup copies44
 Distributing copies of the code
 Identifying the documentation that is affected by a change
 Establishing a new version
 Regulating user access to the code.

11. Media Control:

The Media Control section of the Software Quality Assurance Plan will describe
how the media are to be protected from unauthorized access or damage. Security threats to a
software project come from the following environmental factors:
 Fire Damage
 Water Damage
 Energy Variations
 Structural Damage
 Pollution
 Unauthorized Intrusion
 Viruses and Worms
 Misuse of Software, Data and Services.
 1. Supplier Control:

Prior to any purchase of software to support the development effort, SQA

and project members will define and provide complete requirements to the supplier/vendor.
The Software Tool Evaluation Process will be followed. Part of the evaluation process will
require the supplier or vendor to describe their technical support, handling of user questions
and problems, and software product upgrades.

Records collection, maintenance and retention:

SQA activities are documented by records and reports that provide a history of product
quality throughout the software life cycle. Measurement data collected will be reviewed for
trends and process improvement. All SQA records will be collected and maintained in the
SDL or archival storage for the life cycle of the product.

Australians are embracing the internet, with nearly nine in 10 adults (people aged 18 years
and over) in fixed-line telephone households personally using the internet either at home or
away from home at April 2011. Eighty-seven per cent of fixed-line telephone households in
Australia also had an internet connection, with the majority of these households having a
broadband connection (98 per cent).i The number of households with an internet connection
increased from 82 per cent at November 2009.

In addition to increased levels of online connectivity, Australians are using the internet more
frequently—59 per cent of adults go online several times a day (up from 53 per cent in
November 2010).

Increasing online participation is paralleled by greater knowledge of the internet and the
associated benefits of going online. At the same time, more organisations have integrated the
internet into their operational plans either by providing retail customer-oriented services
online or by developing electronic supply chains with key suppliers and major customers.
These developments have a number of specific and well-documented benefits for businesses
including:
> avoiding high rental costs (or reducing rental costs) for business premises
> comparatively low barriers to entry in terms of business establishment costs
> low barriers to geographic expansion across Australia and overseas
> reducing the amount of advertising needed to sell products
> removing the need for intermediaries and associated costs by interacting directly with
customers. Latest data available from the Australian Bureau of Statistics (ABS) reflects
the increasing importance of the internet to business revenues. The ABS reports that
Australian business received an estimated $143 billion in internet orders during the 2009–
10 financial year, an increase of 15 per cent on 2008–09.ii This included business-to-
business (B2B) and business-to-consumer (B2C) online sales. In addition, the recent
Sensis report The Online Experience of Small and Medium Enterprises shows that an
estimated 59 per cent of small and medium enterprises (SMEs)—businesses with 1–200
employees—in Australia received orders for goods and services online at April 2011,
compared to 58 per cent at April 2010 (Figure 1). Industry sectors most prominent in
 taking orders online include wholesale trade (76 per cent of SMEs in that sector taking
orders online) and manufacturing (72 per cent) (Figure 2). These sectors are more likely to
be involved in B2B e-commerce, providing services to other industries. According to the
Sensis report, at April 2011, approximately 59 per cent of SMEs in the retail trade
industry, where the majority of B2C activity occurs, took online orders for goods and
services.

70

60 59
58
56
54

50 48

40
% of SMEs connected to the internet

30

20

10

0
2007 2008 2009 2010 2011

Figure 1 Australian SMEs taking orders for goods and services online

Profile shopping online

In the six months to April 2011, approximately 62 per cent of adult internet users purchased a
good or service online (Figure 5). A number of demographic factors influence whether a
consumer purchases online.

Age
People aged 35–44 years were the most prominent age group to adopt online shopping, with
73 per cent having made a purchase online in the six months to April 2011. The incidence of
shopping online decreased significantly in people aged over 44, falling to 40 per cent of
internet users aged 65 years and over in the six month to April 2011.

80
73
69
65
% of internet users aged 18 years and over

62 61
60
52

40
40

20

0
Total 18–24 25–34 35–44 45–54 55–64 65 +

Age group

Income
Income level is also strongly correlated to online purchasing, with 86 per cent of those
earning over $150,000 per annum having made a purchase in the six months to April 2011,
compared to 46 per cent of those earning under $50,000 a year (Figure 6).

Other factors
Online purchasing was also influenced by other factors such as level of education and
employment status. The higher the level of education achieved, the higher the incidence of
online shopping—75 per cent of those with postgraduate qualifications shopped online
compared to 43 per cent of those with primary or some secondary

Online payment channels

The majority of online shoppers in Australia pay for their purchases via the internet (Figure
10) rather than in a separate payment process. Approximately 91 per cent of adults who
bought a good or service online during June 2011 paid for it using either a credit card or
money transfer service such as PayPal. Fifty-four per cent of online shoppers used both
payment channels. This could be a consequence of no other payment option being available
or confidence in the security of online payment channels.
 Used neither credit card or money
transfer
9%
Used credit card
only
25%

Use money trans-

fer (e.g. PayPal)
only
Used credit cards 12%
and money trans-
fer services
54%

% of online shoppers aged 18 years and over

Devices used to shop online

Online shopping in Australia is conducted primarily over computers (Figure 11). Of the 2.4
million adult Australians purchasing a good or service online during June 2011:
> 97 per cent purchased online via a computer
> 4 per cent made online purchases via a mobile phone
> 2 per cent made online purchases via other devices such as tablets.
However, as discussed below, mobile phones are increasingly being used for other
e-commerce transactions; specifically, banking and bill payment.
 Computer Mobile Other devices

% of people aged 18 years and over 100 97 97

80
purchasing online

60

40

20

2 2 4 2
0
Jun-10 Jun-11
SNAPSHOTS OF THE PROJECT
LOGIN PAGE
Registration Page
Overview Of the Products we Sell in Our Site
Search Records

Search page for Cosmetic items

Search page for Electronic items

Updation Process

Update Book

Update Electronic Items

Unauthorised/Invalid User Page
DELETE RECORDS

Delete Books
Delete Cosmetic Products
Transaction Page By Entering Credit Card Number
Final Bill Prepared After Shopping
Frequently Asked Questions
About US
 INTERPRETATION OFTHE RESULT

The system has been implemented and tested successfully. It meets the information
requirements specified to the great extent. Although the system has been designed keeping
the present and future requirements in mind and made very flexible.

There are limitations of the System. Proper consideration has been given for a wide range
ofnew enhancements in the future, throughout the development of system. The system is
developed user friendly.

In future, if it is required to generate reports other than provided by the system, it can be
simply achieved by a separate module to the main menu without affecting the design of the
system.
 FEATURES AND UNIQUENESS OF THE THE SITE

It simplifies the operation.

It avoids a lot of manual work.

Every Transaction is obtained and processed immediately.

Avoids errors by avoiding the manual work.

User friendly screen to enter the data and enquire the database tables.

Online help messages available to the operating system.

User can easily access the system without much experience.

Provide Hardware and software securities.

Portable and flexible for further extension.

It helps the user to change the password on his choice for security purpose
 Future Developments In The Project

 ATM-cum-Debit Card and other Pay pal transaction will soon be

available to the system.

 User will himself change the username also.

 Cancellation of the order will be available soon .

 The company will come with “special discounts “with if the specific

users will cross a amount of purchasing .

 The company will come with more of variety of items.

 More of pictorial view of the all the items will be available soon.

 Prices of each of the product will be available while the customer is in the
phase of searching the item rather than in the final bill phase .
 CONCLUSION

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 is for the customers who wish to buy the
articles. Second is for the storekeepers who maintains and updates the information pertaining
to the articles andthose of the customers.The end user of this product is a departmental store
where the application ishosted 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 fromthe 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.
 BIBILIOGRAPHY

 HTML Publishing Bible - Alan Simpson.

 Netscape Java Script – Peter & John Kent.

 The Complete Reference Of Java –Patrick naughton

 Java Network programming – Rusty Harod.

 Software Engineering - Fairly.

 Analysis &Design Of Information - James A. Senn.

 Internet -Scribd.com,google.com
i

ii