1shopping cart[

8/10/2019 1shopping Cart[

1/53

A

Major Project Report

On

ONLINE SHOPPING CART

Submitted in partial fulfilment of Bachelors Degree in Technology from

Rajasthan Technical University

Kota

During 2011-2012

Submitted To: Submitted By:-

Mr.Narender Agarwal Ankit Kumar Khandelwal

Head of CSE Abhishek Bharadwaj

Ankit Kumar Singh

Abhishek Mudgal

Department of Computer Science,

Jaipur Engineering College,

Kukas, Jaipur


2/53

Table Of ontent


3/53

INTRODUCTION

The Project entitled "ONLINE SHOPPING CART" is a web-based application. Softwaredeveloped in JAVA LANGUAGE using Java as frontend and MySqlas backend onWindows Operating System.

The main aim of the project is to improve the services of Customers and vendors. It maintainsthe details of customer payments, product receipts, addition of new customers, products andalso updating, deletion for the same. It also mails the details of users which have logged inthe 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 easyavailability. And also it uses database tables Representing entities and relationships betweenentities.The site containing avery interesting feature sending a mail to the customer abouttheir 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 theirproducts 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 parkingplace, 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


4/53

1.OVERVIEW OF PROJECT

The central concept of the application is to allow the customer to shop virtually using theInternet and allow customers to buy the items and articles of their desire from the store. Theinformation 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 shippedto 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 theweb and the administrator maintains the database. The application which is deployed at thecustomer database, the details of the items are brought forward from the database for thecustomer view based on the selection through the menu and the database of all the productsare updated at the end of each transaction. Data entry into the application can be donethrough.


5/53

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: requestclarification, 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

an agent


6/53

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:


7/53

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:

security

The proposed system can be used even by the nave 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:

organizations?

cost and schedule constrains?

place?

3.4.1 Technical Feasibility:

the project feasibility within the limits of current technology?

it available within given resource constraints (i.e., budget schedule)?

3.4.2 Financial Feasibility:

Is the project possible, given resource constraints?

the costs?


8/53

are the savings that will result from the system, including tangible and

intangible ones?

nd 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.


9/53

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:


10/53

The System must provide following functionalities

eeping the daily sell .

the feedback given by the customer.

eeping details about the product it is delivered

or not.etc.

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 (customers 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. Security2. Reliability

3. Maintainability

4. Portability

5. Extensibility

6. Reusability

7. Application Affinity/Compatibility

8. Resource Utilization


11/53

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 commandline 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


12/53

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):

other application program and an communication channel.

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 shopkeeperwhich 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 thestock of the shop.

GOAL OFTHE PROJECT

The system is capable of maintaining details of various customers, vendors, products andstoring all the day to day transactions such handling customers and product receipts by e-mail,updating of stores.


13/53

MODEL / ARCHITECTURE OF SDLC WHICH WE HAVE

USED


14/53

HARDWARE AND SOFTWARE REQUIREMENTS

HARDWARE REQUIRED:


15/53

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:


16/53


17/53

------------------------------------------------------------------------------------------------

username varchar

password varchar

firstname varchar

middlename varcharlastname 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 doubleitemid int


18/53

itemtype varchar

status int

lot_no varchar

description varchar

Table Name: sales

------------------------------------------------------------------------------------------------

Column Name Type

------------------------------------------------------------------------------------------------

username varchar

total_purchase doublepurchase_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


19/53

price double

edition varchar

category varchar

bookid int

isbn_no varchar

Table Name: book_temp_table

------------------------------------------------------------------------------------------------

Column Name Type

------------------------------------------------------------------------------------------------

title varcharauthor varchar

publication varchar

price double

edition varchar

category varchar

bookid int

isbn_no varchar

Table Name: cloth_info

------------------------------------------------------------------------------------------------

Column Name Type

------------------------------------------------------------------------------------------------

lot_no varchartotal_times int

Table Name: cloth_table

------------------------------------------------------------------------------------------------Column Name Type


20/53

------------------------------------------------------------------------------------------------

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


21/53

Table Name: electronic_table

------------------------------------------------------------------------------------------------

Column Name Type

------------------------------------------------------------------------------------------------

electronicid intcompanyname 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 varcharmodel varchar

price double

lot_no varchar

specification varchar

Table Name: other_info

------------------------------------------------------------------------------------------------

Column Name Type

------------------------------------------------------------------------------------------------

lot_no varchar

total_times int


22/53

Table Name: other_table

------------------------------------------------------------------------------------------------

Column Name Type

------------------------------------------------------------------------------------------------

otherid int

category varchar

company varchar

price doublelot_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 betweenusers and system.


23/53

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 thecontext in which it is intended to operate. Software Testing also provides an objective,


24/53

independent view of the software to allow the business to appreciate and understand the risksat implementation of the software. Test techniques include, but are not limited to, the processof executing a program or application with the intent of finding software bugs. It can also bestated as the process of validating and verifying that a software program/application/productmeets 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 atany time in the development process, however the most test effort is employed after therequirements 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 softwarein the application, isolate it from the remainder of the code, and determine whether it behavesexactly as you expect. Each unit is tested separately before integrating them into modules totest 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 theprogrammer gains confidence that individual units of source code are fit for use. A unit is thesmallest testable part of an application. In procedural programming a unit may be anindividual program, function, procedure, etc., while in object-oriented programming, thesmallest 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 inisolation. Unit tests are typically written and run by software developers to ensure that codemeets its design and behaves as intended. Its implementation can vary from being verymanual (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 softwaredevelopment process which program units are combined and tested as groups in multipleways. 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 ofsoftware development that takes a meticulous approach to building a product by means ofcontinual 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,


25/53

followed by tests of progressively higher-level combinations of units called modules orbuilds. In top-down integration testing, the highest-level modules are tested first andprogressively lower-level modules are tested after that. In a comprehensive softwaredevelopment environment, bottom-up testing is usually done first, followed by top-downtesting.

6.3 Validation testing

: At the validation level, testing focuses on user visible actions and user recognizableoutput from the system. Validations testing is said to be successful when software functionsin 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 anindependent test team at the developers' site .Alpha testing is often employed for off-the-shelfsoftware 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 releasedto 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 fieldto a maximal number of future users.

.Intention of this testing is to find out defects related to bad design or bad implementation ofthe system .it is used for web application.

7. Software Quality Assurance Plan

Each development and maintenance project should have a Software QualityAssurance 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 organizationalstructure.


26/53

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

1. Purpose

2. Reference documents3. Management4. Documentation5. Standards, practices and conventions6. Reviews and Audits7. Configuration Management8. Problem reporting and corrective action9. Tools, techniques and methodologies10. Code Control

11. Media Control12. Supplier Control13. 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 forthe ONLINE SHOPPING. The ONLINE SHOPPING Software Quality Assurance plan

provides the framework necessary to ensure a consistent approach to software qualityassurance throughout the project life cycle.

This plan establishes the SQA activities performed throughout the lifecycle of the ONLINE SHOPPING. Specifically, this SQA Plan will show that the SQAfunction is in place for this project. It will show that the SQA group has a reporting channelto senior management that is independent of the project manager, the projects softwareengineering group, and software related groups that include Software ConfigurationManagement (SCM), System and Software Test, and Logistics .The goal of the SQA programis to verify that all software and documentation to be delivered meet all technicalrequirements.

2. Reference documents:

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

3. Management:


27/53

An IEEE standard lays down three aspects that should be covered in the Software QualityAssurance Plan:

Organization:

The organization section includes the roles of the team members, their hierarchy etc. It isimportant that the head of the Software Quality Assurance (SQA) function in the organizationhas the adequate 37authority to be able to perform independent verification that the processesare adhered to. The following describes the functional groups that influence and controlsoftware 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 theprojects 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 ProgramManagement Plan.

c). System Engineering is responsible for:

Implementing the engineering practices, processes, and procedures as defined inprogram/project planning documents.

d). Software Design/Development is responsible for:

Identifying, implementing, and evaluating the quality factors to beimplemented in the software.

e). Software Test is responsible for:

