Book Store Management System
Book Store Management System
Book Store Management System
1.Introduction :-
1.1Purpose :-
1.2Scope :-
The software provides both the customer and the merchant his PIN number which is
unique.
The software will not provide the following facilities to the customers :
Cannot reserve the product for more than two days
Cannot reserve more than two products
Responsibility of damages
2
The product cannot be changeable when once confirmed
The objective of this software is to provide easy assistance to both the customer as
well as the merchant with proper database and information.
1.4References :-
3
1.5Overview :-
4
The entire srs is documented in view of both customers and the merchant and the
following sub sections are arranged to give a complete outlook of the software, its
perspective, features, system requirements and users know how’s.
5
6
SCREENSHOTS OF THE PROJECT
7
8
9
10
11
12
13
14
2.Overall description:-
In this module we define the overall description of the software e-BOOK SHOPPING
Like the importance of the product, what are the user characteristics, what are the
general constraints and assumptions and dependencies?
2.1Product 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, naive as well as experienced users of the computers.
2.2Product functions :-
The following use case diagram provides complete information regarding how the
product works
15
16
17
2.3.User characteristics :-
2.4.General Constraints :-
The product assumes that the users don’t opt for the same product number
simultaneously.
Cannot support multiple user interfaces.
The bookshop’s database should be accessible in real time.
18
The bookshop’s database will be modified to identify accounts.
3.Specific Requirements:-
3.1.1.User Interfaces :-
The software provides good graphical interface for the front end of the database and a
good informative interface for the rear end.
The system users are:-
The bookshop management as system administrators.
Bookshop cashiers as normal users.
System Administrators
System users
System users are the ones who at the cashier and do transactions with customers.
The users have to enter the user name and password and click on ‘Login’ button.
If user makes any mistake the system will ask for the correct username and
password until he enters the correct one.
When the user wants to do any transaction user has to click on the menu icon on
the main menu. Then the transaction window will open. User has to enter the
Book No and press enter. Then user has to select the transaction type and the
19
quantity. Then click on the update button. Then the system will automatically
update the database according to the transaction type.
Hardware Interfaces
3.1.2.Hardware Interface :-
3.1.3.Software Interfaces :-
The software requires the support of the following softwares for the database and
other requirements
HTML ,JDK and html editor for web interface
MySql for database
20
Server(windows 2000,apache or…)
3.1.4.Communication Interfaces :-
3.2.Functional Requirements :-
Basically there are three modules in this system which are ,the source of input,
for processing of input, to give out the relevant output.
3.2.1.Module 1:-
3.2.1.1.Functional requirement:-
o Customers
o Merchants
o Database administrator
The processing is:-
Customers:-
Do shopping
Reserve products
o Merchants:-
Bid their products
21
Manage transport facility and look after the payment method
Database administrator:-
Update information
Honest transactions
The output is based on the transactions, and the work done by the user like
customer or merchants.
3.3.Performance Requirements :-
Good working pc with all the requirements as stated in the hardware interfaces
Works for medium size information databases
Should not be overloaded
The response time for menu changes will not be more than 3 seconds.
The time for search a book will not be more than 3 seconds.
The time to print the stock evaluation will not be more than 3 seconds.
The time taken to update the database or to get information from the database
will not be more than 2 seconds.
The time taken to prompt the massage box will not be more than 2 seconds.
3.4.Design Constraints:-
22
Java programming environment has been used for secure transactions and
protection from viruses, worms, and other threats like hacking of passwords by
hackers.
While designing this product fault tolerance and standard compliance are kept
in mind.
The system is based on menu driven interfaces. Menu selection will be done by
using mouse or by keyboard.
Confirmation messages on taken action, input acceptance and error condition
will be displayed after each input.
Error messages will be displayed at the time of detection of input errorand the
system errors.
3.5.Attributes :-
23
3.6.Other requirements:-
24