SRS Document:

Hardware Interface :-

The system should have these hardware requirements:

 The processor should be at least Pentium 3 or above

 The processor speed should be greater than 400Mhz
 The video device should support graphics
 Ram should be or greater than 120 mb
Software Interfaces:-

The software requires the support of the following softwares for the database
and other requirements

 HTML
 JDK
 html editor for web interface
 MySql for database
 Server(windows 2000,apache or…)
Communication Interfaces :-

 Local internet and internet protocols.

 Supports all HTTPS, SMTPS and POP3 services

Use Cases:
Browse Catalog
1) Search for a Book
• Purpose: A user can search for a book of his choice by selecting category and
title. Then a select query is used to retrieve data from the database and display
the selected information.
• Actor: User
• Input: The user will select a category and enter title in a text box provided.
• Output: The system will display the books which matches the selected search
criteria. A dataset is created as a result of select query. Later the dataset is
binded to the data repeater to display the selected data.
2) Perform Advanced Search
• Purpose: If the user wants to perform an advanced search he can search for a
book of his choice by selecting category, title, and author and price range. Then
a select query is used to retrieve data from the database and display the
selected information.
• Actor: User
• Input: The user will select a category and enter title, author, and price range in
a text box provided.
• Output: The system will display the books which matches the selected search
criteria. A dataset is created as a result of select query. Later the dataset is
binded to the data repeater to display the selected data.

3) Give rating to a book

• Purpose: If the user wants to give rating according to his opinion for a book he
can select either Excellent, Very good, good, regular or deficient. The final rating
of a book will depend on all the individual user rating
. • Actor: User
• Input: The user will select a rating based on his opinion.
• Output: The system will display the rating of a book and the total number of
votes received. Below is the display for various rating.
***** Excellent
**** Very Good
*** Good
** Regular
* Deficient

Maintain Account
1) Register
• Purpose: If the user doesn’t have an account then he will be asked to
register.
• Actor: User
• Input: The user will enter details in the registration form according to the
required fields. The fields include
1. Username
2. Password
3. Confirm password
4. First name
5. Last name
6. Email
7. Address
 8. Phone
9. CC details
• Output: After registration the user will be directed to the main home page.

2) Login
• Purpose: If the user wants to get access to all the functionalities of Online
Book Store he should login using his username and password.
• Actor: User
• Input: The user will enter his username and password.
• Output: If it is a successful login the user will be directed to the main home
page. Else if the user enters invalid information he will be asked to check the
entered information.

3) Update Profile
• Purpose: If the user wants to change his personal account information then
he can update his selected fields and the entire data will be updated in the
data base through an update query.
• Actor: User
• Input: The user will update his account information.
• Output: The system will update the entered information in the database
using an update query.

4) Logout
• Purpose: If the user wants to end his session and sign out of the website
then he can use the logout option.
• Actor: User 12
• Input: The user will click the logout button.
• Output: The user’s account session comes to an end and he should login
again if he wants to enter into the website.

Manage Shopping Cart

1) Place an order
• Purpose: If the user wants to purchase a book then he can place an order by
selecting the add to shopping cart button and entering the quantity required
under the book description.
• Actor: User
• Input: The user will enter the quantity required and click the add to shopping
cart button.
 • Output: The order will be added to the user’s shopping cart.

2) Update Shopping Cart

• Purpose: If the user wants to change the quantity of a book or change a book
then he can update his shopping cart.
• Actor: User
• Input: The user will click the details button in the shopping cart summary to edit
and update his order details...
• Output: The updated order details are reflected in the shopping cart summary.

3) View Shopping Cart

• Purpose: If the user wants to view the items he added to the shopping cart
then he can click the shopping cart link at the top of the page.
• Actor: User
• Input: The user will click the shopping cart link at the top of every page.
• Output: The user’s shopping cart summary will be displayed in the form of a
tabular format with all the books and their quantity. A total cost of all the items is
also displayed at the bottom.

Administrator

1) Login
• Purpose: If the Administrator wants to get access to all the functionalities of
Online Book Store he should login using his username and password.
• Actor: Administrator
• Input: The Administrator will enter his username and password.
• Output: If it is a successful login the Administrator will be directed to his
menu page. Else if the Administrator enters invalid information he will be
asked to check the entered information.

2) Add or Delete Category

• Purpose: If the Administrator wants to add or delete a book category then
he can insert or delete a book category using his administration rights and
the category table will be updated in the database.
• Actor: Administrator
• Input: If the Administrator wants to add a book category the he should click
the insert link button in the category page else he can delete a particular
selected book category.
 • Output: The updated categories list will be displayed in the main home
page.

3) Add or Delete Book

• Purpose: If the Administrator wants to add or delete a book then he can
insert or delete a book using his administration rights and the book table will
be updated in the database.
• Actor: Administrator
• Input: If the Administrator wants to add a book the he should click the insert
link button in the book page and fill the following fields related to the book. 1.
Title 2. Author 3. Price 4. Category 5. Notes 6. Product URL If he wants to
delete a book he can click the delete button to remove it from the
database.
• Output: The updated books list will be displayed in the main home page
under their particular category.

4) Manage Orders
• Purpose: If the Administrator wants to add or delete an order then he can
insert or delete an order using his administration rights.
• Actor: Administrator
• Input: If the Administrator wants to add an order the he should click the
insert link button in the orders page else he can delete a particular selected
order.
Output: The updated orders list will be processed to the users.

5) Add or Delete CC (Credit Card)

• Purpose: If the Administrator wants to add or delete a CC type then he can
insert or delete a CC type using his administration rights and the CC table will
be updated in the database.
• Actor: Administrator
• Input: If the Administrator wants to add a CC type the he should click the
insert link button in the CC page else he can delete a particular selected CC
type...
• Output: The updated CC list will be displayed in registration page where
the user will select it for his future transactions.

6) Add or Delete Member

• Purpose: If the Administrator wants to add or delete a book category then
he can insert or delete a book category using his administration rights and
the category table will be updated in the database.
• Actor: Administrator
 • Input: If the Administrator wants to add a book category the he should click
the insert link button in the category page else he can delete a particular
selected book category.
• Output: The updated categories list will be displayed in the main home
page.

7) Logout
• Purpose: If the Administrator wants to end his session and sign out of the
website then he can use the logout option.
• Actor: Administrator
• Input: The Administrator will click the logout button.
• Output: The Administrator’s account session comes to an end and he
should login again if he wants to enter into the website.
USER – USECASE DIAGRAM
ADMIN- USECASE DIAGRAM
Data Flow Diagram (DFD):

Data Flow Diagrams show the flow of data from external entities into the system, and from
one process to another within the system.
There are four symbols for drawing a DFD:

1. Rectangles representing external entities, which are sources or destinations of data.

2. Ellipses representing processes, which take data as input, validate and process it and
output it.
3. Arrows representing the data flows, which can either, be electronic data or physical
items.
4. Open-ended rectangles or a Disk symbol representing data stores, including electronic
stores such as databases or XML files and physical stores such as filing cabinets or stacks of
paper.

Zero level DFD

FIRST LEVEL DFD
2nd Level DFD
SECOND LEVEL DFD E-COMMERCE
UML Diagrams:

Class Diagram:

Use case Diagram:

Sequence Diagram:

Collaboration Diagram:
StateChart Diagram:
Activity Diagram:

Component Diagram:
Deployment Diagram:

Entity-Relationship Diagram: