online jewellery shopping final.docx

SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010

CHAPTER-1

INTRODUCTION


1.1Description of the System under Study The organization that has been taken as reference for the development of this online

software system is “Snapdeal.com”. It is a leading destination for online shopping in

India, offering some of the best prices and a completely hassle-free experience with

options of paying through Cash on Delivery, Debit Card, Credit Card and Net Banking

processed through secure and trusted gateways. It offers a wide range of jewellery

products encompassing gold, silver, platinum and much more.

The products offered by Snapdeal are featured on the site with expert descriptions to help

the consumer arrive at the right buying decision.Snapdeal also offers free home delivery

for many of its jewellery products along with easy interest-free EMI options along with a

facility of the 30-day replacement guarantee so that the customer can get the product

replaced in case one doesn’t find oneself satisfied with the quality of the product.

1.2Description of the Proposed System Aim

The main aim of this project is to develop an interactive and dynamic website that

provides the customer with an on-the-click functionality to search for their desired

products over a wide range of jewellery products and buy them easily and at any time

according to the user’s convenience. The customer can even provide their feedback in

return that could be used by the company for the enhancement of the quality of the

products and services it provides.

Objective 1. The objective of the system is to provide the customer with on-the-click functionality

that helps them to search over a variety ofjewellery products at a centralized location

and buy the products that best suit their requirements in an easier and faster fashion.

2. The software system is designed in such a way that anyone can view the updates of

the products being offered on the website at any time that too easily.

3. The system also aims at providing the customers with a quick and easy way to

compare the jewellery products being offered.

4. The software will help in easy maintaining and updatingjewellery products in the

website for the administrator.


Scope 1. The scope of the system is to provide the users with an account through the process of

registration and with a mechanism that lets the customer give some feedback or ask a

query pertaining to the products being offered online.

2. The system also helps in carrying out the transactions with the help of simple

shopping cart and checkout system.

3. The system will also reduce the manual operation associated with the maintenance of

the records consisting of the product order details, customer details.

4. The system also facilitates user by providing an easy search mechanism to search his

desired product on the basis of product name, category and brand.

1.3Methodology of Data Collection

1.3.1 Primary Data Collection

Primary research entails the use of immediate data in determining the survival of the market.

The popular ways to collect primary data consist of surveys, interviews and focus groups,

which shows that direct relationship between potential customers and the companies.

However, we have not attempted to collect the primary data for the development of this online

software system.

1.3.2 Secondary Data Collection

For secondary data, books and websites are referred to acquire knowledge about the running of

such system and which all modules can be incorporated in such systems. It is a means to

reprocess and reuse collected information as an indication for betterments of the service or

product. There are a few references that have been referred to throughout the entire development

process as listed below:

1. http://www.snapdeal.com

2. http://www.pcjeweller.com

1.4Methodology of System Design(SDLC Model)


The iterative waterfall model has been used to build the modules in this online software

system.

Iterative waterfall modal develop a system through repeated cycles as iterative life

cycle model does not attempt to start with a full specification of requirements.

Development begins by specifying and implementing just part of the software, which

can then be reviewed in order to identify further requirements. This process is then

repeated, producing a new version of the software for each cycle of the model.

The iterative involves the redesign & implementation of a task from the project

control list, & the analysis of the current version of the system.

The goal for the design & implementation of any iteration is to be simple,

straightforward, & the modular, supporting redesign at that stage of a task added to

the project control list. Iterative modal involves analysis of the structure, modularity,

usability, reliability, efficiency, & achievement of goals.

Fig-1.1 Iterative model


REASONS FOR CHOOSING ITERATIVE WATERFALL MODEL

1. It is effective in the situations where requirements are defined precisely

2. It is effective in the situations where there is no confusion about the functionality of the final

product.

3. After every cycle a feedback is provided to the other phases of the system.

1.5System Requirement Tools

a.) Hardware Interfaces

Screen resolution 1024*786 pixels(minimum)

System requirement Network based system

Processor Pentium 4, 1.0 GHz or higher

RAM 512 MB or higher

b.) Software Interfaces

Front End Microsoft Visual Studio 2010

Back End SQL Server 2010

Web Server IIS

Operating System Microsoft Windows 7


1.6Project Planning and Gantt Chart


CHAPTER 2

Software Requirement

Specifications


A software requirements specification (SRS) is a comprehensive description of the intended

purpose and environment for software under development. The SRS fully describes what the

software will do and how it will be expected to perform.

The basic issues addressed while writing SRS are:

Functionality

External Interfaces

Performance

Attributes

Design Constraints Imposed on an Implementation

A good SRS should be Correct, Unambiguous, Complete, Consistent, Verifiable, Modifiable,

Traceable, and Ranked for importance and/or stability.

2.1 Introduction

The following subsections of Software Requirement Specifications Document should

facilitate in providing the entire overview of the Information system “SPARKLING

STONES ONLINE SHOPPING SYSTEM” under development. This document aims at

defining the overall software requirements for DBA and CUSTOMER. Efforts have been

made to define the requirements of the Information system exhaustively and accurately.

2.2 Purpose

The main purpose of Software Requirement Specifications Document is to describe in a

precise manner all the capabilities that will be provided by the Software Application

“SPARKLING STONES ONLINE SHOPPING SYSTEM”. It also states the various

