Professional Documents
Culture Documents
CHAPTER-1
INTRODUCTION
SPARKLING STONES ONLINE SHOPPING SYSTEM 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.
SPARKLING STONES ONLINE SHOPPING SYSTEM 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.
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
SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010
CHAPTER 2
Software Requirement
Specifications
SPARKLING STONES ONLINE SHOPPING SYSTEM 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.
SPARKLING STONES ONLINE SHOPPING SYSTEM 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.
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
SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010
2.9System Interfaces
None
2.10Interfaces
The application will have a user friendly and menu based interface. Following screens will be
provided.
SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010
a) A Login Screen for entering username & password. Access to different screens will be
based upon the role of the user.
SPARKLING STONES ONLINE SHOPPING SYSTEM 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.
SPARKLING STONES ONLINE SHOPPING SYSTEM 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.
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 user’s role, he/she will be able to access only specific modules of the
system.
2.15User Characteristics
SPARKLING STONES ONLINE SHOPPING SYSTEM 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
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.
2.28Design Constraints
Standard Compliance
None
SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010
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
SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010
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.
SPARKLING STONES ONLINE SHOPPING SYSTEM 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
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.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.
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 [].
SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010
Chapter 4
Systems Development
SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010
HOMEPAGE:
<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%>"
SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010
USER LOGIN :
CODE: LOGIN
</asp:Content>
SPARKLING STONES ONLINE SHOPPING SYSTEM 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" 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>
SPARKLING STONES ONLINE SHOPPING SYSTEM 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" 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>
SPARKLING STONES ONLINE SHOPPING SYSTEM 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">
SPARKLING STONES ONLINE SHOPPING SYSTEM 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" %>
</tr>
</table>
</asp:Content>
FEEDBACK:
CODE: FEEDBACK
</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>
SPARKLING STONES ONLINE SHOPPING SYSTEM 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" ForeColor="Red">Phone
Required</asp:RequiredFieldValidator>
</td>
</tr>
SPARKLING STONES ONLINE SHOPPING SYSTEM 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" ForeColor="Red">Country
Required</asp:RequiredFieldValidator>
</td>
</tr>
<tr>
<td style="width: 17px">
SPARKLING STONES ONLINE SHOPPING SYSTEM 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" runat="server" Font-Bold="True" Font-Size="XX-
Large"></asp:Label>
</td>
</tr>
<tr>
<td style="width: 17px">
</td>
<td style="width: 87px">
</td>
SPARKLING STONES ONLINE SHOPPING SYSTEM 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 :
VALIDATION:-
1.Mobile Number should not exceed than 10 numbers.
2. Email id should be written in @gmail.com, @yahoo.com, @rediffmail.com.
Complaint :
CHAPTER 5
SCOPE OF IMPROVEMENT,
SUMMARY, AND CONCLUSION
SPARKLING STONES ONLINE SHOPPING SYSTEM 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:
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.
SPARKLING STONES ONLINE SHOPPING SYSTEM 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 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.
SPARKLING STONES ONLINE SHOPPING SYSTEM 02921102010
REFRENCES
www.snapdeal.com
www.flipkart.com
www.wikipedia.com
www.google.com