Software Requirements

Specification
for

E-book Management System

Version 1.0 approved

Prepared by

Gokul B

Balaji N

Faaiz Meeraan A

Object Oriented Analysis and Design

11.09.2022
Software Requirements Specification for <Project> Page iii

Table of Contents
Table of Contents...........................................................................................................................ii
Revision History.............................................................................................................................ii
1. Introduction..............................................................................................................................1
1.1 Purpose...........................................................................................................................................1
1.2 Document Conventions...................................................................................................................1
1.3 Intended Audience and Reading Suggestions.................................................................................1
1.4 Product Scope.................................................................................................................................1
1.5 References......................................................................................................................................1
2. Overall Description..................................................................................................................2
2.1 Product Perspective.........................................................................................................................2
2.2 Product Functions...........................................................................................................................2
2.3 User Classes and Characteristics.....................................................................................................2
2.4 Operating Environment...................................................................................................................2
2.5 Design and Implementation Constraints.........................................................................................2
2.6 User Documentation.......................................................................................................................2
2.7 Assumptions and Dependencies......................................................................................................3
3. External Interface Requirements...........................................................................................3
3.1 User Interfaces................................................................................................................................3
3.2 Hardware Interfaces........................................................................................................................3
3.3 Software Interfaces.........................................................................................................................3
3.4 Communications Interfaces.............................................................................................................3
4. System Features.......................................................................................................................4
4.1 System Feature 1.............................................................................................................................4
4.2 System Feature 2 (and so on)..........................................................................................................4
5. Other Nonfunctional Requirements.......................................................................................4
5.1 Performance Requirements.............................................................................................................4
5.2 Safety Requirements.......................................................................................................................5
5.3 Security Requirements....................................................................................................................5
5.4 Software Quality Attributes............................................................................................................5
5.5 Business Rules................................................................................................................................5
6. Other Requirements................................................................................................................5
Appendix A: Glossary....................................................................................................................5
Appendix B: Analysis Models.......................................................................................................5
Appendix C: To Be Determined List............................................................................................6

Revision History
Name Date Reason For Changes Version
Software Requirements Specification for <Project> Page 1

1. Introduction
Drastic changes in the technology and the way internet is evolving has changed the attitude of users
towards learning resources. The role of libraries as a facilitator by providing access to the electronic
resources like e-journals and e-books using the modern technology is widely encouraged. E-books
provides many advantages, views Armstrong. There is no need of physical space and hence the
problem of shelving or re-shelving doesn't arise. E-books cannot be damaged or mutilated; stock
taking or missing will not be a problem. The most important advantage is that, the same book can
be used by many at a time.

1.1 Purpose

If the entire process of 'Issue of Books or Magazines' is done in a manual manner then it would take
several months for the books or magazines to reach the applicant. Considering the fact that the
number of students for Book Bank is increasing every year, an Automated System becomes
essential to meet the demand. So, this system uses several programming and database techniques to
elucidate the work involved in this process. The system has been carefully verified and validated in
order to satisfy it.

1.2 Document Conventions

This document considers some conventions. For every topic heading font size taken is 18 and for
subheadings, it is 14 and most of the document is written with a font size of 11. The Font used is
Times, Arial Italic. Important topics, headers, and words are highlighted to stand their significance.
Higher-level requirements are given higher priority which is visible by the detailed description of
the requirement.
Software Requirements Specification for <Project> Page 2

1.3 Intended Audience and Reading Suggestions

This document is intended for the end users which includes the administrator, employees, visitors
and Human Resources.

1.4 Product Scope

The System provides an online interface to the user where they can fill in their personal details and
submit the necessary documents (may be by scanning). The authority concerned with the issue of
books can use this system to reduce his workload.

1.5 References

1.IEEE Software Requirement Specification format

2.ADVAS Information Security Requirements: To provide security to the system based on the
current security system currently used by UHCL.

3.The Billing System: To provide the interface between the system being developed and the billing
system currently in use by ADVAS to update the member account due as and when they borrow and
return the books.

4. https://onlineengineering.wordpress.com

5. https://www.academia.edu

2. Overall Description

2.1 Product Perspective

Software Requirements Specification for <Project> Page 3

The ORS acts as an interface between the user and the 'e-book manager'. This system tries to make
the interface as simple as possible and at the same time not risking the security of data stored in.
This minimizes the time duration in which the user receives the books or magazines.

2.2 Product Functions

1. Register - it gets the details of a person in a registration form and checks the given details as per
the constraints.
2. User login method -it verifies the entered user name and password.
3. Search book option – it gets the name of the book, Author and category from the user for
searching and check whether the book available in the database.
4. Payment method – it ensures the selected payment method is completed or not.

2.3 User Classes and Characteristics

User:
They are the people who desire to obtain the books and submit the information to the database.
Visitor:
They are the person who visits the E-book system.
Administrator:
He has the certain privileges to add the books and to approval of the reservation of books.

2.4 Operating Environment

The users of the system are members, librarian of the EMS and the administrators who maintain the
system. The members and the librarian are assumed to have basic knowledge of the computers and
Internet browsing. The administrators of the system to have more knowledge of the internals of the
system and is able to rectify the small problems that may arise due to disk crashes, power failures
and other catastrophes to maintain the system .The proper user interface, user's manual, online help
and the guide to install and maintain the system must be sufficient to educate the users on how to
use the system without any problems. The system needs to be supported on mobile devices. It
requires Internet Explorer or Netscape. It should be able to work on both PC and MAC.

