1. operations, interfaces, performance, and quality assurance requirements

1.
Introduction 

This books management
system (BMS) is used to overcome the entire problem which they are facing
currently, and making manual system to computerized system. An online bookshop
software project that act as a central database containing various books in
stock along with their title, author and cost. This project is a website that
acts as a central book shop. A user visiting the website can see a wide range
of books in respective categories.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

1.1
Purpose 

 The purpose of this software is to manage the
books in the book shop. Generally, it includes the order processing and Stock Management.
We developed this software to maintain records of sales, purchase and staff
records. Requirements specification defines and describes the operations,
interfaces, performance, and quality assurance requirements of the Books
Management System. The user may select desired book and view its price. The
user may even search for specific books on the website. Once the user selects a
book, he then has to fill in a form and the book is booked for the user.  

1.2
Scope

The scope of my project
Books Management System is to record the details various activities of user.

·        
The
product provides the members with online booking of books capabilities and the
Books Management System is up running all the day.

·        
The
system provides login facility to the user.

·        
The
system allows the user to purchase books 24 hours a day.

·        
.customer
also be able to contact with admin.

·        
The
customer can purchase books quicker, easier, and convenient. 

.

·        
The
system will allow user to browse, search, select, and add books to a shopping
cart.

·        
A user
can search books with title and author.

·        
Many
types of categories are available in our site.

 

The document also
describes the non-functional requirements such as the user interfaces. It also
describes the design constraints that are to be considered when the system is
to be design.     

1.3
Definitions, Acronyms, and Abbreviations.

·        
OBMS – Online
Books Management System

·        
SRS –
Software Requirements Specification

1.4
References 

·        
IEEE
830-1998 standard for writing SRS document.

·        
Ian
Somerville, Software Engineering, Edition 10th.

1.5
Overview

 This SRS is organized into a couple major
sections. Section 2 provides an overall description of the system. Section 3
details the specific requirements of the system.

2.  The
Overall Description 

 

2.1 Product Perspective

        This product is an
entirely new product. It is not a component of a larger system. This system is
a replacement for the ordinary books management system which depend on paper
work for books record. Online books management system is a web application
where the customer can purchase books online. Through a web browser the
customers can search for a book by its title or author, later can add to the
shopping cart and finally purchase the books. 
   

2.2
Product Functions

    The following list of function
description explain the major features of online books management system.

 2.2.1. Account Registration

 The Registration
function shall allow the user to create secure accounts. The account will track
the user’s name, address and password.

2.2.2.
Account Login

 Account Login function should allow user to
enter their username and password. Once verified, users will be able to access
account history, purchase books online.

2.2.3.
Search  

The search function
shall offer users the ability to search for books by title and author.

2.2.4.
Books

The Books function
should contain various categories of books.

2.2.5.
New Releases

The New Releases
function add new books should be release.

2.2.6.
Children’s Books  

The Children’s Books
function contain children books.

2.2.7.
Islamic Books

The Islamic Books
function contain Islamic books.

2.2.8.
My Cart

The My Cart function
should allow users to save books in a list that are being considered for
purchase.

2.2.9.
Checkout

 Checkout function will be allow account user
to purchase books online securely.

2.2.10.
Contact Us

The contact us function
should allow users to see store address, telephone number, and email address.

2.3
User Characteristics

The users of the system
are members and the administrators who maintain the system. The members 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.   Friendly
user interface, online contact and user guide must be sufficient to educate the
user how to use this system without any problems or difficulties.

2.4
General Constraints 

·        
The
information of all the users and books must be stored in a database that is
accessible by the website.

·        
The
Online Books Management System is running 24 hours a day.

·        
Users
may access OBMS from any computer that has internet browsing capabilities and
an internet connection.

·        
The
users must have their correct usernames and passwords to enter into their
online accounts and do actions.  

2.5
Assumptions and Dependencies

·        
The
users have sufficient knowledge of computers.

·        
The user
computer should have internet connection and internet server capabilities.

·        
The
users know the English language, as the user interface will be provided in
English.

·        
The
search mechanism should be simple and fast.

3.  Specific
Requirements 

3.1 External Interface Requirements

The user should be
simple and easy to understand and use. Also be an interactive interface. The
system should prompt for the user and to login to the application and for
proper input criteria.

3.1.1 System Interfaces

Each part of the system interface
intends to be as user friendly as possible. The fonts and buttons used will be
intended to be very fast and easy to load on web pages. The system provides
good graphical user interface for the user the administrator operate on the
system, performing the required task and viewing the details of the books.

3.1.2
Interfaces

Various interfaces for the product
could be –

·        
Login
page

·        
Registration
form

·        
There
will be a screen displaying various kinds of books.

·        
If the
customer select the books then another screen of shopping cart will be opened.

·        
After
ordering for the product, the system will sent one copy of the bill to the
customer s Email address.

3.1.3
Hardware Interfaces

Operating system: windows 7 &
or latest windows

Hard disk:  40GB

RAM:  2GB

3.1.4
Software Interfaces

Development tool: HTML, PHP, etc.

Database: MySQL

 

3.1.5
Communications Interfaces

The web based application will be
opened over the internet. All information will accessible through web site. 

3.2 Functional Requirements

   3.2.1. stimulus: Click” Register” Button:
Account Registration

1.      The system shall allow a non-register user to
create a secure account.

2.      The system shall require the following
information from the user: Name, Password, Email address, phone number and
place address.

3.      The system shall ask the user for a user name
and password.

4.      The system shall confirm the user name and
password are acceptable.

5.      The system store all the information in the
database.

   3.2.2. stimulus: Click” Login” Button:
Account Login

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

2.      The system will require a username and
password from the user.

3.      The system will verify the username and
password, and the user will successfully logged in.  

    3.2.3. Stimulus: Click “search” Button:
Search

    1. The search function allow
the user to search books by title and author.

      2. The search results will be include, along
with title, author, price, and the availability of book.

   3.2.4. stimulus: Click” Cart” Button: My
Cart

1.     
The My
Cart function allow a registered and logged-in user to save books that are
being considered for purchases.

2.     
The
system viewing the shopping cart list, the system should display the total
price of the books in the cart.

3.2.5
stimulus: Click” Checkout” Button: Checkout

1.      The registered and logged-in user to purchase
books that are in their shopping cart.

2.      The books (titles, price and quantities) will
be displayed to the screen.

3.2.6.  stimulus:
Click” Contact us” Button: Contact us

1.      The contact us function allow a user to view
various methods of contacting the admin.

2.      The system display the store address,
telephone number, Facebook, twitter, and email address. 

 

3.3 Use Cases

 

Use
case for User:

 

 

Use
Case 2

Use
case for Admin:

3.4 Classes / Objects

 

3.4.1

3.4.1.1 Name, Password
and address

3.4.1.2 A non-register
user to create a secure account.

3.4.2

3.4.2.1
Username and password

3.4.2.2
A registered user to login to their account.

3.4.3

3.4.3.1 Books are
search by Title and author

3.4.3.2 The search
results will include a picture of the front cover, along with the title,
author, price, and the availability of the book.

3.5 Non-Functional Requirements

3.5.1 Performance

·        
The
system shall accommodate high number of books and users without any fault.

·        
Responses
to view information shall take no longer than 5 seconds to appear on the
screen.

3.5.2 Reliability

The system should
accurately performs customer registration, login, and search a books.

3.5.3 Availability

The system is online 24
hours a day, and 7 days a week.

3.5.4 Security

Users will be able to
access only their own personal information and not that of other users.
Purchases should be handled through a secure server to ensure the protection of
the user’s personal information. System will use secured database.

3.5.5 Maintainability

The system shall be
easy to maintain. Any updates or defects fixes shall be able to be made on
server side computers only without any patches required by the user.

3.5.6 Portability

The application is
HTML, PHP 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 use this system on any OS; either it is windows 7
or latest window.

The system shall run on
PC, Laptop, and tablet etc.     

3.6 Inverse Requirements

          NULL

3.7     
Logical Database Requirement

·        
Database
will valid for this project.

·        
Our
database keeps all records of our records.

·        
User
can’t interfere in database.

·        
The data
should not be duplicate.

·        
It
maintain the record of efficiently.

3.8     
Design Constraints

·        
All
mandatory fields should be filled by customer, while buying the books from the
cart.

·        
 Customer data will store in database.

·        
All the
inputs should be checked for validation and messages should be given for the
improper data. The invalid data are to be ignored and error messages should be
given.

3.9 Analysis Models

4.1 Sequence Diagrams

 

 

4.2 Data Flow Diagrams
(DFD)

4.2.1
Context level diagram:

 

 

4.2.2
1 AND 2 LEVEL DFD:

 

 

4.3 State-Transition Diagrams (STD)

x

Hi!
I'm Rita!

Would you like to get a custom essay? How about receiving a customized one?

Check it out