Book Store

Software Requirement Specification

Document
 Table of Contents

1. Introduction
1.1. Purpose
1.2. Scope
1.3. Definitions, acronyms & abbreviations
1.4. References
1.5. Overview
2. Overall description
2.1. Product perspective
2.1.1. System interfaces
2.1.2. User interfaces
2.1.3. Hardware interfaces
2.1.4. Software interfaces
2.1.5. Communications interfaces
2.1.6. Memory constraints
2.1.7. Operations
2.1.8. Site adaptation requirements
2.2. Product functions
2.3. User characteristics
2.4. Constraints
2.5. Assumptions and dependencies
2.6. Apportioning of requirements
3. Specific Requirements
3.1 External interface requirements
3.1.1 User interfaces
3.1.2 Hardware interfaces
3.1.3 Software interfaces
3.1.4 Communication interfaces
3.2 Specific requirements
3.2.1 Sequence diagrams
3.2.2 Classes for classification of specific requirements
3.3 Performance requirements
3.4 Design constraints
3.5 Software system attributes
3.5.1 Reliability
3.5.2 Availability
3.5.3 Security
3.5.4 Maintainability
3.6 Other requirements
4. Supporting information
4.1 Table of contents and index
4.2 Appendixes
1. Introduction
The document aims at defining the overall software requirements for online book store. Efforts have
been made to define the requirements exhaustively and accurately.
1.1.Purpose
A Book Store App project developed using Java and Microsoft Access database. The purpose of
efficiently managing various aspects of a bookshop's operations. It typically includes features like:
1) Inventory Management: Tracking book stock, including details such as title, author, genre,
price, and quantity.
2) Sales Management: Recording sales transactions, generating invoices, and updating inventory
accordingly.
3) Customer Management: Managing customer information, purchase history, and preferences.
4) Supplier Management: Handling information about book suppliers and orders.
5) Reporting and Analytics: Generating reports on sales, inventory, and other relevant data to aid
decision-making.
6) User Authentication and Authorization: Secure login and access control for different roles
within the system.
7) Search and Filtering Capabilities: Allowing users to search for books based on various criteria.
The project aims to streamline bookshop operations, improve inventory accuracy, enhance customer
service, and provide valuable insights for business growth and decision-making.

1.2.Scope
The software product to be produced is a Book Store system which will automate the major library or
bookshop operations.
The Book Store project is able to implement changes and modifications that were made by shopkeeper
or owner as we are making our project at a very low level so the modification that can be done.
The Book Store is useful for a checking availability of books with the help of several measures like
name of books, name of authors, name of publishers, unique book ID, etc. Using this system one can
also book or purchase a book of preferred choice.
The book store system is that if the book store uses this program for their work then it will consume
less time and it will apply accuracy and will able to store the records of the books easily in the system
without any mismatching of the records.
It will help in maintaining the details of the books available, customers details, details of the books
given on rent, sales record, employee's details and many other details can be mentioned in this
application.

1.3. Definitions, acronyms & abbreviations

SRS – Software Requirements Specification

1.4.References
• Object Oriented Software Engineering by Yogesh Singh and Ruchika Malhotra, PHI Learning
private Limited, 2012
• IEEE Recommended Practice for Software Requirement Specifications- IEEE standard 830-
1998
 • IEEE standard for software test documentations-IEEE standard 829/1998
1.5.Overview

The SRS is organized into two main sections. The first is the Overall Description and the second is the
Specific Requirements. The overall description will describe the requirements of the Book Store from
a general high-level perspective. The Specific Requirements section will describe in detail the
requirements of the system.

2. Overall description

Describes the general factors that affect the product and its requirements. This section does not state
specific requirements instead, it provides a background for those requirements, which are defined in
section three, and makes them easier to understand.

2.1. Product perspective

The Book Store is an independent stand–alone system. It is totally self-contained.

2.1.1. System interfaces

Store database: It contains the customer and books details like customer name book ID book name and
book price.

2.1.2. User interfaces

The online book store will have the following user friendly and menu driven interface:

