Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Online Book Store SRS, Summaries of Computer Science

This is short SRS about online book shop

Typology: Summaries

2020/2021
On special offer
30 Points
Discount

Limited-time offer


Uploaded on 08/25/2021

chauhan-shubham
chauhan-shubham 🇮🇳

4.7

(3)

1 document

1 / 20

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
P a g e 1 | 20
Software Requirement Specification
In-House Project On
ONLINE BOOK STORE
Submitted
To
G H Patel P G Department of
Computer Science and Technology
Prepared by Guided By
Shubham Chauhan S. Mr. Bharat B. Patel
(PID: MG20041)
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
Discount

On special offer

Partial preview of the text

Download Online Book Store SRS and more Summaries Computer Science in PDF only on Docsity!

Software Requirement Specification

In-House Project On

“ONLINE BOOK STORE”

Submitted

To

G H Patel P G Department of

Computer Science and Technology

Prepared by Guided By

Shubham Chauhan S. Mr. Bharat B. Patel

(PID: MG20041)

Sr.

No

Content

Page

No.

Introduction

1.1 Purpose

1.2 Scope

1.3 Definitions, Acronyms, and Abbreviations

1.4 References

1.5 Overview

2 General Description

2.1 Product Perspective

2.2 Product Functions

2.3 User Characteristics

2.4 General Constraints

2.5 Assumptions and dependencies

Functional Requirement

3.1 Description

3.1.1 Hardware Interfaces

3.1.2 Software Interfaces

3.1.3 Communication Interfaces

3.2 Functional Requirements

3.2.1 User

3.2.2 Admin

3.3 Performance Requirement

3.4 Software System Attributes Requirements

3.4.1 Security

3.4.2 Reliability

3.4.3 Availability

3.4.4 Maintainability

3.4.5 Portability

3.5 Functional Requirement with UML diagram

revolution of book industry. The traditional bookstores’ operation time, address and space is limited, so the types of books and books to find received a degree of restriction. But the online bookstore broke the management mode of traditional bookstore, as long as you have a computer, you can buy the book anywhere, saving time and effort, shortening the time of book selection link effectively. The online bookstore system based on the principle of provides convenience and service to people.

1.3 Definitions, Acronyms, and Abbreviations

Term Definition

User Someone who interacts with the website.

Admin System administrator who is given specific permission for

managing and controlling the system.

Store Owner Someone who has a book store and wants his book store to be a

part the website.

Stack holder Any person who has interaction with the system who is not a

developer.

1.4 References

✓ An Integrated Approach to Software Engineering Third Edition Pankaj Jalote Indian Institute of Technology Kanpur ✓ https://www.freeprojectz.com/premium-synopsis/synopsis-online-book-store ✓ https://123projectlab.com/22-online-book-store-system-project/ ✓ https://www.researchgate.net/publication/314783622_The_Online_Bookstore

1.5 Overview

Nowadays, the network plays an import role in people’s life. In the process of the improvement of the people’s living standard, people’s demands of the life’s quality and efficiency is more higher, the traditional bookstore’s inconvenience gradually emerge, and the online bookstore has gradually be used in public. The online bookstore is a revolution of book industry. The traditional bookstores’ operation time, address and space is limited, so the types of books and books to find received a degree of restriction. But the online bookstore broke the management mode of traditional bookstore, as long as

you have a computer, you can buy the book anywhere, saving time and effort, shortening the time of book selection link effectively. The online bookstore system based on the principle of provides convenience and service to people. The following SRS contains the detail product perspective from different stakeholders. It provides the detail product functions of E-Store with user characteristics permitted constraints, assumptions and dependencies and requirements subsets.

2 General Description

With the E-bookstore system, consumers do not need to blindly go to various places to find their own books, but only in a computer connected to the Internet log on online bookstore system, in the search box, type you want to find Of the book information retrieval, you can efficiently know whether the site has its own books, if you can online direct purchase, if not, you can change the home bookstore to continue to search or provide advice to the seller in order to supply, This greatly facilitates every consumer, saving time and labor. The online bookstore system can not only reduce costs, save time, space, to bring convenience to everyone, but also to promote the development of the logistics industry, serve three purposes, mutual benefit. More importantly, in today's world, the increasingly close ties between countries, more frequent exchanges, the economy tends to globalization, which promote the future development of online bookstore system has some practical significance.

2.1 Product Perspective

E-book store is developed for everyone who is interested to buy books online to save time and cost. It is an open source and it has a very active developer team to support it and provide feedback to users. It was developed to run on Windows, Mac OS X and Linux. It includes all features needed to fulfill this website requirement.

2.2 Product Functions

