A PROJECT ON ONLINE BOOKSHOPPING SYSTEM

Submitted By:

Submitted To

Online BookShopping System

1. Problem Definition & Statement------------------------------------------------------------------------------------3 1.1 Problem definition------------------------------------------------------------------------------------------------3 1.2 Problem statement------------------------------------------------------------------------------------------------3 2. Software requirement specification----------------------------------------------------------------------------------2.1 Use cases diagram----------------------------------------------------------------------------------------------4 2.2 Entity Relation diagram------------------------------------------------------------------------------------5-6 2.3 Data Flow diagram--------------------------------------------------------------------------------------------07 3. Class Diagram---------------------------------------------------------------------------------------------------------08 4. Object Diagram-------------------------------------------------------------------------------------------------------09 5. Component Diagram-------------------------------------------------------------------------------------------------10 6. Deployment Diagram-------------------------------------------------------------------------------------------------11 7. Sequence Diagram----------------------------------------------------------------------------------------------------12 8. Collaboration diagram-----------------------------------------------------------------------------------------------13 9. Activity Diagram------------------------------------------------------------------------------------------------------14 10. Staechart Diagram--------------------------------------------------------------------------------------------------15

1. Problem definition & statement

1.1 Problem Definition

The current project emphasizes on analysis and design of an online bookshop system. That serves the customer needs. The customers available activities in the proposed system from logging on the browsing the book store, selecting items and making purchase are described.

1.2 Problem Statement

. As a young promising student you are tasked with developing an online book shop system. The system should be competitive enough by providing the facilities/options that are currently provided by reputed systems like Amazon.com and BN.com.The proposed system should allow the customer with activities from logging on to the system, browsing the book store, selecting items and making purchases i.e., the customer will be able to browse, select and buy books online. An internet customer should have a login to access the book store. Registration of the customer with the book shop is primary. A registered customer can browse through the book catalogue and can make selections. The new system should even assist the customer in locating a book in that, the customer can browse the current book catalogue online and this should detail the book details and stock details for the books. The user should be able to filter by book title, author and book category. If the user cannot find a Book in current category. They should place an order and request the book. This Includes details like Author, Publishers, Title, Book Name and Category.The payment is done through credit card and also throughgift cheques etc., the customer is informed about the transactiondetails through emails. The shipment details are entered by the customer and through those details the delivery is processed.

2. Software requirement specification 2.1Use cases diagram

<<in d >> clu e <<in d >> clu e lo in g p ssw rd a o <<in d >> clu e C sto e u mr ca lo ta g list o b o f o ks id

se ct b o le o k <<in d >> clu e

o ebo rd r o k

<<in d >> clu e fill a p tio p lica n

cre it ca /d b ca n . d rd e it rd o

B n Ag n ak et

v lid te b a a ill

p yb a ill

O lin B o o n e o ksh p

d liv r b o e e o ks

For this system, we identified two actors customer, Bank agent and Online Bookshop of the system. Customer has four use cases which include other use cases. 1. The first one is login:-Login is used to enter into the system .It is basically used to check the users authentication. It includes id and password. 2. Catalog:-catalog is basically is place where the entire books lists are available. 3. Select book:-It is used to select book from catalog. 4. Order book: - It is used to order book by filling the application and then paying the bill through credit card/debit card.

Bank Agent:-Bank agent has two use cases which include other use cases .
First is:-Validate bill:-It is used to validate the bill that is paid through credit card/debit card. Pay bill:-It is used to pay the bill through credit card/debit card. Online bookshop has one use case i.e. delivers books:-After all the process of select a book from catalog, fill the application, pay the bill is confirmed the book is delivered to the customers.

2.2 Entity Relation diagram

For this system, we identified seven entities. Customer, which is identified by its id, name, email_id, contact no etc. Books which is identified by its Book_ISBN, name, edition, Author, Price no_of _opies, publishers etc. Supplier which is identified by its id, email address, contact no., publication, name. Sale_Record which is identified by its Book_IsBN, Amount_Paid, Discount, price, id, no_of_copies. Sales which is identified by its Invoice_no, balance, sales_id, customer_id, amount_paid, date. User which is identified by its name, address, login, password etc. Purchase record which is identified by its Amount_no_pay, no_of_copies, Book_IsBN, purchase_id, price.

