Online Ceramics and Tiles

SOFTWARE REQUIREMENTS SPECIFICATION DOCUMENTS

Revision History

Date Description Author Comments

Version 1 First Revision

Document Approval
The following Software Requirements Specification has been accepted and approved by the following:

Signature Printed Name Title Date

Supervisor, CSIT-21306
Table of Contents
Chapter No: 1 Page No
Gathering and Analysis Information 1
1.1 Introduction 2

1.2 Basic purpose 2

1.3 Feasibility study 3

1.3.1 Technical Feasibility 3

1.3.2 Operational Feasibility 3
1.3.3 Economic Feasibility 4
1.3.4 Social Feasibility 4

1.4 Requirement Shell / Traceability Table 5

1.5 Use Case and Use Case Scenarios 8

1.5.1 Register Member 8

1.5.2 Login User 9
1.5.3 View Products 10
1.5.4 Shop Owner Add Product 11
1.5.5 Customer Buy Product 12
1.5.6 Customer track order 13

Chapter No: 2
Envisioning the solution 17
2.1 Scope of the Project 18

2.2 User Requirements 18

2.2.1 Functional Requirements 19

2.2.2 Non Functional Requirements 23
Chapter No: 3
Planning the solution 25
3.1 System Design 26

3.1.1 Overview 26
3.1.2 Data Flow Diagram 27
3.1.3 Entity Relationship Diagram 29
3.1.4 Relational Model
3.1.5 Objectives of Proposed System 32
 CHAPTER 1
Gathering & Analyzing Info
1.1 Introduction
The Online Ceramics and Tiles Store application enables vendors to set up online shops,
customers to browse through the shops, and a system administrator to approve and
reject requests for new shops and maintain lists of shop categories.

Also on the agenda is designing an online shopping site to manage the items in
the shop and also help customers purchase them online without having to visit the shop
physically.

Our Online Ceramics and Tiles Store will use the internet as the sole method for
selling goods to its consumers. The consumer will be in complete control of his/her
shopping experience by using the “unique storefront” concept. Shopping will be highly
personalized and the Shop will provide lower prices than most competitors. This is a
description of our product which will showcase a complete shopping experience in a
Shop package.

1.2 Why this web site is being developed?

This website is developed to (1) provide an online platform in which system

administrator can approve and reject request for new shops and maintain lists of shop
categories. (2) Vendors can set up online shops and (3) Customer can visit different
shops and add product to the cart, check out their order and also track their order as
well.
1.3 Feasibility Study

Feasibility is a determination of whether or not a project is worth doing. Feasibility

Study is performed for determining the feasibility of a project. The content and
recommendations of such a study will be used as a sound basis for deciding to proceed,
postpone, or cancel the project.

In the conduct of feasibility study, we will usually consider following inter-related type
of feasibility:

1.3.1 Technical Feasibility

We concern here with specifying Equipment and software that will satisfy the user
requirement.

It will run on any platform (machine).

It will run with minimum system requirements and with minimum system resources
acquired during run.
It will need a web server, to which it gets from the internet, at run time.

Expandability will be maintained in the new system. New modules can be added later
on the application, if required in the future.

1.3.2 Operational Feasibility

The system will be easy to use as user interface is GUI based.

The system is easy to use so no any special skills will be required to use the
system.
New user will find it easy to use.
So the project will be operationally feasible.

1.3.3 Economic Feasibility

The procedure is to determine the benefit and savings that are expected from the
project and compare them with the cost.
As internet is the cheapest way of communication, we can perform
communication using web.
The cost is just the cost of using the internet based on the channel allocation.
So the project will be economically feasible.

1.3.4 Social Feasibility

The project will be socially feasible as today’s user want quick services in
everywhere. With the help of web based shopping we can make business with
others instantaneously in just seconds, in a large geographical area. In
feasibility study phase we had undergone through various steps which are
describe as under:
 1. Identify the origin of the information at different level.
 2. Identify the expectation of user from computerized system.
 3. Analyze the drawback of existing system (manual) system.
1.4 Requirement Shell/traceability Table

Requirement Shell

Requirement #: 1 Requirement Type: Sign up Member Use Case # 1

Description: Register new Member either a customer or a shop owner on the site by
getting all basic and profile information such as Name, Email ID, Password,
Gender and Address etc.
Source: Member

Customer Yes Customer Dissatisfaction:

Satisfaction:
Dependencies: Integration with the DBMS and server to store appropriate data of
Member.
Supporting Materials: Complete profile information of the Member which is trying to register.

Requirement Shell

Requirement #: 2 Requirement Type: Login Admin Use Case # 2

Description: To assure only authorized person to manage products, shops and Human
Resource Management on the site.
Source: Admin

Customer Yes Customer Dissatisfaction:

Satisfaction:
Dependencies: Integration with the DBMS to provides appropriate data about user.

Supporting Materials: Complete profile information of the Member which is trying to login.

Requirement Shell

Requirement #: 3 Requirement Type: Manage Product Use Case # 3

Description: Only admin has privileges to add, delete and update products .shop owner
can send request to admin if She/he add product to his/her shop.
Source: Admin

Customer Yes Customer Dissatisfaction:

Satisfaction:
Dependencies: Information Storing System to store appropriate data of Member and
product. .
Supporting Materials: Product must be authenticated by the admin.

Requirement Shell

Requirement #: 4 Requirement Type: Manage Shops Use Case # 4

Description: Only admin has privileges to add, delete and update shops .shop owner
can send request to admin if She/he add product to his/her shop.
Source: Admin

Customer Yes Customer Dissatisfaction:

Satisfaction:
Dependencies: Information Storing System to store appropriate data of shop owner and
shops.
Supporting Materials: Shop must be authenticated by the admin.

Requirement Shell

Requirement #: 5 Requirement Type: Shop owner Use Case # 5

Description: Shop owner can see his profile manage shop product and see available
product to his shop.
Source: Shop owner

Customer Yes Customer Dissatisfaction:

Satisfaction:
 Dependencies: Information Storing System to store appropriate data of shop owner.

Supporting Materials: Member must be logged in as shop owner.

Requirement Shell

Requirement #: 6 Requirement Type: Customer Use Case # 6

Description: Customer can see product and compare product price with different shops
add product to shopping cart check out order and track the order as well.
Source: Customer

Customer Yes Customer Dissatisfaction:

Satisfaction:
Dependencies: Information Storing System to store appropriate data of customer.

Supporting Materials: Customer must be logged in before check out the order.

1.5 Use case Scenarios:

1.5.1 Use Case 1: Register Member
Actor User

Preconditions 1. Internet must be connected

2. User must want to sign up
3. Must have a unique user ID
4. User must not be Registered first
5. User must fill First Name, Last Name, Email, Password, Gender, Date of
Birth field of the sign up form

Post conditions 1. User must enter the given verification code in the text field to successfully
register your account

Main If the user enters right first name, last name, email, password, gender, and
Successful Address and user must enter the verification code presses OK button, Now User
scenario can see successful message if his attempts is successful.
1.5.2 Use Case 2: Login user
Actor Member

Preconditions 1. Internet must be connected

2. User must want to login
3. User must enter username and password to login.
4. User should be Registered either shop owner or customer.
5. User should fill the login form first.

Post conditions 1. A home page is opened

2. User can visits complete site now
1.5.3 Use Case 3: View Products
Actor User

Preconditions 6. Internet must be connected

7. User should user should open the site.
8. For viewing the products it is not necessary to login.
9. User must want to view the product.

Post conditions 3. A home page is opened

4. User can visits complete site now
1.5.4 Use Case 4: Shop Owner Add Product

Actor User

Preconditions 1. Internet must be connected

2. Shop owner must be logged in to the site
3. Shop owner can add product to his shop approved by the admin.

Post conditions 1. Added products must be verified by admin.

