A PROJECT REPORT ON

“Online Book Store”

Submitted by
Shubham auti & Adarsh patel

Under The Guidance Of

Prof. Prof’s Dipti Deshpande

In Partial Fulfillment Of
“Bachelor Of Business Administration (Computer
Application)” For The Batch
Savitribai Phule Pune University
ISB&M College Of Commerce
Nande Mulshi

1
 Peoples Empowerment Group

ISB&M College of Commerce

S. No. 44/1,44/1/2, Nande Village, Taluka Mulshi, Pune – 412 11

This is to certify that Mr. Shubham Auti & Mr. Adarsh Patel are bonafide students of
S.Y. B.B.A (CA) for the academic year 2022-2023.

They have undertaken and completed the project work as prescribed by Savitribai Phule
Pune University in the partial fulfillment of B.B.A. (CA) degree course on the topic
“Online Book Store”

He /she has worked out and completed a project under our guidance and direction in all
respect. His/her work is found to be satisfactory.

Prof. Dipti Deshpande Dr. Vaman Naik

Project Guide Principal

Internal Examiner External

Examiner

2
 ACKNOWLEDGMENT

We take this opportunity to express our Sincere gratitude to all those who
helped us in various capacities in undertaking this project and devising the
report. We are privileged to express our sense of gratitude to our respected
teacher Prof.Pravin Suryavanshi , Prof. Dipti Deshpande whose
unparalleled knowledge, moral fibre and judgement along with his know-
how, was an immense support in completing the project

We are also grateful to Principal Dr vaman Naik for the encouragement

given. We take this opportunity also to thank our friends and contemporaries
for their cooperation

3
 INDEX

Sr.No Particulars Page

No.
1 1
TITLE OF THE PROJECT
2 INTRODUCTION 5

3 SURVEY OF TECHNOLOGY 6

4 REQUIREMENTS AND 8
ANALYSIS
4 PROBLEM DEFINITION 8

5 12
ENTIY-RELATIONSHIP MODEL

6 DATA FLOW DIAGRAM 15

7 SYSTEM DESIGN 20

8 DATABASE TABLES 22

9 IMPLEMENTATION AND 24
TESTING
10
DOCUMENTATION
29

11 FUTURE APPLICATION 30

12 CONCLUSION 30

4
 Introduction:
Online shopping is the process whereby consumers directly buy goods, services etc. from
a seller interactively in real-time without an intermediary service over the internet.

Online shopping is the process of buying goods and services from merchants who sell on
the Internet. Since the emergence of the World Wide Web, merchants have sought to sell their
books to people who surf the Internet. Many people choose to conduct shopping online because
of the convenience.

1.1 Background

Online shopping allows you to browse through endless possibilities, and even offers merchandise
that's unavailable in stores. If you're searching for a niche product that may not be distributed
locally, you're sure to find what you're looking for on the internet.

Objective

My objective is to design such an application using which one can say 'goodbye' to the
days when you stood in line waiting, and waiting some more for a store clerk to finally
check out your items. Online shopping transactions occur instantly-saving you time to get
your other errands done! Additionally, unlike a store, online shopping has friendly
customer service representatives available 24 hours a day, 7 days a week to assist you with
locating, purchasing and shipping your merchandise.

1.3 Purpose and Scope

1.3.1 Purpose

Online Shopping system would have the following goals.

● Provide a web user interface to add, view, delete records in different areas.
● Provide a user interface to enter computer details.
● Provide a user interface to change details of all the computers and
accessories.
● Provide a user interface for users to explore the store and choose items to
buy.

5
 1.3.2 Scope

The main scope and deliverables of the project would be to:

● Understand and prepare detailed requirement and specifications

● Prepare high level and detailed design specifications of the system
● Prepare Test Plan and Test cases
● Develop the system and coding
● Perform unit testing, integration and system testing
● Demonstrate a bug free application after suitable modification if needed.

1.4 Achievements

● By successfully implementing the project, a substantial knowledge has been

acquired on the implementation of a database system using .net technologies. This
knowledge will be useful in the future in creating any type of desktop application
or online database systems.

2. SURVEY OF TECHNOLOGY
In a desktop application like Laboratory Management System, there is a scope for a large
number of platforms, languages and frameworks to choose from. Before selecting from
this large array of technologies, the following aspects, which are characteristic to windows
based application like this one, have been kept in mind:

● Data validation
● Performance
● Reliability
● Scalability
● Security
● Portability
● Performance
● Time constraint
● Cost constraint

