Contents

CHAPTER 1: Introduction ............................................................................................ 2

Background ................................................................................................................ 2
Objective: ................................................................................................................... 3
CHAPTER 2: System Analysis ..................................................................................... 5
Existing System ......................................................................................................... 5
Purposed System: ....................................................................................................... 5
Feasibility Study: ....................................................................................................... 6
CHAPTER 3: SYSTEM SPECIFICATION .................................................................. 8
Hardware Specification:............................................................................................. 8
Software Specification: .............................................................................................. 8
CHAPTER 4: PROJECT DESCRIPTION .................................................................... 9
Graphical User Interface: ........................................................................................... 9
NUMBER OF MODULES ........................................................................................ 9
User Class and Characteristics:................................................................................ 10
CHAPTER 5: REQUIREMENTS ............................................................................... 11
Functional Requirements: ........................................................................................ 11
Performance Requirements ...................................................................................... 12
CHAPTER 6: TESTING.............................................................................................. 14
Unit testing: .............................................................................................................. 14
System testing: ......................................................................................................... 14
Performance Testing: ............................................................................................... 15
CHAPTER 7: IMPLEMENTATION .......................................................................... 16

CHAPTER 1: Introduction
Background
The history of online shopping began immediately after the World Wide Web, or
WWW, became a major medium to communicate information around the world.
Online shopping applications allow consumers to buy goods or services directly over
the internet using a web browser. This online shopping evokes the business-toconsumer (B2C) process where a consumer buys directly from the business. The
process where a business buys from another business is called a business-to-business
(B2B) process. The best examples of e-commerce store using B2B process are eBay
and Amazon, both of which were launched in 1995. At present, most users of these
online shopping applications are people who have higher levels of education, have
exposure to technological advancements, and are in a better income group. Such users
develop a positive attitude towards these convenient shopping techniques. According
to a study in December 2011, Equation Research surveyed 1,500 online shoppers and
found that 87% of tablet owners made online transactions during the early Christmas
shopping season.
Building a new successful online shopping application is not simple because of high
competition in the market, and the designer of a these application must consider the
information load, complexity, and novelty. Complexity refers to the number of
features available on the application and the levels of marketing, whereas novelty
involves the unexpected or unfamiliar aspects of the site. A designer must also
consider the consumers needs and expectations. A user-friendly design is very
critical to the success of any online shopping application because, unlike physical
stores, consumers at online stores come from all ages, genders, and cultures. Logistics
clearly says that, to have a successful and profitable online shopping application,
businesses have to spend a significant amount of time and money for designing,
developing, testing, and maintaining the application. Apart from the high-class design
and user interface, a good practice needs to be done to provide quality customer
service. A typical online shopping application should contain certain features such as
adding items to the users cart and checking out those items using the available
payment methods. Most of these applications are implemented using HTTP cookies or
query strings, and an HTML setup is required to install the shopping cart on the
servers that ultimately hosts the site on the internet. Most of these server-based

applications require data related to the items added in the shopping cart to be kept in a
session object which can be accessed later and manipulated dynamically because the
users can add or remove one or more items from the cart. Most simple online
shopping applications do not allow checkout to be done before any items are added to
the cart. Data are often stored in an external database or application-based databases
which can be accessed in real time by the application administrator.
There are many examples of online shopping applications developed in different
languages. Choosing a development platform and language depends on policies set by
the company for which the application is being designed. It also depends on several
other factors which are very important when considering the platform to design an
application, for example, how portable the application will be after being built or if
the application is open sourced.

Objective:
The objective of this project is to develop a general purpose e-commerce store where
any products can be bought from the comfort of home through the Internet. The
Home-Shop is a virtual store on the Internet where customers can browse the
catalog and select products of interest. The selected items may be collected in a
shopping cart. At checkout time, the items in the shopping cart will be presented as an
order. At that time, more information will be needed to complete the transaction.
Usually, the customer will be asked to fill or select a billing address, a shipping
address, a shipping option, and payment information such as credit card number. An
e- mail notification is sent to the customer as soon as the order is placed. The HomeShop is expanded permanently through new products and services in order to offer a
product portfolio corresponding to the market.

Private customer and business

