Online shopping

INTRODUCTION

PROJECT SUMMARY:-

“Online Shopping System” is the process consumers go through to

purchase Products Or services over the Internet.

Seller (Registered, Manage Products Upload By himself)

User (Registered, Browse & Purchase Items)

Administrator (A person who keeps track of the website)

Online Shopping website is built so that users find Products of interest

by visiting website directly. Once the user or the customer has found Products

of his interest, payment can be done using credit cards. Once the payment has

been accepted the goods or services can be delivered to the customer by

shipping Products. Online Shopping System website allow seller to let them

Register with Eshop-trade.com. Here Seller Can Put his Product on Purchase.

Seller can show, update and Delete the Product that is uploaded by him.

“Online Shopping System” is the process consumers go through to purchase

Products or services over the Internet. An online shop, e-shop, e-store, internet

shop, web-shop, web store, online store, or virtual store evokes the physical

analogy of buying Products or services at a bricks-and-mortar retailer or in a

shopping mall.

1

Online shopping

PURPOSE:-

The Online Shopping System website is built so that the users find

Products of interest by visiting the website of the retailer directly. Once the user

or the customer has found Products of his interest payment can be done using

credit cards on delivery. Once a payment has been accepted the goods or

services can be delivered in the following ways: shipping products, drop

shipping or in store pickup Seller can registered with Online Shopping System

website and start selling his products just in few steps. After successful

Registration of seller he can manage and can upload too many items according

to the policy of Online Shopping System website.

The main idea of Online Shopping System is just not having a good

looking website that could be listed in a lot of search engines and it is not about

the art behind the site. It also is not only just about disseminating information,

because it is all about building relationships and making money.Utmost care

was taken so that all the pre defined objectives are achieved and the users get

what they really want. Customers and Seller are benefited not only by high level

of convenience but also by the broader selection; competitive pricing and

greater access to information.

2

Online shopping

SCOPE OF WORK:

The web based application is made reliable and globally accessible by user

and it’s very secure to user.

Internet based application

Integrate with any existing online application

Dynamically make changes.

In future new technology can be applied.

The Project Scope includes total three types of users who can perform different

tasks according to their roles. Customer, Seller, and Administrator. The

functionality of each one of them is described below in detail.

3

Online shopping

PROJECT MANAGEMENT

PROJECT PLANNING:-

Project Development Approach :-

1) Analyzing Current System:

Going to software store for gathering practical knowledge.

Observing and analyzing the system, working in the store.

2) Gathering requirements according to the analysis.

3) Designing the objectives, plan, structure of system and system

model.

4) Designing of forms in Dot Net.

5) Creating database.

6) Establishing connectivity between system forms and database.

7) Testing to check if application is running successfully.

8) Creating documentation and report.

Process model (Incremental life cycle)

4

Online shopping

Incremental model

2.4 RISK MANAGEMENT:-

Risk Identification:-

5

Online shopping

Risk Identification is a systematic attempt to specify threats to the

project plan. By identifying the known and predictable risks, the project

manager takes a first step towards avoiding them when possible and controlling

them when necessary.

One method of identifying risks is to create a risk item checklist. The checklist

can be used for risk identification and focuses on some subset of known and

predictable risks in the following subcategories.

Product Size –risks associated with the overall size of the software to be built

or modified.

Business impact –risks associated with constraints imposed by management.

Customer Characteristics – risks associated with the sophistication of the

customer and the developer’s ability to communicate with the customer in a

timely manner.

Process Definition – risks associated with the degree to which the software

process has been defined and is followed by the development organization.

Development Environment – risks about the availability and quality of the

tools to be used to build the project.

Technology to be built – risk on the complexity of the system to be built and

the newness of the technology.

Staff size and experience – risks with the overall technical and project

experience of the software engineers who will handle the work.

SYSTEM REQUIREMENT STUDY

6

Online shopping

HARDWARE AND SOFTWARE REQUIREMENT:-

Hardware Requirement

Hardware Recommended System Requirements