constraints which the system will be abide to. This document further leads to clear vision of

the software requirements, specifications and capabilities. These are to be exposed to the

development, testing team and end users of the software.


2.3 Scope

1. The scope of the system is to provide the users with an account through the process of

registration and with a mechanism that lets the customer give some feedback or ask a

query pertaining to the products being offered online.

2. The system also helps in carrying out the transactions with the help of simple shopping

cart and checkout system.

3. The system will also reduce the manual operation associated with the maintenance of the

records consisting of the product order details, customer details.

4. The system also facilitates user by providing an easy search mechanism to search his

desired product on the basis of product name, category and brand.

2.4 Definition, acronyms, abbreviations

Frontend: The interacting user interface.

Backend: The one from which the system picks up the data i.e. the database.

SQL: Structured Query Language.

SRS: Software Requirements Specifications

SDLC: Systems Development Life Cycle

IIS: Internet Information Server

DBA: Database Administrator

2.5References

www.snapdeal.com

http://sparklingstones.com

www.pcjeweller.com

2.6 Overview

The rest of this SRS document describes the various system requirements, interfaces, features

and functionality in detail

Front End Client Application (with data entry / update /delete /view and reporting facility)

Backend Database


2.7 Overall description of proposed system

The online shopping system the customer with an on-the-click functionality that helps them to

buy their desired product by comparing the prices using a powerful high-performance search

system to search their desired product on various search attributes. The product purchased is

shipped to the customer after the payment is been made using customer friendly online payment

system. The system also helps in easy maintenance of the product catalog for the DBA.

2.8 Product Perspective

The application will be windows-based, self-contained and independent software product.

2.9System Interfaces

None

2.10Interfaces

The application will have a user friendly and menu based interface. Following screens will be

provided.


a) A Login Screen for entering username & password. Access to different screens will be

based upon the role of the user.


b) A User Registration Screen for entering the user details that could be fetch by the admin

for further use and also the user would be able to view and edit his details at any time.


c) A report that is the Bill Screen will be generated wherein the user details as well as the

product details will be there which the customer has purchased.

2.10.1 Hardware Interfaces

Processor: Pentium 4, 1.2 GHz

RAM: 128 SD-RAM.

Hard Disk: 200 MB or above.

2.10.2 Software Interfaces


Operating system: Windows XP.

Front End: Microsoft Visual Studio 2010

Back end:SQL Server – 2010

Web Server: IIS

2.10.3Communication Interfaces

None

2.11Memory Constraints

The system required minimum 128 MB RAM and 200 MB minimum hard disk space.

2.12Operations

This product will not cover any automated housekeeping aspects of database. The DBA at client

site will be manually deleting old/ non required data. Database backup and recovery will also

have to be handled by DBA.

2.13Site Adaptation Requirement

The terminals at client side will have to support the hardware and software interfaces specified.

2.14Product functions

The system will allow access to users including the DBA and customers from anywhere in the

world. Depending upon the user’s role, he/she will be able to access only specific modules of the

system.

A summary of the major functions that the software will perform:

(i) A Login facility for enabling access to the system both for customers and DBA.

(ii) The customer can view the product catalogue without logging into the system or getting

him/her registered but for making a purchase and giving some feedback he/she will have to

follow the foreseen process.

(iii)DBA will maintain the system by add/update/delete the product details in the catalog.

2.15User Characteristics


2.15.1. Educational Level: At least graduate and should be comfortable with English language.

2.15.2. Technical Expertise: Should be a high or middle level employee of the organization

comfortable with using general purpose applications on a computer.

2.16Constraints

None

2.17Assumptions and Dependencies

None

2.18Apportioning Requirement

Not Required

2.19Specific Requirements

This section contains the software requirements to a level of detail sufficient to enable designers

to design the system, and testers to test the system.

2.20External Interfaces

None

2.21User Interfaces

Refer to 2.10

2.22Hardware Interfaces

Refer to 2.10.1

2.23Software interfaces

Refer to 2.10.2

2.24Communication Interfaces

None

2.25System Features

2.25.1 Module nameOnline Jewellery Shopping System Modules:

- Login Module: In this module,the DBA or the customer will have to authorize his access to the

modules of the online software system.

- Search Module: In this module, product search using high-performance search system with an

option to search by selected attributes.


-Shopping cart: This module displays the customer’s shopping cart.

-My Account: This module helps the customer to edit his/her profile details, view the orders

made, etc.

-Feedback/Query: In this module the customer can give some valuable feedback or ask a query

pertaining to a product.

- Admin Module: In this module,the work of admin can be proceeded with i.e. maintenance of

the website, review customer’s feedback and queries, bill maintenance (can only be accessed by

the DBA).

2.25.2Validity Checks-Login

(a) User name: should not start with special character and not be blank.

(b) User password: should not be blank and should be in an encrypted form “***..” with a

length of minimum of 4.

Error Handling / Response to abnormal situations

a) If the password or user id/name is wrong then show a message regarding field.

b) If system does not respond then close the program and restart again.

c) If entered information does not match with its respective field then show a message to

correct it.

2.26Performance Requirements None2.27Logical Database RequirementsThe proposed information system contains the following data tables in its database collection.

2.27.1 Database used for Login:

Field name Field type Field size Description

User_id Varchar2 20 user id of the user