customers can order the selected products of the Home-Shop service online quickly
and comfortably. Target groups of customer of the Home-Shoparepeople who have
higher levels of education, have exposure to technological advancements, and are in a
better income group. The customers can have a payment option through credit card
only. In order to use the load writing procedure, the customer registers itself and
receives a login for its purchases name. It is an Internet application. Electronic
Commerce (e-commerce) applications support the interaction between different
parties participating in a commerce transaction via the network, as well as the
management of the data involved in the process.

Products can be managed by operators from admin panel. Operator can be created by
admin. Admin can keep track of orders through admin panel. The main purpose of the
system is to enable customers to browse and order from any part of the world and
hence increasing business scope.

CHAPTER 2: System Analysis

Existing System
The existing system was a manual system. And it was found to be inefficient in
meeting the growing demands of population. The major drawback of the existing
system are:

The existing system is manual system. Needs to be converted into automated

system.

Risk of mismanagement of data.

Less Security.

No proper coordination between different Applications and Users.

Fewer Users - Friendly.

Accuracy not guaranteed.

Not in reach of distant users.

So, the development of the new system should contains the following activities, which
should try to automate the entire process keeping in view of the database integration
approach.

User friendliness is provided in the application with various controls.

The system makes the overall project management much easier and flexible.

There is no risk of data mismanagement at any level while the project

development is under process.

It provides high level of security with different level of authentication.

Users from any part of the world can make use of the system.

New system will process accurate results.

New system will be much better in performance as compared to existing one.

Purposed System:
Home-Shop 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 products 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.

Home-Shoptries to enhance access to care and improve the continuity and

efficiency of services. Depending on the specific setting and local, case managers are
responsible for avariety of tasks, ranging from linking clients to services to actually
providing intensive shopping and delivery services themselves.
The main objective of Home-Shop application is:

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 product if someone else is taking that.

"Home-Shop" has great future scope. Online shopping Internet software developed on
and for the Windows and later versions environments and Linux OS. "Home-Shop"
also provides security with the use of Login-id and Password, so that any
unauthorized users cannot use your account. The only Authorized that will have
proper access authority can access the software.
"Home-Shop" is an easy to maintain, ready to run, scalable, affordable and reliable
cost saving tool that can meet requirement for small, medium, and large shopping
complex and shopping malls.
The main benefits of Home-Shop application are:

Providing security

Low cost

Basic computer knowledge required

Configurable and extensible application UI design

Feasibility Study:
Preliminary investigation examine project feasibility, the likelihood the system will be
useful to the organization. The main objective of the feasibility study is to test the
Technical, Operational and Economical feasibility for adding new modules and
debugging old running system. All system is feasible if they are unlimited resources
and infinite time. There are aspects in the feasibility study portion of the preliminary
investigation:

Technical Feasibility

Operation Feasibility

Economic Feasibility

Technical Feasibility:
"Home-Shop" is technically feasible as it is a web based user interface. Thus it
provides an easy access to the users. The databases purpose is to create, establish and
maintain a workflow among various entities in order to facilitate all concerned users
in their various capacities or roles. Permission to the users would be granted based on
the roles specified. Therefore, it provides the technical guarantee of accuracy,
reliability and security. The software and hard requirements for the development of
this project are not many and are already available in-house or are available as free as
open source. The work for the project is done with the current equipment and existing
software technology. Necessary bandwidth exists for providing a fast feedback to the
users irrespective of the number of users using the system.
Operational Feasibility:
Proposed projects are beneficial only if they can be turned out into information
system. That will meet the organizations operating requirements. Operational
feasibility aspects of the project are to be taken as an important part of the project
implementation. This system is targeted to be in accordance with the abovementioned issues. Beforehand, the management issues and user requirements have
been taken into consideration. So there is no question of resistance from the users that
can undermine the possible application benefits. The well-planned design would
ensure the optimal utilization of the computer resources and would help in the
improvement of performance status.
Economic Feasibility:
A system can be developed technically and that will be used if installed must still be a
good investment for the organization. In the economic feasibility, the development
cost in creating the system is evaluated against the ultimate benefit derived from the
new systems. Financial benefits must equal or exceed the costs. The system is
economically feasible. It does not require any addition hardware or software. Since
the interface for this system is developed using the existing resources and
technologies available, there is nominal expenditure and economic feasibility for
certain.

CHAPTER 3: SYSTEM SPECIFICATION

Hardware Specification:
Minimum RAM:-1GB
Hard Disk:-128 GB
Processor:-Intel Pentium 4 (1.50 GHZ) or above