2.3 Data Flow diagram.

CLASS DIAGRAM

O n lin e B o o k s h o p nam e w e b s it e lo c a t io n d e li ve r b o o k s () o ffe rd is c o u n t s ( )

B ooks A p p lic a t io n d e t a ils o fc u s t o m enr a m e a u th o r a p p lic a t io n n o 1 * t y p e o fp a y m e n t p ri c e m a i n t a in b o o k s in fo ( ) n u m b e ro fc o p ie s e d it io n n o s t o r e c u s t o m e r d e t a il s (b)o o k n a m e re c e ive a p p in fo ( ) 1 * d is p la y ( ) c h e c k c re d it va li d a t i o n () e t in fo rm a t i o n ( ) r e a d () g 1 m o d ify () S e rve r ip a d d re s s c o n fig u ra t io n

C u s to m e r nam e a d d re s s phoneno

B ank A gent nam e ac c ountno

va lid a t e c r e d it c a rd () b u y b o o k s () s e n d in fo t o s e r ve r() * r e a d b o o k s ()

OBJECT DIAGRAM

Nam e:A B C B ook s tall o:onlinebook s hop webs ite:abc book s @ online. c om loc ation:B anglore

s :s erver

b:bank agent

Ipaddres s :13.12.1.12.343 c onfiguration:Intel b1:book s

Nam e:Haris h A c No:30121014 201

c :c us tom er

Nam e: Introduc tion to UM L A uthor:G raham G ooc h

a:applic ation

Nam e:S atis h A ddres s :Naras araopet P hNo:9965321457

P ric e:250.00 E dition NO :6

Details :S ai from N RT A pplic ationNo:12445

COMPONENT DIAGRAM

deliver book s to the des tinat ion

o nlinebook s hop.ex e

boo k s .ex e

c ontains the lis t of book s that are for s ale

buy book s or read book s

c us tom er .ex e

s erver.ex e

c ontains the databa s e of all book s and t ran s ac tio ns

bank agen t .ex e

c hec k s w hethe r t he c redit c ard is valid or not

10

DEPLOYMENT DIAGRAM

< < D e vic e > > Te rm ina l D elive r b o o k s < < P roc e s s o r> > O n line B o o k S h o p B uy book s

< < P roc e s s o r> > C u s to m er < < D e vic e > > R aid

< < P roc e s s o r> > S e rve r

< < D e vic e> > C lie n t Te rm ina l M a int ain s lis t of tra n s ac t ion s

11

Sequence Diagram.

c.customer

o.onlinebooksh op

b.bankagent

s.server

b1.books

a.application form

enter website login catalog generate list of books select books order books generate application form fill details submit

get credit card no validate credit card pay bill

receive book details deliver book

12

Collaboration diagram.

c .c u s to m e r 1 4 : d e live r b o o k

o . o n l in e b o o k s h o p

b .b a n k a g e n t

8 : fi ll d e t a i ls 1 : e n t e r w e b s it e 5 : s e le c t b o o k s 2 : lo g in 3 : c a t a lo g 6 : o rd e r b o o k s 9 : s u b m it 1 3 : re c e ive b o o k d e t a i ls 4 : g e n e r a t e lis t o f b o o k s 7 : g e n e r a t e a p p lic a t io n fo r m

1 0 : g e t c re d it c a rd n o

1 1 : va lid a t e c re d it c a r d 1 2 : p a y b ill

a . a p p li c a t i o n fo r m

b 1 .b o o k s

s . s e r ve r

13

Activity Diagram

Browse the site

Search for Catalog

Select book

Fill Order Form

Enter Creditcard Number

Valid submit OrderForm Invalid Deliver Books

14

State chart diagram.

idle

login activ e

search list of books

select book

order book logout fill application credit card inv alid credit card/debit card no

creditcard v alid submit

15

SOFTWARE REQUIREMENTS SPECIFICATIONS

16

