Hind Seva Mandal’s

PEMRAJ SARDA COLLEGE

Ahilya Nagar
DEPARTMENT OF COMPUTER SCIENCE
PROJECT REPORT
ON

“Book shop”
Submitted in Partial Fulfilment of
B.Sc. (Computer Science) Savitribai Phule Pune University
Submitted by
“Mr Chaudhari Shubham Dnyandeo”
Under the Guidance of
Mrs. Aparna Naik
(Asst. Professor)
For the Year (2024-2025)
 Hind Seva Mandal’s
PEMRAJ SARDA COLLEGE
Ahilya Nagar

DEPARTMENT OF COMPUTER SCIENCE

CERTIFICATE
This is to certify that
Mr Chaudhari Shubham Dnyandeo

has satisfactorily completed the project in

‘‘Book Shop’’
for the laboratory course towards fulfilment of
T. Y. B. Sc (Computer Science)
course of university of Pune for the
Academic Year 2024-2025

Prof. A. P. Naik Prof. R.K. Patni

Project Guide Head of Dept.

External
 INDEX

Sr No Name of Content

1 Acknowledgment
1
2 Introduction of Projects

3 System Analysis
4 Feasiblity Study

5 Software & Hardware Requirements

6 ER diagram

7 DFD

8 UML Diagram

9 Data Dictionary

10 Input Output screen

11 Testing

12 Future Enhancement

13 Limitation

14 References
 ACKNOWLEDGEMENT

great pleasure to present a project report entitled as,

“Online Book Shop”
We take this opportunity to express our deep gratitude
towards all faculty members of the institute, for helping us in
completion of this project report.
We are deeply grateful to Prof.R.K.Patni(HOD).our project
Guide. he spends his valuable time for us. She gave us advice
& useful suggestion about system.
We also thank to Prof.A.P.Naik.He guides us in our project
workout. Without his help our project would not be
completed. It reached up at present stage because of help of
all teachers.
And thankful to our friends in giving us valuable thoughts and
ideas. Without these peoples the project could not be possible.
Still designed system has some limitation and requirement, so
Correction & Suggestions Always are most welcome.

Mr Chaudhari Shubham Dnyandeo

 INTRODUCTION

The main objective of the project is to create an online book store that allows users to search

and purchase a book based on title, author and subject. The selected books are displayed in a

tabular format and the user can order theirbooks online through credit card payment. The

Administrator will have additionalfunctionalities when compared to the common user.

The motivation to create this project has many sources

• Interest to develop a good user friendly website with many online transactions using

database.

•To increase my knowledge horizon in technologies like PHP, POSTGreSQL, CSS, HTML.

•To gain good experience in PHP before joining in a full time job.

Background

There are many online book stores like Powell’s, Amazonwhich were designed using

Html. I want to develop a similar website using PHP ,PostGreSQL. Online Book store is an

online web application where the customer can purchase books

online. Through a web browser the customers can search for a book byits title or author,

later can add to the shopping cart and finally purchase using credit card transaction. The user

can login using his account details or new customers can set up an account very quickly.

They should give the details of their name, contact number and shipping address. The user

can also give feedback to a book by giving ratings on a score of five. The books are divided

into many categories based on subject Like Software, Database, Architecture etc
 SYSTEM ANALYSIS

FACTFINDINGTECHNIQUES:-

To Study the the system we need to collect facts i.e.gathering information

about the system.The Proper use of tools for gathering information is the

key to success analysis.

Various fact finding techniques are:

● Observation.

● Record Review.

● Interview.

Any number of these techniques can be used to develop a system which is

accurate & comprehensive.

We used the all of the Fact Finding Techniques /Data Collection Methods .

Observation:

This technique is used to collect information, which can’t be obtained by

other fact finding techniques. This method allows analyst to gain first hand

information about how activities are carried out etc.

Record Review:

Record review technique is used at beginning or at the end of system.This

Kind of record review provides very valuable information to the analyst

about the system,organizations and various procedures and rules.In our

project we had seen past records of patient’s.Also we can search their

records.

Interview:

To gather the information related to real world implementation, we had

interview sessions with few of the owners of local matrimonial service

providers. These were small businesses but still had to deal with thousands

of user registrations. Owner of one such business outlined the drawbacks

of the paper based system he was using. He told us that his job was a

cumbersome one and he had to spend a lot of time on it. As business was

growing, tasks like searching were becoming difficult to manage.

The other owner also faced same difficulties and how they lose customers

because of this. He also provided some suggestions on what new facilities

we can provide in searching. So these two interviews gave us a direction to

proceed with the design phase of project.

 FEASIBILITY STUDY

Depending on the results of the initial investigation the survey is now

expanded to a more detailed feasibility study. “FEASIBILITY STUDY” is

a test of system proposal according to its workability, impact of the

organization, ability to meet needs and effective use of the resources. It

focuses on these major questions:

1. What are the user’s demonstrable needs and how does a candidate

system meet them?

2. What resources are available for given candidate system?