1. Login: allow the entry of only authorised user through valid login ID and password

2. Add to cart: to allow the customer to add book which he wants to buy to the cart

3. Edit cart: to allow the member to edit information of the book

4. Check out: allow the customer to make payment

2.1.3. Hardware interfaces

The Book Store will be placed on PCs throughout the book shop. Screen resolution of at least 640 x
480 or above. Support for printers.
2.1.4. Software interfaces

All databases for the Book Store will be configured using Text pad. These databases include available
books, price of books and customers information. These can be modified by the end users. The book
database will include the book numbers and if they are available or sold. The customers information
database will contain all the information of the customer such as first name, last name, number of copies
of book purchased, default book rate (may be changed) and abbreviated customer feedback.

2.1.5. Communications interfaces

A communication interface for a Book Store is essential to facilitate interaction between different
components and systems within the book store ecosystem. The interface should support communication
among various modules. In Book Store, communication is via WAN (Wide Area Network)

2.1.6. Memory constraints

Memory constraints for a Book Store depend on the specific requirements, size of the book store, and
the technology stack used.

2.1.7. Operations

Operations for book store management encompass various tasks and activities required to efficiently
run a book store. The operation product release will not cover any automated housekeeping aspects of
the database. The administrator at the client site (i.e., Store or Shop) will be responsible for manually
deleting old/ non-required data. Database backup and recovery will also be handled by administrator.
However, the system will provide a Reset System function that will delete (upon confirmation from the
Administrator) all the existing information from the database

2.1.8. Site adaptation requirements

Site adaptation requirements for a Book Store involve ensuring that the system functions optimally in
various environments and conditions. Whether it's an online bookstore, a physical store with an online
presence, or a combination of both, site adaptation is crucial.

2.2. Product functions

Product functions for a Book Store Management System encompass the various features and
capabilities that enable efficient management of a book store's operations.

The Online Shopping Portal will allow access only to the authorised users with specific roles (system
administrator, customer, member). Depending upon the user’s role, he /she will be able to access only
specific modules of the system. A summary of major functions that the Online Shopping Portal shall
perform includes:
1. Login facility for enabling only authorised access to the system.

2. System administrator will be able to add modify delete view product.

3. The customer will be able to item to cart.

2.3. User characteristics

Qualification: At least Matriculation and comfortable with English.

Experience: Should be well versed about the process of university library.

Technical experience: Elementary knowledge of computer.

2.4. Constraints

• Budget Constraints: Limited financial resources

• Physical Space Limitations: Limited the capacity to display and store books
• Competition: Intense competition from other bookstores
• Technology Constraints: Network connectivity issues, outdated hardware or software.

2.5. Assumptions and dependencies

1. The section will provide the list of registered customers.

2. The login ID and password must be created by system administrator and communicated to concerned
users to avoid unauthorised access to the system.

3. The acquisition section of the book will provide the list of the books purchased by the

Book store.

2.6. Apportioning of requirements

There are no such requirements.

3. Specific Requirements

This section contains all the software requirements at a level of detail, that when combined with the
system context diagram, use cases, and use case descriptions, are sufficient to enable designers to design
a system to satisfy those requirements, and testers to test that the system satisfies those requirements.
3.1 External interface requirements

The Book Store will use the standard input/output devices for a personal computer. This includes the
following:

• Keyboard
• Mouse
• Monitor
• Printer

3.1.1 User interfaces

The User Interface Screens are described in the below table:

Screen Name Description

Login Log into the system as an admin or store manager

Add new stock Add new stock of book on demand

Update Update the existing book which is available in stock

Delete Delete the available stock

Distributor Details All distributor details will be stored

Sale Bill Create selling bill

Purchase Order All details regarding purchased books from distributor will be stored

Report Select, view, save, and delete reports

3.1.2 Hardware interfaces

The system shall run on a Microsoft Windows based system.

3.1.3 Software interfaces

The system shall interface with Text pad or Access database.

3.1.4 Communication interfaces

The system shall be a standalone product that does not require any communication interfaces.
3.2 Specific requirements

1. Functional Requirements:

1.1 Inventory Management

• Users can add, update, and delete books in the inventory.

• The system must store book details, including title, author, ISBN, price, quantity, and category.
• Users can search for books based on various criteria (e.g., title, author, category).
• The system should generate alerts when the stock of a book falls below a specified threshold.

1.2 Sales and Orders

• Users can add books to their shopping cart.

• Users can place orders and choose to purchase items in-store or online.
• Admins can process and manage customer orders, mark orders as shipped, and issue invoices.
• The system should calculate the total amount for each order and generate receipts.

1.3 Customer Management

• Users can register, log in, and update their profiles.

• Users can view their purchase history.
• Admins can manage customer information, including contact details and account status.

1.4 Reporting

• Generate and export sales reports for specified time periods.

• Generate inventory reports showing stock levels and sales trends.
• Provide statistics on the bestselling books and customer preferences.

2 Non-Functional Requirements

Functional requirements define the needs in terms of performance, logical database requirements,
design constraints, standards compliance, reliability, availability, security, maintainability, and
portability.

3.3 Performance requirements

It should be run on 1 GHz, 512 MB RAM Machine. Responses should be within 2 seconds.
3.4 Design constraints

The Book Store shall be a stand-alone system running in a Windows environment. The system shall be
developed using Java and an Access database.

3.5 Software system attributes

3.5.1 Reliability

The application will be available to the candidates through the registration period and have a high degree
of fault tolerance

3.5.2 Availability

Aim for 99.9% system availability, with planned maintenance windows.

3.5.3 Security

The application will be password protected. Users will have to enter correct login ID and password to
access the application.

3.5.4 Maintainability

The application will be designed in a maintainable manner It will be easy to incorporate new
requirements in the individual modules.

3.6 Other requirements

In addition to the functional and user-related requirements, a Book Store will have various other
requirements that are essential for its successful operation. These requirements cover aspects like
performance, security, scalability, and more.
Module Specification:

1. Add new stock:

a) Book Details:
I. Book Id: - The Book ID is a fundamental component of a Book Store enabling efficient tracking
and management of the books in stock, as well as providing valuable data for decision-making and
customer service.
II. Book Name: - The Book Name is the primary identifier for a book in the system. It distinguishes
one book from another based on its title. This is important because multiple books can have the
same author or similar attributes, but their titles are usually unique.
III. Book Author: - The Book Author is a critical piece of information for identifying a book. It helps
distinguish books with the same or similar titles and provides clarity about the specific work in
question.
IV. Publication: -The Book Publication attribute includes the name of the publisher that produced and
released the book. This information is essential for tracking which publishing house produced a
specific book and helps in maintaining relationships with publishers for future orders.
V. Book Sales Cost: -"Book Sales Cost" in a Book Store refers to the total cost incurred by the
bookstore to sell a book. This cost includes various expenses associated with acquiring,
maintaining, and selling books to customers.
VI. Book Purchase Cost: -"Book Purchase Cost" in a Book Store refers to the total cost incurred by
the bookstore to acquire books from publishers, distributors, or wholesalers. This cost is a crucial
component in managing the financial aspects of a bookstore's operations.
VII. Quantity: -In a Book Store, "Quantity" typically refers to the number of copies or units of a specific
book available in the bookstore.

b)Notebook Details:
I. Notebook Id: -A "Notebook ID" in a Book Store typically refers to a unique identifier or code
assigned to notebooks or other stationery items available in the bookstore.
II. Notebook Name: -In a Book Store, "Notebook Name" refers to the title or name associated with a
particular notebook or stationery item available for sale in the bookstore.
III. Company: -In a Book Store, the term "Company" can refer to several aspects and entities involved
in the operation and management of the bookstore.
IV. Notebook Size: -In a Book Store, "Notebook Size" typically refers to the physical dimensions or
specifications of a notebook or stationery item, specifically its width, height, and, in some cases,
thickness. Notebooks come in a variety of sizes, and each size serves a different purpose. Common
sizes include letter-size (8.5 x 11 inches), A4 (210 x 297 mm), and pocket-sized (e.g., 3.5 x 5.5
 inches). Notebook Size allows customers to choose the size that best suits their needs, whether it's