Table of Contents 1. Introduction------------------------------------------------------------------------------------------------------------18 1.1 Purpose------------------------------------------------------------------------------------------------------------18 1.2 Scope---------------------------------------------------------------------------------------------------------------18 1.3 Definitions, Acronyms and Abbreviations--------------------------------------------------------------------18 1.4 References---------------------------------------------------------------------------------------------------------18 1.5 Overview----------------------------------------------------------------------------------------------------------18 2. Overall description-------------------------------------------------------------------------------------------------------------------------------20 2.1 Product perspective----------------------------------------------------------------------------------------------20 2.2 Product functions--------------------------------------------------------------------------------------- ---------20 2.3. User characteristics----------------------------------------------------------------------------------------------21 2.4. General Constraints------------------------------------------------------------------------------------ ---------21 2.5. Assumptions and Dependencies---------------------------------------------------------------------------------------------------------21 3. Specific Requirements-------------------------------------------------------------------------------------- ---------21 3.1 External Interface Requirements----------------------------------------------------------------------------------------------------------21 User Interfaces -----------------------------------------------------------------------------------------------------------------21 System Administrators-------------------------------------------------------------------------------------------------------21 System users--------------------------------------------------------------------------------------------------------------------21 3.1.2. Hardware Interface ----------------------------------------------------------------------------------------------------------------21 3.1.3. Software Interfaces -----------------------------------------------------------------------------------------------------------------21 3.1.4. Communication Interfaces --------------------------------------------------------------------------------------------------------21 3.2. Functional Requirements --------------------------------------------------------------------------------------21 3.2.1. Module 1---------------------------------------------------------------------------------------------------22 3.2.1.1. Functional requirement----------------------------------------------------------------------------------------------------------22 3.3. Performance Requirements-------------------------------------------------------------------------------------22 3.4. Design Constraint------------------------------------------------------------------------------------------------22 3.5. Attributes ---------------------------------------------------------------------------------------------------------22 Reliability -----------------------------------------------------------------------------------------------22 Maintainability------------------------------------------------------------------------------------------22 Security -------------------------------------------------------------------------------------------------22 3.6. Other requirements----------------------------------------------------------------------------------------------22

17

1. Introduction:The Bookshop Automation System is to automate all operations in a bookshop. Generally it includes the Order Processing, Stock Management and Accounts Management. Before automating a bookshop we have to understand the concept of automation. In automation of any operation we make a system which do work automatically as the respective events occurs, for which it is meant. There are the some common examples of the automation like that auto pilot system in the aircraft, automatic home systems (electric system, water system, fire alarm system, doors system etc). These are best examples of the automation systems. Here we are try to develop such type system which is provide the automation on the any type of the bookshop. That means a shop which has the type system which provides the facility to the customers of the shop to purchase the books from the shop without any complexity. For example any customer want to purchase any book from the shop than first of all customer just choose the stream of the book than he/she can see the more then one type of books there and than he/she can choose the specific book from there. And then purchase it by paying price on bookshop cash counter and receives its invoice.

1.1 Purpose:Almost every activity in the world today is controlled by computer driven software programs. His trend was first accommodated by engineering applications in the past. However, as the life style became more and more complex, every area of human interactions was invaded by various Software systems, such as real time, business, simulation, embedded, web based, personal and more recently, artificial intelligence software etc. According to the above facts, managing and maintaining a book shop could also be controlled by efficient software. This project focuses attention on designing efficient and reliable software which controls the transactions of a bookshop. In real world, it tends to associate with automated systems as they provide many benefits than doing the same thing in manually. As above mentioned, here we have introduced a system which can be used to maintain a bookshop. When we are concerning the manual process of a bookshop, the major problem is the waste of time. A customer has to waste his/her valuable time when he needs to buy a book as all the events such as searching, purchasing are done by members of the staff .In briefly, the manual process is very slow. But automation will reduce the time taken in the whole process. In a bookshop we should deal with a large store. Then person (storekeeper) has to maintain it with documents which are recorded by him. Therefore, there may be defective reports. Also company has to appointed more persons to complete the maintenance of the stationery. Then the company has to have an additional cost. As we familiar with this type of system at instance we will be able to have the results that we want. Communication with suppliers, customers and other related organizations will be more successful as the system is so fast. When the bookshop issues an item to a customer, all the stages of the transaction procedure will be facilitated by the system & it will be more accurate.