Password Varchar2 20 Password required to access the system

2.27.2Database used for Customer:



First Name Varchar2 10 Customer’s first

name

Last Name Varchar2 10 Customer’s second name

Email_id Varchar2 20 Email address of the user

Address Varchar2 50 Address of the customer

City Varchar2 20 City where the customer resides

State Varchar2 20 State where the customer resides

Pin_code Varchar2 10 Code of the area where the customer

livesPh_num Varchar2 15 Contact number of

the customer

2.27.3 Database used for Product :


Product_id Varchar2 10 Unique ID number of product

Category Varchar2 20 Category to which product belongs

Pr_Type Varchar2 20 Type of the product

Brand Varchar2 25 Brand name of product

Description Varchar2 100 Name and features of product

Stock Varchar2 5 Quantity of product available

Price Varchar2 6 Price to be paid on the purchase of product

Discount Varchar2 5 Discount onto the price of product


2.27.4 Database used for Cart:




Delivery Time Varchar2 5 Days taken to deliver the product


Quantity Varchar2 10 Number of products purchased

Subtotal Varchar2 6 Total amount pertaining to a product

typeGrand Total Varchar2 6 Total amount to be

paid for the products in the cart


2.27.5 Database used for Bill and Order


Order_id Varchar2 20 Unique order number

Order_date Varchar2 10 Date on which the order was placed

Invoice_no Varchar2 20 Bill number

Invoice_date Varchar2 10 Date on which the product is shipped for

deliveryFirst Name Varchar2 10 Customer’s first name


Billing_add Varchar2 50 Address of the customer

Shipping_add Varchar2 50 Address at which the product is to be

deliveredProduct_details Varchar2 100 Product details which

has been purchasedPrice Varchar2 6 Price to be paid on the

purchase of productQuantity Varchar2 10 Number of products

purchasedTax Varchar2 4 Tax to paid on a

productSubtotal Varchar2 6 Total amount

pertaining to a product type

Grand Total Varchar2 6 Total amount to be paid for the products

in the cart

2.27.6 Database used for Customer Feedback:



2.28Design Constraints

Standard Compliance

None


2.29Software System Attributes

2.29.1 Reliability This application is a reliable product that produces fast and verified output of all its processes.

2.29.2 Availability This application will be available to use for DBA and customers and help them to carry out their

operations conveniently.

2.29.3 Security The application will be password protected. User will have to enter correct username, password

and role in order to access the application.

2.29.4 Maintainability The application will be designed in a maintainable manner. It will be easy to incorporate new

requirements in the individual modules.

2.29.5 Portability The application will be easily portable on any windows-based system that has oracle installed

and IE.

2.30 Other RequirementsNone


Chapter-3Systems Design

3.1Overall design of the system:


There are two functional components of this system i.e. the admin and the user. Both admin and user need to login in order to access the information. Main functionality of admin is to maintain the product details that comprise of the stock with the site maintenance. Main functionality of customer is to review the catalogue even if s/he is not registered with the site. If customer needs to purchase any product then he or she will have to register with the website. All the products chosen by the customer for purchase would get added to the shopping cart and the bill will be generated once the customer confirms the purchase. The customer can also edit the personal information and view the order history.

3.1.1 Block Diagram

Block diagram is a diagram of a system, in which the principal parts or functions are represented by blocks connected by lines that show the relationships of the blocks. This block diagram shows the access of the admin and the customer to the different functional modules of the online software system.

3.1: Functional ‘Block Diagram


3.2 Physical Design

This section contains the details about all the processes that are performed in the software system and also tells us about the input and output identification i.e. what is the input being given and what is the desired output.

1. Login process

Input: User will enter his/her ID and password, if the entered details match the database the

userwill be logged in.

Output: The user depending on his role as that of a customer or DBA cannow access the various

system modules.

2. Account

Input: The customer re-enters the details pertaining to his personal profile, order made for a

product if there are some changes to be made.

Output: The report changes made by the customer in the various data fields are reflected back to

the database records.

3. Shopping Cart

Input: This requires a click event as an input on to the button “Add to Cart” if the customer

wishes to buy a particular product and this action adds that product to the shopping cart.

Output: The products in the shopping cart can be reviewed by the customer at any time they log

into the system and can proceed for the placement for the order to make their purchase.

4. Feedback

Input: The customer gives his/her valuable feedback about a particular product and can also ask

a query about the products being displayed in the product catalogue.

Output: The query asked by the customer can be answered by any other customer who uses the

online software system and this would help them arrive at their decision so as to purchase the

products being offered or not and the feedbacks of the customers can be used in the direction of

improving the product quality by the organisation owning the online system.

5. Bill

Input: Any purchase made by the customer.

Output: The bill will get generated that would be given the customer.


6. Product Maintenance

Input: The admin can maintain the database associated with the product catalog by adding ,

deleting and modifying the details.

Output: The customer can choose among those apparel made available to them by admin and

can purchase them.

7. Feedback

Input: After successfully log in to system the admin can view the feedback reports

Output: Feedback review

3.2.1 Use case diagramThis use case diagram graphically represents the user’s interaction with the system. It portrays the 2 different users of the system, customer and the DBA and the various ways that they interact with the system.

Figure No-3.2: USE Case Diagram


3.2.2 Entity Relationship Diagram

Figure No-3.3: ER Diagram