Software Specification:
Operating system: Windows,Windows XP/vista/7 or later version, Linux OS
which supports networking
Front Design: PHP5, HTML5, CSS3, JavaScript
Back-End: MYSQL
Back-End Connectivity: PDO

CHAPTER 4: PROJECT DESCRIPTION

Graphical User Interface:
In the flexibility of the uses the interface has been developed a graphics concept in
mind, associated through a browser interface. The GUIS at the top level have been
categorized as
Administrative user interface
The operational or generic user interface
The administrative user interface concentrates on the consistent information that is
practically, part of the organizational activities and which needs proper authentication
for the data collection. The interfaces help the administrations with all the
transactional states like Data insertion, Data deletion and Date updating along with
the extensive data search capabilities.
The operational or generic user interface helps the users upon the system in
transactions through the existing data and required services. The operational user
interface also helps the ordinary users in managing their own information helps the
ordinary users in managing their own information in a customized manner as per the
assisted flexibilities.

NUMBER OF MODULES
The system after careful analysis has been identified to be presented with the
following modules into 9 modules:
Registration Module
Products Browse Module
Products Search Module
Shopping cart Module
Shipping & Billing Module
Payment Module
Admin User Management Module
Admin Catalog Management Module
Admin Order Management Module

User Class and Characteristics:

The users of the online shopping-cart application, based on their roles, are customers
(users) and the administrator (owner). These users are identified based on their experience
and technical expertise.
1. Admin: The administrator is the owner of this online shopping-cart application. One
must have a basic understanding of computers and the internet as well as prior knowledge
for operating the eclipse and Java programming languages. The administrator is
responsible for maintaining all the training documents required for the system. The
administrator can perform the following functions:

Assign or change the price of the items, update the items in the list, and delete the
items.

Assign sales tax for different states at the time of checkout.

View the history of the customers who purchased the items.

2. Users: The users of this online shopping-cart application are all customers who would
shop to test the application. These users are anyone with shopping experience and the
know-how to browse through a shopping-cart application. They must have basic
understandings about computers and the internet. The users should be able to perform the
following functions using this system:

View, browse, and select a category on the home page.

View, add, and update items in the cart.

Delete items from the cart.

Check out the items from the application or continue shopping.

Sign-on/login using a username and password.

Place the order by completing the order form.

CHAPTER 5: REQUIREMENTS
Functional Requirements:
User: View Categories and Items:
The users shall be able to see the home page of the Home-Shop application when
they first run the program. The users shall be able to view the different categories,
select categories, browse through the items in each category, and add items to the
shopping cart. The users shall be able to view the shopping cart and more information
about each item.

The users shall be able to view the categories on the applications home page.

The users shall be able to view items in different categories.

The users shall be able add items to the cart.

The users shall be able to view more information about an item before adding
it to the cart.

The users shall be able to able view the shopping cart.

The users shall be able to browse through the available items.

User: View Home-Shop:

After the first run of the application, the users shall be able to see their designated
home page. After browsing through the items and adding items to the shopping cart,
the users should be able to view the items in the shopping cart. The users shall be able
to check out or continue shopping. The users shall be able to delete items from the
cart.

The users shall be able to view the items added to the cart.

The users shall be able to check out with the current items in the cart.

The users shall be able to continue shopping.

The users shall be able to delete items from the cart.

User: Checkout Items

The users shall be able to check out items only when there are items in the
shopping cart.

Login/ User Authentication

The users shall login or register using the user authentication form.

The users shall not login or register if the information is incomplete or invalid.

User: Place Order

The users shall place an order by completing the information in the order
form.

The users shall not be able to place an order if the information in the order
form is invalid or incomplete.

Admin: View User Information

The administrator shall be able to view all the users information that
completes the order form and the checkout process.

Admin: Add/Update/Delete Shopping Items

The administrator shall be able to add new items to the list of shopping items.

The administrator shall be able to modify/update an items price and

description.

The administrator shall be able to delete items from the main page of the
Home-Shop application.

Additional Functional Requirements

The administrator shall be able to view the entire history of the checked-out
items.

The administrator shall be able to view the entire history for the users who
successfully complete the checkout process.

Performance Requirements
This section lists the performance requirements expected from the "Home-Shop"
application.

The users shall be able to add an item to the cart in fewer than 5 seconds.