3. What are the likely impacts of the candidate system on the organization?

4. Whether it is worth to solve the problem?

During feasibility analysis for this project, following primary areas of

interest are to be considered. Investigation and generating ideas about a

new system does this.

Steps in feasibility analysis

● Form a project team and appoint a project leader.

● Prepare system flowcharts.

● Enumerate potential proposed system.

● Weight system performance and cost data.

 ● Define and identify characteristics of proposed system.

● Determine and evaluate performance and cost effective of each

proposed system.

● Weight system performance and cost data.

● Select the best-proposed system.

● Prepare and report final project directive to management.

3.1Technical feasibility
A study of resource availability that may affect the ability to achieve an
acceptable system. This evaluation determines whether the technology
needed for the proposed system is available or not.

● Can the work for the project be done with current equipment existing
software technology & available personal?

● Can the system be upgraded if developed?

● If new technology is needed then what can be developed?

● This is concerned with specifying equipment and software that will

successfully satisfy the user requirement. The technical needs of the
system may include:

Front-end and back-end selection

● An important issue for the development of a project is the selection of
suitable front-end and back-end. When we decided to develop the project we
went through an extensive study to determine the most suitable platform that
suits the needs of the organization as well as helps in development of the
project.
● The aspects of our study included the following factors.
Front-end selection:
1. It must have a GUI that assists employees that are not from IT
background.
2. Scalability and extensibility.
3. Flexibility.
4. Robustness.
5. According to the organization requirement and the culture.
6. Must provide excellent reporting features with good printing support.
7. Platform independent.
8. Easy to debug and maintain.
9. Event driven programming facility.
10. Front end must support some popular back end like Ms Access.
According to the above stated features we selected PHP as the front-end
fordeveloping our project.
The technical feasibility is frequently the most difficult area encountered
at this stage. It is essential that the process of analysis and definition be
conducted in parallel with an assessment to technical feasibility. It centers
on the existing computer system and to what extent it can support the
proposed system.
3.2 Economical feasibility
Economic justification is generally the “Bottom Line” consideration for most
systems. Economic justification includes a broad range of concerns that
includes cost benefit analysis. In this we weight the cost and the benefits
associated with the candidate system and if it suits the basic purpose of the
organization i.e. profit making, the project is making to the analysis and design
phase.

The financial and the economic questions during the preliminary investigation
are

verified to estimate the following:

● The cost to conduct a full system investigation.

● The cost of hardware and software for the class of application being
considered.

. The benefits in the form of reduced cost.

● The proposed system will give the minute information, as a result the

performance is improved

● This feasibility checks whether the system can be developed with the
available funds. The Online Book Shop does not require enormous
amount of money to be developed. This can be done economically if
planned judicially, so it is economically feasible. The cost of project
depends upon the number of man-hours required.
3.3 Operational Feasibility
It is mainly related to human organizations and political aspects. The
points to be considered are:

● What changes will be brought with the system?

● What organization structures are disturbed?

● What new skills will be required? Do the existing staff members

have these skills? If not, can they be trained in due course of time?
The system is operationally feasible as it very easy for the End users to
operate it. It only needs basic information about Windows platform.

3.4 Schedule feasibility

Time evaluation is the most important consideration in the development of
project. The time schedule required for the developed of this project is
very important since more development time effect machine time, cost and
cause delay in the development of other systems.
A reliable Online Book Shop can be developed in the considerable
amount of time
SOFTWARE AND HARDWAREREQUIREMENTS

⮚ Software Requirements :-
Operating System : Windows -7 Onwards

Software Packages :
1. Languge: Php
2. Data Base:MySql

⮚ Hardware Requirement :-
Hard Disk : 10 GB & Onwards
RAM : 256 MB
Processor : Intel Core –i5
ER Diagram
 Data Flow Diagram
DFD: Level 01

DFD Level: 1

12
UML Diagram
1. User Sequence diagram

13
2. Add to shopping cart sequence diagram

14
3. Administrator Sequence diagram

15
4. Use Case Diagram
 DATA DICTIONARY

NAME TYPE Description

b_id int Unique identifier for each book

b_subcat varchar(60) Link to the subcatogry table

b_desc TEXT(255) Brief description of the book

b_publisher varchar(60) Publisher of the book

b_isbn varchar(60) International standard book no

b_price int Price of the book

➢ categoryTABLE:

NAME TYPE Description

cat_id int Unique identifier for each category

cat_nm varchar(60) Name of the book category

➢ contactTABLE:
NAME TYPE Description

con_id int Unique identifier for each

contact

con_nm varchar(60) Contact number

con_email varchar(60) Email address of the contact

 ➢ subcatTABLE:

NAME TYPE Description

subcat_id int Unique id for each subcat

parent_id int Refers to the unquie identifier of

the parent caetgory

subcat_nm varchar(60) Name of the subcat

➢ userTABLE:
NAME TYPE Description

u_id int Unique identifier for each user

u_fnm varchar(60) User frist name

u_unm varchar(60) The frist of the user