Main After that product will be include to the shop of shop owner.
Successful
scenario
1.5.5 Use Case 5: Customer Buy Product

Actor User

Preconditions 1. Internet must be connected

2. Visit the site
3. Select available products from different available shops and add to cart
with their quantity finally click check out button to confirm their order.
4. Member must be logged in to the site

Post conditions 1. Select payment method and provide shipping information and click ok.
2. Display successful message (if check out is completed successfully)
3. Customer can track the order to confirm that order is successful placed.

Main User must click on the “check out” button; the product is delivered to the shipping
Successful address.
scenario
15.7 Use Case 6: Customer can track their order
Actor User

Preconditions 1. Internet must be connected

2. It is not necessary that user must be logged in.
3. Must want to track their order.
4. Must click on the track order link
5. Must remember their order ID.

Post conditions 1. As the user click on the track order link a page is open in which user give
order ID, click OK to know its order processing status.

Main User sees order processing status message (if the given order ID is correct).
Successful
scenario
 CHAPTER 2
Envisioning the Solution
2.1 Scope of the Project

The Online Ceramics and Tiles Store (OCTS) web application is intended to provide
complete solutions for vendors as well as customer through a single get way using the
internet as the sole medium. It will enable vendors to setup online shops, customer to
browse through the shop and purchase them online without having to visit the shop
physically. The administration module will enable a system administrator to approve
and reject requests for new shops and maintain various lists of shop category.
ONS is aimed towards the vendors who want to reach out to the maximum cross-section of
customer and common people who can be potential customer. This project envisages bridging
the gap between the seller, the retailer and the customer. OCTS should be user-friendly, ‘quick
to learn’ and reliable software for the above purpose.

This documentation is meant to delineate the features of OCTS, so as to serve as a guide

to the developers on one hand and a software validation document for the prospective
client on the other.

2.2 User Requirements

1. Secure registration and profile management facilities for Customers.
2. Browsing through the e-Shop to see the items.

3. Creating a Shopping cart so that customer can shop ‘n’ no. of items and
checkout finally with the entire shopping carts.
4. Regular updates to registered customer of the OCTS about new arrivals.
5. Shop employee are responsible for internal affairs like processing orders, assure
home delivery, getting customer’s delivery-time feedback, updating order’s
status and answering client’s queries online.

6. Feedback mechanism, so that customer can give feedback for the product or
service which they have purchased. Also facility rating of individual products
by relevant customers. Also feedback can be given on the performance of
particular vendors and the entire Shop as well.

2.2.1 Functional Requirements

The actors involved in the system are:

 Shop Administrator
 Shop Owner
  System
 Shop Customer
 Employees

Shop Administrator

 The Shop Administrator is the super user and has complete control over
all the activities that can be performed.
 The application notifies the administrator of all shop creation requests,
and the administrator can then approve or reject them.
 The administrator also manages the list of available product categories.
 The administrator can also view and delete the list of available shops.

Shop Owner

 Any user can submit a shop creation request through the application.
 When the request is approved by the Shop Administrator, the requester
is notified, and from there on is given the role of Shop Owner.
 The Shop Owner is responsible for setting up the shop and maintaining
it.
 Also, the shop owner can add or remove items from his shop.
 The Shop Owner can also decide to close shop and remove it from the
Shop.

System

 Authenticate old user login information

 Save information for new user registration
 Update database according to user changes
 Update complete system according to database records
Shop Customer

 A Shop Customer can browse through the shops and choose products to
place in a virtual shopping cart.
 The shopping cart details can be viewed and items can be removed from
the cart.
 To proceed with the purchase, the customer is prompted to login.
 Also, the customer can modify personal profile information (such as
phone number and shipping address) stored by the application.
 The customer can also view the status of any previous orders, and cancel
any order that has not been shipped yet.

Employees

 Shop employee are responsible for internal affairs like processing orders,
assure home delivery, getting customer’s delivery-time feedback,
updating order’s status and answering client’s queries online.
 Employee can also view its one detail and profile.

