Mahatma Education Society's PILLAI COLLEGE OF

ARTS COMMERCE & SCIENCE

(AUTONOMUS),

NEW PANVEL

PROJECT REPORT ON

“ONLINE BOOKS SHOPPING WEBSITE”

Submitted to, “UNIVERSITY OF MUMBAI”

By, MISS.TELI TISHA DINESH

UNDER THE GUIDANCE OF,

PROF. – Mrs. Rashmi Subodh Chavan

2022-2023

Department of Information Technology

 CERTIFICATE
This is to certify that the project entitled “Online Books Shopping Website” is
successfully completed by Miss. Teli Tisha Dinesh as per the syllabus and in
partial fulfillment for the completion of Bsc. Degree in Information Technology
of University of Mumbai. It is also to certify that this is the original work of the
candidate done during the academic year 2022-2023.

Exam seat no:

Place:
Date:

Signature of Signature of Signature of

Guide Principal/Coordinator External Examiner
 ACKNOWLEDGEMENT
I Miss. Tisha Teli student of PILLAI COLLEGE OF ARTS , COMMERCE & SCIENCE ,
NEW PANVEL would like to express my sincere gratitude towards Information
Technology Department.
I would like to thank Mrs. Deepika Sharma H.O.D.(I.T.&C.S.) for granting me the
opportunity to build project for the college. Last but not least I thank Lecturers.
(Mrs. Rashmi) for their constant support during the project. The project would
not have been completed without dedication, creativity and energy which my
family provided.
Yours faithfully,
Tisha Teli
(Final Year Information Technology)
 DECLARATION
I hereby declare that the project entitled, “Online Books Shopping Website”
done at place Pillai College New Panvel, has not been in any case duplicated to
submit to any other university for the award of any degree. To the best of my
knowledge other than me, no one has submitted to any other university. The
project is done in partial fulfillment of the requirements for the award of degree
of BACHELOR OF SCIENCE (INFORMATIONTECHNOLOGY) to be submitted as
final semester project as par to four curriculums.
Tisha Teli
Signature of the Student
 INDEX
Sr.no. Chapter 1 Signature
1 Introduction
1.1 Background
1.2 Objective
1.3 Purpose
1.4 Scope
Chapter 2
2 System Planning
2.1 Survey of Technologies
2.2 Fact Finding Techniques
2.3 Feasibility Study
2.4 Stake Holders
Chapter 3
3 Requirement and Analysis
3.1 Problem Definition
3.2 Requirement Specification
3.3 Planning and Scheduling
3.4 Software and Hardware Requirements
3.5 Conceptual Diagrams
ER ER Diagram
3.5.2 Use Case Diagram
3.5.3 Sequence Diagram
3.5.4 Class Diagram
3.5.5 Deployment Diagram
3.5.6 Component Diagram
3.5.7 Dataflow Diagram
Chapter 4
4 System Design
4.1 User Interface and Design
4.2 Data Integrity and Constraints
4.3 Security Cases
4.4 Test Cases
 Chapter 1

Introduction
The Online Book Shopping Website is an easy to use website that allows
the user to buy any book they want. This website includes a wide variety of
books from various different genres. Users can search for the book they want
from the book’s genre or title or author name. They can read the description
and then decide to add the book to their cart. The website offers an easy
payment method and tracking of the order for users. Users can pay for the
books via card or can choose the COD option. After confirming the order, the
user will receive an order invoice on their email.
The Admin can update the books. They can have access to the books
database and can check the quantity of books or if the book is in stock or not.
Admin can view the customer details for confirming the order. This website
provides login security for both user and admin.

Background
Online shopping allows us to browse and order the things we want from
the comfort of our home. It allows us to search for things without directly going
anywhere. There are many online websites for book shopping but customers
were not very happy with them. Some of them were dissatisfied with the
website. This website will have new features that will keep the customer base
happy.
 Objectives
 Provides login security for both user and admin
 Provides a simple and easy to use user interface
 Provides a variety of genre of books
 Provides detailed description of every book
 All the books are sorted according to their genre, title and author name to
make it easy for the user.
 Provides easy payment methods for the user
 Provides order tracking for the user
 Admin can easily update the books in the database
 Admin can view the user details and can confirm orders
 Admin can check if the product is in stock or not

Purpose
The main purpose of this project is to provide a simple and easy to use
interface for the user which they can access anywhere. To provide customers
with various categories of books and to make it easier for them to buy them.
Customers won’t have to go to their bookshops to buy their favorite books out
of their busy schedules. They can buy them from the comfort of their home.

Scope
Nowadays people find it difficult to find time and visit the bookshop to buy
books. That’s why having a online website makes it so much easier to buy
books. It’s the perfect place for books lovers to find the books they want to read
and buy from anytime and anywhere.
 Chapter 2