for writing, sketching, or note-taking.
V. Notebook Type: -In a Book Store, "Notebook Type" typically refers to the specific category or
style of notebooks and stationery items available in the bookstore.
VI. Pages: -In a Book Store, "Pages" typically refers to the number of pages or sheets in a book,
notebook, or any other printed material. The attribute "Pages" plays a significant role in managing
books and stationery products efficiently.
VII. Sale Cost: -In a Book Store, "Sale Cost" refers to the total cost incurred by the bookstore when
purchasing books from a distributor or wholesale supplier. This cost encompasses various expenses
associated with acquiring books from the distributor for resale to customers.
VIII. Purchase cost: -Purchase Cost in a Book Store refers to the total cost incurred by a bookstore when
purchasing books from a distributor or wholesale supplier. This cost includes various expenses
associated with acquiring books from the distributor for resale to customers. Here are the key
components and factors related to Distributor.
IX. Quantity: -In a Book Store, "Quantity" refers to the number of copies or units of a specific book
title or product that a bookstore is purchasing from a distributor or wholesale supplier. This
attribute is vital for effective inventory management, ensuring that the bookstore has the
appropriate number of copies to meet customer demand and maintain a well-stocked inventory.

c) Stationary Details:
I. Stationary Id: -In a Book Store, "Stationery ID" typically refers to a unique identifier or code
assigned to stationery items and office supplies available in the bookstore.
II. Stationary Name: -In a Book Storr, "Stationery Name" refers to the name or title associated with
specific stationery items and office supplies available in the bookstore.
III. Manufacturer: -In a Book Store, "Manufacturer" refers to the company or entity responsible for
producing or publishing books and other products available in the bookstore's inventory. The
Manufacturer is a key attribute used to categorize and identify the source of various items, and it
plays an important role in managing the inventory, product information, and supplier relationships.
IV. Sale Cost: -In a Book Store, "Sale Cost" typically refers to the total cost incurred by the bookstore
when selling stationery items and office supplies to customers. This cost includes various expenses
associated with the sale of stationery products and impacts the profitability of the bookstore.
V. Purchase Cost: - In a Book Store, "Purchase Cost" refers to the total cost incurred by the bookstore
when purchasing stationery items and office supplies from suppliers or distributors. This cost
encompasses various expenses associated with acquiring stationery products for resale to
customers.
2. Distributor Details:
I. Distributor Id: -In a Book Store, a "Distributor ID" typically refers to a unique identifier or code
assigned to distributors or wholesale suppliers with whom the bookstore has established business
relationships. This ID is used to uniquely identify and categorize each distributor in the system and
plays a crucial role in various aspects of inventory management, ordering, and tracking.
II. Distributor Name: -The Distributor Name helps store staff and systems accurately identify and
distinguish different distributors or wholesale suppliers. It ensures that each supplier is uniquely
recognized within the system.
III. Address: - In a Book Store, "Address" refers to the physical location or mailing address of the
distributors or wholesale suppliers from whom the bookstore procures books and other products.
The Distributor Address is an essential piece of information used for various purposes in managing
the supply chain, ordering, and communication with suppliers.
IV. Phone No.: -In a Book Store, the "Phone No." is a key piece of contact information for distributors
or wholesale suppliers from whom the bookstore procures books and other products. The phone
number serves as a means of communication and plays a significant role in several aspects of supply
chain management, order placement, and issue resolution.
V. Mobile No.: -Distributor mobile numbers provide a direct and efficient means of communication
between the bookstore and the distributor. Bookstores can use these mobile numbers to discuss
orders, pricing, and any issues that may arise.
VI. Distributor For: - In a Book Store, "Distributor For" typically refers to a field or attribute that stores
information about the specific books or products supplied by a particular distributor or wholesale
supplier

