0% found this document useful (0 votes)
16 views

Project Report

This document provides a software requirements specification for an online bookstore management system. The system will allow users to create accounts, search for books, add books to carts, purchase books online, and view purchase histories. It will also include functions for account login/logout, updating account information, reserving books, and contacting customer support. The system is intended for any users with internet access and will operate on devices running modern web browsers and Windows XP or higher. Security and usability constraints include unencrypted credit card transactions, lack of password recovery, and unrestricted delete operations.

Uploaded by

NTM SOFT
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
16 views

Project Report

This document provides a software requirements specification for an online bookstore management system. The system will allow users to create accounts, search for books, add books to carts, purchase books online, and view purchase histories. It will also include functions for account login/logout, updating account information, reserving books, and contacting customer support. The system is intended for any users with internet access and will operate on devices running modern web browsers and Windows XP or higher. Security and usability constraints include unencrypted credit card transactions, lack of password recovery, and unrestricted delete operations.

Uploaded by

NTM SOFT
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Software Requirement Specification

For
Online Book Store Management

Prepared By:

Muhammad Ali (18514)


Haroon Akram (16711)
Abdual Manan (19909)
Submitted To:

Muhabbat Ali
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
Introduction

1.1 Purpose

The purpose of this Software Requirement Specification (SRS) is to document the


specification andrequirement of Book Store Management System.

1.2 Document Conventions

This SRS is written in the Arial font with the size 11 in italics, and Times font with the
size 14 for bullet points. The priorities of higher level requirement are inherited in detailed
requirements.

1.3 Intended Audience and Reading Suggestions

The audience of this software is the client who want the software to be built and the
development team. Website Administrators, Customers etc.

1.4 Product Scope

The objective of this project is to create and implement a software for the Bookstore. It is
being produced for the customer who want to sell the books through online .This software
will allow user to create its personal account, search the books and secured online
purchase of books. User of this software will also contact with the administration of the
software.

1.5 References
The following material was used in this document:
• IEEE version 1.0, IEEE recommended for Software Requirement Specification.

2. Overall Description

2.1 Product Perspective

This product is entirely new product. It is not a component of large system. It provides
the facility ofonline transaction, credit card transaction. You can purchase books online
and this website is available for those who are using internet .It also record the quantity
of books available for sale .This system will also interact with the database to store all the
records.

2.2 Product Functions

The following function explain the major features of Book Store Management System.
2.2.1 Account Registration
The account will track the user’s name address, credit card information, username
andpassword.
This provide security to the user by creating an account that is password protected. This
functionassures the user only has the to enter the information required for creating an
account.

2.1.1 Account Login


The account login function allow user to enter their username and password. Once account
is verified user will be able to access account history, purchase books online and update
their account information.
This function provide the restricted operations to user.

2.1.2 Search
The search function will offers user the ability to search for books by title, author, subject.
This offers a way to find a book if the user does not have complete information about
it. It alsoprovide the price and availability of books.

2.1.3 Add To the Shopping Cart


This function offers the user to store books of their interest online and allow the
continuation of shopping.

2.1.4 Delete From Shopping Cart


This function will allow user to change their orders and not to be forced to purchase the
books.
2.1.5 Reserve Book
This offers assures the user by allowing them to make sure a book will be in stock for
immediate pickup. This also offers the convenience to the user who are unable or
unwilling to give credit card information over the internet.

2.1.6 Contact Us
This help the user to gain trust in the bookstore by showing how easy it is to have person
to personbook store employee.

2.1.7 Update Account Information


This offers convenience to the account members by allowing them to make changes to the
accountinformation.

2.1.1 View Account Purchase History


This function allows user to see previous purchase made under their usernames.
This function provide convenience to the user by allowing them to easily view purchase history.

2.1.2 Account Logout


This function will allow user account member to exit their account for security purposes.
This allows user to exit their account , and prevent others from accessing it.
2.1.3 Help
This help function will give the overview of how to use different functions .
This allows the user to get answer to immediate questions on using the system.

2.2 User Classes and Characteristic

This Book store provide the facility of online purchase, so the user is simply the anyone
that has access to the internet and a browser. It is assume that the user is familiar with the
computer to operate the browser. User of this website must possess the minimal education
which conforms theentrance standards, and comfortable with English. User of the website
must know how to navigate in a website.

2.3 Operating Environment

The system will work on any hardware device having an internet connectivity and browsers to
browse the website. The browser should be up to date to run various features of the website. The
system will not run on OS below Windows XP.

