Project: Software Requirement Specification for a Book Shopping System

This document provides a comprehensive software requirements specification (SRS) for a book shopping system. It outlines the project's goals and objectives, including creating a software specification document and an MS Access prototype for a booking store. The document details the system's functional and non-functional requirements, such as browsing inventory, searching for books, managing inventory (CRUD operations), shopping cart functionality, checkout procedures, authentication, promotions, automated reordering, and order logging. It also includes analysis models like ERD, use case, and context diagrams, along with a data dictionary. Assumptions and constraints are clearly defined, ensuring a clear understanding of the system's behavior and limitations. The system aims to streamline the book purchasing process for customers and simplify user and product database management for store owners.

Software Engineer

Contents
1. Introduction.......................................................................................................................................3
2. Project Goals......................................................................................................................................3
3. Project Objectives..............................................................................................................................3
4. Project Description............................................................................................................................4
5. Project Assumptions..........................................................................................................................4
6. Project constraints.............................................................................................................................5
7. Specific Requirements.......................................................................................................................5
7.1 Restrictions.....................................................................................................................................5
7.2 Database Structure requirement..................................................................................................5
7.3 System, functional and non- functional Requirement.................................................................7
8. Analysis Models.................................................................................................................................8
8.1 ERD diagram.................................................................................................................................9
8.2 USE-CASE DIAGRAM...............................................................................................................10
8.3 CONTEXT DIAGRAM...............................................................................................................11
8.4 Data Dictionary............................................................................................................................12
8.5 Class diagram...............................................................................................................................14
9. Conclusion........................................................................................................................................15
References................................................................................................................................................16

1. Introduction
Introduction of the software requirement specification is to provide the overview of the
entire software requirement specification with purpose, scope, goals, objectives and assumptions.
It is used to gather and analyze the book shopping to provide an in-depth insight of the software
requirement document for a shopping. It also defining the high-level product features and it
requires the stakeholder capabilities. It provides the detailed requirement of book shopping that
is provided in software requirement document. Purpose of the software requirement document is
used to analyze and collect the all assorted ideas for shopping that is used to define the system
models and it requirements with respect to the consumers. It also sorts and predicts out the book
shopping that will be used in order to gain a better understanding of the projects. The purpose of
the software requirement document is used to provide the detailed overview of product that is
book, it goals and parameters. It also describes the project target audience and it specific
requirements. This document also defines the how or team, audience and clients are seeing the
products and it functionality. It is very helpful for designer and developer to assist in processes
of software delivery lifecycle.
2. Project Goals
This project is used to produce the
1. Software Specification document
2. MS access prototype for booking store
The book store is used to provide the shopping for a user’s. The software specification
document also enables the database component for book store.
3. Project Objectives

Main objective of this project to create the software requirement document for book
shopping and it enable the database component for this document. This project is also aimed at
specifying the software requirements to be developed and it can be applied to assist in the book
shopping. It also used to create the specific requirements or model to defining the software
requirement document for book shopping and this project is does not identify the any specific
method and nomenclature or tool for preparing the software requirement document. This
document is also managed the book purchase and sales with regard to speeding up and
simplifying the process of purchasing, selection and ordering the books for customers as well as
managing a user database and product database for book store owners.
4. Project Description
This project to create the software requirement document for book shopping and also
needs to do in depth analysis to complete the software requirement documents. It also develops
the MS access prototype that related to book shopping. The software requirement document is
used to describe the system requirement and it behavior under defined condition and constraints
based on book shopping. It must be operating under the system behavior and it will typically be
read by variety of stakeholders and this document is used to create a model to provide the
effective software requirement document for book shopping. The project description is used to
contains the problem statement that the current system and it facing the booking shopping
growth opportunities. It also contains the list of the users and stakeholders of the purposed
solutions. It is used to illustrate the wants and needs of the stakeholders and it identified the
brainstorming as part of the specific requirements. It briefly describes the major features and
description of the software requirement document. It also provides the detail product perceptive
from the various stakeholders and detail product function of book shopping with user
characteristics, assumptions, requirement subset, dependencies and constraints. This
documentation will be provided in the form of a user Manaus which contains the detailed
description for all system requirements and functions.
5. Project Assumptions

We have assumed that all of the system and database requirements and it allows to performing
all communication with clients. The assumptions are listed below.
 The owner and manager cannot ne a customer.
 The manager accounts username and password may be hard coded.
 There is no need for anyone to be able to order more than a one copy of a book in a single
transaction.
 Ay user cannot edit their account information.
6. Project constraints
The Project constraints are to provide the system requirement that should be build using
the database prototype by using the Microsoft access. The book shopping is does not need
memory requirement and the computers should be equipped with database component. The
product must be stored in such as easy way that allows the client easy access to it. It does not
take longer time to response time for loading the products.
7. Specific Requirements
The specific requirements are listed below.
7.1 Restrictions
1. User side
Software-Internet explorer or chrome
Hardware-Personal Computer
2. System side
Software-web based application and database information storage system that is Microsoft
access.
7.2 Database Structure requirement
The book has the following attributes
 isbn
 Author name
 title
 Publisher name
 Publication year

 binding
 Source number
 retail price
 Number on hand
The Order has the following attributes,
 Order number
 Customer number
 Order date
 credit card number
 Order filled
 credit card expiry date
The order lines have the following attributes,
 Order number
 Isbn
 Quantity
 Cost each
 Cost line
 Shipped
