Mini Project Report

on

Online Book Store

Submitted In Partial Fulfillment of the Requirement

Computer Science and Engineering Department

By

ADITI SHARMA

Under the Supervision of

Prof. VINOD KUMAR

ACCURATE INSTITUTE OF POLYTECHNIC

GREATER NOIDA
 DECLARATION

We hereby declare that this submission is our own work and that to the best of our knowledge and
belief. It contains no material previously published or written by another person nor material which
to a substantial extent has been accepted for the award of any other degree or diploma of the
university or other institute of higher learning, except where due acknowledgment has been made
in the text.

Signature:

Name: Aditi Sharma

RollNo: 2486523555010

Date:
 CERTIFICATE

This is to certify that Project Report entitled “ONLINE BOOK STORE” which is submitted by
Aditi Sharma in partial fulfillment of the requirement for the award of diploma. The matter
embodied in this thesis is original and has not been submitted for the award of any other degree.
Date:

Supervisor
VINOD KUMAR
 ACKNOWLEDGEMENT

It gives us a great sense of pleasure to present the report of the B.Tech Project undertaken during B.Tech
Final Year. We owe special debt of gratitude to Prof. Nawneet Kumar for his constant support and guidance
throughout the course of our work. Her sincerity, thoroughness and perseverance have been a constant
source of inspiration for us. It is only her cognizant efforts that our endeavors have seen light of the day.

We also take the opportunity to acknowledge the contribution of Professor Sunil Yadav, Head of
Department, Department of Computer Science & Engineering, Accurate Institute of Management and
Technology, Greater Noida for his full support and assistance during the development of the project.

We also would not like to miss the opportunity to acknowledge the contribution of all faculty members of
the department for their kind assistance and cooperation during the development of our project. Last but not
the least, we acknowledge our parents and friends for their constant support throughout the project.

Signature:

Name: ADITI SHARMA

Roll No: 2486523555010

Date:
 ABSTRACT

The main objective of the project is to create an online book store that allows users to search
and purchase a book online based on title, author and subject. The selected books are displayed
in a tabular format and the user can order their books online through credit card payment.
Using this Website the user can purchase a book online instead of going out to a book store
and wasting time.

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 by its 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 Online Book Store Website provides customers with online shopping through a web browser.
A customer can, create, sign in to his account, place items into a shopping cart and purchase
using his credit card details.

The Admin will have additional functionalities when compared to the common user. He can
add, delete and update the book details, book categories, member information and also confirm
a placed order.
 TABLE OF CONTENTS

CHAPTER 1: INTRODUCTION

1.1 Background

1.2 Objective

1.3 Purpose, Scope and Applicability

1.3.1 Purpose

1.3.2 Scope

1.4 Achievements

1.5 Organization of Report

CHAPTER 2: SERVEY OF TECHNOLOGY CHAPTER

3: REQUIREMENTS AND ANALYSIS

3.1 Problem Definition

3.2 Requirement Specification

3.3 Software and Hardware Requirements

3.3.1 Hardware Requirements

3.3.2 Software Requirements

3.4 Preliminary Product Description

3.5 Conceptual Models

3.6.1 Module Specifications

3.6.2 Screen Views

3.6.3 Data Flow Diagrams

CHAPTER 4: SYSTEM DESIGN

4.1 Basic Modules

4.2 Data Design

4.2.1 Schema Design

4.2.2 Data Integrity and Constraints

4.3 Procedural Design

 4.3.1 Logic Diagrams

4.4 User Interface Design

4.5 Security Issues CHAPTER 5: IMPLEMENTATION AND TESTING

5.1 Implementation Approaches

5.2 Coding Details and Code Efficiency

5.2.1 Coding

5.2.2 Code Efficiency

5.3 Testing Approach

5.3.1 Unit Testing

5.3.2 Integrated Testing

5.4 Modifications and Improvements

CHAPTER 6: RESULTS AND DISCUSSION

6.1 Test Reports

6.2 User Documentation

CHAPTER 7: CONCLUSION

7.1 Conclusion

7.2 Limitations of the System

7.3 Future scope of the Project