With the website, the users will be able to search for books. The result will be based on the criteria the user inputs. There are several search criteria and it will be possible for the administrator of the system to manage the options for those criteria that have. The result of the search will be viewed either in a list view or in a grid view, depending on what criteria included in the search. The list view will have one list item for each book matching the search criteria and show a small part of the book information so

3 Specific Requirement

3.1 External Interface Requirement

This section provides a detailed description of all inputs into and outputs from the system. It also gives a description of the hardware, software and communication interfaces and provides basic prototypes of the user interface

3.1.1 HARDWARE INTERFACE REQUIREMENT

  • Processor: - i 3 Processor.
  • Ram : - 4 GB RAM
  • HDD : - 1024 GB HARD DISK

3 .1.2 SOFTWARE INTERFACE REQUIREMENT

  • Operating System: Windows 7, Windows 8 Windows 10
  • Programming Platform: ASP.NET MVC
  • Framework: VISUAL STUDIO
  • Backend Database: SQL SERVER 2017
  • Web Server: IIS SERVER
  • Other Tools : CSS, HTML, JS, jQuery, AJAX,BOOTSTRAP
  • Compatible Browser: - Mozilla Firefox, Google Chrome, Safari etc.

3.1.3 COMMUNICATION INTERFACES

The communication between the different parts of the system is important since they depend on each other. However, in what way the communication is achieved is not important for the system and is therefore handled by the underlying operating systems for both the mobile application and the web portal

3.2 FUNCTIONAL REQUIREMENTS USER

3.2.1 USER

1 LOG IN

Description of feature This feature used by the user to login into system. A user must login with his user’s name and password to the system after registration. If they are invalid, the user not allowed to enter the system.

2 REGISTER NEW USER

Description of feature A new user will have to register in the system by providing essential details in order to view the products in the system. The admin must accept a new user by unblocking him.

3 PURCHASING AN ITEM

Description of feature The user can add the desired product into his cart by clicking add to cart option on the product. He can view his cart by clicking on the cart button. All products added by cart can be viewed in the cart. User can remove an item from the cart by clicking remove. After confirming the items in the cart, the user can submit the cart by providing a delivery address. On successful submitting the cart will become empty. 4 EDIT PROFILE Description of Feature The user can edit their information anytime as per requirement. They can update their account details or they can create multiple accounts. 5 CONTACT WITH SELLER OF THE BOOK Description of feature If user decided to buy the book, then he/she can contact with the seller via email or can call the seller using his/her contact number. 6 UPLOAD FREE E-BOOKS Description of feature If any user want to upload the e-books for the purpose to help other users who can not afford. The user can download the e-books for free. 7 CHANGE OR RETRIVE PASSWORD Description of feature In case if user wants to change the password he/she is able to do that. If they forgot their password they can again retrieve it via email.

8 LOGOUT

After the payment or surf the product, the customer will be logged out.

3.4 Software System Attributes Requirements

3.4.1 Security

  • The system uses SSL (secured socket layer) in all transactions that include

any confidential customer information.

  • The system must automatically log out all customers after a period of

inactivity.

  • The system should not leave any cookies on the customer’s computer

containing the user’s password.

  • The system’s back-end servers shall only be accessible to authenticated

administrators.

  • Sensitive data will be encrypted before being sent over insecure connections

like the internet.

3.4.2 Reliability

  • The system provides storage of all databases on redundant computers with

automatic switchover.

  • The reliability of the overall program depends on the reliability of the

separate components. The main pillar of reliability of the system is the

backup of the database which is continuously maintained and updated to

reflect the most recent changes.

  • Thus, the overall stability of the system depends on the stability of container

and its underlying operating system.

3.4.3 Availability

  • The system should be available at all times, meaning the user can access it

using a web browser, only restricted by the down time of the server on

which the system runs. In case of a of a hardware failure or database

corruption, a replacement page will be shown. Also, in case of a hardware

failure or database corruption, backups of the database should be retrieved

from the server and saved by the administrator. Then the service will be

restarted. It means 24*7 availability.

  • The application should be connected to the Internet in order for the application to communicate with the database

3.4.4 Maintainability

  • A commercial database is used for maintaining the database and the

application server takes care of the site. In case of a failure, a re-initialization

of the program will be done. Also, the software design is being done with

modularity in mind so that maintainability can be done efficiently.

  • The application should be easy to extend. The code should be written in a way that it favors implementation of new functions

3.4.5 Portability

  • The application is HTML and scripting language based. So, the end-user part

is fully portable and any system using any web browser should be able to

use the features of the system, including any hardware platform that is

available or will be available in the future.

  • An end-user is using this system on any OS; either it is Windows or Linux.
  • The system shall run on PC, Laptops, and PDA etc.

User Side Log-in Use Case Diagram

Activity Diagram

User Registration

Sequence diagram (Forgot Password)

Sequence diagram (Change Password)