Sandip

1
A
PROJECT REPORT
ON
SHOPEE.COM
Submitted in Partial Fulfillment of Requirement for
Degree of
BACHELOR OF SCIENCE-INFORMATION
TECHNOLOGY
SUBMITTED
BY
ASHOK BAHIR(5580)
SANDESH CHAULKAR(5585)
UNDER THE GUIDACE OF

PROF:Mrs.VIJAY KOTHAWADE
Ms. SRUSHA CHAVAN
SAKET COLLEGE OF ARTS, SCIENCE &COMMERCE

KALYAN - 421 306
AFFILIATED TO UNIVERSITY OF MUMBAI
ACADEMIC YEAR-2013-2014
2
ACKOWLEDGEMENT
We express sincere gratitude to the HOD of IT Department Mrs.

ShrushaChavan and core faculty of Information Technology.
SaketCollege of Arts, Commerce & Science Kalyan (E) for providing an
opportunity to acquire knowledge from corporate world and
understand IT business.
I also thank them for giving us opportunity to work on “SHOPEE ”

project and constant source of inspiration and guidance to us. Their
valuable knowledge and experience helped us to get through the all
difficulties.
I would also thank my friends for giving me the opinions and

various inputs in long discussion on the project which helped me shape
the Website keeping in mind the user friendly.
I would also like to thank everyone who helped me in my project in

some way or other which includes providing me with some information.
ASHOK BAHIR(5580)
SANDESH CHAULKAR(5585)
3
TABLE OF CONTENTS
Sr.No Description Page No.
1. Introduction 8
2. Preliminary Investigation 10
 Overview of Online Shopping 11
 e-shopping 12
 Existing System 13
 Problems in Existing System 13
 Advantages Of Proposed System 16
 Needs Of The System 17
 Description Of System 19
 Project Management 22
 System Specification 27
 Feasibility Study 32
 Gantt Chart 34
3. System Analysis 38
 Study of the current system 39
 Use-Case Diagrams 40
 Entity-Relationship Diagram 47
4. System Design 50
 Activity Diagram 51
 Class Diagram 56
 Sequence Diagram 60
 Component Diagram 63
 Deployment Diagram 65
5. System Coding 68
 List of Tables with Attributes and Constraints 68
 Screen Layout 71
 Source Code 88
6. System Testing 179
 Testability 182
 Testing Objectives 184
7. Future Enhancement 185
8. Conclusion 186
9. Bibliography 188
4
Introduction
The Project entitled "e-Shopping" is a web-based application
Software developed in ASP.NET using C# as front end on
Pentium machine. The main aim of "e- Shopping" 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 stores
the details of invoices generated by customer and payments
made by them with all Payments details like credit card. The
primary features of the project entitled "ONLINE SHOPPING" are
high accuracy, design flexibility and easy availability. And also it
uses database tables Representing entities and relationships
between entities.
The Shopping Cart program allows visitors to your on-line
shopping site to collect items in a virtual shopping cart. They may
view the contents of their shopping cart at any time and may add
or delete items at will. The program automatically calculates the
subtotal, sales tax, shipping charges, and grand total. When a
visitor decides to check-out, the order information including the
buyer's name, address and billing instruction is e-mailed to your
order department (or whomever you choose) and a receipt is sent
to the shopper.
5
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.
6
PRELIMINARY
INVESTIGATION
7
Overview Of Online Shopping
The central concept of the application is to allow the customer to

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

buyer is directly online to the seller's computer usually via the
internet. There is no intermediary service. The sale and purchase
transaction is completed electronically and interactively in real-
time such as Amazon.com for new books. If an intermediary is
present, then the sale and purchase transaction is called
electronic commerce such as eBay.com.
Here the customer will feel a virtual shopping by adding the
selected product to his cart in addition to that, he can also do bulk
addition into the cart before purchasing. This all options are done
by session management. To ensure the authentification of the
customer, He/She must have to register before proceeding
Modules:
 Register (for new users)

 Login (Existing users)
 View Products by product category
 Search products by price range and/or category
 Select products and add them to cart.
 View cart contents
 Pay pricing
 Acknowledgement
9
10
Existing System
In existing system shopping can done in a manual way, the

customer has to go for shopping, and then he is having the
possibility to choose the products whatever he wants.
It is a time consuming process.
Thus, the system has to be automated.
Problems in Existing System:
 In Existing System the Customer is completely depending on

the manual process for buying the products.
 Manual process is a time consuming factor. And when

customer approaches for a manual shopping directly,
actually he/she does not have an idea about things like,
price range, items, etc.,
 The time which has been spent by the customer in manual

shopping can equates to multiple number of shopping. As
11
customer can sit at home and browse in a fraction of
seconds.
 Thus we need to change to a system like “Online Shopping“.
 Time Consuming
 It is tedious to manage historical data which needs much

space to keep all the previous years’ ledgers, books etc.
 Daily sales and purchases details must be entered into

books are very difficult to maintain.
 Needed an agent
 We have to out for that.
12
Proposed System
The development of this new system contains the following

activities, which try to develop on-line application by keeping the
entire process in the view of database integration approach.
 Secure registration and profile management facilities for

Customers.
 Browsing through the e-Mall to see the items that are there
in each category of products like Apparel, Kitchen
accessories, Bath accessories, Food items etc.
 Creating a Shopping cart so that customer can Shoppe ‘n’
no. of items and checkout finally with the entire shopping
cart
 Customers should be able to mail the Shop about the items
they would like to see in the Shop
 Secured mechanism for checking out from the Shop( Credit
card verification mechanism )
 Updates to customers about the Recent Items in the Shop.
13
ADVANTAGES OF PROPOSED SYSTEM
 Proposed online Shopping system provides very easy

process of buying Books.
 It is more comfortable and flexible rather than offline System.
 It takes very less time for processing of various tasks.
 From any place user can get more information about various
categories of books.
 The advertisement work as an ideal task because through it

people come to know about existing and upcoming books’
categories.
 It can handle all the tasks very easily and accurately.
 The process to store the data about customer and books is

done by computer system so it provides much more
accuracy and security.
14
NEEDS OF THE SYSTEM
Social and economic factor: a wave of social and economic

changes often follows in the wake of the new technology. New
opportunities may arise to improve on a production process or to
do something that was not previously possible. Changes in the
ways individuals are organized into groups may then be
necessary, and the new groups may complete for economic
resources with established units.
Technological factor: people have never before in a time when the
scope of scientific inquiry was so broad, so when the speed of
applying the new technology accounts for many changes in the
organization.
High level decisions and operating processes: in response to
technological, socio-economical factors, top level managers may
decide to recognize operations and introduce new products. To
deal with these needs, people commonly seek new modified
information to support the decision. When that happens, then they
obtain turn to a computer system for help the information users
and data processing specialist then work together to complete a
series of steps in a system study to produce output results to
satisfy information needs.
15
Features of Proposed System
 Accommodates up to four types of shipping

 Allows owner to predefine sales tax based a specific state
 Tracks purchases even if user clicks the back button
 Tracks each customer by Shopper ID (SID) (does not use cookies)