3.2 Explain Processing Logic: Using Programme Flow Charts, Algorithm, Decision Table/Tree or Pseudo codes.

3.3.1 Output Design: Screen & Print layouts, i.e., the format and contents (fields) to be included – along with the file to which it is linked.

3.3.2 Input (Form or Screen) Design: For keying-in data. Give fields, format, codes to be used, validation (error detection) requirements & the file to which it is linked.

3.4 Database & File Design: Depending on the tool/package used, give contents of each file including Field Name, Type, and Size & Description.

3.4.1Database used for Login:


User_id Varchar2 20 user id of the user

Password Varchar2 20 Password required to access the system

3.4.2Database used for Customer:


First Name Varchar2 10 Customer’s first name



Gender Varchar2 5 Customer’s gender

Address Varchar2 50 Address of the customer

City Varchar2 20 City where the customer resides

State Varchar2 20 State where the customer resides

Pin_code Varchar2 10 Code of the area where the customer

livesPh_num Varchar2 15 Contact number of the

customer


3.4.3Database used for Product:


Product_id Varchar2 10 Unique ID number of product

Category Varchar2 20 Category to which product belongs


Brand Varchar2 25 Brand name of product


Stock Varchar2 5 Quantity of product available


Discount Varchar2 5 Discount onto the price of product

3.4.4Database used for Cart:




Delivery Time Varchar2 5 Days taken to deliver the product


Quantity Varchar2 10 Number of products purchased

Subtotal Varchar2 6 Total amount pertaining to a product

typeGrand Total Varchar2 6 Total amount to be

paid for the products in the cart


3.4.5Database used for Bill & order:


Order_id Varchar2 20 Unique order number

Order_date Varchar2 10 Date on which the order was placed

Invoice_no Varchar2 20 Bill number

Invoice_date Varchar2 10 Date on which the product is shipped for

deliveryFirst Name Varchar2 10 Customer’s first name


Billing_add Varchar2 50 Address of the customer

Shipping_add Varchar2 50 Address at which the product is to be

deliveredProduct_details Varchar2 100 Product details which

has been purchasedPrice Varchar2 6 Price to be paid on the

purchase of productQuantity Varchar2 10 Number of products

purchasedSubtotal Varchar2 6 Total amount

pertaining to a product type

Grand Total Varchar2 6 Total amount to be paid for the products

in the cart

3.4.6Database used for Customer Feedback:



Content Varchr2 100 Feedback/Query


3.5Activity Diagram

An activity diagram is a special kind of diagram that shows the flow from activity to activity within a system. Activity diagrams address the dynamic view of a system. They are especially important in modelling the function of a system and emphasize the flow of control among objects. An activity is an ongoing monatomic execution within a state machine. Activities ultimately result in some action that is made up of executable atomic computations that result in a change in state of the system or a return of a value.

3.5.1 Registration Activity Diagram

Fig3.12 Activity Diagram For Registration


3.6.2 Login Activity Diagram

Fig3.13 Activity Diagram

3.7 Sequence DiagramIt is a kind of an interaction diagram. An interaction diagram shows an interaction. Sequence diagrams describe interactions among classes in terms of an exchange of messages over time i.e. it emphasizes the time-ordering of messages.Sequence Diagram Components:

1) Class roles – Class roles describe the way an object will behave in context. The UML object symbol can be used to illustrate class roles, but not for listing object attributes.

2) Activation – Activation boxes represent the time an object needs to complete a task.

3) Messages – Messages are arrows that represent communication between objects. Half-arrow lines are used to represent asynchronous messages. Asynchronous messages are sent from an object that will not wait for a response from the receiver before continuing its tasks.

4) Lifelines – Lifelines are vertical dashed lines that indicate the object's presence over time.

5) Destroying Objects – Objects can be terminated early using an arrow labelled "<< destroy >>" that points to an X.

6) Loops– A repetition or loop within a sequence diagram is depicted as a rectangle. Place the condition for exiting the loop at the bottom left corner in square brackets [].


3.7.1 Sequence Diagram for LOGIN

Fig3.14 Sequence Diagram For Login

3.7.2 Sequence Diagram for REGISTERATION

Fig3.15 Sequence Diagram For Registeration


Chapter 4 Systems Development


HOMEPAGE:

CODE : HOME PAGE

<%@ Page Title="" Language="VB" MasterPageFile="~/eMartMain.master" AutoEventWireup="false" CodeFile="Home.aspx.vb" Inherits="Home" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"><asp:Label ID="Label3" runat="server" Text="Label" Visible="False"></asp:Label><asp:LinkButton ID="LinkButton1" runat="server" Font-Bold="True" ForeColor="Maroon"OnClick="LinkButton1_Click">GET PRINT OF PRODUCTS</asp:LinkButton> <br /><div style="height:469px;overflow-y:scroll"><asp:DataList ID="DataList1" runat="server" BackColor="White" BorderColor="Maroon"BorderStyle="None" BorderWidth="2px" CellPadding="0" CellSpacing="2" GridLines="Both"RepeatColumns="3" RepeatDirection="Horizontal" OnSelectedIndexChanged="Page_Load" style="padding-left: 20px" DataKeyField="Pr_ID" Font-Bold="True" Font-Size="Small" DataSourceID="DataListSqlDataSource"><FooterStyleBackColor="#F7DFB5" ForeColor="#8C4510" /><EditItemStyleBackColor="White" BorderColor="Maroon" BorderWidth="2px" Font-Bold="True" Font-Names="Arial Black" />


