Requirement Gathering

REQUIREMENT GATHERING *the system should help customer, query the availability of a book either by using the book title or by using the name of author or publisher. * If a book is in stock, the exact number of copies available should be displayed. *If a book is not in the stock, the query for the book is used to increment a request field for the book. * the software should maintain the price of various books. * As soon as customer selects his book for purchase, the sale clerk would enter the book_id number of the books. The product should update the stock and generate the sales receipt for the book. * the software should allow employees to update inventory whenever new supply arrives. Also upon request by the owner of book shop. * the software should generate sales statistics (viz, book name, publisher, book_id number, number of copies sold and the sales revenue) for any period. * The sales statistics will help the owner to know the exact business done over any period of time and also determine the inventory level required for various books.

1.Introduction PURPOSE: This document describes the software requirements specifications for BOOKSTORE BILLING SYSTEM , specifically developed to automate all operations in a bookshop. The purpose of the software product is to aid book store customers and owners to manage their book purchases and sales with regard to simplifying and speeding up the process of selection, ordering and purchasing books for customers as well as managing a database of users and a database of products for book store owners through a conveniently designed Graphical User Interface which will utilize a user-friendly intuitive design approach. The system will be designed to be used by book store customers with little or no experience in using computerized systems and by book store owners who will be trained to use the product.

SCOPE: The name of the product Bookstore billing automation system. The main function of the software will be to aid book sales for both customers and the store owners. Generally it includes the Order Processing, Stock Management and Accounts Management. The system will be therefore designed to allow a user to perform the following functions: User Identification Check for availability of book Search for existing books. Update stock. Generating bill. Generate purchase report. Generate sales statistics.

Overview : The following subsections provide the complete overview

of

requirements

the

software

documentation

for

specifications the

product

Bookstore billing automation system . The entire SRS is documented in view of both customers and the administrator and the following sub sections are arranged to give a complete outlook of the software, its perspective, features, system requirements and users know how.

2.General description Product perspective This software is totally self contained and works relatively as efficient as other packages related to the subject. It provides simple database rather than complex ones for high requirements and it provides good and easy graphical user interface to both new, naïve as well as experienced users of the computers.

User Characteristics: *The users (Book shop officers) should have a basic computer literacy to work with a computer. * The users of this software should be well trained and should be given the relevant user documentation, reference materials and instructions. * The user should be able to follow simple instructions given by the system. General constraints * The users must have their correct usernames and passwords to enter into the bookstore.

Assumptions and dependencies * The users have sufficient knowledge of computers. * The users know the English language, as the user interface will be provided in English.

3. Specific requirements Functional requirement: USE CASES:

Use_caseID

001

use_caseName

User identification.

Actor

User

Main-success scenario

the user enters the name and the password.if user registers ,the main menu opens up , else, administrator account opens up.

Normal flow

User registers

Precondition

User enters password.

Postcondition

Main menu opens up.

Alternate flow

Administrators registers, administrator’s account opens up. 007

Exception

Invalid UserId and password 014

Reference

the

Use case 002

username

and

Use Case Id

002

Use Case Name

Change Password

Actor

Administrator

Main Success Scenario Application ask user to change Password Normal Flow

User Changes Details

His

Precondition

User Enter Valid entry At Identification Page

Post Condition

Main Menu Opens

Alternate Flow

User Didn’t Change The Details 003

Reference

003

Use_caseID

003

use_caseName

Main menu

Actor

User

Main-success scenario

User is provided various options to perform different operation. Depending on the operation selected by the user,corresponding operation is performed.

Normal flow

The user selects ‘search’.

Precondition

User registers using valid username and password.

Postcondition

search form opens up.

Alternate flow

The user selects ‘sale book’. 006

Reference

Use case 004.

Use_caseID

004

use_caseName

Search page.

Actor

User

Main-success scenerio

The user enters the details of the book, depending on the search category selected by the customer i.e.

1.author. 2.book title. 3.publisher. The book details are dispayed.(book name.book id,no of copies available). Precondition

User selects the ‘search’ option in the main menu.

Postcondition

Book availability details opens up.

Alternate Flow

user cancels the search and returns to main menu 003.

Exception

Search entry is invalid 013

Reference

use case 005

Use_caseID

005

use_caseName

Book availability details.

Actor

User.

Main-success scenerio

If the customer selects to purchase the book,user proceeds with the sales transation,else returns to the main menu or opt for another search.

Normal flow

Custormer chooses to purchase the

book. Precondition

the user enters the details of the book to be searched.

Postcondition

sales page opens up.