u_pwd varchar(60) Hashed user password

u_gender varchar(60) Gender identity of the user

u_email varchar(60) Usar email address

 INPUT OUTPUT SCREEN
Online book
Admin Page
Admin Category
Admin Contact
Normal User
User contact us
user perchase book
Book descrytion book
Viewcart
 USING OF TESTING
1. White box testing:
● It is also called as STRUCTURAL TESTING or GLASS BOX
TESTING.
● Testers use the knowledge of internal logic of the
system.
● Mostly verification techniques are used.
● It does not ensure that the user requirement had been
met.

● The test may not mimic the real world situations.

● Cost is very high since expert testers are required.
● Example: feasibility review, designer review, code
inspection and code walk through.

2. Black box testing:

● It is also called as FUNCTIONAL TESTING. These tests are
conducted at interface.
● Testers do not have information about the internal
functionality of the system.
 ● Mostly validation techniques are used.

● It stimulates the actual system usage.

● They have potential of not detecting the logical errors.
● The possibility that efforts are duplicated is high.
● Example: unit testing, integration testing, system
testing, and acceptance testing.
3. Unit testing:
● In unit testing the individual component are tested
independently to ensure their quality.
● The focus is to uncover the errors in design and
implementation.
● The various test that are conducted during the unit test
are described below:
i. Module interfaces are tested for proper information
flow in and out of the program.
ii. Local data are examined to ensure that integrity is
maintained.
iii. Boundary conditions are tested to ensure that the
module operates properly at boundaries established to
limit or restrict processing
iv. All the basis (independent) paths are tested for ensuring
that all statements in the module have been executed
only once.
v. All errors handling paths should be tested.
4. Integration testing:

● A group of dependent components are tested together

to ensure their quality of their integration unit.
● The objective is to take unit tested components and
build a program structure that has been dictated by
software design
● The focus of integration testing is to uncover errors in:
▪ Design and construction of software architecture.
▪ Integrated functions or operations at subsystem
level
▪ Interface and interaction between them.
▪ Resources interaction and / or environment
integration.
 ● The integration testing can be carried out using two
approaches.
i. The non incremental integration.
ii. Incremental integration

5. System testing:
The system test is a series of tests conducted to fully the
computer based system.
Various types of system tests are:
I. Recovery testing.
II. Security testing.
III. Stress testing.
IV. Performance testing.
The main focus of such testing is to test
▪ System functions and performance.
▪ System reliability and recoverability(recovery test).
▪ System installation (installation test).
▪ System behavior in special condition (stress test).
 ▪ System user operations (acceptance test).
▪ Hardware and software integration and collaboration.
▪ Integration of external software and the system.
I. Recovery testing:
● Recovery testing is intended to check the system’s
ability to recover from failures
● In this type of testing the software is forced to fail and
then it is verified whether the system recovers properly
or not.
● For automated recovery then reinitialization , check
point mechanisms , data recovery and restart are
verified
II. Security testing:
● Security testing verifies that system protection
mechanism prevent improper penetration of data
alteration.
● It also verifies that protection mechanism built into the
system prevent intrusion such as unauthorized internal
or external access or willful damage.
● System design goal is to make the penetration attempt
more costly than the value of information that will be
obtained in it
III. Stress testing:
● Determines breakpoint of a system to establish
maximum service level.
● In stress testing the system is executed in manner that
demands resources in abnormal quality, frequency or
volume.
● A variation of stress testing is a technique called
sensitivity testing.
● A variation of stress testing is a technique called
sensitivity testing.
● The sensitivity testing is a testing in which it is tried to
uncover data from a large class of valid data that may
cause instability or improper processing.
IV. Performance testing:
● Performance testing evaluates the run time
performance of the software especially real time
software.
● In performance testing resources utilization such as CPU
load , throughput ,response time, memory usage can be
measured.
 FUTURE ENHANCEMENT

The Book Shop system platform can be made more

secure by using the following methods
▪ Password Changing
▪ Fingerprinting
▪ Cornea Detection
The password used by the user
to vote is provided by the administrator. In the future the
user can be given the privilege of changing the password. So
it helps to increase the security of the system. The other two
methods that can be used are cornea detection and
fingerprinting. But here the problem is that it decreases the
scope of the platform because these systems need some
electronic components to implement

Results update through SMS.

In future we can add an SMS query also. ie we wil get
the result updates at the time of counting. To receive the
SMS we need to register with our mobile number in the site.
 LIMITATIONS OF THE SYSTEM
1. Need skilled person to handle it.
2. As computer does not have its own brain, manual
mistakes can lead to hazards.
3. If users want report, which is not mention in the listed
option for the reports, then the new program query for
that report has to be needed.
4. Possibility of displaying wrong message while at runtime
if user enter wrong information
 References
1. Web Development and PHP Programming
2. Object Oriented Software Engineering
3. Database Management System
4. Java Script – Robert Hellers
5. HTML
6. Use Internet
Online References:

● www.w3school.com
● www.google.co.in