CPU – Speed <1.0Ghz>

RAM <256 MB>

Hard-disk

Space

<40 GB>

Network

Configuration

<Client Server Application>

Table Hardware requirement

Software Requirement

Front End <Visual Studio.Net 2008>

Back End <MS SQL Server 2005>

Operating System <Windows 98,NT,XP,VISTA>

Programming

Language

C#.net 3.5

Project

Technology

ASP.net 3.5

Browser

Compatibility

IE, Netscape, Mozilla, and Opera, Google

Chrome

Table Software Requirement

7

Online shopping

PLATFORM DETAILS:-

Introduction to .NET

Visual Studio .NET is a complete set of development tools for

building ASP Web applications, XML Web services, desktop applications, and

mobile applications. Visual Basic .NET, Visual C++ .NET, and Visual C# .NET

all use the same integrated development environment (IDE), which allows them

to share tools and facilitates in the creation of mixed-language solutions. In

addition, these languages leverage the functionality of the .NET Framework,

which provides access to key technologies that simplify the development of

ASP Web applications and XML Web services.The .NET Framework is an

integral Windows component that supports building and running the next

generation of applications and XML Web services. The .NET Framework is

designed to fulfill the following objectives:

To provide a consistent object-oriented programming environment

whether object code is stored and executed locally, executed locally but

Internet-distributed, or executed remotely.

To provide a code-execution environment that promotes safe execution of

code, including code created by an unknown or semi-trusted third party.

To provide a code-execution environment that eliminates the performance

problems of scripted or interpreted environments.

To build all communication on industry standards to ensure that code

based on the .NET Framework can integrate with any other code.

8

Online shopping

The .NET Framework has two main components: the common language

runtime and the .NET Framework class library. The common language runtime

is the foundation of the .NET Framework. You can think of the runtime as an

agent that manages code at execution time, providing core services such as

memory management, thread management, and remoting, while also enforcing

strict type safety and other forms of code accuracy that promote security and

robustness. In fact, the concept of code management is a fundamental principle

of the runtime. Code that targets the runtime is known as managed code, while

code that does not target the runtime is known as unmanaged code. The class

library, the other main component of the .NET Framework, is a comprehensive,

object-oriented collection of reusable types that you can use to develop

applications ranging from traditional command-line or graphical user interface

(GUI) applications to applications based on the latest innovations provided by

ASP.NET, such as Web Forms and XML Web services.

MS SQL SERVER 2005 Express Edition

ADO.NET Components

The ADO.NET components have been designed to factor data access

from data manipulation. There are two central components of ADO.NET that

accomplish this: the Dataset, and the .NET Framework data provider, which is

a set of components including the Connection, Command, DataReader, and

DataAdapter objects.

The ADO.NET Dataset is the core component of the disconnected

architecture of ADO.NET. The Dataset is explicitly designed for data access

independent of any data source. As a result it can be used with multiple and

differing data sources, used with XML data, or used to manage data local to the

application. The Dataset contains a collection of one or more DataTable

9

Online shopping

objects made up of rows and columns of data, as well as primary key, foreign

key, constraint, and relation information about the data in the DataTable

objects.

The Connection object provides connectivity to a data source. The

Command object enables access to database commands to return data, modify

data, run stored procedures, and send or retrieve parameter information. The

DataReader provides a high-performance stream of data from the data source.

Finally, the DataAdapter provides the bridge between the DataSet object and

the data source. The DataAdapter uses Command objects to execute SQL

commands at the data source to both load the DataSet with data, and reconcile

changes made to the data in the DataSet back to the data source.

You can write .NET Framework data providers for any data source.

The .NET Framework ships with two .NET Framework data providers:

the .NET Framework Data Provider for SQL Server and the .NET Framework

Data Provider for OLE DB.

The following diagram illustrates the components of ADO.NET

SYSTEM ANALYSIS

REQUIREMENT SPECEFICATION

Requirements Analysis is the process of understanding the

problem and the requirements for a workable solution.

10

Online shopping