Following is the detail of functional requirements:

FR01: Authenticate User to Navigate Site.

FR01-01 System shall ask a user ID

FR01-02 System should ask password

FR01-03 ONS will authenticate, if all the credit are valid

FR01-04 ONS will reject, if there is something wrong, intruder etc.

FR02: Register a User’s Full Name, Username, Password, Address, and Security
Code.
FR02-01 System shall get Full Name from User

FR02-02 System shall get user name from User

FR02-03 System shall get Password

FR02-04 System shall get address.

FR02-05 System shall get security code.

FR03: If there is any mistake in the registration it should provide complete help to
the user.
FR03-01 If name is not entered system shall show an error message and guide the user.

FR03-02 If username is not entered system shall show an error message and guide the user.

FR03-03 IF username is not Valid system shall show an error message and guide the user.

FR03-04 If Password is not entered system shall show an error message and guide the user.

If security code is not enter system shall show an error message and guide the
FR03-05
user.

FR04: It should provide the facility to shop owner to manage his shop.
Any shop owner that is logged in can add product that is approved by the admin
FR04-01
to his shop.

FR04-02 Any shop owner that is logged in can update or delete the product to his shop.

FR05: It should provide the option to manage shopping cart.

Provide the facility to the customer to buy `n` no. of items by using the shopping
FR05-01
cart.

FR05-02 Also provide the facility to add, edit and manage shopping cart.

After selecting the products customer then click on checkout link to placed its
FR05-03
order successfully.

FR06: It should provide the facility to employee to manage its control panel.

FR06-01 Any employee that is logged in can view its profile send messages to admin.

FR06-02 Any employee that is logged in can also view its overtime hours details.

FR07: It should have the option that customer can give its feedback.
FR07-01 Anyone who is visited the site can give its important and valuable comments.

FR07-02 After that She/he should display message that comment is send successfully.
2.2.2 Non Functional Requirements

NFR01: Performance

The Average load time of the starting page of the system must be less
NFR01-01 than 5 seconds.

Average processing time taken by the system to complete a

NFR01-02 transaction/request by a user should be less than 10 seconds.

System Mean Time to Failure should not be more than 30 seconds

NFR01-03 within 24 hours of use.

NFR01-04 Average system response time should not be greater than 5 seconds.

System must successfully run on a client machine with 256 MB RAM

NFR01-05 or above.

NFR01-06 Multiple Advisers may access the site for Organization’s consultancy.

System shall be able to handle multiple requests over the Internet of

NFR01-07 100 users at the maximum

NFR02: Security

System must provide access to authorized users only that enter

NFR02-01 through the login module.

System must not provide access to ANY user EXCEPT the designated
NFR02-02 user to update the database.

NFR02-03 Any user is not allowed to see any other users overall profile.

After the end of a user Session, no information must be saved

NFR02-04 anywhere on the client machine.

NFR02-05 All access to the system shall be logged

NFR02-06 A proper mechanism shall be adopted in order to avoid any hacker’s

attacks on the application.
NFR03: Availability

NFR03-01
This web based application shall be available 24 hours a day
NFR03-02
User may access it from any part of the world

NFR04: Documentation

NFR04-01 User Documentation must be done giving details of all the

functionalities.

NFR04-02 Online help should be available in case of any problem...

NFR05: Disaster Recovery

NFR05-01 This should be made sure that a proper recovery system exists in case of
any disaster.

NFR05-02 In case of client /server crash all information/data should be

recoverable within 30 minutes of the incidence.

NFR06: Usability

NFR06-01 The system should be easy to use for a novice user.

NFR06-02 Time to learn overall interface of the system should be minimal.

 CHAPTER 3
Planning the Solution
3.1 System Design
The conclusion made for the development if the new Online Ceramics and Tiles Store
Website system to work along with the present computerized system let us to analyze:

 How to develop the online system?

 How to control the functionality and data flow in our system?
 What should be the cost of the new system? Is it affordable or not?
 What type of computer software and hardware is required to find the