Alternate flow

1.

2.

reference

Customer asks for another search 004. Customer unsatisfied,thus system returns to the main menu 003

Use case 006.

Use_caseID

006

use_caseName

Sales page

Actor

User

Main-success scenerio

User enters the bookid and number of books to be purchased. Bill generated. Customer pays the amount.

Precondition

Customer chooses to purchase the book.

Postcondition

Main menu opens back.

Alternate flow

Customer refuses to purchase and returns to main menu 003.

Exception

Bookid is not valid 013

reference

Use case 003

Use_caseID

007

use_caseName

Administrator account.

Actor

Administrator .

Main-success scenerio

The administrator selects one among various operation provided at his end and further operation proceeds depending on the operation selected.

Normal flow

He chooses to purchase book.

Precondition

The administrator registers entering his username and password.

Postcondition

Purchase page opens up.

Alternate flow

He selects either of the following: 1.sales report(010). 2.purchase report.(011). 3.view database.(012).

reference

Use case 008.

Use_caseID

008

use_caseName

Purchase page

Actor

Administrator

Main-success scenerio

The administrator from supplier.

purchases

books

Pays amount to supplier. Updates stock in the inventory. Precondition

The administrator choose to purchase books from the supplier.

Postcondition

Update page opens up.

Alternate flow

Administrator cancels the current transaction and returns to administrator end 007.

reference

Use case 009.

Use_caseID

009

use_caseName

Update stock.

Actor

Administrator

Main-success

The admistrator enters the details of

scenerio

new books into the database updates the books database.

Precondition

Administrator purchase books form the supplier.

Postcondition

Administrator’s menu opens up.

reference

i.e.

Use case 007.

Use_caseID

010

use_caseName

Sales report

Actor

Administrator.

Main-success scenerio

Report generated containing details of sold books,amount,sales revenue.

Precondition

‘sales report’ administrators’s end.

Postcondition

Administrator’s end menu opens up.

reference

Use case 007.

Use_caseID

011

use_caseName

Purchase report.

Actor

Administrator

selected

at

Main-success scenerio

Administrator generates the purchase report containing details of purchase id,date and amount.

Precondition

Administrator selects purchase report at his end.

Postcondition

Administrator’s end menu opens up.

reference

Use case 007.

Use Case Id

012

Use Case Name

View Data Base .

Main success scenario.

The administrator selects to view the complete book database.

Actor

Administrator

Precondition

Administrator selects the ‘view database’ option.

Post condition

Book database opens up.

Reference

007

Use_caseID

013

use_caseName

Invalid Book_id

Actor

User

Precondition

When the user makes an invalid entry in the search form.

Postcondition

Search page opens back.

Alternate Flow

Sales Page Opens :- 006

reference

Use case 004.

Use_caseID

014

use_caseName

Invaliduser

Actor

User

Normal flow

User enters invalid name an password.

Precondition

User enters password

Postcondition

User identification page re-opens.

reference

invalid

Use case 001 .

Non-functional requirement

username

and

Performance Requirements: *The response time for menu changes will be not more than 3 seconds. *The time for search for a book will not more than 3 seconds. * The time to print the stock valuation will not be more than 3 seconds. *The time taken to update the database or get information from the database will not be more than 2 seconds. * The time taken to prompt message boxes will not more than 2 seconds

Design Constraints: The system is based on menu driven interfaces. Menu selection will be done by using the mouse and the key board keys. * Confirmation messages on taken actions, input acceptance and error conditions will be displayed after each input. *Error messages will be displayed at the time of detection of input errors and the system errors. *

Other requirements: Security - Only the administrators have the authority to edit details in Users and Items tables. No One can enter the system without a username and a password. Normal system users cannot access the Administrators login. All deleting actions are notified by a message box asking to confirm deletion. Robust Error Handling: - The errors and undesirable situation, generated through the user intervention, are handled successfully to ensure that the system operates without halting by providing the appropriate error messages to the user.

User Friendly Environment: – Graphical user interface is used for easy handling of the system. A user can use the system efficiently without meeting any difficulty.

System Interface:The Software provides good graphical interface for the front end of the data base and a good informative for the rear end. Hardware Interface:The system should have these hardware requirements: •

The

processor

should

be

at

least

Pentium

for

windows

and

powermac for macOS or above. •

The processor speed should be greater than 456 MHz.

•

RAM should be or greater than 128 MB.

Software Interface:The Application requires the support of the following software’s for the database and other requirements •

JDK

•

Mysql 5.0

•

Server (windows Pentium or above…)