Modules

 Pay pricing
 Acknowledgement
16
Description Of System
Modules of proposed system

 Pay pricing
 Acknowledgement
Characteristic of proposed system
The development of this new system contains the following

entities, which try to develop on-line application by keeping the
entire process in the view of database integration approach
17
Detail view of Modules-
1. Register (for new users)
New user can register can register at this part of the project.
Here user means client who enters into the web site.
2. Login (Existing users)
This part of the project for the previous clients of the site,
whose are already registered at here they can login and view the
related things to them selves and they can do shopping over here.
3. View Products by product category
This is the display view of the products. Here user can view
and select the desired products. And these he can add to the cart.
4. View cart contents

18
User can view their selected products or items. And they can
update or delete their products.
5. Pay pricing
This is the payment part of the project user can pay their price to
products through credit cards, debit cards and etc…..
The mode of pay through online.
6. Acknowledgement
This is report generation module of the project. Here the user can
receive the acknowledge messages from the server system.
19
Project Management
Project Planning and Scheduling:-
Project planning establishes a plan for the software

engineering work that follows. It describes the technical
tasks to be conducted, the risks that are likely, the
resources that will be required, the work product to be
produces, and a work schedule.
Project scheduling is an activity that distributes

estimated effort across the planned project duration by
allocating the effort to specific software engineering tasks.
It is important to note, however, that the schedule evolves
overtime. During early stages of project planning, a
macroscopic schedule is developed. This type of schedule
identifies all software framework activities and the product
functions to which they are applied. As the project gets
under way, each entry on the macroscopic schedule is
refined into a detailed schedule. Here, specific software
20
tasks ( required to accomplish an activity) are identified
and scheduled.
To solve actual problems in an industry setting,

software engineer or a team of engineers must incorporate
a development strategy that encompasses the process,
methods and tools layers and generic phase. This strategy
is often referred to as process model or a software
engineering paradigm. A process model for software
engineering is often chosen based on the nature of the
project and application, the methods and tools to be used,
and the controls and deliverables that required.
To solve actual problems in an industry setting, a

software engineer or a team of engineers must incorporate
a development strategy that encompass the process,
methods, and tool layers.
21
SOFTWARE DEVELOPMENT
METHODOLOGY
Software engineering is the practice of using selected process

techniques to improve the quality of a software development
effort. This is based on the assumption, subject to endless
debate and supported by patient experience, that a methodical
approach to software development results in fewer defects and,
therefore, ultimately provides shorter delivery times and better
value. The documented collection of policies, processes and
procedures used by a development team or organization to
practice software engineering is called its software development
methodology (SDM) or system development life cycle (SDLC).
All projects can be managed better when segmented into a

hierarchy of chunks such as phases, stages, activities, tasks and
steps. In system development projects, the simplest rendition of
this is called the "waterfall" methodology, as shown in the
following figure:
22
In looking at this graphic, which was for major defence systems
developments, please note this presumes that the system
requirement have already been defined and scrubbed
exhaustively, which is probably the most important step towards
project success. Nevertheless, the graphic illustrates a few
critical principles of a good methodology:
 Work is done in stages,

 Content reviews are conducted between stages, and
 Reviews represent quality gates and decision points for
continuing.
23
The waterfall provides an orderly sequence of development steps
and helps ensure the adequacy of documentation and design
reviews to ensure the quality, reliability, and maintainability of the
developed software. While almost everyone these days
disparages the "waterfall methodology" as being needlessly slow
and cumbersome, it does illustrate a few sound principles of life
cycle development.
24
System Specification
Hardware Requirements:-
 Pentium-IV(Processor).
 1 GB Ram
 512 KB Cache Memory
 Hard disk 1 GB
 Microsoft Compatible 101 or more Key Board
 Internet Connection
Software Requirements: -
 Web Technologies : ASP.NET 10
 Language : C#
 Database : SQL SERVER 2005
 Web Server : IIS
 Operating System: WINDOWS XP,7
25
Front-End Used- ASP.NET:
ASP.NET is Microsoft’s server side scripting technology that

enables scripts (embedded in web pages) to be executed by an
Internet server.
 When a browser requests an HTML file, the server returns

the file.
 When a browser requests an ASP.NET file, IIS passes the
request to the ASP.NET engine onthe server.
 The ASP.NET engine reads the file, line by line, and
executes the scripts in the file.
 Why use ASP.NET?
1. Better language support :
 ASP.NET contains a large set of HTML controls. Almost all

HTML elements on a page can be defined as ASP.NET
control objects that can be controlled by scripts.
 ASP.NET also contains a new set of object oriented input
controls, like programmable list boxes and validation
controls.
26
 A new data grid control supports sorting, data paging, and
everything you expect from a dataset control.
2. Event-driven programming :
 All ASP.NET objects on a Web page can expose events

that can be processed by ASP.NET code.
 Load, Click and Change events handled by code makes
coding much simpler and much better organized.
3. Increased performance - Compiled code:
 The first request for an ASP.NET page on the server will

compile the ASP.NET code and keep a cached copy in
memory. The result of this is greatly increased
performance.
4. Easy Configuration & Deployment:
 Configuration of ASP.NET is done with plain text files.

Configuration files can be uploaded or changed while the
application is running. No need to restart the server.
27
Backend used:
 Microsoft SQL Server
Microsoft SQL Server is a relational database

management system (RDBMS) produced by Microsoft. Its
primary query language is Transact-SQL.
 SQL ("Structured Query Language") is an ANSI Standard

computer language commonly used to access data stored
in databases. SQL is a tool for managing, organizing, and
retrieving data stored in a computer database.
 SQL works with relational databases which all organize
data into tables, rows, and columns which correspond to
files, records and fields.
28
29
FEASIBILITY STUDY
Feasibility study is a process to check possibilities of