Once the requirements have been gathered they become the

basis for “Requirements Analysis”. Analysis categorizes requirements and

organizes them into related subsets, explores each requirement in relationship to

others, examines requirement for consistency, omissions and ambiguity, and

prioritizes requirements based on the needs of the customer. Rough estimates of

development are made and used to assess the impact of each requirement on

project cost and delivery time.

Using an iterative approach, requirements are eliminated,

combined, and/or modified so that each party achieves some measure of

satisfaction. The requirements are used to generate Business Process Flows, Use

Cases Modelling and Data Flow diagrams which facilitates a clearer

understanding of the requirements and its solution, for both the customer and

the developer.

Requirements Analysis Process

System Requirements

1. Requirement Specification

11

Online shopping

Requirements Specifications the process of

describing what a system will do. It involves scoping the requirements so that it

meets the customer’s vision. Requirements Specification serves as a foundation

software, hardware and database design. It describes the function (Functional

and Non-Functional) and performance of the system and the constraints that

will govern its development. It specifies the inputs and also describes the

outputs. These specifications need to be complete, comprehensive, Testable,

Consistent, Unambiguous, Writable, Modifiable, and Implemental.

Table Name: Customer

Attributes Type Description

Cust_id Nvarchar(50) PK(not null)

Name Nvarchar(max) Not null

User_id Nvarchar(50) FK(not null)

Email Nvarchar(50) Not null

Ph_no Numeric(18,0) Not null

Mobile_no Numeric(18,0) Not null

Home_address Nvarchar(Max) Not null

City Nvarchar(50) Not null

Pin_code Numeric(18,0) Not null

Secret_question Nvarchar(Max) Not null

Date_of_birth Nvarchar(Max) Not null

12

Online shopping

Table Name: Login

Attributes Type Description

User_Id Nvarchar(50) PK(not null)

User_Type Nvarchar(50) Not null

Password Varchar(20) Not Null

Table Name: Categoeris_item

Attributes Type Description

categoeris_id Nvarchar(50) PK(not null)

Cat_Name Nvarchar(max) Not null

No_subcategoeris Int not null

Table Name: Sub_Categoeris_item

Attributes Type Description

Sub_cat_id Nvarchar(50) PK(not null)

categoeris_id Nvarchar(50) FK(Not null)

Qty Int not null

Table Name: item

Attributes Type Description

item_id Nvarchar(50) PK(not null)

Sub_cat_id Nvarchar(50) FK(Not null)

categoeris_id Nvarchar(50) FK(not null)

Price money Not null

13

Online shopping

Seller_id Nvarchar(50) FK(not null)

Item_name Nvarchar(MAX) Not null

Qty Int Not null

Item_title Nvarchar(MAX) Not null

Description_item Nvarchar(MAX) Not null

Auction_detail Boolean Not null

Company_add Nvarchar(Max) Not null

Item_image Varchar(100) null

Table Name: Admin_info

Attributes Type Description

User_Id Nvarchar(50) PK(not null)

Password Varchar(20) Not Null

Table Name: Seller

Attributes Type Description

Seller_id Nvarchar(50) PK(not null)

Seller_Name Nvarchar(max) Not null

User_id Nvarchar(50) FK(not null)

14

Online shopping

Email Nvarchar(50) Not null

Ph_no Numeric(18,0) Not null

Mobile_no Numeric(18,0) Not null

Seller_address Nvarchar(Max) Not null

City Nvarchar(50) Not null

Pin_code Numeric(18,0) Not null

Secret_question Nvarchar(Max) Not null

Date_of_birth Nvarchar(Max) Not null

Table Name: Payment

Attributes Type Description

User_id Nvarchar(50) FK(not null)

Payment_Details Nvarchar(max) Not null

Card_holder’sDetai

l

Nvarchar(50) FK(not null)

Amount money Not null

Cart_id Nvarchar(max) Not null

Transaction_id Int (PK)Not null

Delivery_add Nvarchar(MAX) FK(not null)

Table Name: Cart