<SelectedItemStyleBackColor="#738A9C" Font-Bold="True" ForeColor="White" /><ItemTemplate> <table><tr><td rowspan="11" style="width: 100px"> <asp:Image ID="Image1" runat="server" Height="192px" Width="133px" ImageUrl='<%# Eval("Pr_Image") %>' BorderColor="Maroon" BorderStyle="Solid" BorderWidth="1px" /></td><td colspan="2" valign="bottom"><asp:Label ID="Label5" runat="server" Text="Item Code"></asp:Label></td></tr><tr><td colspan="2" valign="bottom"></td></tr><tr><td colspan="2" valign="bottom"><asp:Label ID="Label2" runat="server" Text='<%# Eval("Pr_Id") %>'></asp:Label></td></tr><tr><td colspan="2" valign="bottom"></td></tr><tr><td colspan="2" valign="bottom"><asp:Label ID="Label6" runat="server" Text="Price"></asp:Label></td></tr><tr><td colspan="2" valign="bottom"></td></tr><tr><td colspan="2" valign="bottom"><asp:Label ID="Label1" runat="server" Text='<%# Eval("Pr_Price") %>'></asp:Label></td></tr><tr><td colspan="2" style="padding-top: 0px" valign="top"></td></tr>


<tr><td colspan="2" style="padding-top: 0px" valign="top"><asp:Label ID="Label7" runat="server" Text="Name"></asp:Label></td></tr><tr><td colspan="2"></td></tr><tr><td colspan="2"> <asp:Label ID="Label4" runat="server" Text='<%# Eval("Pr_Name") %>'></asp:Label></td></tr><tr><td style="width: 100px; text-align: center;"><asp:ImageButton ID="ImageButton1" runat="server" ImageUrl="~/Images/buy.gif" PostBackUrl='<%# Eval("Pr_Id", "ShoppingCart.aspx?{0}") %>' /></td><td colspan="2"></td></tr><tr><td style="width: 100px; text-align: center;"><asp:ImageButton ID="ImageButton2" runat="server" ImageUrl="~/Images/DETAIL.gif" PostBackUrl='<%# Eval("Pr_Id", "Detail.aspx?{0}") %>' DescriptionUrl="~/Detail.aspx" /></td><td colspan="2"></td></tr></table></ItemTemplate><ItemStyleBackColor="White" ForeColor="Maroon" /><HeaderStyleBackColor="#A55129" Font-Bold="True" ForeColor="White" /><SeparatorStyleBorderColor="Maroon" BorderStyle="Solid" BorderWidth="5px" /></asp:DataList><asp:SqlDataSource ID="DataListSqlDataSource" runat="server" ConnectionString="<%$ ConnectionStrings:constr%>"


SelectCommand="SELECT Pr_Id, Pr_Name, Pr_Price, Pr_Description, Pr_Image FROM Products WHERE (Pr_Id IN (SELECT Pr_Id FROM [Products-Categories] WHERE (Cat_Id = @Cat_Id)))"><SelectParameters><asp:ControlParameterControlID="Label3" DefaultValue="557" Name="Cat_Id" PropertyName="Text" /></SelectParameters></asp:SqlDataSource></div><br /> <br /></asp:Content>

USER LOGIN :

CODE: LOGIN

<%@ Page Title="" Language="VB" MasterPageFile="~/eMartMain.master" AutoEventWireup="false" CodeFile="LogIn.aspx.vb" Inherits="LogIn" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"><table align="center"><tr><td colspan="2">


<asp:Label ID="Label1" runat="server" Font-Bold="True" ForeColor="DarkRed" Text="Sign In" Width="74px"></asp:Label><asp:Label ID="lblMsg" runat="server" Font-Bold="True" ForeColor="Maroon" Visible="False"></asp:Label></td></tr><tr><td colspan="2" style="height: 39px" width="300"><asp:Image ID="Image5" runat="server" ImageUrl="~/Images/Signin1.gif" /></td></tr><tr><td style="padding-left: 4px; width: 30px; padding-top: 10px; height: 28px" valign="top"><asp:Image ID="Image6" runat="server" ImageUrl="~/Images/uid.gif" /></td><td style="width: 94px; padding-top: 10px; height: 28px" valign="top"><asp:TextBox ID="txtUser" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" Height="27px" Font-Bold="True" Font-Size="Medium" ForeColor="Maroon" Width="152px"></asp:TextBox></td></tr><tr><td style="width: 30px; padding-top: 10px" valign="middle"><asp:Image ID="Image7" runat="server" ImageUrl="~/Images/pss.gif" /></td><td style="width: 94px; padding-top: 10px"><asp:TextBox ID="txtPassword" runat="server" BorderColor="Maroon" BorderStyle="Solid" Height="27px" Font-Bold="True" Font-Size="Medium" ForeColor="Maroon" TextMode="Password" Width="152px"></asp:TextBox></td></tr><tr><td style="width: 30px"><asp:CheckBox ID="CheckBox1" runat="server" Width="10px" /><asp:Label ID="Label2" runat="server" Font-Bold="True" Font-Size="Medium" ForeColor="Maroon" Text="Admin"></asp:Label></td><td style="width: 94px; padding-top: 15px"><asp:ImageButton ID="ImageButton1" runat="server" ImageUrl="~/Images/Signbtn.gif" OnClick="ImageButton1_Click" OnClientClick="return validate()" CausesValidation="False" /></td></tr><tr><td colspan="2" style="padding-bottom: 15px; padding-top: 10px" valign="top"><asp:Image ID="Image9" runat="server" ImageUrl="~/Images/msg1.gif" />