system development. It is a method to check various different
requirements and availability of financial &technical resources.
Before starting the process various parameters must be checked
like:
•Estimated finance is there or not?
•The man power to operate the system is there or not?
•The man power is trained or not?
All the above conditions must be satisfied to start the
project. This is why in depth analysis of feasibility is carried out.
There are three different ways feasibility can be tested
1) Economical Feasibility
2) Technical Feasibility
3) Operational Feasibility.
1)Economic Feasibility:
In economic feasibility, analysis of the cost of the system is
carried out. The system should be only developed if it is going
to give returned the current manual system user can get the
price only by purchasing the newspapers. In addition if he/she
30
wants to see archives of particular equity then he has to refer
to all the old newspapers. For research reports he has to buy
another magazine. So Instead of buying no of magazines user
has to just go online and with a single click he can get
whatever information he wants. So our project of online share
news passes the test of economic feasibility.
2) Technical Feasibility:
It is basically used to see existing computer, hardware and
software etc., weather it is sufficient or additional equipment’s
are required? Minimum System Requirement is such that it can
be affordable by of the user who is having computer. All the user
requires is compatible browser and.net framework installed so our
system is fully technical feasible.
3) Operational Feasibility:
Once the system is designed there must be trained and expert
operator. If there are not trained they should give training
according to the needs of the system. From the user’s
perspective our system fully operational feasible as it just
requires some knowledge of computer. Operators only need
add daily prices of various equities and there are enough
validations available so operator does not require any special
technical knowledge. So our system also passes the test of
operational feasibility.
31
Gantt Chart
Gantt chart are a project-planning tool that can be

used to represent the timing of tasks required to complete
a project, because Gantt charts are easy to understand
and easy to construct, used by most project managers for
all but the most complex projects.
In a Gantt charts, each task takes up one row. Dates

run along the top in Increment of days, weeks or months,
depending upon total length of project. The expected time
for each task is represented by a horizontal bar whose left
end marks the expected beginning of the task and whose
right end marks the expected completion date. Task may
run sequentially, in parallel or overlapping.
Completed tasks lie to the left of the line and are

completely filled in current task across the time and are
behind schedule if there filled-in section is to left of the line
and ahead of the schedule if the filled-in section to the
right of the line. Future task lie completely to the right of
the line.
32
As the project progresses, the charts is updated by
filling in the bars to length proportional to fraction of words
that has been accomplished on the task. This way, one
can get quick reading of projects progress by drawing
vertical lines through the chart by the current rates.
In constructing a Gantt chart keep the task

manageable number(no more than 15 and 20) so that the
chart fits on a single page. For a team projects it often it
help to have an additional columns containing number or
initials, which identifies that on the team is responsible for
the task.
33
We plan our project according to Gantt Chart as
shown as follows:-
Grantt Chat
34
SYSTEM
ANALYSIS
35
Study of the current system:
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
Functional Components of project:
 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..
 Admin can see daily sell and feedback given by customer
.
 Administrator is adding the delivery report to the database.
36
USE-CASE DIAGRAM
A use case diagram acts as a focus for the description of user requirements. It
describes the relationships between requirements, users, and the major
components. It does not describe the requirements in detail; these can be described
in separate diagrams or in documents that can be linked to each use case.
ELEMENTS OF USE CASE DIAGRAMS:-
ELEMENT DESCRIPTION
(1)Actor An actor portrays any entity (or

entities) that perform certain roles in a
given system. The different roles the
actor represents are the actual business
roles of users in a given system. An
actor in a use case diagram interacts
with a use case
(2)Use Case Represents the actions performed by

one or more actors in the pursuit of a
Use case
particular goal. A use case is a kind of
type.
37
(3)System Boundary A system boundary defines the scope of
what a system will be. A system cannot
have infinite functionality. So, it follows
that use cases also need to have
definitive limits defined. A system
boundary of a use case diagram defines
the limits of the system
(4)Include An including use case calls or invokes

the included one. Inclusion is used to
Usecase usecase show how a use case breaks into
se smaller steps. The included use case is
sese
at the arrowhead end.
38
Login
39
Registration
40
Category
Shopping Cart Web Portal
<<extend>>
Category Management
<<extend>>
Product Management
<<extend>>
Content Management
Customer
<<extend>> Admin
Order Management
<<extend>>
Customer Management
Purchase Module
41
Category Management
View Category
Add Category
Customer Update Category Admin
42
Customer Man
Customer Management
View Customer Details
List Customer
Customer Add Customer Admin
Update Customer
Delete Customer
Content Management
View Content Page
Update Content Page
Customer Admin
43
ER Diagram
ER- DIAGRAM
An Entity Relationship Diagram (ERD) is a snapshot of data

structures. ERDs show entities in a database and relationships
between tables within that database. It is essential to have one of
these if you want to create a good database design. We use an
Entity Relation Model (ERM) to create a data model of a system
and its requirements in a top-down approach. This is frequently
the approach utilized in database design.
ELEMENT DESCRIPTION
Entity: An entity is an object or

concept about which you want to
store information.
Relationships: Relationships
illustrate how two entities share
information in the database
structure.
44
Key attribute: A key attribute is
the unique, distinguishing
characteristic of the entity.
Weak Entity: Weak entity is an

entity that cannot be uniquely
identified by its attributes alone.
Underline: Underline in attributes

stand for Primary key
45
ER DIAGRAM
46
SYSTEM
DESIGN
47
ACTIVITY DIAGRAM
Activity diagram are useful for analyzing a use case by describe

what action needs totake place and when they should occur.
Describing a complicated sequential algorithm and modeling
application with parallel process.
Activity diagram do not give detail about how object behave but
shows the effect of external events on internal processing
Element of Activity Diagram:-

ELEMENTS DESCRIPTION
Initial activity
This show the starting point.
There can be only one initial
state .
48
Activity Description
Represent by
rectangle with rounded
edges.
Transition
Transition are used
mark with movement.
Transition are model using
arrow.
Decisions
Synchronization bar(fork and

joint)
Activities can be done in
parallel to split processing(fork).
Final activity
It is an end of activity
diagram shown with bull’s eye.
49
ACTOR: CUSTOMER
USECASE: LOGIN
Click on LOG IN
button
If member
NO
Sign up for new
registration
Enter
username
Enter password
Password
validation
NO Please enter correct
password
YES
Click ok
50
ACTOR: CUSTOMER, SALES PERSON, WAREHOUSE EMPLOYEE
USECASE: REGISTER
Click on LOG IN
button
click on Sign
up link
Fill registration
form
Enter Verification
Code
Is Verification
Code Valid?
NO Reenter Verification
Code
YES
Submit Form
Is given Mail
ID correct?
NO
Please enter
correct mail Id
YES
Confirm
Registration
51
ACTOR: CUSTOMER
USECASE: CHANGE PROFILE
52
CLASS DIAGRAM
 The purpose of class diagram is to identify and classify the
object that will make up the new system
 The properties and attributes of each object that need to be

recorded are also identified.
 The classes of objects have attributes and association just

like data entities.
 Cardinalities also apply among classes.
 The processing done is possible because object have

methods as well as attributes
Things can be represented in 2 ways:
1. Generalization/specialization hierarchy
2. Aggregation hierarchy
53
54
Sequence Diagram
A sequence diagram shows an interaction, which represents