Survey Of Technologies
A technological survey can be a technique for gathering insights on software,
tools, and relevant technical skills in an explicit context. Technology surveys
have a broad range—from being used to find out how tech-savvy your target
audience is to conducting market research and collecting product feedback.
Technology trends change like the speed of light. And businesses need to adapt
to them quickly. If we want to reach a techno-savvy crowd, we must stay on the
trends. Our survey needs to get into every nook and corner of the online
channels so that it gets distributed on a large scale.
 Fact Finding Techniques
Fact-finding is the process of collecting data and information based on
techniques containing the samples of existing documents, research,
observation, questionnaires, interviews, and planning. System analysts use
suitable fact-finding techniques to develop and implement the current system.
Collecting facts are vital to use tools in System Development Life Cycle because
tools cannot be used efficiently and effectively without proper extracting from
facts. Fact-finding techniques are used in the early stage of the System
Development Life Cycle including the system analysis phase, design, and post-
implementation review. Facts included in any information system can be tested
based on three steps: data- facts used to create useful information, process-
functions to perform the objectives, and interface- designs to interact with
users.
To do Fact-Finding, we can use the following techniques:-
o Interviews
An Interview is the most commonly used fact-finding technique, and it is also
the most useful. An Interview is conducted to find out facts, verify those facts,
identify the requirements and collect ideas and opinions. An Interviewer must
have good communicating skills to effectively gather data from the people.
o Site Visit
The main objective of a site visit is to examine the working of the current
existing system. It is a technique that tells us about the previous problems of
the system and how some other companies have solved them. It tells us what
will be required for our projects. In addition, we can also gather data by
studying reference books, databases, case studies, and the Internet.
o Questionaries
Questionaries are also one of the useful fact-finding techniques which can be
done in a short amount of time. Questionnaires allow us to gather facts from a
large number of people while upholding some control over their responses. The
questions in a questionary should be short, precise, and easy to understand so
that the customer can give correct facts.
 Feasibility Study
A feasibility study is like a detailed analysis which considers all of the critical
aspects of a project to determine if it will succeed or not. It will also tell us if a
project is worth investing in or not. It is based on investigating and research to
support the process of decision-making. The result of a feasibility study will be a
report which will summarize the nature and scope of the proposed solution.
We have to study the following in the feasibility study:-
o Technical Feasibility
A Technical Feasibility involves the list of hardware and software needed, and
the skilled labor required to make them work. It helps us to understand if the
technical resources meet our capacity and whether the technical team can use
and convert them into working systems.
o Economical Feasibility
Economical Feasibility involves a cost/benefit analysis of the project, helping us
determine the possibility, cost, and benefit of the project before we will allocate
the financial resources. It is the most frequently used method for evaluating the
effectiveness of a project.
The procedure is to calculate the benefits which are to be expected from the
project and compare them with the cost. If the benefit is more than the cost
then we can implement the system but if it is not then we will have adjustments
or make alternate plans until it can be approved.
o Operational Feasibility
Operational Feasibility involves undertaking a study to analyze and determine
whether our needs can be met by completing the project and how well will the
project be. It also examines how will a project plan satisfies the requirements
which are identified in the requirement analysis phase of the system
development.
o Financial Feasibility
Financial Feasibility tells us whether our project is financially feasible or not. It
gives us knowledge of how much capital will be needed for the project’s launch
and success and whether we can invest that much or not. It also identifies areas
for growth.

Stake Holders
Stakeholders are those with an interest in our project's outcome. They are
either directly or indirectly involved in our project.
This project includes the following stakeholders:-
o Admin
o Customers
o Project Leader
o Suppliers
o End Users
 Chapter 3

Modules of the proposed system

Module 1: Registration
Customers can register to shop on the website and Admin can register to make
changes in the website.

Module 2: Login
Here customers and admin can verify their account details.

Module 3: Admin
Admin can add, update or delete the products. The admin can also confirm the
payment and make sure that the orders are delivered on time.

Module 4: Products
It contains the details of all the products available. It also shows whether a
product is in stock or not.

Module 5: Shopping Cart

After choosing the products of their likes, the customer can add the products to
the cart to order.

Module 6: Order
Here customers can add details on their address for ordering the product.

Module 7: Payment
Customers can choose their mode of payment here.
 Gantt chart
No. of Tasks:-
(1) Planning
(2) Estimating Schedule
(3) Gathering Information and Requirements
(4) Designing the Project
(5) Documentation
https://app.asana.com/0/1202814678817033/timeline
 ERD