desired result?
 What tool should be used for the development of the new system?

3.1.1 Overview (of proposed system)

Overview
This project envisages bridging the gap between the seller, the retailer and the
customer. A very high flexibility is being maintained in the design process. This system
provides the following facilities:

 Access the web with-out user registration

 User can be register as customer or shop owner.
 Browsing through the e-Store to see the items that are there in each category of
products.
 Creating a Shopping cart so that customer can shop ‘n’ no. of items and checkout
Finally with the entire shopping carts.

 Regular updates to registered customer of the OCTS about new arrivals.

 Shop employee are responsible for internal affairs like processing orders, assure
home delivery, getting customer’s delivery-time feedback, updating order’s
status and answering client’s queries online.
 Feedback mechanism, so that customer can give feedback for the product or
service which they have purchased. Also facility rating of individual products
by relevant customers. Also feedback can be given on the performance of
particular vendors and the entire store as well.

The System administrators are responsible for the maintaining the system. For example,

 Can manage the products

 Can manage product category
 Can manage the shops
 Can manage the shop category
  Can manage the shop owner
 Can check the vendor
 Can mail to the vendor

3.1.2 Data Flow Diagram

After the processes have been identified and decomposed into lower level processes,
the next step is to develop the models that show flow of data between related processes.
The most common means for modeling these flows is to use data flow diagrams. A
graphical representation of the flow of use the transformation of the data through a set
processes. (Reference: Modern Database Management System by Jeffery A. Hoffer)

Context Level Diagram:

ADMIN Online Smart CUSTOMER

Computer
Store Mart

Level 1 Diagram:
 Merchant panel
Start Messag
Box
If (visitor)
Visit or view website View profile My Shop Edit produc
Shop owner
Check
user/pass Mess
Go to admin panel
Admin Bo
Select product

If Manage
user
DML DML DML
Available
(Products) (Categories) (Merchan
User employee

Yes Shipment
Order detail
detail
Go to user account
Add to cart

Ordered placed

Place order

Check out

Payment
processing
Yes
Sign in

no

Sign out

Sign up

3.1.3 Entity Relationship Diagram

The second major component of analysis is a detailed entity relationship diagram. A

graphical representation of the relationship between the instances of two or more
entities. The ERD enables a software engineer to fully specify the data objects that are
input and output from a system, the attributes that define the properties of these
objects, and their relationship. (Reference: Software Engineering by Roger S. Pressman)

There are three basic elements in an ER Diagram: entity, attribute, relationship. There

are more elements which are based on the main elements. They are weak entity,

multivalued attribute, derived attribute, weak relationship and recursive relationship.

Cardinality and ordinality are two other notations used in ER diagrams to further

define relationships.
3.1.4 Relational Model
From the ER Diagram we can conceive the following tables
t_admin_mst
This table stores the basic Registration Information about the user
t_custreg_mst
This table stores all the details about customer

t_backup_trn
This table stores all the details about backup
t_Orders_trn
This table stores all the details about Orders
t_Product_mst
This table stores details about products

t_price_mst
This table stores all the information about price
t_Category_mst
This table stores all the information about the category.

t_Cart_temp
This table stores all the information of available cart

t_Country
This table stores all the information about product country.

3.1.5 Objectives of Proposed System

The main objective of the proposed system is to provide a high accessibility of service
we will design the Online Ceramics and Tiles Store Website, so that potential customers
need not go to a physical shop to buy products or services. They just need to online to
complete their purchases.

 Provide facility to add product in shopping cart

 Provide facility to check out their order
 Provide facility to track their order
 Provide facility to open shop
 Provide facility to contact us
 Provide facility to feed back
 Provide facility to create and Edit complete profile
 The Online Ceramics and Tiles store Website system is more reliable than the
manual one due to speed and security.
 Efficiency
 Data Security
 Time factor
 Accuracy
 Flexibility
 User friendly
 Reliability
 Performance