<asp:LinkButton ID="LinkButton7" runat="server" Font-Bold="True" OnClick="LinkButton7_Click">Click Here</asp:LinkButton></td></tr><tr><td colspan="2"><asp:Image ID="Image10" runat="server" ImageUrl="~/Images/sign2.gif" /></td></tr><tr><td colspan="2" style="padding-bottom: 15px; padding-top: 15px"><asp:Image ID="Image11" runat="server" ImageUrl="~/Images/msg2.gif" /></td></tr><tr><td colspan="1"></td><td colspan="2"><asp:ImageButton ID="ImageButton2" runat="server" ImageUrl="~/Images/signup.gif" PostBackUrl="~/UserRegistration.aspx" /></td></tr></table>

</asp:Content>


USER AFTER LOGIN :

CODE: AFTER LOGINPage Title="" Language="VB" MasterPageFile="~/AdminMaster.master" AutoEventWireup="false" CodeFile="LoginDetail.aspx.vb" Inherits="LoginDetail" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"><strong><span style="font-size: 14pt; color: #990033; text-decoration: underline">DETAILS OF LOGINS BY NORMAL USER AND ADMIN LATEST FIRST</span></strong><br /><asp:GridView ID="GridView1" runat="server" AllowPaging="True" AutoGenerateColumns="False"BackColor="#DEBA84" BorderColor="#DEBA84" BorderStyle="None" BorderWidth="1px"CellPadding="3" CellSpacing="2" DataSourceID="SqlDataSource1" OnPageIndexChanging="GridView1_PageIndexChanging"><FooterStyleBackColor="#F7DFB5" ForeColor="#8C4510" /><Columns><asp:BoundFieldDataField="U_Id" HeaderText="U_Id" SortExpression="U_Id" /><asp:BoundFieldDataField="Login_Date" HeaderText="Login_Date" SortExpression="Login_Date" /></Columns><RowStyleBackColor="#FFF7E7" ForeColor="#8C4510" /><SelectedRowStyleBackColor="#738A9C" Font-Bold="True" ForeColor="White" /><PagerStyleForeColor="#8C4510" HorizontalAlign="Center" /><HeaderStyleBackColor="#A55129" Font-Bold="True" ForeColor="White" /></asp:GridView><br />


<asp:SqlDataSource ID="SqlDataSource1" runat="server" ConnectionString="<%$ ConnectionStrings:constr%>"SelectCommand="SELECT * FROM [LoginOccurance] ORDER BY [Login_Date] DESC"></asp:SqlDataSource></asp:Content>

USER REGISTRATION FORM :

CODE: REGISTRATION FORM<%@ Page Title="" Language="VB" MasterPageFile="~/eMartMain.master" AutoEventWireup="false" CodeFile="UserRegistration.aspx.vb" Inherits="UserRegistration" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"><table width="200" align="center"><tr><td colspan="4" style="padding-left: 50px; text-align: left;"><asp:Image ID="Image1" runat="server" ImageUrl="~/Images/UserRegistration.gif" /></td></tr><tr><td width="200"></td><td colspan="2" style="padding-top: 5px"><asp:Label ID="Label11" runat="server" Font-Bold="True" ForeColor="Maroon" Visible="False"></asp:Label></td><td width="229"></td>


</tr><tr><td width="200"></td><td width="150" style="padding-top: 5px"><asp:Label ID="Label1" runat="server" Text="User Name" Width="77px" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="width: 150px; padding-top: 5px"><asp:TextBox ID="txtUserName" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" ForeColor="Maroon"></asp:TextBox></td><td width="229"></td></tr><tr><td style="height: 21px" width="200"></td><td style="height: 21px; padding-top: 5px;" width="150"><asp:Label ID="Label2" runat="server" Text="Password" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="height: 21px; width: 150px; padding-top: 5px;"><asp:TextBox ID="txtPassword" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" ForeColor="Maroon" TextMode="Password"></asp:TextBox></td><td style="height: 21px" width="229"></td></tr><tr><td width="200"></td><td width="150" style="padding-top: 5px"><asp:Label ID="Label3" runat="server" Text="Re-Type Password" Width="122px" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="width: 150px; padding-top: 5px"><asp:TextBox ID="txtRePassword" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" ForeColor="Maroon" TextMode="Password"></asp:TextBox></td><td width="229"></td></tr>kl<tr><td style="height: 21px" width="200"></td>