3. Sale Bill:
I. Customer Name: -In a Book Store, the "Customer Name" on a sale bill refers to the name of the
customer who has made a purchase at the bookstore.
II. Phone No.: - The customer's phone number on the sale bill provides a means of contact for the
bookstore to reach out to the customer. It is often used to confirm orders, provide updates on order
status, and address any questions or issues related to the purchase.
III. Quantity: -In a Book Store, the "Quantity" field on a sale bill refers to the number of units or items
of a particular book or product that a customer has purchased in a single transaction.
IV. Price: -In a Book Store, the "Price" field on a sale bill refers to the cost or unit price of a book or
product that a customer has purchased.
V. Amount: -In a Book Store, the "Amount" field on a sale bill refers to the total monetary value or
sum of the purchase.
 VI. Buy Item: -The "Buy Item" field specifies the names and details of the books or products that the
customer has purchased.
VII. Bill Pending: -The "Bill Pending" status is used to keep track of transactions for which payment is
still outstanding. This helps bookstore staff and management monitor accounts receivable.
VIII. Total Amount: -The "Total Amount" confirms the exact amount that the customer is required to pay
for the entire purchase. This ensures accurate payment collection.
IX. Paid: -In a Book Store, "Paid" on a sale bill refers to the specific amount that a customer is required
to pay for the items they have purchased in a single transaction.
X. Balance: -In a Book Store, the "Balance" on a sale bill refers to the amount that a customer owes or
the amount of change due after a transaction is completed.

4. Purchase Order:
I. Distributor Id: -When the bookstore needs to place orders for books or products, it uses the
"Distributor ID" to specify which distributor the order is intended for. This ensures that the correct
distributor receives the order.
II. Distributor Name: -When the bookstore needs to place orders for books or products, it uses the
"Distributor Name" to specify which distributor the order is intended for.
III. Distributor For: -The "Distributor For" field in a purchase order within a Book Store can have
various interpretations and uses.
IV. Particulars: -The " Particular" in a purchase order within a Book Store typically refers to specific
details or information related to a distributor's role or a particular aspect of the purchase order.
V. Purchase Cost: -In a Book Store, the "Purchase Cost" in a purchase order refers to the cost or price
at which the bookstore is purchasing books or products from a specific distributor or supplier.
VI. Quantity: -In a Book Store, the "Quantity" field in a purchase order is used to specify the quantity
of each product or item that the bookstore wishes to purchase from a distributor or supplier.
VII. Amount Type: -The "Amount Type" in a purchase order within a Book Store typically refers to the
categorization or classification of different amounts or costs associated with the purchase order.
VIII. Amount: -The "Amount" field confirms the total financial commitment for the purchase order.
IX. Cheque DD/No.: -It helps identify the specific payment instrument that will be used to pay for the
purchase order. This is particularly important for tracking payments, especially in cases where
multiple payment methods are used (e.g., checks, bank drafts, electronic transfers).
5. Report:
a)Stock Detail:
I. Item Name: -In a Book Store, "Item Name" typically refers to the name or title of a specific book,
product, or item that is part of the store.
II. ID: -Each ID uniquely identifies a specific entity, making it distinguishable from others. For
example, a book ID would uniquely identify a particular book in the store.
III. Available Stock: -In a Book Store Management System, "Available Stock" refers to the quantity of
a specific book or product that is currently in stock and available for sale.

b)Pending Bill:
I.Customer Name: -"Customer Name" helps identify the individual or entity that made the purchase
but has not yet settled the bill.
II.Phone/Mobile No.: -The phone number allows the store to contact the customer regarding their
pending bill or transaction.
III.Paid: -The "Paid" field indicates the amount that the customer has paid toward a particular bill. It
helps store staff and management quickly determine the payment status of each pending bill.
IV.Balance: -The "Balance" field helps track the outstanding amount that a customer needs to pay to
settle their bill. It provides an overview of unpaid bills.
V.Total: -It provides an itemized total of all charges incurred by the customer during the transaction,
ensuring clarity and transparency in the billing process.