1.2 Scope:The name of the project is E- BOOK SHOPPING .The software provides both the customer and the merchant his PIN number which isunique.The software provides the following facilities to the customers: Facilitates easy shopping online any where with free shipping (conditions apply) Provides information about the products in categories Can avail the facility of purchasing second hand products Can reserve or order if the particular product is not available Customers are provided with up to date information on the products available Provides email facility for future correspondence Can add nearly ten products to their shopping cart at a time Provides complete information about the customers Provides complete information about their products Can avail the facility of email correspondence Provides on spot payment for the product at the time of delivery

1.3 Definitions, Acronyms and Abbreviations:1. Customer: The person who purchases the product 2. Merchant: The person/dealer/company who sell the product 3. PIN Number: The unique id given to either customer or merchant who access the data in the site

1.4 References: Appendix for the online shopping security information. Foundation of E-commerce by Ravi Kalakota. Internet and many online e- book shopping websites

1.5Overview:The following subsections provide the complete overview of the specifications requirements documentation for the product 18

e -BOOK SHOPPING.

19

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 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 the bookshop system will perform the following function: User identification Select service Record purchases Record sales Search for existing books Calculate budgets Prepare stock evaluation Display stock details

20

2.3. User characteristics: No pre knowledge of html No pre knowledge of database management should be familiar with internet should know English should be able to use and do according to the graphical user interface the user (Book Shop Officer) should have a basic computer literacy to work with computer. the user of this software should be well trained and should given the relevant user documentation, reference material and instruction. the user should be able to follow simple instruction given by the system.

2.4. General Constraints: the browser should support java.

the browser should be at least Netscape navigator v 4.0 or internet explorer. Data encoding scheme: ASCII character. Total available memory for programming, logic, tables etc as specified in this document should not be exceeded.

2.5. Assumptions and Dependencies: the product assumes that the users dont opt for the same product number simultaneously. cannot support multiple user interfaces. The bookshops database should be accessible in real time. The bookshops database will be modified to identify accounts.

3.Specific Requirements:3.1External Interface 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
The administrator log on to the system by inserting administrator name and password. Administrator can do any transaction as well as editing all details inside the database such as adding, editing, deleting a new user as well as adding, editing, deleting a new item.

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 quantity. Then click on update button. Hardware Interfaces The Book Shop System is having the following hardware: Book shop main computer Other pcsSoftware Interfaces System will interact with the system database to record all transaction data

3.1.2.Hardware Interface :The system should have these hardware requirements : The processor should be at least Pentium 3 or above The processor speed should be greater than 400Mhz The video device should support graphics Ram should be or greater than 120 mb

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 Server (windows 2000, apache or)

3.1.4.Communication Interfaces : Local intranet and internet protocols. Supports all HTTPS, SMTPS and POP3 services

3.2.Functional Requirements :Basically there are three modules in this system which is the source of input, for processing of input, to give out the relevant output. 21

3.2.1.Module 1:3.2.1.1.Functional requirement:The source of input are:o Customers o Merchants o Database administrator The processing is:Customers: Do shopping Reserve products o Merchants: Bid their products Manage transport facility and look after the payment method Database administrator: Update information 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 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: The browser should support java. The browser should be at least Netscape navigator v 4.0 or internet explorer. 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 error and the system errors.

3.5.Attributes :Qualities of the product.

Reliability The system is thoroughly tested at the time of delivery so that computational errors are minimized.

Maintainability To make ease of maintain the system to the Book shop administrators the user manual and the system manual is provided at the delivery. Each module is designed independently so that at any change of are quest can be modified easily.

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. All deleting actions are notified by a message box asking to confirm deletion.

3.6. Other requirements: Future aspects of the projects Changes in upcoming technologies Requirements needed in the expansion of the system

AS PER THE FORMAT PROPOSAL BY IEEE OF SRS [92] 22

23