Professional Documents
Culture Documents
CHAPTER-1
INTRODUCTION
02921102010
02921102010
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.
02921102010
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.
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
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
02921102010
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.
02921102010
1024*786 pixels(minimum)
System requirement
Processor
RAM
512 MB or higher
Back End
Web Server
IIS
Operating System
Microsoft Windows 7
02921102010
02921102010
02921102010
CHAPTER 2
Software Requirement
Specifications
02921102010
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.
02921102010
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.
Backend: The one from which the system picks up the data i.e. the database.
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
02921102010
Backend
Database
2.9System Interfaces
None
2.10Interfaces
The application will have a user friendly and menu based interface. Following screens will be
provided.
02921102010
a) A Login Screen for entering username & password. Access to different screens will be
based upon the role of the user.
02921102010
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.
02921102010
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.
02921102010
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.14Product functions
The system will allow access to users including the DBA and customers from anywhere in the
world. Depending upon the users role, he/she will be able to access only specific modules of the
system.
2.15User Characteristics
02921102010
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
02921102010
2.25.2Validity ChecksLogin
(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.
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
None
2.27Logical Database Requirements
The proposed information system contains the following data tables in its database collection.
2.27.1 Database used forLogin:
Field name
Field type
Field size
Description
User_id
Varchar2
20
Password
Varchar2
20
Password required
to access the system
02921102010
Field name
Field type
Field size
First Name
Varchar2
10
Description
Customers
first
name
Last Name
Varchar2
10
Email_id
Varchar2
20
Address
Varchar2
50
City
Varchar2
20
State
Varchar2
20
Pin_code
Varchar2
10
Ph_num
Varchar2
15
Customers second
name
Email address of the
user
Address of the
customer
City where the
customer resides
State where the
customer resides
Code of the area
where the customer
lives
Contact number of
the customer
Field type
Field size
Description
Product_id
Varchar2
10
Category
Varchar2
20
Pr_Type
Varchar2
20
Unique ID number of
product
Category to which
product belongs
Type of the product
Brand
Varchar2
25
Description
Varchar2
100
Stock
Varchar2
Price
Varchar2
Discount
Varchar2
Brand name of
product
Name and features of
product
Quantity of product
available
Price to be paid on the
purchase of product
Discount onto the
price of product
02921102010
Field type
Field size
Description
Pr_Type
Varchar2
20
Description
Varchar2
100
Delivery Time
Varchar2
Price
Varchar2
Quantity
Varchar2
10
Subtotal
Varchar2
Grand Total
Varchar2
02921102010
Field type
Field size
Description
Order_id
Varchar2
20
Order_date
Varchar2
10
Invoice_no
Varchar2
20
Invoice_date
Varchar2
10
First Name
Varchar2
10
Last Name
Varchar2
10
Billing_add
Varchar2
50
Shipping_add
Varchar2
50
Product_details
Varchar2
100
Price
Varchar2
Quantity
Varchar2
10
Tax
Varchar2
Subtotal
Varchar2
Grand Total
Varchar2
Field type
Field size
Description
Email_id
Varchar2
20
2.28Design Constraints
Standard Compliance
None
02921102010
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.
Chapter-3
Systems Design
02921102010
02921102010
02921102010
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.
02921102010
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
02921102010
02921102010
3.2 Explain Processing Logic: Using Programme Flow Charts, Algorithm, Decision Table/Tree
or Pseudo codes.
3.3.1
3.3.2
Output Design: Screen & Print layouts, i.e., the format and contents (fields) to be included
along with the file to which it is linked.
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.
Field type
Field size
Description
User_id
Varchar2
20
Password
Varchar2
20
Password required to
access the system
Field type
Field size
Description
First Name
Varchar2
10
Last Name
Varchar2
10
Email_id
Varchar2
20
Gender
Varchar2
Customers second
name
Email address of the
user
Customers gender
Address
Varchar2
50
City
Varchar2
20
State
Varchar2
20
Pin_code
Varchar2
10
Ph_num
Varchar2
15
Address of the
customer
City where the
customer resides
State where the
customer resides
Code of the area
where the customer
lives
Contact number of the
customer
02921102010
Field type
Field size
Description
Product_id
Varchar2
10
Category
Varchar2
20
Pr_Type
Varchar2
20
Unique ID number of
product
Category to which
product belongs
Type of the product
Brand
Varchar2
25
Description
Varchar2
100
Stock
Varchar2
Price
Varchar2
Discount
Varchar2
Brand name of
product
Name and features of
product
Quantity of product
available
Price to be paid on the
purchase of product
Discount onto the
price of product
Field type
Field size
Description
Pr_Type
Varchar2
20
Description
Varchar2
100
Delivery Time
Varchar2
Price
Varchar2
Quantity
Varchar2
10
Subtotal
Varchar2
Grand Total
Varchar2
02921102010
Field type
Field size
Description
Order_id
Varchar2
20
Order_date
Varchar2
10
Invoice_no
Varchar2
20
Invoice_date
Varchar2
10
First Name
Varchar2
10
Last Name
Varchar2
10
Billing_add
Varchar2
50
Shipping_add
Varchar2
50
Product_details
Varchar2
100
Price
Varchar2
Quantity
Varchar2
10
Subtotal
Varchar2
Grand Total
Varchar2
Field type
Field size
Description
Email_id
Varchar2
20
Content
Varchr2
100
02921102010
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.
02921102010
02921102010
02921102010
Chapter 4
Systems Development
02921102010
HOMEPAGE:
02921102010
02921102010
<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%>"
02921102010
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">
02921102010
02921102010
<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>
02921102010
02921102010
<asp:SqlDataSource
ID="SqlDataSource1"
runat="server"
ConnectionString="<%$
ConnectionStrings:constr%>"
SelectCommand="SELECT * FROM [LoginOccurance] ORDER BY [Login_Date]
DESC"></asp:SqlDataSource>
</asp:Content>
02921102010
</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" FontBold="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>
02921102010
02921102010
<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" FontBold="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>
02921102010
</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">
02921102010
</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: COMPLAINT
Page
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>
02921102010
02921102010
</tr>
</table>
</asp:Content>
FEEDBACK:
CODE: FEEDBACK
Page
Title=""
Language="VB"
MasterPageFile="~/eMartMain.master"
02921102010
</tr>
<tr>
<td style="width: 17px">
</td>
<td style="width: 87px">
<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 style="width: 17px">
</td>
<td style="width: 87px">
<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>
02921102010
</td>
<td style="height: 17px" align="left">
<asp:TextBox ID="TextBox2" runat="server" Width="260px"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator2" runat="server"
ControlToValidate="TextBox2" ErrorMessage="RequiredFieldValidator"
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 style="width: 17px">
</td>
<td style="width: 87px">
<asp:Label
ID="Label5"
runat="server"
Font-Bold="True"
Text="Phone
Mobile"></asp:Label>
</td>
<td align="left">
<asp:TextBox ID="TextBox4" runat="server" Width="259px"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator4" runat="server"
ControlToValidate="TextBox4" ErrorMessage="RequiredFieldValidator"
Font-Bold="True"
Required</asp:RequiredFieldValidator>
</td>
</tr>
ForeColor="Red">Phone
02921102010
<tr>
<td style="width: 17px">
</td>
<td style="width: 87px">
<asp:Label ID="Label6" runat="server" Font-Bold="True" Text="State"></asp:Label>
</td>
<td align="left">
<asp:TextBox ID="TextBox5" runat="server" Width="258px"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator5" runat="server"
ControlToValidate="TextBox5" ErrorMessage="RequiredFieldValidator"
Font-Bold="True" ForeColor="Red">State Required</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td style="width: 17px">
</td>
<td style="width: 87px">
<asp:Label ID="Label7" runat="server" Font-Bold="True" Text="Country"></asp:Label>
</td>
<td align="left">
<asp:TextBox ID="TextBox6" runat="server" Width="258px"></asp:TextBox>
<asp:RequiredFieldValidator ID="RequiredFieldValidator6" runat="server"
ControlToValidate="TextBox6" ErrorMessage="RequiredFieldValidator"
Font-Bold="True"
Required</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td style="width: 17px">
ForeColor="Red">Country
02921102010
</td>
<td style="width: 87px">
<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>
<asp:RequiredFieldValidator ID="RequiredFieldValidator3" runat="server"
ControlToValidate="TextBox3" ErrorMessage="RequiredFieldValidator"
Font-Bold="True" ForeColor="Red">Feedback
Required</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td style="width: 17px">
</td>
<td style="width: 87px">
</td>
<td>
<asp:TextBox
ID="txtmail"
runat="server"
TextMode="MultiLine"
Visible="False"></asp:TextBox>
<asp:Label
ID="Label8"
Large"></asp:Label>
</td>
</tr>
<tr>
<td style="width: 17px">
</td>
<td style="width: 87px">
</td>
runat="server"
Font-Bold="True"
Font-Size="XX-
02921102010
<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>
REGISTRATION FORM :
Complaint :
02921102010
02921102010
CHAPTER 5
SCOPE OF IMPROVEMENT,
SUMMARY, AND CONCLUSION
02921102010
5.1 Limitations
The 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:
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.
02921102010
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 ones 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
02921102010