ER Diagrams are composed of entities and attributes. They also depict
cardinality, which defines relationships in terms of numbers.
(1)Entity:- A definable thing—such as a person, object, concept or event—
that can have data stored about it. Think of entities as nouns.
(2)Attribute:- A property or characteristic of an entity.
(3)Cardinality:- Defines the numerical attributes of the relationship between
two entities or entity sets. The three main cardinal relationships are one-
to-one, one-to-many, and many-many.
 Use case
The Diagram Symbols and Notations used in this Use Case Diagram are:-
(1)Use cases: Horizontally shaped ovals that represent the different uses that
a user might have.
(2)Actors: Stick figures that represent the people employing the use cases.
(3)Associations: A line between actors and use cases. It is important to know
which actors are associated with which use cases in complex diagrams.
(4)System boundary boxes: A box that sets a system scope to use cases. All
use cases outside the box would be considered outside the scope of that
system.
 Sequence diagram
In the following Sequence diagram the following icons and elements are used:-
(1) Object Symbol:- Represents a class or object in UML. The object
symbol demonstrates how an object will behave in the context of the
system. Class attributes should not be listed in this shape.
(2) Activation Box:- Represents the time needed for an object to
complete a task. The longer the task will take, the longer the activation
box becomes.
(3)Lifeline Symbol:- Represents the passage of time as it extends downward.
This dashed vertical line shows the sequential events that occur to an
 object during the charted process. Lifelines may begin with a labeled
rectangle shape or an actor symbol.
(4)Synchronous message symbol:- Represented by a solid line with a solid
arrowhead. This symbol is used when a sender must wait for a response to
a message before it continues. The diagram should show both the call and
the reply.
(5)Reply message symbol:- Represented by a dashed line with a lined
arrowhead, these messages are replies to calls.
(6)Delete message symbol:- Represented by a solid line with a solid
arrowhead, followed by an X. This message destroys an object.
 Class Diagram
The basic components used in Class Diagram are:-
(1)Upper section: Contains the name of the class. This section is always
required, whether we are talking about the classifier or an object.
(2)Middle section: Contains the attributes of the class. We use this section to
describe the qualities of the class.
(3)Bottom section: Includes class operations (methods). They are displayed in
list format, each operation takes up its own line.
 Deployment diagram
Components used in this deployment diagram:-
(1)Node: A hardware or software object, shown by a three-dimensional box.
(2)Node as container: A node that contains another node inside of it—such as
in the example below, where the nodes contain components.
(3)Component: A rectangle with two tabs that indicates a software element.
(4)Association: A line that indicates a message or other type of
communication between nodes.
 Component diagram
Components of a Component Diagram are as following:-
(1)Component Symbol:- An entity required to execute a stereotype function.
A component provides and consumes behavior through interfaces, as well
as through other components.
(2)Node Symbol:- Represents hardware or software objects, which are of a
higher level than components.
(3)Dependency Symbol:- Shows that one part of your system depends on
another. Dependencies are represented by dashed lines linking one
component (or element) to another.
(4) Required interfaces: A straight line from the component box with an
attached half circle (also represented as a dashed arrow with an open
arrow). These symbols represent the interfaces where a component
requires information in order to perform its proper function.
 Data Flow Diagram
The symbols that depict the components of Data Flow Diagrams are as follows:-
(1)External entity: An outside system that sends or receives data,
communicating with the system being diagrammed. They are the sources
and destinations of information entering or leaving the system. They might
be an outside organization or person, a computer system or a business
system. They are also known as terminators, sources and sinks or actors.
They are typically drawn on the edges of the diagram.
(2)Process: Any process that changes the data, producing an output. It might
perform computations, or sort data based on logic, or direct the data flow
based on business rules. A short label is used to describe the process.
(3)Data flow: The route that data takes between the external entities,
processes, and data stores. It portrays the interface between the other
components and is shown with arrows.
 Chapter 4

User Interface
SignUp.aspx
Login.aspx
UserHome.aspx
Books.aspx
GHorror.aspx
Product1.aspx
BestSellers.aspx
Cart.aspx
Payment.aspx
AddProduct.aspx
ViewOrder.aspx
 Data table constraints and integrity
Sign_Up
Name Data Type Constraints
name varchar Not Null
uname varchar Primary Key, Not Null
password varchar Not Null

Login
Name Data Type Constraints
uname varchar Not Null, Primary Key
password varchar Not Null

Payment
Name Data Type Constraints
fname varchar Not Null
lname varchar Not Null
address varchar Not Null
emid email Not Null
cnumber integer Not Null
cvv integer Not Null
amount integer Not Null

Add_Product
Name Data Type Constraints
bid varchar Not Null
bname varchar Not Null
bimage image Not Null
auname varchar Not Null
bdes varchar Not Null
bprice integer Not Null
bgenre varchar Not Null
bpages integer Not Null
bpubyear integer Not Null
bpub varchar Not Null