<td style="height: 21px; padding-top: 5px;" width="150"><asp:Label ID="Label4" runat="server" Text="Name" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="height: 21px; width: 150px; padding-top: 5px;"><asp:TextBox ID="txtName" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" ForeColor="Maroon"></asp:TextBox></td><td style="height: 21px" width="229"></td></tr><tr><td style="height: 21px" width="200"></td><td style="height: 21px; padding-top: 5px;" width="150"><asp:Label ID="Label5" runat="server" Text="Phone" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="height: 21px; width: 150px; padding-top: 5px;"><asp:TextBox ID="txtPhone" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" ForeColor="Maroon"></asp:TextBox></td><td style="height: 21px" width="229"><asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server" ControlToValidate="txtPhone" ErrorMessage="RegularExpressionValidator" ValidationExpression="\d{10}">Invalid Mobile Number</asp:RegularExpressionValidator></td></tr><tr><td width="200" style="height: 30px"></td><td width="150" style="padding-top: 5px; height: 30px;"><asp:Label ID="Label6" runat="server" Text="Email" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="width: 150px; padding-top: 5px; height: 30px;"><asp:TextBox ID="txtEmail" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" ForeColor="Maroon"></asp:TextBox></td><td width="229" style="height: 30px"><asp:RegularExpressionValidator ID="RegularExpressionValidator2" runat="server" ControlToValidate="txtEmail" ErrorMessage="RegularExpressionValidator" ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*">Invalid EMail ID</asp:RegularExpressionValidator></td></tr>


<tr><td width="200"> </td><td width="150" style="padding-top: 5px" valign="top"><asp:Label ID="Label7" runat="server" Text="Address" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="width: 150px; padding-top: 5px"><asp:TextBox ID="txtAddress" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" ForeColor="Maroon" Height="105px" TextMode="MultiLine"></asp:TextBox></td><td width="229"></td></tr><tr><td style="height: 7px" width="200"></td><td style="height: 7px; padding-top: 5px;" width="150"><asp:Label ID="Label8" runat="server" Text="Country" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="height: 7px; width: 150px; padding-top: 5px;"><asp:TextBox ID="txtCountry" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" ForeColor="Maroon"></asp:TextBox></td><td style="height: 7px" width="229"></td></tr><tr><td style="height: 21px" width="200"></td><td style="height: 21px; padding-top: 5px;" width="150"><asp:Label ID="Label9" runat="server" Text="Security Question" Width="113px" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="height: 21px; width: 150px; padding-top: 5px;"><asp:DropDownList ID="SecurityQuestionList" runat="server" Font-Bold="False" ForeColor="Maroon" Width="153px"><asp:ListItem Selected="True">What Is Your Pet Name?</asp:ListItem><asp:ListItem>What Is School Name?</asp:ListItem><asp:ListItem>I Love?</asp:ListItem><asp:ListItem>I Hate?</asp:ListItem>


</asp:DropDownList></td><td style="height: 21px" width="229"></td></tr><tr><td style="height: 21px" width="200"></td><td style="height: 21px; padding-top: 5px;" width="150"><asp:Label ID="Label10" runat="server" Text="Answer" Font-Bold="False" ForeColor="Maroon"></asp:Label></td><td style="height: 21px; width: 150px; padding-top: 5px;"><asp:TextBox ID="txtAnswer" runat="server" BorderColor="Maroon" BorderStyle="Solid"BorderWidth="2px" ForeColor="Maroon"></asp:TextBox></td><td style="height: 21px" width="229"></td></tr><tr><td style="height: 21px" width="200"></td><td style="height: 21px" width="150"></td><td style="height: 21px; width: 150px;"></td><td style="height: 21px" width="229"></td></tr><tr><td width="200" style="height: 21px"></td><td width="150" align="right" style="height: 21px"><asp:ImageButton ID="btnSubmit" runat="server" ImageUrl="~/Images/submit.gif" OnClick="btnSubmit_Click" OnClientClick="return validate()" /></td><td align="right" style="width: 150px; height: 21px"><asp:ImageButton ID="btnReset" runat="server" ImageUrl="~/Images/reset.gif" OnClick="btnReset_Click" /></td><td width="229" style="height: 21px"></td></tr><tr><td width="200">


</td><td width="150"></td><td style="width: 150px"></td><td width="229"></td></tr><tr><td width="200"></td><td width="150"></td><td style="width: 150px"></td><td width="229"></td></tr></table></asp:Content>

COMPLAINT :

CODE: COMPLAINTPage Title="" Language="VB" MasterPageFile="~/eMartMain.master" AutoEventWireup="false" CodeFile="Complain.aspx.vb" Inherits="Complain" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server"><table style="width: 698px"><tr>


</tr></table></asp:Content>

FEEDBACK:

CODE: FEEDBACK

Page Title="" Language="VB" MasterPageFile="~/eMartMain.master"

AutoEventWireup="false" CodeFile="feedback.aspx.vb" Inherits="feedback" %>

<asp:Content ID="Content1" ContentPlaceHolderID="ContentPlaceHolder1" Runat="Server">

<table style="width: 100%">

<tr>

<td style="width: 17px">

</td>

<td colspan="2">

<asp:Label ID="Label4" runat="server" Font-Bold="True" Font-Size="XX-Large"

ForeColor="#CC3300" Text="Feedback"></asp:Label>

</td>


</tr>

<tr>


</td>


<asp:Label ID="Label9" runat="server" Font-Bold="True" Text="Date"></asp:Label>

</td>

<td align="left">

<asp:Label ID="Label10" runat="server" Font-Bold="True"></asp:Label>

</td>

</tr>

<tr>


</td>


<asp:Label ID="Label1" runat="server" Font-Bold="True" Text="Name"></asp:Label>