The various technologies available for consideration are as follows:

Operating System: Windows 7

Client Side Scripting:

6
 ● HTML12
● CSS
● JavaScript

Server Side Scripting: PHP

Database Tool: My SQL

Testing Server: Apache

HTML

HTML or HyperText Markup Language is the standard markup language used to create
web pages.

HTML is written in the form of HTML elements consisting of tags enclosed in angle
brackets (like <html>). HTML tags most commonly come in pairs like <h1> and </h1>,
although some tags represent empty elements and so are unpaired, for example <img>. The
first tag in a pair is the start tag, and the second tag is the end tag (they are also called
opening tags and closing tags).

The purpose of a web browser is to read HTML documents and compose them into visible
or audible web pages. The browser does not display the HTML tags, but uses the tags to
interpret the content of the page. HTML describes the structure of a website semantically
along with cues for presentation, making it a markup language rather than a programming
language.

HTML elements form the building blocks of all websites. HTML allows images and
objects to be embedded and can be used to create interactive forms. It provides a means to
create structured documents by denoting structural semantics for text such as headings,
paragraphs, lists, links, quotes and other items. It can embed scripts written in languages
such as JavaScript which affect the behavior of HTML web pages.

CSS

CSS was first developed in 1997, as a way for Web developers to define the look and feel
of their Web pages. CSS didn't gain in popularity until around 2000, when Web browsers
began using more than the basic font and color aspects of CSS.Style sheet refers to the

7
document itself. Style sheets have been used for document design for years. They are the
technical specifications for a layout, whether print or online. Print designers use style
sheets to insure that their designs are printed exactly to specifications. A style sheet for a
Web page serves the same purpose, but with the added functionality of also telling the
viewing engine (the Web browser) how to render the document being viewed.

PHP:

PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source
general-purpose scripting language that is especially suited for web development and can
be embedded into HTML. Instead of lots of commands to output HTML (as seen in C or Perl),
PHP pages contain HTML with embedded code that does "something" (in this case, output "Hi,
I'm a PHP script!"). The PHP code is enclosed in special start and end processing instructions
<?php and ?> that allow you to jump into and out of "PHP mode." The best things in using PHP
are that it is extremely simple for a newcomer, but offers many advanced features for a
professional programmer. Don't be afraid reading the long list of PHP's features. You can jump
in, in a short time, and start writing simple scripts in a few hours.

MYSQL:

MySQL, the most popular Open Source SQL database management system, is developed,
distributed, and supported by Oracle Corporation.

The MySQL Web site (http://www.mysql.com/) provides the latest information about
MySQL software.

● MySQL is a database management system.

● MySQL databases are relational.
● MySQL software is Open Source.

3. REQUIREMENTS AND ANALYSIS

3.1 Problem Definition

8
Problem Definition and Need for the New System
● Online Book Store is a specific requirement of the client that integrates the
buying and selling services specifically to their customers.
● Reports can be generated at any time within few seconds, so that manual labor is
not required, and also analysis can be performed much more frequently which
helps in taking decision.
● The details regarding all users, books can also be maintained as their information
is very helpful and sometimes becomes a critical requirement.
● Allows user to get registered from their places and transact for the required
product.
● To overcome these problems we develop “Online Book Store”.

SYSTEM REQUIREMENTS SPECIFICATIONS

System requirements are expressed in a software requirement document. The
Software requirement specification (SRS) is the official statement of what is required of
the system developers. This requirement document includes the requirements definition
and the requirement specification. The software requirement document is not a design
document. It should set out what the system should do without specifying how it should
be done. The requirement set out in this document is complete and consistent.

The software specification document satisfies the following:-

● It specifies the external system behaviours.

● It specifies constraints on the implementation.
● It is easy to change.
● It serves as reference tool for system maintainers.
● It record forethought about the life cycle of the system.
● It characterizes acceptable response to undesired events.

User Class and Characteristics:

● General public
● Customers
● Administrator

9
 ● General public can use the system to see the books, their prices and quantity
available.
● Non registered user cannot buy the books.
● Customers are using for viewing and buying the books.
● Customer can also write feedbacks for books and services
● Administrators can add, edit & delete books and provide services to the customer.
● Administrator can see the daily sell. Can also see the feedback given by the
customer.
● Administrator maintaining the deliveries.

Functional Requirements:
● The System must provide following functionalities—
● Keeping records of registration of customers.
● Keeping the records of books.
● Keeping the daily sell.
● Storing the feedback given by the customer.
● Keeping details about the product it is delivered or not. etc.
● Storing the items selected by the customer in the temporary storage.

Non Functional Requirements:

Following Non-functional requirements will be there in the online shopping portal.

● Secure access of confidential data (customer’s details).

● 24 X 7 availability.
● Better component design to get better performance at peak time.

Flexible service based architecture will be highly desirable for future extension Non
functional requirements define system properties and constraints It arise through user
needs, because of budget constraints or organizational policies, or due to the external
factors such as safety regulations, privacy registration and so on.

Various other Non-functional requirements are:

1. Security

2. Reliability

10
3. Maintainability

4. Portability

5. Extensibility

6. Reusability

7. Application Affinity/Compatibility

8. Resource Utilization

External Interface Requirements:

User Interface:
User of the system will be provided with the Graphical user interface, there is no command
line interface for any functions of the product.

Hardware Interface:

Hardware requirements for running this project are as follows:

Processor: - Pentium I or above.

RAM: - 128 MB or above.

HD: - 20 GB or above.

Software Interface:-
Software required to make working of product is:-

Front end- HTML/PHP

Back end- My SQL

3.5 Conceptual Models

11
Entity-Relationship Model

Simply stated the ER model is a conceptual data model that views the real world
as entities and relationships. A basic component of the model is the Entity-Relationship
diagram which is used to visually represent data objects..

Basic Constructs of E-R Modeling

The ER model views the real world as a construct of entities and association
between entities.

Entities

Entities are the principal data object about which information is to be collected.
Entities are classified as independent or dependent

Relationships

A Relationship represents an association between two or more entities.

Relationships are classified in terms of degree, connectivity, cardinality, and existence.

Attributes

Attributes describe the entity of which they are associated. A particular instance of
an attribute is a value.

Classifying Relationships

Relationships are classified by their degree, connectivity, cardinality, direction,

type, and existence.

Degree of a Relationship

The degree of a relationship is the number of entities associated with the

relationship..

Connectivity and Cardinality

The connectivity of a relationship describes the mapping of associated entity

instances in the relationship. The values of connectivity are "one" or "many”

12
Direction

The direction of a relationship indicates the originating entity of a binary

relationship. The entity from which a relationship originates is the parent entity; the entity
where the relationship terminates is the child entity.

Existence

Existence denotes whether the existence of an entity instance is dependent upon

the existence of another, related, entity instance.

Generalization Hierarchies

A generalization hierarchy is a form of abstraction that specifies that two or more

entities that share common attributes can be generalized into a higher level entity type
called a supertype or generic entity.

ER Notation

The symbols used for the basic ER constructs are:

❑ Entities are represented by labeled rectangles. The label is the name of the entity.
❑ Relationships are represented by a solid line connecting two entities. The name of
the relationship is written above the line. Relationship names should be verbs.
❑ Attributes, when included, are listed inside the entity rectangle. Attributes which
are identifiers are underlined. Attribute names should be singular nouns.
❑ Cardinality of many is represented by a line ending in a crow's foot. If the crow's
foot is omitted, the cardinality is one.
❑ Existence is represented by placing a circle or a perpendicular bar on the line.
Mandatory existence is shown by the bar (looks like a 1) next to the entity for an
instance is required. Optional existence is shown by placing a circle next to the
entity that is optional.
❑ Existence is represented by placing a circle or a perpendicular bar on the line.
Mandatory existence is shown by the bar (looks like a 1) next to the entity for an
instance is required. Optional existence is shown by placing a circle next to the
entity that is optional.

13
ER Diagram
pin country
U_id
state

passwor
d city

name user

email

1 address
phone

Choo
se

B_nam usern
e
B_subca
1 m
Book_i
t d
b_id B_desc Cart_id
Bk_nam
e

M 1
Book Adds Cart
to
qty
B_publish
er
price amoun
Edition
1 1 t

page ISBN
Write
confir query
ms

M query
1
Cart_i
orderID d

email
contact
order

con_id usern
Order_ m
date

amoun
t

14
DATA FLOW DIAGRAM

What it is?

The Data Flow Diagram shows the flow of data or information. It can be partitioned
into single processes or functions. Data Flow Diagrams can be grouped together or
decomposed into multiple processes. There can be physical DFD's that represent the
physical files and transactions, or they can be business DFD's (logical, or conceptual).

When it's used?

The DFD is an excellent communication tool for analysts to model processes and
functional requirements. One of the primary tools of the structured analysis efforts of the
1970's it was developed and enhanced by the likes of Yourdon, McMenamin, Palmer, Gane
and Sarson. It is still considered one of the best modeling techniques for eliciting and
representing the processing requirements of a system.

The different versions are Context Diagrams (Level 0), Partitioned

Diagrams (single process only -- one level), functionally decomposed, leveled sets of Data
Flow Diagrams.

Data Store

It is a repository of information. In the physical model, this represents a file, table,

etc. In the logical model, a data store is an object or entity.

DataFlows
DFDs show the flow of data from external entities into the system, showed how
the data moved from one process to another, as well as its logical storage. There are only
four symbols:

❑ Squares representing external entities, which are sources or destinations of data.

❑ Rounded rectangles representing processes, which take data as input, do something
to it, and output it.
❑ Arrows representing the data flows, which can either, be electronic data or
physical items.

15
 ❑ Open-ended rectangles representing data stores, including electronic stores such
as databases or XML files and physical stores such as or filing cabinets or stacks
of paper.

There are several common modeling rules for creating DFDs:

❑ All processes must have at least one data flow in and one data flow out.
❑ All processes should modify the incoming data, producing new forms of outgoing
data.
❑ Each data store must be involved with at least one data flow.
❑ Each external entity must be involved with at least one data flow.
❑ A data flow must be attached to at least one process.

DFDs are nothing more than a network of related system functions and indicate
from where information is received and to where it is sent. It is the starting point in the
system that decomposes the requirement specifications down to the lowest level detail.

The high level processes in a system are:

❑ Receivable process.
❑ Verifiable process.
❑ Disposal process.

❑ File or data store is a repository of data. They contain data that is retained in the
system. Process can enter data into data store or retrieved data from the data store.
An open rectangle is a data store, data at rest.

16
0-Level DFD:

Books & other Order receipt &

details confirmation
Online Book
Admin User
Order & reports Store Personal Details &
Select product

CONTEXT DTAGRAM

Admin

Data
Status

1.0

Admin
Process

Reviews
Store
Access process

Book Order
Product

DFD for Admin Process

17
 Registration
Enter data
Process User Details
User Register

status
2.0

View Profile

Edit data Profile Update

User Updates
2.1

DFD For User Registration and Profile Update

18
 Login Select
User Book info
Product Book

3.0

order Details

Selected
Product
Add to Cart Cart

3.1

confirms Cart Details

User Checkout
Confirmation
& receipt
3.2

Place Order

Order

DFD for shopping and checkout process

1
19
SYSTEM DESIGN

Introduction:

System design is the solution of a “how to approach to the creation of the new
system. It is composed of several steps. Design goes through logical and physical stages
of development.

● Strong Problem Definition

● Pictorial description of the Existing System
● Set of Requirements of the new system

Modules Description:
1. Registration: Customer can register their account here to continue shopping.
2. Admin: Admin can add books, check orders and make sure the orders are
delivered on time and can confirm payments by the customers.
3. Shopping Cart: Customers after login can browse through the different books and
choose one or more products and can add them to cart.
4. Payment: Cash on Delivery facility is available.

3.2 INPUT DESIGN

Very careful attention had to be given to input design, which is a major part of the
overall system design. In order to make the data entry as easy, logical and error free as
possible, specific standards had been followed.

3.2.1 VALIDATIONS:

Some fields are having only number, as an I/P. For this key ASCII is checked. If
they entered characters, it would display the message to enter number only. Exchange rates
field will be validated for number and dot symbols.

3.2.2 INPUT DESIGN OBJECTIVES:

The numbers of clear objectives of input design are,

20
 ▪ To produce a cost effective method of input
▪ To achieve the highest possible level of accuracy
▪ To ensure that the input is acceptable to and understand by the user staff

3.3 OUTPUT DESIGN:

Output, as you probably know, generally refers to the results and information that
are generated by the system.
When designing output, systems analysts must accomplish the following.
▪ Determine what information to present
▪ Decide whether to display, print, or “speak” the information and select the output
medium.
▪ Arrange the presentation of information in an acceptable format.
▪ Decide how to distribute the output to intended recipients.

The output design is specified on layout performs, sheets that describe the location
characteristics.

3.4 DATABASE DESIGN

The general theme behind a database is to handle information as an integrated

whole. A database is a collection of inter-related data stored with minimum redundancy to
serve single users quickly and efficiently

21
Database Tables

user Table

Field Name Data Type Size Allow Null Constrain

u_id int 4 No PK
u_fnm varchar 35 No
u_unm varchar 25 No
u_pwd varchar 20 No
u_gender varchar 7 No
u_email varchar 35 No
u_contact varchar 12 No
u_city varchar 20 No

Category Table

Field Name Data Type Size Allow Null Constrain

cat_id int 4 No PK
cat_nm varchar 30 No

Subcat Table

Field Name Data Type Size Allow Null Constrain

subcat_id int 4 No PK
Parent_id Int 4 No
Subcat_nm varchar 35 No

Contact Table

Field Name Data Type Size Allow Null Constrain

con_id int 4 No PK
Con_nm varchar 40 No
Con_email varchar 40 No
Con_query Longtext 0 No

22
Book Table

Field Name Data Type Size Allow Null Constrain

b_id int 4 No PK
b_nm varchar 60 No
b_subcat varchar 25 No
b_desc longtext 0 No
b_publisher varchar 40 No
b_edition varchar 20 No
b_isbn varchar 10 No
b_page int 5 No
b_price int 5 No
b_img longtext 0 No
b_pdf longtext 0 No

Cart Table

Field Name Data Type Size Allow Null Constrain

cart_id int 4 No PK
user_nm varchar 20 No
Book_id varchar 10 No PK
Book_name varchar 25 No
Qty int 4 No
Amount Float No

Checkout Table

Field Name Data Type Size Allow Null Constrain

order_id int 4 No PK
Cart_id varchar 60 No
Order_date datetime No
Total_Amount Float 0 No

23
5. IMPLEMENTATION AND TESTING

5.1 Implementation approaches

The Software Design Description Document has been used as input in the
implementation process. The actual implementation has been done using PHP. PHP has
been used to interact with the backend database. In this implementation, My SQL Server
has been used as the backend RDBMS. PHP processes the inputs or commands given by
the user and translates them in the commands understandable to the backend database.
The output produced by the backend database is also handled by PHP which then
displayed on the Browser screen.

Coding and Screenshots

Index Page

24
Login Page

Book List Page

25
Registration Page

26
View Cart Page

27
5.2 Code efficiency

Code efficiency has been achieved through proper validation using various methods in
PHP coding. Fist no data can be added, viewed, edited and deleted to database without
login or session. For this we have implanted session tracking techniques through PHP.
Codlings have been used to validate various forms to ensure correct data should enter
in database.

5.3Testing Approach
TESTING PROCEDURES

● Unit Testing: A Unit corresponds to a form/class in the package. Unit testing focuses on
verification of the corresponding form or class. In this level we have tested all our
forms/classes individually. This testing includes testing of control paths, interfaces, local
data structures, logical decisions, boundary conditions, and error handling. From this
testing we were able to save, retrieve, update, delete and the search records on a
table.
● Integration Testing: Integration testing is used to verify the combination of the software
modules. In this level, we have tested by combining all unit tested forms into a
subsystem. Here we found that the subsystems are performing well.
● System Testing: System testing is used to verify, whether the developed system meets
the requirements.
● Acceptance Testing: Acceptance is the part of the project by which the customer
accepts the product. The system under consideration is tested for user acceptance by
constantly keeping in touch with the system users at time of developing and making
changes whenever required.

We hope that after the acceptance testing the system will perform the best result for the
organization. When modification will be made, we will use regression testing during the
maintenance of the system.

The Software System delivered to the customer may undergo changes. Changes may be
due to addition of new functional modules or performance enhancement .For this purpose
proper maintenance of the system is must.

28
7. DOCUMENTATION

❖ For Management
Online Shopping System is primarily designed for providing information from the
data after processing them. This system is designed for supplying information to the
strategic level of management from the operational control. It includes almost all the
functional areas needed like keeping Employee Records Student Records and Fees
Records.

❖ For User
With this electronic data processing system, the operators will able to maintain the
following task:

● Information regarding Patients.

● Records of Test Report with their details.
● Regular Transaction Details

❖ For data processing department

⮚ In maintenance, the data processing department needs to create
backup of the database file from time to time.
⮚ The main menu of the system provides different menus for different
purposes.

29
 FUTURE APPLICATION

Software development is never –ending process and continues the life of the software as
per the changing needs of the user from time to time. The project is no doubt has been developed
keeping in mind easy modification and enhancement that may be required from time to time.

CONCLUSION

After implementing the application it will contain the advantages were

incomparable to the present contemporary systems used by company. The most admirable
feature founded was its simplicity in terms of application to the user but its highly
beneficial outputs can’t be ignored. The users will be highly benefited after using the
system.

30