Verifying, Implementing the software test practices, processes, and procedures as defined inprogram/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:


28/53

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 andother 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 inprogram/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 activitiesare taking place. One or more SQA tasks can be performed concurrently until a taskis completed The following are the tasks of SQA plan:

Process

-item delivery Process

b) Responsibilities:

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

The quality manager will:


29/53

applicable to the project.th the project manager.

personnel.

relating to quality.performed by project personnel to ensure that the requirements of the

quality plan and quality procedures are being satisfied.

Quality personnel will:

objectives.e on corrective action with the project manager for any discrepancies, non-

conformities found and ensure that corrective action is taken.

4. Documentation:

The basic purpose of the documentation section of the Software Quality Assurance Plan is todescribe the documentation to be produced and how it is to be reviewed. The documentationsection normally includes the following:

Software Verification Plan

defined as in the Quality Manual and Quality Management System.

Configuration Management PlanQuality Objectives.

5. Standards, practices and conventions:

To verify the delivery of a fully conforming, high-quality product, every individual assignedto 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 applicablestandards, practices, conventions, and metrics are met .The following measurements will bemade and used to determine the cost and schedule status of the SQA activities: SQAmilestone 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)


30/53

6. Reviews and Audits:

The review and audits sections of Software Quality Assurance Plan will state which technicaland 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:

defining the software requirements specifications and it aims to check the adequacy of therequirements.

