online book store ( Project Report)

Project on ONLINE BOOK STORE

ACKNOWLEDGEMENT

I would like to extend my whole hearted thanks to Mr. .... for extending his full support in all the phases of our project as our project guide. He instructed us to carry the work flow in right direction to achieve the best result in limited time.

Our H.O.D. ....also provided suggestions to enhance the project and make it useful project.

INDEX & TABLES

1) Introduction:

1.1) Purpose:

1.2) Scope:

1.3) References:

1.4) Technologies:

2) Overall Description:

2.1) book Perspective:

2.02) Software Interface:

2.03) Hardware Interface:

2.04)Communication Interface:

2.05) Bookstore Function:

2.06) User Characteristics:

2.07) Constraints:

2.08) 0-Level Data Flow Diagram:

2.09) 1-Level Data Flow Diagram:

2.10) 2-Level Data Flow Diagram:

2.10) Entity Relationship Diagram:

2.12) Use Case Diagram:

1. Introduction:

1. Purpose:Book store management is designed to deal with the customer queries regarding information about different types of books. This is an online System that matches the customer queries regarding the author, publishers, title, price, latest updates, storage information, upgrades etc. against the information stored in the centralized database.

1. In order to create strong market impact, the issue of any type of books must have enough attractive features so as to attract the professionals. Through outstanding customer service, can gain customer loyalty, increase the number of customer referrals and provide more customers with lucrative preventive maintenance services.

2. To assist its services staff in retrieving information needed for their work and to meet the heightened service expectations of its customers, the client Web-enabled its internal information systems.so that it could better serve customers, the client also sought to improve the timely exchange of data.

3. Improved customer satisfaction by reducing the need for customers to fill out forms and provide information about their book to customer service representatives during the check-in process. The representatives can more quickly access the book history and suggest which periodic maintenance services should be performed. They can also determine what parts are in stock for the various publications, which helps customer service representatives keep customers informed about their queries while respecting their time. This improved level of service results in higher customer loyalty.

2. Scope:

• Create different system users and assign different roles with related permissions.

• Manage all the account details such as user name, phone numbers, address.

Websites, email addresses of the entire customer from one central location.

• Manage all the details regarding features of the books suchCompany, book dimension, book cost.

• Track all the customers and their contact details.

• Group the contacts together in a single account according to some criteria.

• Capture, View and edit all user transactions.

• Confirmation of end user identity and will verify which users are authorized to receive support.

• Maintain history of each customer and their related information about the book sale, & support related transactions.

• View all the details of all the interactions made with the customer.

3. References:

• www.google.com
• www.oracle.com
  
  

4. Technologies:

• Developer 6i.
• Oracle 8i.
  
  

5. Overview: SRS will include two sections:

• Overall Description will describe major components of the system, interconnection and external interfaces.
• Specific Requirements will describe the functions of actors, their role in the system and constraints.
• Use Case Diagram will describe the functional relationship between different entities, i.e. Actors (users).

2) Overall Description:

2.02) Software Interface:

Client on Internet: Web Browser, Operating System (any)

Client on Intranet: Client Software, Web Browser, Operating System (any)

Web Server: WAS, Operating System (any)

Data Base Server: Oracle.

Development End:Developer6i,oracle8i..

2.03) Hardware Interface:

Client Side
	Processor	RAM	Disk Space
Internet Explorer 6.0	Pentium II at 500 MHz	128 MB	1 GB
Server Side
Web sphere application server V5.0	Pentium III at 1 GHz	512 MB	1 GB
Oracle	Pentium IV at 3 GHz	512 MB	1GB (Excluding data size)

2.04) Communication Interface:

• Client on Internet will be using HTTP/HTTPS protocol.

• Client on Intranet will be using TCP/IP protocol.

2.05) Bookstore Function:

• It will be used by book workshop for better customer service.

2.06) User Characteristics: Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too.

2.07) Constraints:

• GUI is only in English.

• Login and password is used for identification of customer.

• This system is working for single server.

2.08) 0-Level Data Flow Diagram

USER

2.09) 1- Level Data Flow Diagram

SEARCH OUTPUT

SEARCH

INPUT

USER

USER

TRANSACTION TRANSACTION OUTPUT

INPUT

REQUEST

INPUT

REPORT OUTPUT

2.10)2 –Level Data Flow Diagram

Replacement output

Replacement input

Complaint output

Complaint input

USER

USER

Purchase

2.11)ER DIAGRAM

USER/ADMIN

Book store

USER

Bookstore

database

USER

Bookstore

ADMIN

Updation

2.12) Use Case Diagram

1) Admistrator: He maintains all records of the customers regarding information of their

Books ,he can add or delete books.

2) User: He makes request for obtaining various services and take benefits from

them.