the sequence of messages between instances of classes,
components, subsystems, or actors. Time flows down the
diagram, and it shows the flow of control from one participant to
another.
Elements of a Sequence Diagram:-
(1)Actor A participant that is external to the

system that you are developing.
Or
: Class name
(2)LifeLine A vertical line that represents the

sequence of events that occur in a
participant during an interaction, while
time progresses down the line. This
participant can be an instance of a
class, component, or actor.
55
(3)Messages
The sender sent the message to the
(a)Synchronous receiver and wait for the procedure
completion
(b)Simple One object sends the messages to the

passive object
(c)Return It returns message from called

procedure of receiver to the sender.
56
Registration
57
Login
58
Product Order
59
COMPONENT DIAGRAM
A component diagram shows the organizational dependency

among software components including source code components,
binary code components or executable components.
Elements of a Component Diagram
ELEMENT DESCRIPTION
(1)
Component The objects interacting with each other
in the system. Depicted by a rectangle
with the name of the object in it,
preceded by a colon and underlined.
60
(2)
Class/Interface/ Similar to the notations used in class
Object and object diagrams
(3)
Relation/Association Similar to the relation/association used
in class diagrams. Gives relation
between two components
61
62
DEPLOYMENT DIAGRAM:
The basic deployment diagram element is the node. The
node represents the environment in which a component or a set
of components execute The different nodes in the deployment
diagram can be interconnected to represent interdependencies,
thus providing a deployment diagram that is easy to comprehend
and provides the complete deployment environment of a system.
Elements of a Deployment Diagram
(1)Node The element that provides the

execution environment for the
components of a system. Depicted by a
cube with the name of the object in it,
preceded by a colon, and underlined.
(2)Connection Similar to the relation/association used