Design Review: The purpose of this review is to approve formally, the softwaretop-level design document.

design document as a basis for further development work.ftware 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.software

requirements specification have been met.

consistent prior to delivery to the user.-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, whichensures that software problems are documented and resolved. It should be a closed-loopsystem. All the problems should be promptly reported at appropriate level, acted upon andresolved. Each problem should be analyzed problem must have severity level and a prioritynumber.

For each problem, some corrective action and a target completion date should beidentified. The appropriate level of management should be made aware of the problems andadverse 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 allunresolved problems.

9. Tools, techniques and methodologies:

Tools - SQA software tools include, but are not limited to, operating systemutilities, debugging aids, documentation aids, checklists, structuring preprocessors, file

comparators, structure analyzers, code analyzers, standards auditors, simulators, executionanalyzers, performance monitors, statistical analysis packages, software development


31/53

folder/files, software traceability matrices, test drivers, test case generators, static or dynamictest tools, and information engineering CASE tools.

Techniques - techniques include review of the use of standards, softwareinspections, 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 andtechniques. The methodologies should be well documented for accomplishing the task oractivity and provide a description of the process to be used.

10. Code Control:

Code control includes the items listed below:ling, and cataloging the software to be controlled

the physical location of the software under controlcopies44

the documentation that is affected by a changea new version

11. Media Control:

The Media Control section of the Software Quality Assurance Plan will describehow the media are to be protected from unauthorized access or damage. Security threats to asoftware project come from the following environmental factors:

Damage

1. Supplier Control:

Prior to any purchase of software to support the development effort, SQAand 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 willrequire the supplier or vendor to describe their technical support, handling of user questions

and problems, and software product upgrades.


32/53

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 fortrends and process improvement. All SQA records will be collected and maintained in theSDL 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).iThe 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

frequently59 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 withcustomers. Latest data available from the Australian Bureau of Statistics (ABS) reflectsthe increasing importance of the internet to business revenues. The ABS reports thatAustralian business received an estimated $143 billion in internet orders during the 200910 financial year, an increase of 15 per cent on 200809.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 anestimated 59 per cent of small and medium enterprises (SMEs)businesses with 1200employeesin 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 intaking orders online include wholesale trade (76 per cent of SMEs in that sector takingorders 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 theSensis report, at April 2011, approximately 59 per cent of SMEs in the retail tradeindustry, where the majority of B2C activity occurs, took online orders for goods andservices.


33/53


34/53


35/53

Devices used to shop onlineOnline 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.

Used credit card

only25%

Use money transfer(e.g. PayPal) only

12%

Used credit cardsand money transfer

services54%

Used neither creditcard or money

transfer9%

% of online shoppers aged 18 years and over


36/53

97 97

2 42 2

0

20

40

60

80

100

Jun-10 Jun-11

%o

fpeopleaged18yearsandover

purchasingonline

Computer Mobile Other devices


37/53

SNAPSHOTS OF THE PROJECT

LOGIN PAGE


38/53

Registration Page


39/53


40/53

Search Records

Search page for Cosmetic items

Search page for Electronic items


41/53

Updation Process

Update Book

Update Electronic Items


42/53

Unauthorised/Invalid User Page


43/53

DELETE RECORDS

Delete Books


44/53

Delete Cosmetic Products


45/53

Transaction Page By Entering Credit Card Number


46/53

Final Bill Prepared After Shopping


47/53

Frequently Asked Questions


48/53

About US


49/53

INTERPRETATION OFTHE RESULT

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

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

In future, if it is required to generate reports other than provided by the system, it can besimply achieved by a separate module to the main menu without affecting the design of thesystem.


50/53

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.

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.


51/53

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 .


52/53

CONCLUSION

The central concept of the application is to allow the customer to shop virtually using theInternet and allow customers to buy the items and articles of their desire from the store. Theinformation pertaining to the products are stores on an RDBMS at the server side (store). TheServer 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 thearticles. Second is for the storekeepers who maintains and updates the information pertainingto the articles andthose of the customers.The end user of this product is a departmental storewhere the application ishosted on the web and the administrator maintains the database. Theapplication which is deployed at the customer database, the details of the items are broughtforward 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 variouslevels of users. Once the authorized personnel feed the relevant data into the system, severalreports could be generated as per the requirements. This system offers information relevant tothe user accessing the application thus avoiding unnecessary overloading and at the sametime maintaining the security.


53/53

BIBILIOGRAPHY

HTML Publishing Bible - Alan Simpson.

Netscape Java ScriptPeter & John Kent.

The Complete Reference Of JavaPatrick naughton

Java Network programmingRusty Harod.

Software Engineering - Fairly.

Analysis &Design Of Information - James A. Senn.

Internet -Scribd.com,google.com

i

1shopping cart[

Documents