2.5 Design and Implementation Constraints

1. The information of all the users must be stored in a database that is accessible by the E-Book
Management System.
2. The university information security system must be compatible with the Internet applications.
3. The E-Book Management System is connected to the university computer and is running all 24
hours a day.
4. The users access the E-Book Management System from any computer that has Internet browsing
capabilities and an Internet connection.
5. The billing system is connected to the E-Book Management System and the database used by the
billing system must be compatible with the interface of the E-Book Management System.
Software Requirements Specification for <Project> Page 4

6. The users must have their correct usernames and passwords to enter into the E- Book
Management System.

2.6 User Documentation

The typical user is simply anyone that has access to the Internet and a web browser
in the computer science department at Michigan State University. It is assumed that the
user is familiar enough with a computer to operate the browser, keyboard and mouse and
is capable of browsing to, from and within simple websites.

2.7 Assumptions and Dependencies

Client:
We have assumed that all of the computer systems in the Engineering building labs are in
proper working condition and that the user is capable of operating these system's basic
functions including but not limited to being able to power on the system, login and open
either Internet Explorer or Mozilla Firefox, and navigate the browser to the address of this
BECS website.
Provider:
We have assumed that the BECS 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:
1. There is no need for anyone to be able to order more than a single copy of a
book (or any item) in a single transaction.
2. The manager account’s username and password maybe hard coded.
3. The manager cannot be a customer.
4. Any user cannot edit their account information.

3. External Interface Requirements

3.1 User Interfaces

Admin:
The administrator is used to register a new visitor for the website. Admin can keep those
records update. Admin keep sales record i.e., now much book is downloaded and how much book is
bought newly with copy write etc.

Registered user:
Registered user can search the book whatever needs and can read the book in online. If
user is satisfied with this book, can download the book but after payment.

Visitor:
The visitor can register the application form and become a member of the website. The
visitor can search books and read the book but he must register to buy or download the book.
Software Requirements Specification for <Project> Page 5

3.2 Hardware Interfaces

1. Processor – Intel Pentium IV-2.0 GHZ.
2. Hardware – 40 GB(segate).
3. RAM – 512mb.
4. DVD RAM – 1 nos.

3.3 Software Interfaces

1. OS – windows XP
2. Front end Tool – Rational Rose Enterprise suite
3. Back-end Tool – Oracle 10i

3.4 Communications Interfaces

1. The communication with the customer is done through mail.
2. This application can be used in any web browser.
3. The verification is sent as OTP (One Time Password).
4. TCP/IP - Transmission Control Protocol/Internet Protocol is the communication protocol used to
connect hosts on the Internet.

4. System Features
1. Save your trip to library and save your time.
2. Read anytime, anywhere you want.
3. With a single device read as many books you want.
4. Search in seconds and access anything you want.
5. A dictionary at your fingertips

4.1 System Feature 1

E-books provides many advantages, views Armstrong. There is no need of physical space and hence
the problem of shelving or re-shelving doesn't arise. E-books cannot be damaged or mutilated; stock
taking or missing will not be a problem.
4.1.1 Description and Priority

The user can view his/her profile and can see the book he/she reading including the books
they acquired. The priority of the user is based on subscription the user holds. Member,
Premium member, Premium pro member.

4.1.2 Stimulus/Response Sequences

The user actions and the system response are one of the major important tasks in e book
management.

1. Search- The search engine is used by the user to search the kind of books that he/she
needs and the system shows the desired results or error messages.
Software Requirements Specification for <Project> Page 6

2. login- Here the user is asked to provide the correct identification and password in order to
login to their account. If the Id or password is wrong an error message is shown.

4.1.3 Functional Requirements

The system should record all the details of a user. The system should provide the applicant to
edit his profile details. The system should allow users to give feedback about the system. The
system should have the facility of administrative help for users to solve important problems.
The system should allow the admin to have full authority over user accounts.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

1. The Splash Page or Information page should be able to be downloaded within a minute
using a56K modem.

2. The access time for a mobile device should be less than a minute.

3. The information is refreshed every two minutes.

5.2 Safety Requirements

The source of this software will be kept at more than one place with user ID, password and
also, in CD ROM in case of server failure

5.3 Security Requirements

The system is being built with login capabilities so that only authorized users can access the
system. To improve the security, feature an OTP (One Time Password) is sent to the user every
single time they login.

5.4 Software Quality Attributes

1. Security
Controlling the access to the database provides security to the system.
2. Availability
The system is online 24 hours a day and 365 days a year.
3. Usability
The system is easy to use for all the users.
Software Requirements Specification for <Project> Page 7

5.5 Business Rules

1. Username & password are sent to the users via mobile SMS and email after registration
2. Password recovery system is also provided in case of forgetting the password.
3. The system should allow the admin to send notifications about the upcoming offers and the
expiration dates of the subscriptions.
4. The system should allow the admin to filter or categorize the users based on the subscription
he/she holds.

6. Other Requirements
To run this web application, you must have a system with an internet connection and a browser.

Appendix A: Glossary
1. Admin – administrator who manages the application.
2. OS – Operating System
3. RAM – Random Access Memory

Appendix B: Analysis Models

Use-Case Diagram: