EXPERIMENT-2

Aim
To develop Software Requirement Specification (SRS) document for Online Book Store.

1. Introduction
This document aims at defining the overall software requirements for "Online Book Store".
Online Book store is an online web application where the customer can purchase books online,
through a web browser. The customers can select a book; later can add to the shopping cart and
finally purchase using his preferred way of transaction. The users can login using his account
details or new customers can set up an account very quickly. The books are divided into many
categories based on subjects like fiction, cooking, Adventure, etc.

1.1. Purpose:
This Software Requirement Specification (SRS) is meant for an Online Bookstore (OBS).
The OBS is meant as a way for customers to browse books on the website and buy them
from home without the need to travel to a book shop. Defining the functions and
specifications of the Online Bookstore is the primary purpose of this SRS. The clear
understanding of the system and its functionality will allow for the correct software to be
developed for the end user and will be used for the development of the future stages of the
project. This SRS will provide the foundation for the project.

1.2. Scope:
The software system being produced is called Online Bookstore. It is being produced for a
customer interested in selling books via the Internet. This system is designed to “provide
automation support” for the process of placing books for sale on the Internet and facilitating
the actual sale. This system is largely cross-platform and is available to anyone using the
internet. The system will be run on a central server with each user having a remote user
interface through a web browser to interact with it. The Online Bookstore will allow any
user to create an account to become a customer. The customer, through the process of
account creation, will have the option to become a member of the site. The system will
allow customers to browse, search, select, and add books to a shopping cart. Then, provided
they have books in their shopping cart, check out books in the shopping cart and decrement
the stock that the inventory the system maintains. The Online Bookstore also allows a
manager to manage the inventory with full create, retrieve, update, and delete (CRUD)
functionality with regards to books in the system.
1.3. Definition, Acronyms, Abbreviations:
 OBS - Online Book Store
 SRS - Software Requirements Specification
 IEEE- Institute of Electrical and Electronics Engineers
 API - Application Programming Interface
 ETA - Estimated Time of Arrival
 HTTPS - Hyper Text Transfer Protocol Secure
 MIS - Management Information System
 ODBC - Open Database Connectivity

1.4. References:
 Jie Liu.Design and Implementation of Online Bookstore Based on JSP and JavaBean
Technology.Modern Information,2015,(12):42-47.
 Lingxi Meng.Design of Online Bookstore System Based on B2C Model.Value
engineering,2011,(36):101-102.
 Yingqian Tan.Research on Evaluation Index System of Online Bookstore Based on
University Students' Satisfaction. Journal of Sun Yat-sen University (Social Science
Edition),2011,(4):174-184.
 Yinghui Xu.Design and Realization of Online Used Book Sale System.Consumer
Electronics,2012,(9):67-68.
 Zhuanhong Chen,Huan Li.A typical application of jQuery in WEB query
module.Electronic Technology,2013,(12):28-32.
 Paz J R G. Ajax and jQuery.Beginning Asp Net Mvc,2013,(3):11-13.
 Dan Deng.The Operating Mode and Development Prospect of China 's Online
Bookstore. Entrepreneur World,2013,(4):110-111.

1.5. Overview:
The Overall Description section of this document gives an overview of the functionality of
the system. It describes the informal requirements and is used to establish a context for the
technical requirements specification.
Requirements Specification section, this document is written primarily for both the
stakeholders involved and developers. It describes in technical terms the details of the
functionality of the system.

2. OVERALL DESCRIPTION
This section consists of functionality/non-functionality features such as security,
reliability, and interactions of the system with other contexts and contents.

2.1. Product Perspective:

 This product is an entirely new product. It is not a component of a larger system. The
OBS website supports several functions for both the consumer and store's management.
The website is available to anyone using the internet and as such must work correctly in
all browsers (Google Chrome, Internet Explorer, Mozilla Firefox, Microsoft Edge, Safari,
etc.).

There are no hardware or software requirements beyond these including, but not limited
to, memory or specific software packages that need to be utilized nor software packages
that need not be utilized. The Online Bookstore system will interact with a credit/debit
card processing system in order to process purchases from the website. The system will
also interact with the Bookstore’s Inventory database, which records the quantity of
books available for sale in the inventory.

2.1.1. System Interfaces

The system will interface with the following two systems:

1. A Transaction processing system: The system will access the transaction processing
system via its web services API.

2. The Bookstore Inventory database: The system will interact with the inventory database
via an ODBC connection.

2.1.2. User Interfaces

The system will provide the ability for everyone to access the Online Bookstore via the
Internet.
There will be two different user interfaces that will accompany this website: one for the
buyers
and one for administrators.
• Buyers will be allowed to search the database without having to login, however, they
must login in order to perform any other transaction. These other transactions will include
purchasing textbooks, or viewing and changing their online account.
 • Administrator will have to login to perform any functions. Administrator will be able to
add/delete books to be displayed to the users, and change the information on any books as
required. He/she will also be able to investigate the inventory database to check the
availability of books and their quantity-in-stock.

2.1.3. Hardware Interfaces

Since the application must run over the internet, all the hardware required to connect to the
internet will be hardware interface for the system. As for e.g., Modem, WAN–LAN,
Ethernet Cross-Cable. The machine is connected to a printer for printing bills, etc.

2.1.4. Software Interfaces

The software runs under Linux or Windows operating systems. This software uses two
different databases for travel agents and customers. Internet use is a must.

2.1.5. Communication Interfaces

The software must be web browser enabled and HTTP protocol is used to transfer data.

2.1.6. Memory Constraints

The software will need at least 512 GB hard disk/128gb SSD for boot drive and minimum

8 GB RAM space in order to run at optimum performance.

2.1.7. Operations
o The administrator of the system must first login into the system before operating the
system for security purposes.
o The system is accessible by the customer for searching books but login is required for
any other operations.
o The system is available and active 24 hrs by online execution.
o The system will be able to update the stock daily.

2.1.8. Site Adaptation Requirements

The software does not require any modifications for site adaptation. The system works on
a basic computer that is connected to the organization's local area network.

2.2. Product Functions

The Online Bookstore will provide several functions, each is listed below.
•Maintain data associated with the inventory (a collection of books).
• A book has a title, author, and price.
• The inventory also keeps track of the stock/quantity of each book.
•Maintain records for many customers.
 • A customer can be either a member or non-member.
• A customer has a username (unique across all users), password (no restrictions), email
address (no restrictions), and postal address (unverified).
• Anyone may sign up for a customer account.
•Allow any customer to become a member.
•Show a listing of available books.
• Books are to be displayed in ascending alphabetical order by title.
• Each book will list the following from left to right.
• Title.
• Author.
• Price.
• Allow customers and managers to log in and out of the system.
•Shopping cart.
• Anyone can add one or more books to the shopping cart.
•Checkout.
• Checkout is only available to logged-in customers. A user that is not logged in as a
the customer is given a chance to log in.
• Collect a 16-digit credit card number from the customer.
• Log/record the transaction.
•Allow the manager to specify a stop-order for a book.
• Each book has its own stop-order status – either on or off. Details of its use are involved
in the following feature.
•Notify the manager when books need to be reordered.
• When the quantity of a book falls below a threshold, the manager is notified that the book
needs to be reordered.
• One exception is if the manager has already specified a stop-order for this book.
• Every book must either have stop-order enabled or disabled.
•Allow managers to update stock quantities.
• Allow the manager to change any book's price.
• Allow the manager to view transaction logs.

2.3. User Characteristics

The typical Online Bookstore user is simply anyone that has access to the Internet and a
web browser. It is assumed that the user is familiar enough with a computer to operate the
browser, keyboard and mouse and can browse to, from and within simple websites

2.4. Constraints
Security is not a concern for this system. The database may store passwords in plain text
and there does not need to be a password recovery feature nor lockout after numerous
invalid login attempts. As such, the system may not work correctly in cases when security
is a concern. These cases include those listed above in addition to lack of an encrypted
connection when sending credit card information and forcing users to use “strong”
passwords. A strong password is a password that meets several conditions that are set in
place so that the user's passwords cannot be easily guessed by an attacker. Generally, these
 rules include ensuring that the password contains enough characters and contains not only
lowercase letters but also capitals, numbers, and in some cases, symbols

2.5. Assumptions and Dependencies

Since the Online Bookstore is only accessible through the internet, it is assumed that the
end user has a connection to the internet. It is also assumed that the user has a web browser
able to display the website.
 Client:
We have assumed that all the computer systems are in proper working condition and
that the user can operate these system's basic functions including but not limited to
being able to power on the system, login and open browsers, and navigate the browser
to the address of the website.

 Provider:
We have assumed that the Online Bookstore will be running on a properly working
web server and database system with an Internet connection that allows this system to
perform all communications with clients. Assumptions:
The manager account’s username and password may be hard coded.
• The manager cannot be a customer.
• Any user cannot edit their account information.

2.6. Apportioning of Requirements

As stated by the customer, security is not a concern of this project. As such, it is beyond
the scope of this system to encrypt personal user data, encrypt credit card information,
prevent unauthorized login attempts, or any other concern of this nature. Additionally, the
system is not responsible for the following:
• Verifying that credit card information is valid.
• Verifying the email address provided by a user.
• Storing additional information about a book beyond simply the title, name of
author, and price.
• Allowing users to edit their account details (username, password, mailing address,
etc).
• Allowing customers to order multiple copies of a book in a single order.
• Providing individual product pages (one page for every item in the inventory).
• Allowing the manager to update login credentials or other information about the
manager.