The users shall be able to view information about an item in fewer than 5
seconds.

The users shall be able to check out the items in the shopping cart within 10
seconds after completing the order form.

The navigation between pages shall take fewer than 5 seconds.

The application shall be able to do a validation check on the information

provided in the user-authentication form and the place-order form to avoid
false or incomplete information.

Non Functional Requirements:

Following Non-functional requirements will be there in the Insurance on internet:

Secure access of confidential data (customers details).

24 X 7 availability.

Better component design to get better performance at peak time.

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:

Security

Reliability

Maintainability

Portability

Extensibility

Reusability

Application Affinity/Compatibility

Resource Utilization

CHAPTER 6: TESTING
Once source code has been generated, software must be tested to uncover (and
correct) as many errors as possible before delivery to customer. Our goal is to design
a series of test cases that have a high likelihood of finding errors. To uncover the
errors software techniques are used. These techniques provide systematic guidance for
designing test that

Exercise the internal logic of software components, and

Exercise the input and output domains of the program to uncover errors in
program function, behavior and performance.

Software is tested from two different perspectives:

Internal program logic is exercised using White box test case design
Techniques.

Software requirements are exercised using block box test case Design
techniques.

In both cases, the intent is to find the maximum number of errors with the Minimum
amount of effort and time.

Unit testing:
Unit testing focuses verification effort on the smallest unit of software design- the
software component or module. The unit test is white-box oriented. The unit testing
implemented in every module of student attendance management System. By giving
correct manual input to the system, the datas are stored in database and retrieved. If
you want required module to access input or gets the output from the End user. Any
error will accrued the time will provide handler to show what type of error will
accrued.

System testing:
System testing is actually a series of different tests whose primary purpose is to fully
exercise the computer-based system. Below we have described the two types of
testing which have been taken for this project. It is to check all modules worked on
input basis .if you want change any values or inputs will change all information. so
specified input is must.

Performance Testing:
Performance testing is designed to test the run-time performance of software within
the context of an integrated system. Performance testing occurs throughout all steps in
the testing process. Even at the unit level, the performance of an individual module
may be assessed as white-box tests are conducted.
This project reduce table, codes. It will generate report fast. No have extra time or
waiting of results .entered correct data will show result few millisecond. Just used
only low memory of our system. Automatically do not getting access at software. Get
user permission and access to other applications.

CHAPTER 7: IMPLEMENTATION
System implementation is the important stage of project when the theoretical design is
tuned into practical system. The main stages in the implementation are as follows:

Planning

Training

System testing and

Changeover Planning

Planning is the first task in the system implementation. At the time of implementation
of any system people from different departments and system analysis involve. They
are confirmed to practical problem of controlling various activities of people outside
their own data processing departments.
The line managers controlled through an implementation coordinating committee. The
committee considers ideas, problems and complaints of user department, it must also
consider:

The implication of system environment

Self selection and allocation for implementation tasks

Consultation with unions and resources available

Standby facilities and channels of communication

This project is supposed to be delivered in three phases, with each phase being an
add-on to the project that makes it more usable and acceptable. In the first delivery,
the application must be able to add an item to the shopping cart and case.

Browse categories on the home page

Select a category and browse through the items

View more information about an item.

Add an item to the shopping cart.

Continue shopping or go to checkout for the item.

The application must be able to check out the items in the cart.

Check out the items.

Continue shopping.

Delete the items to update the shopping cart.

The application asks for user authentication before checking out.

Add items to the cart.

Check out the items

Log in with a valid username and password.

The application must bring up the order form for the check out.

Complete the information on the order form.

Place the order.

System Maintenance
Software maintenance is far more than finding mistakes. Provision must be made for
environment changes, which may affect either the computer, or other parts of the
computer based systems. Such activity is normally called maintenance. It includes
both the improvement of the system functions and the corrections of faults, which
arise during the operation of a new system.
It may involve the continuing involvement of a large proportion of computer
department recourses. The main task may be to adapt existing systems in a changing
environment.
Back up for the entire database files are taken and stored in storage devices like flash
drives, pen drives and disks so that it is possible to restore the system at the earliest. If
there is a breakdown or collapse, then the system gives provision to restore database
files. Storing data in a separate secondary device leads to an effective and efficient
maintains of the system. The nominated person has sufficient knowledge of the
organizations computer passed based system to be able to judge the relevance of each
proposed change.