2.4 Design and Implementation Constraints

This system will interact with the database and database may store passwords in plain
text, and does not need to be password recovery feature nor lockout after invalid password
attempts. The system may not work correctly when security is concerned. It include lack
of encrypted connection when sending credit card information and forcing user to use
strong password. To reduce the complexity of the system, there is no check on delete
operation. The administrator should be very careful before editing of any product.

2.5 User Documentation

User Manuals:
A user manual will be provided to the staff in pdf form and outline the detail of system
function.

Online Help:

System documentation will also be available online,it will include the user
manual,FAQsection etc.

Installation Guides And Read Me files:

Installation guide will be provided as a part of read me file which is included as a text file.

2.3 Assumptions and Dependencies

This Book store provide the online service to its users and is only accessible through the
internet .Itis assumed that its end user is connected to the internet .It is also assumed
that the user has aweb browser able to display this system/website. User assumed that
this website is working properly and allow the system to perform all the communications
with the client. The manager can not be a customer.The login ID and password must be
created by the system administrator and communicated to the user to avoid unauthorized
access to the system.

3. External Interface Requirements

3.1 User Interfaces

This system will provide the ability to students and teachers to access the bookstore
online. There will be three different user interfaces that will accompany this
system/website: the students,teachers and administrators.
• Customer will be able to search books without having login, they must be login
to perform any transaction. These transaction include reserving , purchasing,
viewing and changing their online account. Customer must required login in
order to perform any transaction.
Once logged make any changes to the personal account .
• Administrator will be required to login all the time. The administrator will have
to login to the host machine inside the book store network in order to build reports
and ensure backups are running. Administrator will be able to add/delete books
to be displayed to the
user, and change the information on any book as required. He will also able to
check the availability of books in the stock.

3.2 Hardware Interfaces

There are no special hardware interface requirement.

3.3 Software Interfaces

There are no special interface requirement.

3.4 Communications Interfaces

There are no special communication interface requirement.


4. System Features
Use Case Diagram Of Online Book Store Management System:

4.1 Account Registration

4.1.1 Description and Priority


This function allow user to create secure accounts.
The account will track the user’s name ,address, credit card information, username and
password.This provide security to the user by creating an account that is password
protected. Thisfunction assures the user only has the to enter the information required for
creating an account. The user’s name, address, credit card information and password are
provided by the customer/user.When the user account is created the user is able to access
all the functionalities provided by the system.
4.1.2 Functional Requirements

Stimulus: Click “Register” Button


1. The system shall allow a non registered user to create a secure account.
2. The system shall require the following information from the user:
name, Address,Credit Card Information.
3. The system shall ask the user for user name and password.
4. The system shall store the information in database.
5. The system must confirm the username and password are acceptable.
4.2 Account Login

4.2.1 Description and Priority

The function allowthe registered user to login to his account . If the user is not registered
the website should allow user to create account first .The system will check the user name
and password, when user attempts to login .Once account is verified user will be able to
access account history, purchase books online and update their account information.
This function provide the restricted operations to user.

4.2.2 Functional

Requirements
Stimulus: Click

“Login” Button

1. The system shall allow a registered user to login to their account.

2. The system shall require a user name and password from the user.

3. The system will verify the username and password and user will be
considered“logged in”.

4.3 Search

4.3.1 Description and Priority

The search function will offers user the ability to search for books by title, author,
subject.Thisoffers a way to find a book if the user does not have complete information
about it. It also provide the price and availability of books.

4.3.2 Functional

Requirements

Stimulus: Click

“Search” Button

1. The system shall allow a user to search for books by title , author, subject.

2. The search result will include the picture of front cover , along with the title
,author ,price
,availability and condition of book.

4.4 Add To the Shopping Cart


4.4.1 Description and Priority

Add to the shopping cart function will allow the user to temporarily store books in a list
and considered for purchase. This function offers the user to store books of their interest
online and allow the continuation of shopping

4.4.2 Functional Requirements


Stimulus: Click “Add To Shopping Cart” Button
1. The system will allow user a registered and logged-in user to temporarily saved
book that are being considered to purchase into a list associated with their account.
2. When viewing the purchasing list the system will show the total price of book in the
cart.

4.5 Delete From Shopping Cart

4.5.1 Description and Priority


Delete from the shopping cart will allow user to delete unwanted books from the
cart.
This function will allow user to change their orders and not to be forced to purchase
the books.
4.5.2 Functional Requirements
Stimulus: Click “Delete To Shopping Cart” Button
1. The system will allow user a registered and logged-in user to temporarily delete
unwanted book from their shopping cart.
2. The system will provide the user a way to select one of the book from his/her cart
for deletion.
3. After the user has indicated that particular book to be deleted from their shopping
cart, the list which store the shopping details should be updated and show the
remaining book in thecart.

4.6 Reserve Book

4.6.1 Description and Priority

This function will hold the books for 7 days that will purchased and picked up at the book
store . This offers assures the user by allowing them to make sure a book will be in stock
for immediate pickup. The system will display the available books in the store . The user
selects from the available books in the store and confirm the selected book. This also
offers the convenience to the user who are unable or unwilling to give credit card
information over the internet.
4.6.1 Functional Requirements

Stimulus: Click “Reserve” Button


1. The system will allow registered and logged-in user to to reserve a book to be
picked upat the bookstore within 7 days.
2. The user must enter a name, mailing address , phone number ,and email address.
3. The items in the user shopping cart will be placed on reserve, and removed from
the user’sshopping cart.
4. The user must be given a conformation number.
5. The selected books are no longer available to any other customer.

4.7 Contact Us

4.7.1 Description and Priority

This function gives the user the store address, telephone number, email address and
location on map. This help the user to gain trust in the bookstore by showing how easy it
is to have person to person book store employee.
4.7.2 Functional Requirements

Stimulus: Click “Contact Us” Button


1. The system will allow a user to view various methods of contacting the store.
2. The system will display the store address, telephone number, email address, and
directionson how to get to the store.
3. The system should also display a map showing the location of the store.

4.8 Update Account Information

4.8.1 Description and Priority

This function gives access to the user to edit their stored account information.This offers
convenience to the account members by allowing them to make changes to the account
information. The user change his/her name, email ,password. The account changes is
made by user. The user must have an account with the website and must be logged-in and
prior to access his/her account.
4.8.2 Functional Requirements

Stimulus: Click “Update Account Information” Button


1. The system will allow a user to update the information in their account.
2. The user will be allowed to view and change their name, mailing address, billing
address, creditcard type, credit card number, expiration date, and security code.
3. The user will be able to change their password by entering the old one once
4.9 Account Logout

4.9.1 Description and Priority

This function will allow user account member to exit their account for security purposes.
This process will save all the user operations when he/she will exit the website. He/ She
must login again to access users features. This allows user to exit their account ,
andprevent others from accessing it.
4.9.2 Functional

RequirementsStimulus: Click

"Logout" Button

1. The system shall allow the registered and logged-in user to exit his/her account, so
that accessto operations requiring a user to be logged in are now disabled

4.10 Help

4.10.1 Description and Priority

This function will give the overview of how to use different functions .This allows the
user to get answer to immediate questions on using the system.

4.10.2 Functional Requirements

Stimulus: Click "Help" Button

1: The system will allow the user to view an overview of how to used various.

2: The system must allow the user to select one of the operations by name.

3: The system will then display information on how to use that operation.

5. Other Nonfunctional Requirements

5.1 Performance Requirement

The performance requirement are as fallows:


• System login/logout takes less than 5 seconds.
• Searches will return result within 10 seconds.
• Orders shall be processed within 10 seconds.
• System shall support 10,000 simultaneous users.

5.2 Safety Requirements

The password should be visible while typing. The system should use a secure connection
to connect with the credit card processing system.

5.3 Security Requirements

User will be able to access their own personal information and not that of others users .
The user require a user name and password to login in to the system .The buyer can not
buy books without logging . Purchases will be handled through a secure server to ensure
the protection of user’s credit card and personal information.

5.4 Software Quality Attributes

Quality Attributes of the system is as follows:

5.4.1 Reliability
The average time to failure is 60 days . In the event server does crash ,a backup server
will be up and running within in 1 hour.

5.4.2 Availability
This online Book store will be available to users 24 hours a day, 7 days of week, with the
exceptionof down for maintenance no more than one hour a week. If the system crashes
it should be backupwithin one hour.

5.4.3 Maintainability
Any defects or updates fixes shall be able to be made on server side computers without
any patches required by users.

5.5 Business Rules

The business rules are as follows:


• The administrator can not be a customer.
• The administrator can not access the buyer personals information.
• The administrator will receive notification from the credit card processing
system to processthe order and confirm payment of order is received.

6. Other Requirements
None.
Zero Level:

First Level Diagram Of Online Book Store Management System:


Second Level Diagram Of Online Book Store Management System:

You might also like