Attributes Type Description

15

Online shopping

User_id Nvarchar(50) FK(not null)

Item_id int FK(not null)

User_quntity int not null

Price money Not null

Sub_total bigint Not null

Item_name Nvarchar(50) Not null

Item_image Varchar(50) not null

Cart_id int PK(Not null)

Table Name: Shipping

Attributes Type Description

Shipping_id Nvarchar(50) PK(not null)

Type_shipping Nvarchar(max) Not null

Item_id Nvarchar(50) FK(not null)

Cust_id Nvarchar(50) FK(not null)

Shipping_address Nvarchar(max) Not null

Mobile_no Numeric(18,0) Not null

Status Nvarchar(Max) Not null

City Nvarchar(50) Not null

Courier_id Nvarchar(50) FK(Not Null)

Date_of_Shipment Date/time Not null

Name_reciver Nvarchar(Max) Not null

16

Online shopping

Data Flow Diagram

LEVEL DFD FOR ADMIN:

17

Online shopping

SCREEN SHOTS

18

Online shopping

Home page

Admin Home page

19

Online shopping

Admin login page

20

Online shopping

Add / Manage product

Manage Category

21

Online shopping

Manage Subcatagory

Registration

22

Online shopping

User login page

Product search report

23

Online shopping

Product detail

24

Online shopping

Product chart

25

Online shopping

Payment

26

Online shopping

Seller registration

Seller insert new item

27

Online shopping

CONCLUSION

Every project work does not matter website project or any other project

could not be the result of sole effort; even though, developer team consists one

member. We think success of any project does not depend only on better

software development skills, but also, zeal to listen and help the users. Only

user interaction at development phase can give you an idea to fulfill their

requirements. Because, up to development or installation phase software is for

developer, but then after it is for users .We experienced that do make the

website for users not for fame of being better programmer or software

developer. Ultimately, users appraise your efforts not your peers.

After making this project we can conclude that, we have tried to fulfill the

need of customer i.e. EShop-trade.com. We have tried to make our website very

user-friendly. One can easily operate the system. So this project is very useful

for any user. Customer can purchase faster and it will be cost and time effective.

Some limitations are there, but it they do not matter on the shining of this

website.

28

Online shopping

LIMITATIONS AND FUTURE ENHANCEMENTS

LIMITATIONS:

The mentioned requirements in SRS are subject to change as Clients

changes mind every now & then.

The deadline cannot be estimated for Project as requirements are not

clear.

Goods once sold will not be taken back.

Goods received with broken piece, burn parts, Cracks, Missing or

tampered components and tampered warranty card will be rejected and

warranty will be void.

Warranty will be honored only on presentation of our invoice.

Visitor of the website, if it is not any user then he will not be able to

purchase products.

User will not able to see the inventory about the products.

Because of heavy graphics, the size of the website is increased. So it

takes more time to load at user side.

This tool is running only on Microsoft platform.

Visual Studio .Net version 3.5 only supports MS SQL SERVER-2005 or

higher version on the server.

FUTURE ENHANCEMENTS:

In future we are going to remove maximum limitations of the website as mentioned above. And we will also try to reduce the size of the website. And we will add new and new functionalities to the website and make it user-friendly and very attractive. We are trying to send messages directly on the mobiles of customers. We are thinking to provide live chat also, so that users can get more and more information as soon as possible.

29

Online shopping

REFERENCES

Analysis of Project Requirements

For basic requirements and to know the processes we visited our guide.

Technical Know How

Books

Programming on Visual Studio 2008 by OReilly, working with LinQ

Developing Web Applications Using Microsoft Visual Studio

2008,Microsoft Officail Course-2310C

Software Engineering by Rajib Mall, Structural Diagram

Internet Sources

For Code Snippets of web services -

http://snippets.dzone.com/tag/webservice,

http://www.a1vbcode.com/snippet-3121.asp

http:/www.projectortoprojector.com

For temples – http://www.templatemo.com.

For asp.net errors – http://www.asp.net.

30