The Publisher has the following attributes,
 Publisher Name
The Customer has the following attributes,
 Customer number
 Customer first name
 Customer last name
 Customer city
 Customer state
 Customer zip
 Customer phone
 Customer email
The source has the following attributes,
 Source number
 Source name
 Source street
 Source city

 Source state
 Source zip
 Source phone
The author has the following attributes,
 Author name
 country of birth
 date of birth
7.3 System, functional and non- functional Requirement
The system, functional and non - functional requirement includes the,
 Browse inventory
The browse inventory requirement is used to List the items on single page, Shows
the item in tabular format, List the item contains the title, price and author name. It also
listed the items by ascending order and it does not have individual item pages. It also has
the single button to add all selected items to shopping cart.
 Search inventory
The search inventory is used to search the available only by book title and exact
matches only.
 Create, update and destroy functionality
The functionality of CRUD is only accessible for manager that is allowed to
modify the inventory. The managers are having the interface to create, update the book
entry, create a new promotion, update the quantity and stock of a particular book, delete
the items from the inventory and review the current inventory.
 Shopping Cart
If logged in, shopping cart is used to add the items to cart and customer can only
purchase the one of each item. If not logged in, shopping cart is used to add the items to
cart and user must be login before check out the procedure.
 Checkout Procedure
In checkout procedure, the user must successfully use the shopping cart before
start this procedure and it consists of following activities such as a text box for hold the
credit card number, another text box for promotion entering, a button to complete the
order and another button to overview the purchase. The check-out procedure also
completes the order and it decremented the items based on purchased in inventory.

 Authentication system
The authentication system is including the following aspects such as user levels,
account creation, login and log out and account modification. In user levels, the
authentication must be carried out by manager and customer. In account creation, every
user must be allowed to create an account and provide the full information about the user.
In account modification, the users do not have the permission to modify their account
after completing the account creation. In login and log out, there no password recovery,
logging processes in allows to check out the inventory and logging in allows one to
logout.
 Promotions
The promotions include the following specifications like expiration occurs at
manager specified date, percentage off type promotion, it applies to entire order and
multiple coupons cannot be applied to same order. The creation of promotion is done by
manager and it has unique identifying number. The promotions are auto delete when date
is expired.
 Automated reorder
The automated reorder also has the specification such as the managers are
increase the stock of the item by using the manager account and the manager are sets the
reorder threshold on a per item basis.
 Order logging
The order logging requires the user information to logging the account and
manager can be view the all past transaction from all users.
8. Analysis Models
The Microsoft access database will be used for storing products, records and customers
information. The search engine located on each customer screen will interact with way of
retrieving the data from the database through the user interface that is Microsoft access forms.
The screens are associated with the database and it will be data display screen and manage
database screen. The subsystem functionality will be carried out through the GUI components
like message boxes, labels, bars, navigation bars, images, tables, text input boxes and buttons.

8.1 ERD diagram
The entity relationship diagram is shown below.
The entity relationship diagram is used to display the book shopping and it used for
software requirement specification. The Entity relationship diagram has following tables such as
Books, Orders, order line, publishers, sources, customers and authors. The Order tables consists
of Order_numb, customer_numb, order_date, credit_card-number, order_filled and credit card
exp date. The order_numb is primary key and customer_numb is the foreign key. The orderlines
table consists of order_numb, isbn, quantity, cost_each, cost_line and shipped. Here, the
order_numb is the primary key. The Atuhors table consists of author_name, country of birth and
data of birth. The author_name is the primary key. The publichers tables contains the publisher
name and it is the primary key. The customer tables consist of customer_numb,
customer_first_name, customer_last_name, customer_city, customer_state, customer_zip,
customer_phone and customer_email. Here, the customer_numb is the primary key. The source
table contains the source_numb, source_name, source_street, source_city, source_state,
source_zip and source_phone. Here, the source_numb is the primay key. The Book tables

contains the isbn, author_name, title, publisher_name, publication_year, binding, source_numb,
retail price and number_on hand. Here, isbn is the primay key. The publisher_name and
source_numb is the foreign key. The entity relationship diagram is connected with each other. It
provides the effective database system and it very useful the software requirement specification
document.
8.2 USE-CASE DIAGRAM
Use case diagram is shown below.

8.3 CONTEXT DIAGRAM
Context diagram is shown below.
8.4 Data Dictionary
Name: customer
System Usage: Input to order subsystem
Output to login the subsystem
Attributes
Customer number-Number
Customer first name-Short Text
Customer last name-Short Text
Customer city-Short Text
Customer state-Short Text
Customer zip-Number
Customer phone-Number
Customer email-Short Text
Name: Book
System Usage: Input to order subsystem
Attributes

Isbn-Short Text
Author name-Short Text
Title-Short Text
Publisher name-Short Text
Publication year-Date
Binding-Short Text
Source number-Short Text
Retail price -currency
Number on hand-Number
Name: Order
System Usage: Input to order subsystem
Output to order the subsystem
Attributes
Order number-Number
Customer number-Number
Order date-Date
Credit card number-Number
Order filled-Short Text
Credit card expiry date-Date
Name: Order line
System Usage: Input to order subsystem
Output to order subsystem
Attributes
Order number-Number
Isbn-Short Text
Quantity-Number
Cost each-currency
Cost line -Short Text
Shipped-Short Text
Name: Publisher