in class diagrams to define the
interconnection between nodes.
63
Web Server
Data
Base
Server
64
SYSTEM
CODING
65
List Of Tables With Attribute And
Constraints:-
Login TABLE
Column name Data type size Allow nulls Constraints Remarks
Username Varchar 50 true Foreign key
Password Varchar 50 true
Type Varchar 50 true
Registration TABLE
Column name Data type size Allow nulls Constraints Remarks
Uname varchar 50 false Primary key
Password varchar 50 true
email_add varchar 50 true
DOB datetime true
address varchar max true
Ph_no Int true
f_name varchar 50 true
L_name Varchar 50 true
pin int true
city varchar 50 true
66
PRODUCTS TABLE
Column name Data type size Allow null
Pid varchar max true
pname varchar max true
thumb varchar max true
image varchar max true
price int true
company varchar max true
feature Varchar max true
cat varchar 50 true
Order_detail
o_id varchar 50 true
p_id varchar 50 true
pname varchar 50 true
qty int true
price int true
subtotal int true
67
Order_master
o_id varchar 50 true
p_id varchar 50 true
uid int true
total int true
o_date datetime true
68
Screen Layout
Homepage
User Sign-in:
69
Authorized User Home page:
Registration Form
70
Admin Login
71
All Mobiles:
Company wise distribution:
72
Product wise:
Accessories:
73
All Tv’s:
74
Product wise:
Accessories:
75
All mp3:
76
Product wise:
Accessories:
77
All Laptops:
78
Product wise:
Accessories:
79
All Tab’s:
80
Product wise:
All Camera’s:
81
Product wise:
82
Accessories:
Order Summary:
83
Add to cart:
Transaction
1. Address
2.Type
84
Final page
Source Code
Main.master.cs
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.IO;
using System.Data;
using System.Data.SqlClient;
namespace Shopee.com
{
public partial class Main : System.Web.UI.MasterPage
{
SqlDataAdapter da,da1;
DataSet ds,ds1;
string a, b, d, e;
SqlConnection con;
protected void Page_Load(object sender, EventArgs e)
{con = new SqlConnection("Data Source=.;Initial Catalog=Project;Integrated
Security=True");
con.Open();
if (Session["uname"] == null)
{
LinkButton1.Text = "Sign_in";
}
else
{
LinkButton1.Text = "Sign_out";
}
85
con = new SqlConnection("Data Source=.;Initial Catalog=Project;Integrated
Security=True");
con.Open();
a = "select pname from product";

da = new SqlDataAdapter(a, con);
ds = new DataSet();
da.Fill(ds);
for (int i = 0; i < ds.Tables[0].Rows.Count; i++)
{
DropDownList1.Items.Add(ds.Tables[0].Rows[i].ItemArray[0].ToString());
}
}
protected void ImageButton2_Click(object sender, ImageClickEventArgs e)

{
Response.Redirect("Login.aspx");
}

{
Response.Redirect("Registration.aspx");
}

{
Response.Redirect("https://www.facebook.com/");
}

{
Response.Redirect("https://accounts.google.com/ServiceLogin?service=oz&continue=https://p
lus.google.com/up/?type%3Dst%26continue%3Dhttps://plus.google.com/%252BGoogleIndia?gpsrc%
253Dsrc%25253Asignup-header%25253Bactn%25253Asignup%2526hl%253Den-
GB%2523%252BGoogleIndia/posts&hl=en-GB");
}

{
}

{
Response.Redirect("https://twitter.com/");
}

{
Response.Redirect("callus.aspx");
}

{
Response.Redirect("mailus.aspx");
}
86
protected void Menu7_MenuItemClick(object sender, MenuEventArgs e)
{
if (Menu7.SelectedValue.ToString().Equals("All Brands"))
{
Session["Catagories"]="Mobile";
Response.Redirect("mobile.aspx");
}
if (Menu7.SelectedValue.ToString().Equals("HTC"))
{
Session["Catagories"] = "Mobile";
Session["brand"] = "HTC";
Response.Redirect("mobile_one.aspx");
}
if (Menu7.SelectedValue.ToString().Equals("Sony"))
{
Session["brand"] = "Sony";
}
if (Menu7.SelectedValue.ToString().Equals("Samsung"))
{
Session["brand"] = "Samsung";
}
if (Menu7.SelectedValue.ToString().Equals("Nokia"))
{
Session["brand"] = "Nokia";
}
if (Menu7.SelectedValue.ToString().Equals("Blackberry"))
{
Session["brand"] = "BlackBerry";
}
if (Menu7.SelectedValue.ToString().Equals("Accessories"))
{
Session["Catagories"] = "mob_acc";
Response.Redirect("mobile_acc.aspx");
}
}
protected void LinkButton1_Click(object sender, EventArgs e)

{
{
LinkButton1.Text = "Sign_out";
}
else
{
Session.Remove("uname");
string w = "delete from order_detail1";
da1 = new SqlDataAdapter(w, con);
ds1 = new DataSet();
87
da1.Fill(ds1);
LinkButton1.Text = "Sign_in";
}
}

{
if (Menu6.SelectedValue.ToString().Equals("All brands"))
{
Session["Catagories"] = "camera";
Response.Redirect("camera.aspx");
}
if (Menu6.SelectedValue.ToString().Equals("Canon"))
{
Session["brand"] = "Canon";
Response.Redirect("camera_one.aspx");
}
if (Menu6.SelectedValue.ToString().Equals("Fujifilm"))
{
Session["brand"] = "Fujifilm";
}
if (Menu6.SelectedValue.ToString().Equals("Nikon"))
{
Session["brand"] = "Nikon";
}
if (Menu6.SelectedValue.ToString().Equals("Olympus"))
{
Session["brand"] = "Olympus";
}
{
}
{
Session["Catagories"] = "camera_acc";
Response.Redirect("camera_acc.aspx");
}
}

{
{
Session["Catagories"] = "Laptop";
Response.Redirect("laptop.aspx");
}
if (Menu4.SelectedValue.ToString().Equals("Acer"))
{
88
Session["brand"] = "Acer";
Response.Redirect("laptop_one.aspx");
}
if (Menu4.SelectedValue.ToString().Equals("Dell"))
{
Session["brand"] = "Dell";
}
if (Menu4.SelectedValue.ToString().Equals("HP"))
{
Session["brand"] = "HP";
}
if (Menu4.SelectedValue.ToString().Equals("Lenovo"))
{
Session["brand"] = "Lenovo";
}
{
}
{
Session["Catagories"] = "laptop_acc";
Response.Redirect("laptop_acc.aspx");
}

{
if (Menu5.SelectedValue.ToString().Equals("All brands"))
{
Session["Catagories"] = "tab";
Response.Redirect("tab.aspx");
}
if (Menu5.SelectedValue.ToString().Equals("Micromax"))
{
Session["brand"] = "Micromax";
Response.Redirect("tab_one.aspx");
}
if (Menu5.SelectedValue.ToString().Equals("Apple"))
{
Session["brand"] = "Apple";
}
if (Menu5.SelectedValue.ToString().Equals("HCL"))
{
89
Session["brand"] = "HCL";
}
if (Menu5.SelectedValue.ToString().Equals("Karbonn"))
{
Session["brand"] = "Karbonn";
}
if (Menu5.SelectedValue.ToString().Equals("Milagrow"))
{
Session["brand"] = "Milagrow";
}
}
protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)

{
string j = DropDownList1.SelectedValue;
Session["dropdown"] = j;
Response.Redirect("detail1.aspx");

{
{
Session["Catagories"] = "Tv";
Response.Redirect("Tv.aspx");
}
if (Menu2.SelectedValue.ToString().Equals("LG"))
{
Session["brand"] = "Lg";
Response.Redirect("tv_one.aspx");
}
if (Menu2.SelectedValue.ToString().Equals("Philips"))
{
Session["brand"] = "philips";
}
if (Menu2.SelectedValue.ToString().Equals("Samsung"))
{
Session["brand"] = "Samsung";
}
{
}
if (Menu2.SelectedValue.ToString().Equals("Vediocon"))
{
90
Session["brand"] = "Videocon";
}
{
Session["Catagories"] = "Tv_acc";
Response.Redirect("tv_acc.aspx");
}
}

{
{
Session["Catagories"] = "mp3";
Response.Redirect("mp3.aspx");
}
if (Menu3.SelectedValue.ToString().Equals("Apple"))
{
Session["brand"] = "Apple";
Response.Redirect("mp3_one.aspx");
}
if (Menu3.SelectedValue.ToString().Equals("Cowon"))
{
Session["brand"] = "Cowon";
}
if (Menu3.SelectedValue.ToString().Equals("Philips"))
{
Session["brand"] = "Philips";
}
{
}
if (Menu3.SelectedValue.ToString().Equals("Transcend"))
{
Session["brand"] = "Transcend";
}
{
Session["Catagories"] = "mp3_acc";
//Session["brand"] = "Transcend";
Response.Redirect("mp3_acc.aspx");
}
}
}
}
91
AdminMaster.master.cs
using System;
using System.Linq;
using System.Web;
{
public partial class Main_AdminMaster : System.Web.UI.MasterPage
{
{

{
}
{
Response.Redirect("https://twitter.com/");
}

{
Response.Redirect("callus.aspx");
}

{
Response.Redirect("mailus.aspx");
}

{
}
{
Response.Redirect("https://accounts.google.com/ServiceLogin?service=oz&continue=https://p
lus.google.com/up/?type%3Dst%26continue%3Dhttps://plus.google.com/%252BGoogleIndia?gpsrc%
253Dsrc%25253Asignup-header%25253Bactn%25253Asignup%2526hl%253Den-
GB%2523%252BGoogleIndia/posts&hl=en-GB");
}
}
}
92
DailyDeals.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
public partial class WebForm3 : System.Web.UI.Page
{
SqlDataAdapter da, da1;
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Security=True");
con.Open();
}

{
}
}
}
Admin-mobile-acc.aspx.cs
using System;
using System.Data;
using System.Linq;
using System.Web;
{
93
{
string s1;
Boolean flag;
string filenameLoc;
string filenameLoc1, a, b, filenameLoc2, filenameLoc3;
SqlConnection con;
SqlDataAdapter da,da1,da2;
DataSet ds,ds1,ds2;
{
Security=True");
con.Open();
if (IsPostBack == false)
{
combofill();
}
}
public void combofill()
{
string s2;
s2 = "Select pid from product";
da2 = new SqlDataAdapter(s2, con);
da2.Fill(ds2);
for (int i = 0; i < ds2.Tables[0].Rows.Count; i++)
{
DropDownList1.Items.Add(ds2.Tables[0].Rows[i].ItemArray[0].ToString());
}
}
public void photo()
{
if (Fileupload1.HasFile == true)
{
filenameLoc = Server.MapPath("~/Images/product/") + Fileupload1.FileName;
filenameLoc1 = ("~/Images/product/" + Fileupload1.FileName);
Session["Pick"] = filenameLoc1;
Fileupload1.SaveAs(filenameLoc);
Image1.ImageUrl = filenameLoc1;
}
}
public void photo1()
{
if (FileUpload2.HasFile == true)
{
filenameLoc2 = Server.MapPath("~/Images/product/") +
FileUpload2.FileName;
filenameLoc3 = ("~/Images/product/" + FileUpload2.FileName);
Session["Pick1"] = filenameLoc3;
FileUpload2.SaveAs(filenameLoc2);
Image2.ImageUrl = filenameLoc3;
94
}
}
protected void Button2_Click(object sender, EventArgs e)

{
a = "select case when count(pid)=0 then 'P1' else 'P'
+cast(max(cast(substring(pid,2,len(pid)) as int))+1 as varchar) end from product";
ds = new DataSet();
da.Fill(ds);
TextBox1 .Text = ds.Tables[0].Rows[0].ItemArray[0].ToString();
Session["Flag"] = false;
}

{
photo();
photo1();
if (Session["Flag"].ToString().Equals("False"))
{
b = "insert into product(pid,pname,thumb,image,price,company,feature)

values('" + TextBox1.Text + "','" + TextBox2.Text + "','" + Session["Pick1"] + "','" +
Session["Pick"] + "'," + TextBox3.Text + ",'" + TextBox4.Text + "','" + TextBox5.Text +
"')";
da = new SqlDataAdapter(b, con);
ds = new DataSet();
da.Fill(ds);
combofill();
}
else
{
if (Session["Pick1"] == null || Session["Pick"] == null)

{
s1 = "update product set pname='" + TextBox2.Text + "',thumb='" +

Session["Pickupdate1"] + "',image='" + Session["Pickupdate"] + "',price=" + TextBox3.Text
+ ",company='" + TextBox4.Text + "',feature='" + TextBox5.Text + "'where pid='" +
TextBox1.Text + "'";
da1.Fill(ds1);
combofill();
}
else
{
s1 = "update product set pname='" + TextBox2.Text + "',thumb='" +
Session["Pick1"] + "',image='" + Session["Pick"] + "',price=" + TextBox3.Text +
",company='" + TextBox4.Text + "',feature='" + TextBox5.Text + "'where pid='" +
TextBox1.Text + "'";
95
da1.Fill(ds1);
combofill();
}
//}

{
flag = true ;
Session["Flag"] = flag;

{
string f;
f = "delete from product where pid = '" + TextBox1.Text + "' ";
da = new SqlDataAdapter(f, con);
ds = new DataSet();
da.Fill(ds);
protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)

{
string s3;
s3 = "select * from product where pid='" + DropDownList1.SelectedValue +
"'";
da = new SqlDataAdapter(s3, con);
ds = new DataSet();
da.Fill(ds);
TextBox1.Text = ds.Tables[0].Rows[0].ItemArray[0].ToString();
Image2.ImageUrl = ds.Tables[0].Rows[0].ItemArray[2].ToString();
Session["Pickupdate"] = ds.Tables[0].Rows[0].ItemArray[2].ToString();
Session["Pickupdate1"] = ds.Tables[0].Rows[0].ItemArray[3].ToString();
}
}
96
Login.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{

{
SqlDataAdapter da;
DataSet ds;
string a, b, d, e, aa;
SqlConnection con;
{
Security=True");
con.Open();
}

{
Response.Redirect("Registration.aspx");
}

{
a = "select * from Login where uname='" + TextBox3.Text + "' and password='"

+ TextBox4.Text + "'";
ds = new DataSet();
da.Fill(ds);
if (ds.Tables[0].Rows.Count > 0)
{
aa = ds.Tables[0].Rows[0].ItemArray[2].ToString();
if (aa == "user")
{
Session["uname"] = TextBox3.Text;
a = "select case when count(oid)=0 then 'o1' else 'o'
+cast(max(cast(substring(oid,2,len(oid)) as int))+1 as varchar) end from Order_Master";
97
ds = new DataSet();
da.Fill(ds);
d = ds.Tables[0].Rows[0].ItemArray[0].ToString();
Session["order_id"] = d;
Response.Redirect("DailyDeals.aspx");
}
else
{
Response.Redirect("admin-mobile-acc.aspx");
}
}
else
{
Label2.Text = "Please enter correct username and password ";
string w = "delete from order_detail1";

da = new SqlDataAdapter(w, con);
ds = new DataSet();
da.Fill(ds);
}
Registration.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{

{
DataSet ds,ds1;
string a, b, c;
SqlConnection con;
{
Security=True");
con.Open();
98
}

{
b = "insert into
Registration(uname,password,email_add,address,f_name,l_name,ph_no,pin,b_day,city)
values('" + TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox7.Text + "','" +
TextBox8.Text + "','" + TextBox12.Text + "','" + TextBox2.Text + "'," + TextBox10.Text +
"," + TextBox9.Text + ",'" + TextBox15.Text +"','" + TextBox13.Text + "')";
da = new SqlDataAdapter(b, con);
ds = new DataSet();
da.Fill(ds);
c = "insert into Login(uname,password,type) values('" + TextBox4.Text + "','"
+ TextBox5.Text + "','user')";
da1 = new SqlDataAdapter(c, con);
da1.Fill(ds1);
}
Mobile.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{

{
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Security=True");
con.Open();
{
a = "select pname,price,Image from product where cat ='" +
Session["Catagories"] + "'";
ds = new DataSet();
da.Fill(ds);
Label2.Text = ds.Tables[0].Rows[0].ItemArray[0].ToString();
Session["Name"] = Label2.Text;
99
ImageButton13.ImageUrl = ds.Tables[0].Rows[0].ItemArray[2].ToString();
Session["Name1"] = Label4.Text;
100
101
}
}

{
string aa1;
aa1 = Session["Name"].ToString();
b = "select pid from product where pname='" + aa1 + "'";
da1 = new SqlDataAdapter(b, con);
da1.Fill(ds1);
string c = ds1.Tables[0].Rows[0].ItemArray[0].ToString();
Session["pid"] = c;
Response.Redirect("detail.aspx");
}

{
string aa1;
aa1 = Session["Name1"].ToString();
da1.Fill(ds1);
Session["pid"] = c;
}
{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
102
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
103
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
104
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
105
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
106
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
107
Mobile_acc.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{

{
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Security=True");
con.Open();
{
ds = new DataSet();
da.Fill(ds);
108
109

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
Response.Redirect("detail_acc.aspx");
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
110
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
111
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
112
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
113
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
114
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
}
Mobile_one.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
115
{
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Label12.Text = Session["brand"].ToString();
Security=True");
con.Open();
{
Session["Catagories"] + "' and company='" + Session["brand"] + " '";
ds = new DataSet();
da.Fill(ds);
}
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
116
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
}
117
Tv.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
public partial class Tv : System.Web.UI.Page
{
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Security=True");
con.Open();
{
ds = new DataSet();
da.Fill(ds);
118
119
}
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
120
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
121
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
122
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
123
{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
}
}
124
Tv_acc.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
public partial class tv_acc : System.Web.UI.Page
{
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Security=True");
con.Open();
{
ds = new DataSet();
da.Fill(ds);
125
}
}
126
{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
127
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
128
{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
129
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
}
}
Tv_one.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
public partial class tv_one : System.Web.UI.Page
{
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Security=True");
con.Open();
{
a = "select pname,price,Image from product where cat='" +
Session["Catagories"] + "' AND company='" + Session["brand"] + "'";
130
ds = new DataSet();
da.Fill(ds);
}
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
131
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
}
}
Camera.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
public partial class camera : System.Web.UI.Page
{
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Security=True");
con.Open();
{
132
ds = new DataSet();
da.Fill(ds);
133
134
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
135
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
136
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
137
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
138
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
139
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
140
{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
}
}
Camera_acc.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
{
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Security=True");
con.Open();
{
ds = new DataSet();
da.Fill(ds);
141
142
}
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
143
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
144
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
145
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
}
}
Camera_one.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
public partial class camera_one : System.Web.UI.Page
146
{
DataSet ds, ds1;
string a, b;
SqlConnection con;
{
Security=True");
con.Open();
{
a = "select pname,price,Image from product where cat='" +
Session["Catagories"] + "' AND company='" + Session["brand"] + "'";
ds = new DataSet();
da.Fill(ds);
}
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
147
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}

{
string aa1;
da1.Fill(ds1);
Session["pid"] = c;
}
}
}
148
Order-summary.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
using System.Data .SqlClient ;
{
public partial class Orders_summary : System.Web.UI.Page
{
DataSet ds,ds1;
string a, b ,c,d,e1,f,f1;
SqlConnection con;
{
Security=True");
con.Open();
Label9.Text =DateTime.Now.ToShortDateString();
Label3.Text = Session["pid"].ToString ();
Label4.Text = Session["pname"].ToString();
Label5.Text = Session["company"].ToString();
Label8.Text = Session["price"].ToString();

{
a = "select case when count(shop_id)=0 then 'S1' else 'S'
+cast(max(cast(substring(shop_id,2,len(shop_id)) as int))+1 as varchar) end from
Order_detail1";
ds = new DataSet();
da.Fill(ds);
b = ds.Tables[0].Rows[0].ItemArray[0].ToString();
Session["shoping_id"] = b;
f = Session["uname"].ToString ();
f1 = Session["order_id"].ToString ();
b = "insert into Order_detail1(o_id,p_id,pname,qty,price,subtotal,shop_id)

values('" + Session["order_id"] + "','" + Label3.Text + "','" + Label4.Text + "'," +
TextBox1.Text + "," + Label8.Text + "," + Label6.Text + ",'" + Session["shoping_id"] +
"')";
da1.Fill(ds1);
149
Session["qty"] = TextBox1.Text;
Session["subtotal"] =Label6.Text ;
Response.Redirect("Add-to-cart.aspx");

{
Double a, b, c;
a = double.Parse(Label8.Text);
b = double.Parse(TextBox1.Text);
c = a * b;
Label6.Text = c.ToString();
}
}
}
Add-to-cart.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
public partial class Add_to_cart : System.Web.UI.Page
{
SqlDataAdapter da,da1,da3;
DataSet ds,ds1,ds3;
string a,b,c,f,f1,f3,f4,f5,f6,f7,f8;
SqlConnection con;
{
Security=True");
con.Open();
Label2.Text = DateTime.Now.ToShortDateString();
a="select * from Order_detail1";
ds = new DataSet();
da.Fill(ds);
GridView1.DataSource = ds.Tables[0];
150
GridView1.DataBind();

{
b = "Select SUM (subtotal) from Order_detail1 ";
da1.Fill(ds1);
Label1.Text = ds1.Tables[0].Rows[0].ItemArray[0].ToString();

{
}

{
f = Session["uname"].ToString();
f1 = Session["order_id"].ToString();
f3 = Session["pid"].ToString();
f4 = Session["pname"].ToString();
f5 = Session["qty"].ToString();
f7 = Session["price"].ToString();
f8 = Session["subtotal"].ToString();
c = "insert into Order_master(oid,pid,uid,total,o_date) values('" +

Session["order_id"] + "','" + Session["pid"] + "','" + Session["uname"] + "'," +
Label1.Text + ",'"+Label2.Text+"')";
da3 = new SqlDataAdapter(c, con);
da3.Fill(ds3);
f6 = "insert into Order_detail(o_id,p_id,pname,qty,price,subtotal) values('"

+ Session["order_id"] + "','" + Session["pid"] + "','" + Session["pname"] + "','" +
Session["qty"] + "'," + Session["price"] + "," + Session["subtotal"] + ")";
da = new SqlDataAdapter(f6, con);
ds = new DataSet();
da.Fill(ds);
Response.Redirect("Transaction.aspx");
}
}
}
151
Detail.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
{
SqlDataAdapter da;
DataSet ds;
string a, b, c;
SqlConnection con;
{
Security=True");
con.Open();
a = "select * from product where pid='" + Session["pid"].ToString() + "'";
ds = new DataSet();
da.Fill(ds);
// Label7.Text = ds.Tables[0].Rows[0].ItemArray[0].ToString();
Session["pid"]= Label7.Text = ds.Tables[0].Rows[0].ItemArray[0].ToString();
Session["pname"] =Label2.Text = ds.Tables[0].Rows[0].ItemArray[1].ToString();
Session["price"] =Label6.Text = ds.Tables[0].Rows[0].ItemArray[4].ToString();
Session["company"] =Label4.Text =
ds.Tables[0].Rows[0].ItemArray[5].ToString();
Session["feature"]= Label5.Text = ds.Tables[0].Rows[0].ItemArray[6].ToString();

{
{
}
else
{
Response.Redirect("Order_summary.aspx");
}
}
}
}
152
Detail1.aspx.cs
using System;
using System.Linq;
using System.Web;
using System.Data;
{
{
SqlDataAdapter da;
DataSet ds;
string a, b, c;
SqlConnection con;
{
Security=True");
con.Open();
string p = Session["dropdown"].ToString();
a = "select * from product where pname ='" + Session["dropdown"].ToString()
+ "'";
ds = new DataSet();
da.Fill(ds);
}

{
{
}
else
{
Response.Redirect("Order_summary.aspx");
}
}
}
}
153
SYSTEM
TESTING
154
Kinds of Testing
 Black Box Testing- Not based on any knowledge of

internal designs or code. Tests are based on
requirements and functionality.
 White Box Testing- Based on the knowledge of the

internal logic of an application’s code. Tests are based
on coverage of code statements, branches, paths and
statements.
 Unit Testing- The most ‘micro’ scale of testing; to test

particular functions and code modules. Typically done
by the programmer and not by the testers, as it requires
detailed knowledge of the internal program design and
code. Not always
155
easily done unless the application has a well-designed
architecture with tight code; may require developing test
driver modules or test harnesses.
 Integration Testing- Testing of combined parts of an

application to determine if they function together
correctly. The ‘parts’ can be code modules, individual
applications, client and server applications on a
network, etc. This type of testing is especially relevant
to client/ server and distributed systems.
 Functional Testing- Black-box type testing geared to

functional requirements of an application; testers should
do this type of testing. This doesn’t mean that the
programmers shouldn’t check that their code works
before releasing it.
 Regression Testing- Re-testing after fixes or

modifications of the software or its environment. It is
difficult to determine how much re testing is needed,
especially near the end of the development cycle.
Automated testing tools can be especially useful for this
type of testing.
 Acceptance Testing- Final testing based on the

specifications of the end user or customer or based on
usse by end-users/ customers over some limited period
of time.
156
 User Acceptance Testing- Determining if software is
satisfactory to an end user customer.
Testability
Software Testability is simply how easily a computer

program can be tasted. The check list that follows provides a
set of characteristics that lead to testable software.
 Operability
 Observables
 Controllability
 Decomposability
 Simplicity
 Stability
 Understandability
Following are the attributes of the Good Test

 A good test has a high probability of finding an error.
 A good test is not redundant.
 A good test should be “Best of Breed”.
157
 A good test would be neither too simple nor too
complex.
Compartmentalization
In this step we divide the project into number of manageable

activities and task like
 Selection Module
 System Admin data module
 Dept. Admin data module
 Store and assign rendered module
 Employee data module
 Task creation data module
 Task allocation and reply data module
 Insert category and pwd Authority module
 Testing Module
 Documentation Module
Why testing is done
 Testing is the process of running a system with the intention

of finding errors.
158
 Testing enhances the integrity of a system by detecting
deviations in design and errors in the system.
 Testing aims at detecting error-prone areas. This helps in

the prevention of errors in a system.
 Testing also add value to the product by confirming to the

user requirements.
Testing Principles
 To discover as yet undiscovered errors.

 All tests should be traceable to customer’s requirement.
 Tests should be planned long before the testing actually
begins.
 Testing should begin “in the small” & progress towards
“testing in the large”.
 Exhaustive Testing is not possible.
 To be most effective training should be conducted by an
Independent Third Party
Testing Objectives
159
 Testing is a process of executing a program with the intent of
finding errors.
 A good test case is one that has a high probability of finding
an as yet undiscovered error.
 A successful test is one that uncovers an as yet
undiscovered error.
FUTURE ENHANCEMENT
Future enhancement
 The shop will require more secure encryption to provide

more secure transaction
 Customer should have be given with reward points for

frequent purchase
 Live support should be enabled
 Updating the website according the user’s needs

160
 More efficient and easier categorical search engine.
 By including a better security for the both the users
 And by making the communication between the user and

admin very easy
CONCLUSION
Online sales will continue to rise. Every webpage designed to sell

a product or market a service should understand the future of
online shopping.
There are several major variables that make online sales

attractive to the worldwide market. These variables include:
1) Value of Products/Services offered
2) Dependability and Reputation of the Seller
3) Ease and Security of payment
161
4) Ease and Security of shipping.
Online buyers establish shopping habits. They abandon bricks

and mortar stores and malls as value, dependability, security and
convenience of online buying improves.
Although the online buyer cannot return an item as quickly in

some situations as the buyer who can walk in and out of a Wal-
Mart or Sears when the parking lot isn't crowded or there is no
line at the returns
desk, there are many other reasons to buy online.
Sellers of low-mass products - small books, DVDs, lightweight

clothing have a marked edge in sales because shipping is
relatively low in cost. The seller of these items doesn't need to
pay the overhead of a store, staff, parking lot, utilities, etc. They
pay only storage and shipping which is becoming increasingly
automated.
Although people are rightfully afraid of bankcard fraud, I believe

all card services will continue to improve security and improve
buyer dispute processes.
162
BIBILIOGRAPHY
1. ASP.NET – The Complete Reference
2. Weinberg, SQL-2 Complete Reference

5th Edition, Tata McGraw Hill
Web Sites referred
 www.google.com
 www.flipkart.com
163
 www.ebay.in
 www.amazon.com
 www.jabong.com
 www.wikipedia.org
 www.w3schools.com
164

Sandip

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Sandip

Загружено:

Авторское право:

Доступные форматы

1

UNDER THE GUIDACE OF

SAKET COLLEGE OF ARTS, SCIENCE &COMMERCE

We express sincere gratitude to the HOD of IT Department Mrs.

I also thank them for giving us opportunity to work on “SHOPEE ”

I would also thank my friends for giving me the opinions and

I would also like to thank everyone who helped me in my project in

The central concept of the application is to allow the customer to

Online shopping is a form of electronic commerce where the

 Register (for new users)

In existing system shopping can done in a manual way, the

Problems in Existing System:

 In Existing System the Customer is completely depending on

 Manual process is a time consuming factor. And when

 The time which has been spent by the customer in manual

 Thus we need to change to a system like “Online Shopping“.

 It is tedious to manage historical data which needs much

 Daily sales and purchases details must be entered into

 We have to out for that.

The development of this new system contains the following

 Secure registration and profile management facilities for

 Proposed online Shopping system provides very easy

 It is more comfortable and flexible rather than offline System.

 It takes very less time for processing of various tasks.

 The advertisement work as an ideal task because through it

 It can handle all the tasks very easily and accurately.

 The process to store the data about customer and books is

Social and economic factor: a wave of social and economic

 Accommodates up to four types of shipping

 Register (for new users)

Modules of proposed system

 Register (for new users)

Characteristic of proposed system

The development of this new system contains the following

1. Register (for new users)

2. Login (Existing users)

3. View Products by product category

4. View cart contents

Project Planning and Scheduling:-

Project planning establishes a plan for the software

Project scheduling is an activity that distributes

To solve actual problems in an industry setting,

To solve actual problems in an industry setting, a

Software engineering is the practice of using selected process

All projects can be managed better when segmented into a

 Work is done in stages,

 512 KB Cache Memory

 Microsoft Compatible 101 or more Key Board

 Database : SQL SERVER 2005

 Web Server : IIS

 Operating System: WINDOWS XP,7

ASP.NET is Microsoft’s server side scripting technology that

 When a browser requests an HTML file, the server returns

1. Better language support :

 ASP.NET contains a large set of HTML controls. Almost all

 All ASP.NET objects on a Web page can expose events

3. Increased performance - Compiled code:

 The first request for an ASP.NET page on the server will

4. Easy Configuration & Deployment:

 Configuration of ASP.NET is done with plain text files.

 Microsoft SQL Server

Microsoft SQL Server is a relational database

 SQL ("Structured Query Language") is an ANSI Standard