CHAPTER 8: BIBLIOGRAPHY

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. Shoppers can visit web stores from the comfort of their homes and shop as they sit
in front of the computer. Consumers buy a variety of items from online stores. In fact, people can purchase
just about anything from companies that provide their books online. Books, clothing, household
appliances, toys, hardware, software, and health insurance are just some of the hundreds of books
consumers can buy from an online store.

Many people choose to conduct shopping online because of the convenience. For example, when
a person shops at a brick-and-mortar store, she has to drive to the store, find a parking place, and walk
throughout the store until she locates the books she needs. After finding the items she wants to purchase,
she may often need to stand in long lines at the cash register.

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. What's even more useful is the ability to compare items,
similar or not, online. You can search through multiple stores at the same time, comparing material quality,
sizes and pricing simultaneously.

Say 'goodbye' to the days when you stood in line waiting, and 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.2 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.

My main aim is to design such a book store where customer can visit our site anytime of the day
from anywhere to view the available books, choose any of them and can order by paying online or can opt
for cash on delivery as well. The administrator will regularly add any new books available to them for sale.
The administrator will take books from the reputed publishers and vendors only.

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.

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 11

Client Side Scripting:

• HTML
• CSS
• JavaScript

Server Side Scripting: Java

Database Tool: My SQL

Testing Server: Apache Tomcat 9.0

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. It was intended to allow developers to separate content from design so that HTML
could perform more of the function that it was originally based on the markup of content, without
worry about the design and layout.

CSS didn't gain in popularity until around 2000, when Web browsers began using more than the
basic font and color aspects of CSS.

Web Designers that don't use CSS for their design and development of Web sites are rapidly
becoming a thing of the past. And it is arguably as important to understand CSS as it is to know
HTML - and some would say it was more important to know CSS.

Style sheet refers to the 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.

JAVA:

Java is a widely-used programming language for coding web applications. It has been a popular choice
among developers for over two decades, with millions of Java applications in use today. Java is a
multi-platform, object-oriented, and network-centric language that can be used as a platform in itself.
It is a fast, secure, reliable programming language for coding everything from mobile apps and
enterprise software to big data applications and server-side technologies.

Java is popular because it has been designed for ease of use. Some reasons developers continue to
choose Java over other programming languages include:

High quality learning resources

Java has been around for a long time, so many learning resources are available for new
programmers. Detailed documentation, comprehensive books, and courses support developers
through the learning curve. In addition, beginners can start writing code in Core Java before moving to
Advanced Java.

Inbuilt functions and libraries

When using Java, developers don’t need to write every new function from scratch. Instead, Java
provides a rich ecosystem of in-built functions and libraries to develop a range of applications.

Active community support

Java has many active users and a community that can support developers when they face coding
challenges. The Java platform software is also maintained and updated regularly.

High-quality development tools

Java offers various tools to support automated editing, debugging, testing, deployment, and change
management. These tools make Java programming time and cost-efficient.

Platform Independent
Java code can run on any underlying platform like Windows, Linux, iOS, or Android without rewriting.
This makes it especially powerful in today’s environment, where we want to run applications on
multiple devices.

Security
Users can download untrusted Java code over a network and run it in a secure environment in which
it cannot do any harm. Untrusted code cannot infect the host system with a virus nor can it read or
write files from the hard drive. The security levels and restrictions in Java are also highly configurable.
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.

A database is a structured collection of data. It may be anything from a simple

shopping list to a picture gallery or the vast amounts of information in a corporate network.
To add, access, and process data stored in a computer database, you need a database
management system such as MySQL Server. Since computers are very good at handling
large amounts of data, database management systems play a central role in computing, as
standalone utilities, or as parts of other applications.

• MySQL databases are relational.

A relational database stores data in separate tables rather than putting all the data in
one big storeroom. The database structures are organized into physical files optimized for
speed. The logical model, with objects such as databases, tables, views, rows, and columns,
offers a flexible programming environment. You set up rules governing the relationships
between different data fields, such as one-to-one, one-to-many, unique, required or
optional, and “pointers” between different tables. The database enforces these rules, so that
with a well-designed database, your application never sees inconsistent, duplicate, orphan,
out-of-date, or missing data.