</td>

<td align="left">

<asp:TextBox ID="TextBox1" runat="server" Width="260px"></asp:TextBox>

<asp:RequiredFieldValidator ID="RequiredFieldValidator1" runat="server"

ControlToValidate="TextBox1" ErrorMessage="RequiredFieldValidator"

Font-Bold="True" ForeColor="Red">Name Can't

be blank</asp:RequiredFieldValidator>

</td>

</tr>

<tr>

<td style="width: 17px; height: 17px">

</td>

<td style="width: 87px; height: 17px">

<asp:Label ID="Label2" runat="server" Font-Bold="True" Text="Email Address"></asp:Label>


</td>

<td style="height: 17px" align="left">




Font-Bold="True" ForeColor="Red">EMail Can't

be Blank</asp:RequiredFieldValidator>

<asp:RegularExpressionValidator ID="RegularExpressionValidator1" runat="server"

ControlToValidate="TextBox2" ErrorMessage="RegularExpressionValidator"

Font-Bold="True" ForeColor="Red"

ValidationExpression="\w+([-+.']\w+)*@\w+([-.]\w+)*\.\w+([-.]\w+)*">Invalid

EMail ID</asp:RegularExpressionValidator>

</td>

</tr>

<tr>


</td>


<asp:Label ID="Label5" runat="server" Font-Bold="True" Text="Phone /

Mobile"></asp:Label>

</td>

<td align="left">




Font-Bold="True" ForeColor="Red">Phone

Required</asp:RequiredFieldValidator>

</td>

</tr>


<tr>


</td>


<asp:Label ID="Label6" runat="server" Font-Bold="True" Text="State"></asp:Label>

</td>

<td align="left">




Font-Bold="True" ForeColor="Red">State Required</asp:RequiredFieldValidator>

</td>

</tr>

<tr>


</td>


<asp:Label ID="Label7" runat="server" Font-Bold="True" Text="Country"></asp:Label>

</td>

<td align="left">




Font-Bold="True" ForeColor="Red">Country


</td>

</tr>

<tr>



</td>


<asp:Label ID="Label3" runat="server" Font-Bold="True" Text="Your

Feedback"></asp:Label>

</td>

<td align="left">

<asp:TextBox ID="TextBox3" runat="server" Height="235px" TextMode="MultiLine"

Width="358px"></asp:TextBox>



Font-Bold="True" ForeColor="Red">Feedback


</td>

</tr>

<tr>


</td>


</td>

<td>

<asp:TextBox ID="txtmail" runat="server" TextMode="MultiLine"

Visible="False"></asp:TextBox>

<asp:Label ID="Label8" runat="server" Font-Bold="True"

Font-Size="XX-Large"></asp:Label>

</td>

</tr>

<tr>


</td>


</td>


<td>

<asp:Button ID="Button1" runat="server" Text="Submit" Width="71px"

onclick="Button1_Click1" />

<asp:Button ID="Button2" runat="server" Text="Clear" onclick="Button2_Click" />

</td>

</tr>

</table>

</asp:Content>

4.2 TESTING AND DEBUGGING

USER LOGIN :

VALIDATION :- Username and Password can`t remain empty.


REGISTRATION FORM :

VALIDATION:- 1.Mobile Number should not exceed than 10 numbers. 2. Email id should be written in @gmail.com, @yahoo.com, @rediffmail.com.

Complaint :

VALIDTION:- You should write your complaint in your complaint box.


CHAPTER 5

SCOPE OF IMPROVEMENT, SUMMARY, AND CONCLUSION


5.1 LimitationsThe project entitled “ONLINE JEWELLERY SHOPPING SYSTEM” provides various

functionalities which are LOGIN that lets the customer access the purchase functionality of the

products and edit his/her personal details, etc. and the admin can do the maintenance part.

However there are some limitations to the system:

Number of modules are limited

Security checks are limited

5.2 Summary

The Online Jewellery Shopping System provides the user with the provision to shop the desired

products from variety of products at anytime and anywhere across the country saving on to their efforts,

time and money. But for that the customers must get registered with the website. This system is three

tier architecture.

The customer sends requests, on receiving the request the server processes it and extracts the data from

database and sends the result back to the customer. This system provides separate interface and login

module for customer and admin.

Customers can search for the products, give feedback. They can also buy the products and edit their

personal details and view the order history by logging into the system.

The admin can carry out the product maintenance of the product database by adding, deleting and

modifying the details, can view the customer details that the customer provides and view the customer

feedback.


5.3 Conclusion The package was designed in such a way that future modifications can be done easily. The

following conclusions can be deduced from the development of the project.

Online Jewellery Shopping System provides with the capability to shop for one’s desired products

from anywhere in the world in no time thus reducing time, cost and effort factors.

It provides a friendly graphical user interface which proves to be more beneficial and productive as

compared to the traditional shopping system.

It gives appropriate access to the authorized users depending on their permissions.

Updating of information becomes so easier.

System security, data security and reliability are the striking features.

The System has adequate scope for modification in future if it is necessary.


REFRENCES

www.snapdeal.com

www.flipkart.com

www.wikipedia.com

www.google.com

online jewellery shopping final.docx

Documents

project control list

product belongs type

bill number date

customer resides state

delivered product details

simple shopping cart

performance search system

online software system