The SQL part of “MySQL” stands for “Structured Query Language”. SQL is the most
common standardized language used to access databases. Depending on your programming
environment, you might enter SQL directly (for example, to generate reports), embed SQL
statements into code written in another language, or use a language-specific API that hides
the SQL syntax.
 SQL is defined by the ANSI/ISO SQL Standard. The SQL standard has been evolving since
1986 and several versions exist. In this manual, “SQL-92” refers to the standard released
in 1992, “SQL:1999” refers to the standard released in 1999, and “SQL:2003” refers to the
current version of the standard. We use the phrase “the SQL standard” to mean the current
version of the SQL Standard at any time.

• MySQL software is Open Source.

Open Source means that it is possible for anyone to use and modify the software. Anybody
can download the MySQL software from the Internet and use it without paying anything.
If you wish, you may study the source code and change it to suit your needs. The MySQL
software uses the GPL (GNU General Public License), http://www.fsf.org/licenses/, to
define what you may and may not do with the software in different situations. If you feel
uncomfortable with the GPL or need to embed MySQL code into a commercial application,
you can buy a commercially licensed version from us. See the MySQL Licensing Overview
for more information (http://www.mysql.com/company/legal/licensing/).

3. REQUIREMENTS AND ANALYSIS

3.1 Problem Definition

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
 • 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
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, CSS, Javascript, BootStrap

• Back end- Java, JDBC, Servlet
• Database- MySql

3.5 Conceptual Models

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.

Used effectively, it is a useful and easy to understand modeling tool. It has broad application and
usability across most software development projects. It is easily integrated with data modeling,
workflow modeling tools, and textual specs. Together with these, it provides analysts and
developers with solid models and specs. Alone, however, it has limited usability. It is simple and
easy to understand by users and can be easily extended and refined with further specification into
a physical version for the design and development teams.

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.
 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 four symbols in DFD, each of which has its meaning. They are given below:

 External entities are outside to system but they either supply input data in the system or use
the system output. These are represented by square of rectangle. External entities that
supply data into a system are sometimes called Sources. External entities that use system
data are sometimes called sinks.
 Dataflow models that passages of data in the system and are represented by line by joining
system components. An arrow indicates the direction of the flow and the line is labeled by
the name of the dataflow.
 Process show that the systems do. Each process has one or more data inputs and one or data
outputs. Circles in DFD represent them. Each high level process may be consisting of more
than one lower level processes. Process will be expanded in sequent level DFD. A circle or
a bubble represents a process that transforms incoming data flow into outgoing dataflow.

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.
 DFD for Admin Process

DFD For User Registration and Profile Update

 DFD for shopping and checkout process

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. Since Chen wrote his paper the model has been extended and today
it is commonly used for database.

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 (in some methodologies, the terms used are strong and
weak, respectively). An independent entity is one that does not rely on another for identification.
A dependent entity is one that relies on another for identification. .

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. The domain of an attribute is the collection of all possible values an attribute can have.
The domain of Name is a character string.

Classifying Relationships

Relationships are classified by their degree, connectivity, cardinality, direction, type, and
existence. Not all modeling methodologies use all these classifications.

Degree of a Relationship

The degree of a relationship is the number of entities associated with the relationship. The n-ary
relationship is the general form for degree n. Special cases are the binary, and ternary, where the
degree is 2 and 3 respectively.
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". The cardinality of a relationship is
the actual number of related occurrences for each of the two entities. The basic types of
connectivity for relations are: one-to-one, one-to-many, and many-to-many.

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.

The direction of a relationship is determined by its connectivity type .An identifying relationship
is one in which one of the child entities is also a dependent entity. A non-identifying relationship
is one in which both entities are independent.

Existence

Existence denotes whether the existence of an entity instance is dependent upon the existence of
another, related, entity instance. The existence of an entity in a relationship is defined as either
mandatory or optional.

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. The lower-level of entities become the subtype, or categories, to the supertype.
Subtypes are dependent entities.

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.
1. 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. It facilitates the understanding and provides the procedural details
necessary for implementation of the system recommended in the feasibility study. Emphasis is
given on translating the performance requirements into design specification. Design goes through
logical and physical stages of development.

Logical design reviews the present physical system; prepares input and output specification; make
editing; security and control specification; details the implementation plan, and prepare logical
design walk through. The physical design maps out the details of the physical system; plans the
system implementation plan and specifies hardware and software. System design translates the
system requirement into the ways of the system as recommended in the feasibility study. Thus the
system design is the translation from user-oriented document to a programmer or a database
personal oriented document. System design is a highly creative process that can be greatly
facilitated by the following:-

• 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. Validation checks, provided in the system prevented the user in
entering incorrect, erroneous data. This made sure that, only valid data had been available for data
processing. If valid data was entered, then meaningful error messages had been prompted to enter
correct data. The interactive screen formats facilitate the entry of valid data.

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,

▪ 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. For many end-users, output is the main reason for developing the system
and the basis on which they will evaluate the usefulness of the application. Most end users will not
actually operate the information system or enter data through workstations, but they will use the
output from 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.
That alignment of information on a display or printed document is termed as layout.
Accomplishing the general activities listed above will require specific decisions, such as whether
to use preprinted forms when preparing reports and documents, how many lines to plan on a printed
page, or whether to use graphics and color.
The output design is specified on layout performs, sheets that describe the location
characteristics, and format of the column headings and pagination. As we indicated at the beginning
of this discussion, these elements are analogous to an architect’s blue print that shows the location
of the each component.
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. The general objective is to make information necessary, quick, inexpensive
and flexible for the user.

create database if not exists onlinebookstore;

use onlinebookstore;

create table if not exists books(barcode varchar(100) primary key, name varchar(100),

author varchar(100), price int, quantity int);

create table if not exists users(username varchar(100) primary key,password varchar(100),

firstname varchar(100), lastname varchar(100),address text, phone varchar(100),mailid
varchar(100),usertype int);

insert into books values('9780134190563','The Go Programming Language','Alan A. A.

Donovan and Brian W. Kernighan',400,8); insert into books values('9780133053036','C++
Primer','Stanley Lippman and Josée Lajoie and Barbara Moo',976,13); insert into books
values('9781718500457','The Rust Programming Language','Steve
Klabnik and Carol Nichols',560,12); insert into books values('9781491910740','Head First
Java','Kathy Sierra and Bert Bates and Trisha Gee',754,23); insert into books
values('9781492056300','Fluent Python','Luciano
Ramalho',1014,5); insert into books values('9781720043997','The Road to Learn
React','Robin
Wieruch',239,18); insert into books values('9780132350884','Clean Code: A Handbook of Agile
Software

Craftsmanship','Robert C Martin',288,3);
 insert into books values('9780132181273','Domain-Driven Design','Eric Evans',560,28);
insert into books values('9781951204006','A Programmers Guide to Computer
Science','William Springer',188,4); insert into books values('9780316204552','The Soul of a New
Machine','Tracy
Kidder',293,30); insert into books values('9780132778046','Effective Java','Joshua
Bloch',368,21); insert into books values('9781484255995','Practical Rust
Projects','Shing Lyu',257,15);

insert into users values('demo','demo','Demo','User','Demo

Home','42502216225','demo@gmail.com',2);

insert into users values('Admin','Admin','Mr.','Admin','Haldia

WB','9584552224521','admin@gmail.com',1);

insert into users

values('shashi','shashi','Shashi','Raj','Bihar','1236547089','shashi@gmail.com',2);

commit;
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 Java. Java has been used to interact with
the backend database. In this implementation, My SQL Server has been used as the backend
RDBMS. Java 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 Java which then displayed on the Browser screen.
Coding and Screenshots

Index Page
Login Page

Book List Page

Registration Page

View Cart Page

Coding of index
<html>
<head>
<meta charset="ISO-8859-1">
<title>Book Store</title>
<link rel="apple-touch-icon" sizes="180x180"
href="./favicons/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32"
href="./favicons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="./favicons/favicon-
16x16.png">
<link rel="manifest" href="./favicons/site.webmanifest">
<link rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/bootstrap@4.4.1/dist/css/bootstrap.min.css"
>
<link rel="stylesheet" href="styles.css">

</head>
<body onload="funload()">
<header>
<nav class="navbar navbar-expand-sm bg-dark">
<a class="navbar-brand">
<!-- The below line can be an image or a h1,
either will work -->
<img src="logo.png" alt="Google logo" width="60"
height="30px">
</a>

<button style="background-color:white;" class="navbar-

toggler" type="button" data-toggle="collapse" data-target="#navbarNav"
ariacontrols="navbarNav" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon" ></span>
</button>

<div class="collapse navbar-collapse" id="navbarNav">

<ul class="navbar-nav" >
<li class="nav-item"><span><a class="nav-link
active" href="index.html">Home</a></span></li>
<li class="nav-item "><span><a class="nav-link"
href="CustomerLogin.html">Login</a></span></li>
<li class="nav-item "><span><a class="nav-link"
href="CustomerRegister.html">Register</a></span></li>
</ul>
</div>
</nav>
</header>
<br>
<div id="topmid"><h1>Welcome to Online <br>Book Store</h1></div>
<br>
 <table class="tab">
<tr>
<td><a href="index.html" id="happy">Happy
Learning!!<br>Welcome to our book store!</a></td>
</tr>
</table>

<script src="https://code.jquery.com/jquery-3.3.1.slim.min.js"
></script>
<script
src="https://cdn.jsdelivr.net/npm/popper.js@1.14.6/dist/umd/popper.min.js"
></script>
<script
src="https://cdn.jsdelivr.net/npm/bootstrap@4.2.1/dist/js/bootstrap.min.js"></
script>
<script>
// Preloder script
var tmp = document.getElementById("loding");
function funload() {
loding.style.display = "none";
}
</script>

</body>
</html>

Process_Login
<html>
<head>
<meta charset="ISO-8859-1">
<title>Book Store</title>
<link rel="apple-touch-icon" sizes="180x180"
href="./favicons/apple-touch-icon.png"> <link
rel="icon" type="image/png" sizes="32x32"
href="./favicons/favicon-32x32.png"> <link
rel="icon" type="image/png" sizes="16x16"
href="./favicons/favicon-16x16.png">
<link rel="manifest" href="./favicons/site.webmanifest">
<link rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/bootstrap@4.4.1/dist/css/bootstrap.min.css"
>
<link rel="stylesheet" href="styles.css">
</head>
<body onload="funload()">
<header>
<nav class="navbar navbar-expand-sm bg-dark">
<a class="navbar-brand">
<!-- The below line can be an image or a h1,
either will work -->
<img src="logo.png" alt="Google logo" width="60"
height="30px">
</a>

<button style="background-color:white;" class="navbar-

toggler" type="button" data-toggle="collapse" data-target="#navbarNav"
ariacontrols="navbarNav" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>

<div class="collapse navbar-collapse" id="navbarNav">

<ul class="navbar-nav" >
<li class="nav-item"><span><a class="nav-link"
href="index.html">Home</a></span></li>
<li class="nav-item "><span><a class="nav-link
active" href="login.html">Login</a></span></li>
<li class="nav-item "><span><a class="nav-link"
href="CustomerRegister.html">Register</a></span></li>
</ul>
</div>
</nav>
</header>
<div id="topmid"><h1>Welcome to Online Book Store</h1></div>
<br>
<table class="tab">
<tr style="background-color: white; color: green; border-radius:
25%">
<td>Login or SignUp Below</td>
</tr>
<tr>
<td><a href="SellerLogin.html">Login As Admin</a></td>
</tr>

<tr>
<td><a href="CustomerLogin.html"> Login As<span>
Customer</span></a></td>
</tr>
<tr>
 <td><a href="CustomerRegister.html">New user ! Register
Here</a></td>
</tr>
</table>
<script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" ></script>
<script
src="https://cdn.jsdelivr.net/npm/popper.js@1.14.6/dist/umd/popper.min.js"
></script>
<script
src="https://cdn.jsdelivr.net/npm/bootstrap@4.2.1/dist/js/bootstrap.min.js"></
script>
<script>
// Preloder script
var tmp = document.getElementById("loding");
function funload() {
loding.style.display = "none";
}
</script>

</body>
</html>
Process Register

<html>
<head>
<meta charset="ISO-8859-1">
<title>Book Store</title>
<link rel="apple-touch-icon" sizes="180x180" href="./favicons/apple-
touchicon.png"> <link rel="icon" type="image/png" sizes="32x32"
href="./favicons/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="./favicons/favicon-
16x16.png">
<link rel="manifest" href="./favicons/site.webmanifest">
<link rel="stylesheet"
href="https://cdn.jsdelivr.net/npm/bootstrap@4.4.1/dist/css/bootstrap.min.css"
>
<link rel="stylesheet" href="styles.css">

</head>
<body onload="funload()">
<header>
<nav class="navbar navbar-expand-sm bg-dark">
<a class="navbar-brand">
<!-- The below line can be an image or a h1,
either will work -->
<img src="logo.png" alt="Google logo" width="60"
height="30px">
 </a>

<button style="background-color:white;" class="navbar-

toggler" type="button" data-toggle="collapse" data-target="#navbarNav"
ariacontrols="navbarNav" aria-expanded="false" aria-label="Toggle navigation">
<span class="navbar-toggler-icon"></span>
</button>

<div class="collapse navbar-collapse" id="navbarNav">

<ul class="navbar-nav" >
<li class="nav-item"><span><a class="nav-link"
href="index.html">Home</a></span></li>
<li class="nav-item "><span><a class="nav-link
active" href="login.html">Login</a></span></li>
<li class="nav-item "><span><a class="nav-link"
href="CustomerRegister.html">Register</a></span></li>
</ul>
</div>
</nav>
</header>
<div id="topmid"><h1>Welcome to Online Book Store</h1></div>
<br>
<table class="tab">
<tr style="background-color: white; color: green; border-radius:
25%">
<td>Login or SignUp Below</td>
</tr>
<tr>
<td><a href="SellerLogin.html">Login As Admin</a></td>
</tr>

<tr>
<td><a href="CustomerLogin.html"> Login As<span>
Customer</span></a></td>
</tr>
<tr>
<td><a href="CustomerRegister.html">New user ! Register
Here</a></td>
</tr>
</table>
<script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" ></script>
<script
src="https://cdn.jsdelivr.net/npm/popper.js@1.14.6/dist/umd/popper.min.js"
></script>
<script
src="https://cdn.jsdelivr.net/npm/bootstrap@4.2.1/dist/js/bootstrap.min.js"></
script>
<script>
// Preloder script var tmp =
document.getElementById("loding"); function
funload() { loding.style.display = "none";
}
</script>

</body>
</html>

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.

5.3.1 Unit Testing

Test case Ref No TCT-001

Functionality : Log in to the System

Expected outcome : The user should not login to member’s area

. and some error message follow

Step No. Data Used Actual Outcome

 1. Click on the log in button An alert message came to enter
without entering username or username
password
2. Click on the log in button An alert message came to enter
after entering some username password
leaving password field blank
3. Click on the log in button after An alert message came to enter
entering some password but username
leaving username field blank

4. Click on the log in button after A message displayed on Log in page

entering some wrong about this
username but correct
password

Test case Ref No TCT-002

Functionality : Enter valid Data for customer registration

Expected outcome : The user should not get register any record without filling
all necessary fields and some error message follow The
user should not get registered again with same patient id

Step No. Data Used Actual Outcome

1. Click on the save button without An alert message came to each
entering valid details details and focused on the respective
fields
2. Click on the submit button A message displayed about
after entering a duplicate patient existence of such patient
id

6. RESULTS AND DISCUSSION

6.1 Test Reports

 Test Case No Date Pass / Fail

TCT-001 11/1/2023 Pass

TCT-002 02/02/2023 Pass

TCT-003 12/5/2023 Pass

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.

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.
However, there are many scopes to modify this software. As because due to shortage of time, we here
become unable to include many things. We are trying to cover all their existing system for sales return
records of the items but due to shortage of time we become unable to include many things. Due to lake of
time I here include none of them and a future scope one can develop these returns which are so much
essential. Only with a little more doing it is possible to design the formats for those returns. Moreover, an
on-line system will be more helpful to the organization. . With almost the same data with only a little
modification an on-line system can be designed to fulfill their demands. All these can be considered to be
future scope for this project.
 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.

It is hoped that this project will help the future developers to modify and implement the
system. After modifying some techniques of the programs, it will give us the best performance as
our requirements. The project will be very useful for the users.