MINOR PROJECT REPORT

On

ONLINE BOOK STORE SYSTEM

At

GOVERNMENT GIRLS POLYTECHNIC, AYODHYA

Submitted Towards Partial Fulfillment of

THREE YEAR OF DIPLOMA IN INFORMATION TECHNOLOGY

Under the Supervision of

Mrs. Rashmi Sonkar

SUBMITTED TO: SUBMITTED BY:

Mrs. Rashmi Sonkar Lakshmi Prajapati (E23220639000007),

(H.O.D. of IT) Sakshi Verma (E2322063900002),

Ananya Pandey (E2322063900004),

Saumya Srivastava (E2322063900003),

Anjali Tripathi (E2322063900002)

GOVERNMENT GIRLS POLYTECHNIC AYODHYA

Session: 2024-2025

ABSTRACT
The project's main goal is to develop an online book store where users can search for and make
purchases of books based on title, author, and subject. The user's chosen books are displayed in
a tabular format, and they can order them online using a debit card or credit card. Instead of
going to a bookstore and wasting time, the user can purchase a book on this website.

Many online book retailers, such as MPHOnline and BookDepository were developed using
HTML. I'd like to create a comparable website with.NET and SQL Server.

An online book store is a web application that allows customers to buy books online. Customers
can search for a book by title or author using a web browser, add it to their shopping cart, and
then purchase it using a debit or credit card transaction. The user can log in using his or her
account information, or new customers can swiftly create an account. They should include their
full name, phone number, and shipping address. A user can also provide feedback to a book by
rating it on a scale of one to five. The books are organized into several categories based on the
subject matter, such as Action and Adventure, Classics, Fantasy, Fiction, Non-fiction, Horror etc.

Customers can shop online for books at the Online Book Store using a web browser. A customer
can create an account, sign in, add items to a shopping cart, and make purchases using his or
her debit/credit card information.

When compared to a regular user, the Administrator will have more features. The Administrator
can add, delete, and edit book data, and member information, as well as confirm an order that
has been placed. The Online Book Store is built using the Master page, data sets, data grids,
and user controls.

ACKNOWLEDGEMENT

2
I'd would like to express my sincere appreciation to everyone who made it possible for me to
complete this project. I offer a special thanks to Dr. Kamaluddeen Usman Danyaro of UTP's
Computer and Information Sciences department, whose stimulating comments and support
helped me to coordinate my project, particularly in writing this report. I want to express my
gratitude to my family and friends who have always been there for me since I was a child. Last
but not least, I'd want to express my gratitude to all of my classmates in the Information
Systems and Information and Communication Technology batch for their support and
cooperation.

3
 TABLE OF CONTENT

ABSTRACT ………………………………………………………………………………………………………………………………...2

ACKOWLEDNGEMENT
……………………………………………………………………………………………………………….3

CHAPTER 1: INTRODUCTION ……………………………………………………………………………………….

…………….9

1.1 Background of Study ………………………………………………………………………………………….…….….9

1.2 Problem Statement …………………………………………………………………………………………………....10
1.3 Objective …………………………………………………………………………………………….……………………..11
1.4 Purpose and Scope of Study ……………………………………………………………………………………….12

CHAPTER 2: LITERATURE REVIEW AND THEORY ………………………………………………………………….……

13

2.1 Literature Review ………………………………………………………………………………………………….

…….13

2.2 Existing System …………………………………………………………………………………………………….

…….14 CHAPTER 3: METHODOLOGY

…………………………………………………………………………………………….…….18

3.1 Research Methodology

……………………………………………………………………………………………….18

3.2 Agile Methodology

……………………………………………………………………………………………………..19

3.3 Process …………………………………………………………………………………………………………...

………….20 CHAPTER 4: DESIGN …………….

…………………………………………………………………………………………….…….27

4
 4.1 Introduction …………………………………………………………………………….……………………..
………….27

4.2 Development Strategy ……………………………………………………………………………………..

………….27

4.3 Why chose the Web-Based System ………………………………………………………………………..

…….28

4.4 Design of the Online Book Store System

……………………………………………………………………….28
4.5 Database Design
………………………………………………………………………………………………………….33

4.6 User Interface Design

………………………………………………………………………………………………….34 CHAPTER 5:

IMPLEMENTATION AND EVALUATION……………….……………………………………..…….…….41

5.1 Introduction ………………………………………………………………………………………….

…………………….41

5.2 Development Tools and Technologies

………………………………………………………………………….42

5.3 System Testing ………………………………………………………………………………………..………….

……….42

5.4 Testing Methods

………………………………………………………………………………………………………….43

5.5 Test Data and Results ………………………………………………………………………………………….

……….47

5.6 Acceptance Testing ………………………………………………………………………………………………………

47 CHAPTER 6: CONCLUSION AND FUTURE

WORK………………………………………………………………………..48

5
 6.1 Conclusion …………………………………………………………………………………………………………….
…...49

6.2 Recommendation for Future Work ………………………………………………………………………..……

49

6.3 Lessons Learnt …………………………………………………………………………………………….………………

50

REFERENCES ………………………………………………………………………………….
………………………………………..51

APPENDIX A – OUTPUT

SCREENSHOT……………………………………………………………………………………….53 APPENDIX B –

CODING LISTS…………………………………………………………………………………………………….64

LIST OF TABLES

Gantt Chart for FYP 1

……………………………………………………………………………………………………………….20 Gantt Chart for FYP

2 ……………………………………………………………………………………………………………….23

LIST OF FIGURES ...........................................................................................................................................

Figure 1: MPHOnline.................................................................................................................................

Figure 2: BookDepository..........................................................................................................................

Figure 3: Amazon.......................................................................................................................................

Figure 4: Illustration of SDLC......................................................................................................................

Figure 5: Illustration of Agile Methodology...............................................................................................

Figure 6: Use case diagram for Web Module.............................................................................................

6
Figure 7.1: Register Interface.....................................................................................................................

Figure 7.2: Login Interface.........................................................................................................................

Figure 8: Admin Home Page......................................................................................................................

Figure 9.1: User Home Page......................................................................................................................

Figure 9.2: User Home Page......................................................................................................................

Figure 9.3: User Home Page......................................................................................................................

Figure 10: Shopping Cart Page...................................................................................................................

Figure 11.1: Form Interface (admin)..........................................................................................................

Figure 11.2: Form Interface (user).............................................................................................................

Figure 11.3: Form Interface (user) ……………………………………………………………………………………………

42

Chapter 1: INTRODUCTION

7
1.1 Background of Study
The advent of the internet and e-commerce has revolutionized the way people shop and access
information. . The book industry, in particular, has undergone significant changes with the rise
of online bookstores. The book industry, in particular, has undergone significant changes with
the rise of online bookstores. An online bookstore provides a platform for customers to
browse, search, and purchase books from the comfort of their own homes.

The concept of online bookstores is not new, with pioneers like Amazon and Barnes & Noble
launching their online platforms in the mid-1990s. However, with the rapid growth of
e-commerce and digital technologies, the online book market has become increasingly
competitive and dynamic.

In recent years, there has been a significant shift in consumer behavior, with more people
turning to online platforms for book purchases. According to a report by the Association of
American Publishers, online book sales have grown steadily over the past decade, with a
significant increase in e-book sales.

Despite the growth of online bookstores, there are still several challenges and limitations
associated with these platforms. For instance, many online bookstores lack personalized
recommendations, effective search functionality, and user-friendly interfaces. Moreover, issues
related to book availability, shipping, and customer support can also impact the overall user
experience.

In this context, our project aims to design and develop an online bookstore that addresses the
existing limitations and provides a seamless and enjoyable user experience. Our platform will
offer a wide range of books, personalized recommendations, effective search functionality, and
user-friendly interfaces. Additionally, our platform will prioritize customer support, book
availability, and shipping to ensure that customers receive their books in a timely and efficient
manner.

1.2 Problem Statement

The existing online bookstores lack personalized recommendations, effective search
functionality, and user-friendly interfaces, resulting in a poor user experience. Moreover,
8
 issues related to book availability, shipping, and customer support further exacerbate the
problem. As a result, book lovers are unable to find and purchase books efficiently, leading
to a decrease in online book sales.

Specific Problems
1. Inefficient Search Functionality: Existing online bookstores have limited search
functionality, making it difficult for users to find specific books.
2. Lack of Personalized Recommendations: Online bookstores fail to provide personalized
book recommendations, resulting in users missing out on relevant and interesting books.
3. Poor User Experience: Cluttered and complex interfaces make it difficult for users to
navigate and find books, leading to a poor user experience.
4. Book Availability and Shipping Issues: Online bookstores often face issues related to
book availability and shipping, resulting in delayed or cancelled orders.
5. Inadequate Customer Support: Existing online bookstores often lack effective customer
support, making it difficult for users to resolve issues or get help when needed.

1.3 Objective
1.3.1 Main Objective

9
 An online bookstore software project that serves as a central database for all of the
books in stock, as well as their title, author, and price. The goal of this project is to
create a website that serves as a central book store. This website was built with php on
the front end and SQL on the back end. Various book-related details are stored in the
SQL database. A user visiting the website will find a wide selection of books organized
by category. The user can choose a book and see its price. The user can even utilize the
website to look for certain books. After the user chooses a book, he/she must fill out a
form before the book is booked for the user.

Customers may shop for books online using a web browser thanks to the Online Book
Store Project. A customer can create an account, log in, sort books by category, add
books to a shopping basket, and pay their bill using their credit card information. When
compared to a regular user, the Administrator will have more options. He can edit the
author, publisher, book categories, book details, and member information, as well as
confirm an order.

The following are the three main components of the software:

1. Implementation of a new user registration and login process.
2. Allow the user to select any book.
3. Allow the user to purchase books.

1.3.2 Specific Objectives

• To design an online book store management system.

10
 • To analyze the problems in the existing system.
• To analyze the possible requirements for the new system.

1.4 Purpose and Scope of Study

1.4.1 Purpose

The purpose of an online shopping system would be to achieve the following goals:
• Create a web user interface for adding, viewing, and deleting records in
different areas.

• Create a user interface for inputting computer details.

• Provide a user interface for changing computer and accessory details.
• Provide a user interface that allows users to browse the store and select
things to purchase.

1.4.2 Scope

The main scope deliverables of the project would be to:

• Analyze and develop detailed specifications and requirements
• Prepare high-level and detailed system design specifications  Prepare a
test plan as well as test cases.
• Develop the system and write the code.
• Unit, integration, and system testing should all be performed.

Chapter 2: LITERATURE REVIEW AND THEORY

2.1 Literature Review

When we use Google to search for educational websites and applications, we will find a lot of
options. However, there is some ambiguity in selecting suitable content at the proper time.
Some websites have been developed that contain stories, novels, essays, and other types of
11
content. Electronic Commerce (e-commerce) applications allow multiple parties involved in a
commerce transaction to connect in order to shop for new, secondhand, rare, and out-of-print
books. Review of literature for an online bookstore. The prototype serves as a roadmap for
establishing a solid Online Book Ordering System based on user feedback, notably from the
perspective of academics, which will be handled by the university's book store. The arranging,
however, is still done manually.

According to a software development firm, an e-catalogue delivers vital information about

product specifications to potential customers. It makes it easier for potential customers to find
the items they want in the format they want. It is the ideal and ideal product catalogue because
it does not require printing, has no number or color restrictions, and does not require
distribution. The system is described as self-updatable in a few simple clicks, with the content in
the e-catalogue always being accurate and, best of all, requiring no reprinting. Furthermore,
the e-catalogue promotes the products on its own, with greater interactivity, consumer
personalization, and even a shopping cart for inquiries.

MPHOnline, BookDepository, and Amazon are few of the most popular online shopping sites
that employ an e-catalogue to display their products. The website lists the many types of books
that are available. The book cover can be found on the left side of the main frame, as well as
the book description, which includes information such as the title, author, price, and number of
volumes left to be sold, as well as customer ratings.

Chapter 3: METHODOLOGY

3.1 Research Methodology

The first step in starting this project is gathering all of the necessary requirements in order to
develop a website that is easy to maintain and meets user needs. The emphasis is primarily on
study into various online bookstores that are already operational. Accordingly, questionnaires

12
and interviews with target end users have been shown to be the most effective methods for
gathering exact data from them. The design paradigm starts with a prototype of the graphical
user interface (GUI) layer and then outlines the website's back end (database and system
architecture) system, which is only visible to the portal's administrators. The prototype's
construction was adjusted in response to end-user feedback in order to build an online book
catalogue that meets the project's requirements at the completion. Iteration occurs as the
prototype is refined to meet the user's needs while also allowing the developer to gain a better
understanding of what needs to be done. The website is then deployed on a web hosting to
make it available via the internet after the GUI design prototype is finalized.

Within a software project, the Software Development Life Cycle (SDLC) is a process that is
followed for a software project. It is a detailed strategy that describes how to build, maintain,
replace, and change or improve particular software. The life cycle is a mechanism for enhancing
software quality and the development process itself. During the software development process,
numerous software development life cycle models have been established and designed. To
assure success in the software development process, each process model follows a set of stages
specific to its type. Agile Methodology is the model I'm using for this project.

13
 Figure 4: Illustration of SDLC

3.2 Agile Methodology

To deliver a smooth execution of the project, a methodology has been chosen to assist in
managing the project phase by phase, beginning with the initiation and ending with the
closure. A methodology is necessary for selecting the best methods, practices, approaches, and
procedures from among the many available. As a result, Agile Methodology was chosen for the
development of the Online Book Store System platform. Agile technique is the ideal strategy to
complete this project because it divides it into phases and requires constant adjustments and
input until the final product is completed.

Agile methodology is an iterative project management strategy that allows a project to adapt to
changing working conditions and develop in a short amount of time. In this method, which is
referred to as "sprint," a project term is divided into shorter and repeatable stages. Sprint
lengths were decided during the project's early planning stages and will be reflected in the final
product.

14
 Figure 5: Illustration of Agile Methodology

3.3 Process

3.3.1 Research, Analysis and Gathering Requirement

This phase includes conducting literature reviews and analyses of existing systems in order to
determine the requirements and features for an online book system website. Prepare
documentation after evaluating the research study. Surveys and feedback are used to gather
requirements. Requirements are subject to change over time. The prerequisites for the Online
Book System platform are listed below:

1) A product catalogue on the home page

After a successful login, the user will be directed to this page. It will provide all of the
book categories and provide a search keyword option for finding the desired title. It also
has some unique elements, such as recommended titles and weekly special books.
2) Search
Search textbox provides the user with the option of searching by keyword. The book
title should be used as the keyword.

3) Advanced Search
The user can utilize advanced search to find a book based on the title, author, category,
and price range. The total number of books that match the specific search criteria will
be presented. The user can choose a book and add it to their shopping cart from here.
4) Book Description

15
 If a user wants more information about a book, he/she can click on the title and be
taken to a Book Description page. It includes annotations on the book's content as well
as a link to Amazon.com where you can read the book review.
5) Voting by users
A user can rate a book based on his or her interests. They can give it a five-star rating if
it's excellent, four if it's very good, three if it's good, two if it's regular, and one if it's
deficient. The final rating of a book is determined by the sum of all user ratings.
6) Shopping Cart
The user can manage a shopping cart that contains all of the books that they had
chosen. The user can change, delete, and update the contents of their shopping cart. A
final shopping cart summary is shown, which includes all of the products selected by
the user as well as the overall cost.
7) Managing User Account
To access all of the website's functions, each user should create an account. The user
can log in and out using the login and logout pages, respectively. The database will save
all of the user sessions.
8) Administration
Special functions for the Administrator will be granted, such as adding or deleting a
book category, adding or deleting a member, managing member orders, adding or
deleting a debit/credit card type, and so on.

3.3.2 Planning Phase

Project 1 2 3 4 5 6 7 8 9 10 11 12
Tasks/Weeks

Idea & Title

Proposal

16
 Introduction

Aim & Objective

Analysis & Survey

Methodology

Proposal Defense

Design &
Development

Interim Report
Submission

Table 1: Gantt Chart for FYP 1

Project 1 2 3 4 5 6 7 8 9 10 11 12
Tasks/Weeks

Design Phase

17
 Prototype
Development

Prototype Testing &

Maintenance

Prototype
Finalization &
Documentation

Dissertation
Submission

Viva Presentation

Table 2: Gantt Chart for FYP 2

3.3.3 Project Design Phase

In order to design a web site, the relational database must be designed first. The data model
and the process model are the two aspects of conceptual design. The data model specifies
which data should be stored in the database, whereas the process model defines how the data
should be handled. To put it another way, the data model is used to construct the relational

18
tables of a relational database. The process model is used to design the queries that will access
those tables and perform operations on them.

A decomposition diagram illustrates a system's top-down functional decomposition and

highlights its structure. The goal of the Functional Decomposition is to break down a system
step by step, starting with the system's main function and progressing through the
intermediate levels to the level of basic functions. More extensive process diagrams, such as
Data Flow Diagrams (DFD) start with this diagram. Data Flow Diagrams illustrate the flow of
data from external entities into the system, as well as from one process to the next. A DFD can
be drawn using four symbols:

i. Rectangles that represent external entities such as data sources and destinations.
ii. Ellipses, which represent processes that receive data as input, validate, process, and
output it.
iii. Data flows are represented by arrows, which can be electronic data or physical items.
iv. Data stores, especially electronic stores such as databases, are represented by
openended rectangles or a Disk symbol.

0-Level DFD:

19
DFD for Admin Process:

DFD for User Registration and Profile Update:

20
DFD for Shopping and Checkout Process:

21
3.3.4 Development, Testing and Review Phase

Development Phase includes writing codes using programming languages. The website will be
programmed using HTML and CSS. In the meantime, MySQL will be used as the database. This
process will be repeated until the client is satisfied with the final product.

Maintaining Phase test the website's functionality. This process will take place in parallel with
the development phase. This is to check that the programmed codes are working properly and
that there are no errors in the coding.

Review Phase includes obtaining feedback from users and testers. This process will be followed
once the finalized website has been created. This process is necessary in order to develop the
platform in the future. For the evaluation process, this website will be shared with a group of
users or testers.

22
 Chapter 4: DESIGN

4.1 Introduction

The design phase of the system development process determines the best solution for the
problem that was found during the analysis phase. The suggested system's comprehensive
blueprint is produced at the end of the design phase. This chapter discusses popular software
development processes and the proposed system, alternative solutions, design techniques, and
the Web-Based Book Store System overall design.

4.2 Development Strategy

The development strategy is the path to follow in order to meet the requirements that have
been identified. In terms of the Web Book Store System, numerous strategies have been
considered. Purchasing a set of commercial software can decrease development costs and time
while also providing more quality, but you may have to pay for certain needless features, it may
not match all of your requirements precisely, and it is not configurable. Standalone systems
have advantages such as being simple to set up and maintain, having fewer incompatibilities,
and having less security risks, but they are unable to handle remote users.

The Online Book Store System chose to construct a web-based system from scratch as its
development strategy. When software is built from scratch, the end result is software that is
exactly aligned to the defined requirements. In addition, a highly configurable and upgradeable
solution with few incompatibility difficulties is created. The ability to serve remote users via a
web-based system is critical in order to meet needs such as allowing clients to place orders,
searching for books, and tracking order status.

23
The well-defined methods for the purpose of system design and modelling are known as design
techniques. Each one has its own set of techniques, features, advantages, and disadvantages.
As a result, it should be carefully studied before deciding on a method.

4.3 Why chose the Web-Based System

• From any location, it's simple to keep track of stock processes and provide useful data.
• Because the database is centralized and everything is synchronized, maintenance is
simple.

• It is simple to set up.

• Client-server architecture with a web browser as the client interface is possible.
• The user is merely redirected to the proper pages.
• Because model-view-controller has been adapted, future updates and maintenance are
simple.

• By implementing a web-based solution, developer can save money on both hardware

and software.

• Web systems are platform independent, meaning it can run on any platform.

4.4 Design of the Online Book Store System

In order to make the design process and subsequent execution more efficient, Online Book
Store Web-Based System is organized into five parts.

• Purchase Module
• Stock Module
• Financial Module
• Web Module

24
 • Administration Module

Each module's top-level use case diagram is illustrated in the sub sections below. Case
narratives are used in some situations, and additional diagrams are provided as needed.

4.4.1 Purchase Module

Only the administrator has access to this module. Requisitions, purchase orders, purchase,
purchase return orders, and purchase returns are all covered in this section. Admin manages
requisitions and purchase orders as completed or cancelled. Before creating a new purchase
order, the admin examines the pending requisitions, checks their availability, and if everything
is in order, they can add it as a new book and place an order. Because the details provided by
the customer may vary and the availability of the agent is uncertain, we cannot use the
requisitions automatically for the purchase order procedure. They should be confirmed before
being added as a new book.

Case name Manage purchase orders

Actors Admin
Description Admin manages the purchase orders
Pre-conditions Admin must log in to the system
Main flow 1. Actor navigates to the ‘Purchase’ section.
2. System displays the section.
3. System provide options to add, complete and cancel purchase orders.
4. System updates and confirms.
Post-conditions None

25
4.4.2 Stock Module

This module contains three sections: Admin - the organization that supplies the books, Books -
the book details, and Stock - the stock details. Stock keep unit (SKU) is a standard term for
product ID, a unique code used to identify products in inventory control. The current status
determines the availability of functionalities such as edit and terminate.

Case name Manage Books

Actors Admin
Description Admin manages the books’ details
Pre-conditions Admin must log in to the system
Main flow 1. Admin navigates to the ‘Product’ section.
2. System displays the section with the book details.
3. System provide options to add, update and delete a book.
Post-conditions None

Case name Add Book

Actors Admin
Description Admin adds a new book
Pre-conditions The use case “Manage Books” must have been executed
Main flow 1. Admin navigates to ‘Add Product’ sub section.
2. System displays a form to fill.
3. Admin fills the form and sends.
4. System validates the inputs.
6. System adds the book and conforms.
Post-conditions The new book is added successfully

26
4.4.3 Financial Module

The function of this module is to manage the Dealers' credits and debits connected to sales and
purchases, not to track the financial position of the business. As a result, it does not comply to
any standard accounting principles. On-the-spot cash sales in retail.

Case name View Orders

Actors Admin
Description Admin views the orders and transactions
Pre-conditions Admin must log in to the system
Main flow 1. Admin navigates to the ‘Orders’ section.
2. System displays the section with the recent orders and
transactions details.
3. Admin updates the orders by pending or completed.
Post-conditions None

4.4.4 Web Module

The Web module is the front-end of the Web-Based System, and it is in charge of making it
easier for customers and suppliers to engage with the business. This handles a variety of
functions, including making purchases online, viewing order history, and so on.

27
 Figure 6: Use case diagram for Web Module

4.4.5 Administration Module

This module is responsible for managing the Web-Based System. This includes managing system
users, access levels, system log management, and data backup compilation. If required, the
administrator can deactivate or reactivate the users. The data backup is also generated at the
administrator's request. Super admin is a virtual administrator who has complete control over
all modules. However, it is only recommended that a new administrator be created. Operators
and managers are created by the administrator.

Case name Manage Users

Actors Admin
Description Admin updates users
Pre-conditions Admin must log in to the system
Main flow 1. Admin navigates to the user administration section of the system.

28
 2. System displays the user’s details.
3. System allows admin to edit, deactivate or reactivate the user
based on the user’s current status.
4. System updates the user and confirms.
Post-conditions None

4.5 Database Design

One of the most important components of any data-driven application, such as a Web-Based
System, is the database. As a result, appropriate approaches are used to ensure the database's
integrity. MySQL is used as the backend database in this project. MySQL is a database
management system that is free and open source. The following are some of MySQL's features:

• MySQL is a database management system that uses a relational model. Rather than one
big table, a relational database stores data in multiple tables. These tables can be linked
together to make it easier to access and manage data.

• MySQL is a free and open-source database management system. Anyone can use and
modify the database software to meet their specific needs. It's quick, dependable, and
simple to use to enhance the level of performance.

• MySQL is a database engine that runs in several threads. A multithreaded application

accomplishes multiple tasks at once, as if multiple instances of the application were
executing at the same time.

• MySQL provides a lot of advantages because it is multithreaded. Each incoming

connection is managed by a single thread, with an additional thread that is always
running to manage the connections. Multiple clients can perform read operations at the
same time, but only one client can access the data being modified while writing.
Despite the fact that the threads share the same process space, they operate separately,
allowing multiprocessor machines to spread the thread across many CPUs as long as the

29
 host operating system supports multiple CPUs. Multithreading is a critical component
for MySQL's performance goals. It is the foundation upon which MySQL is based.

• An ODBC driver is used to link the MySQL database to Java. Open Database Connectivity
(ODBC) is a frequently used database access Application Programming Interface (API).
The ODBC driver is a library that implements the ODBC API's functions. It handles ODBC
function calls, sends SQL requests to the MySQL server, and then returns the results to
the application. If necessary, the driver alters an application's request so that it is
compatible with MySQL's syntax.

4.6 User Interface Design

One of the most important factors in determining an application's user friendliness is its user
interface. Because it is the component with which the user interacts. The following are some of
the guidelines that were followed:

• Colors, text styles, component structure, and functionality, such as navigations, should
all be consistent across all interfaces.

• All interface effects and dynamic changes should have a clear meaning for the user, such
as links with a red pointer cursor for deletion or deletion warning, and so on.

• It should be simple for users to understand. Interfaces should be as basic as possible,

with helpful features such as tool tips, popup messages, and notifications
recommended.

• Error and confirmation messages, for example, should be consistent, straightforward,

and free of technical terms.

• For interfaces such as forms, the data input process should be improved and as many
errors as possible detected. It would be helpful to provide default values and
watermarks, as well as to use lists and option buttons instead of text boxes for selecting
data rather than typing.

30
 4.6.1 Register and Login Interface

The system registers and login page, which is part of the developed system, is the primary
interface for logging into the system. Both pages are the initial interface a user encounters
in any computerized system. As a result, by properly designing and managing errors, the
user might develop a positive attitude toward the rest of the system. The main register and
login interface for Web-Based Book Store System is shown in Figure 7 and 8.

Figure 7.1: Register Interface

Figure 7.2: Login

Interface

31
4.6.2 Administration Home Page

Figure 8 shows the home page of the administrator's account. The final output was
developed based on the research into other similar web-based system interfaces. It displays
the user's basic information, including login history. Web-Based Book Store System Admin
page is shown in Figure 8.

Figure 8: Admin Home Page

4.6.3 User Home Page

Since first impressions can influence how many people perceive your company, the web
homepage is typically the first opportunity to hook a potential customer. The homepage of
the website should be well-designed because it is the anchor that ties the rest of the
website together.

32
Figure 9.1: User Home Page

Figure 9.2: User Home Page

33
 Figure 9.3: User Home Page

Figure 9.4: User Home Page

34
4.6.4 Shopping Cart Page

The aim of this program is to give users with an online store where they would purchase
books from the comfort of their own homes. For this purpose, a shopping cart is
implemented. The customer can choose the books they want, add them to their shopping
cart, and pay for them with a debit or credit card. The user's order will be shipped based on
the delivery method selected at the time of purchase. Figure 10 illustrate the main
shopping cart page.

Figure 10: Shopping Cart Page

4.6.5 Forms

The forms shown in Figure 11 are used to add new products to the system, send a message
to admin, and checkout products. Depending on the type of data to be entered, different
form elements have been chosen. Error warnings are also designed to keep data input
mistakes to a minimum.

35
Figure 11.1: Form Interface (admin)

Figure 11.2: Form Interface (user)

36
 Chapter 5: IMPLEMENTATION AND EVALUATION

5.1 Introduction

The implementation phase entails the development of an executable program based on the
design created during the design phase. Selecting programming languages, additional tools and
technologies like as frameworks, selecting hardware platforms, and coding the system are some
of the main activities carried out during this phase.

The system is evaluated against multiple factors such as functional and non-functional
requirements in order to guarantee that it is working properly and meets all of its specified
standards during the evaluation phase of the software development process. This chapter
discusses the web-based system testing methodologies, test plan, and test cases, as well as test
data and outputs and acceptance testing.

This chapter covers the application's implementation environment, the framework, the
development tools used, the application's structure, and an explanation of the key code
segments.

5.2 Development Tools and Technologies

• Visual Studio Code for coding.

• Connectivity with MySQL database.
• .Net Core (MVC)

37
The Web-Based Book Store System was built using the following technologies:

• The web pages were developed using Visual Studio Code. The new features that were
added in the new version are developed to increase the semantics of web pages. This is
the most basic web-related language, and it assists in maintaining a clear and conscious
system structure.

• The pages were styled with CSS3. It makes it possible to create a unified design for the
entire system in an easy-to-manage manner.

• When developing the system, PHP was employed as the server-side object-oriented
programming language.

• The application's database was implemented using MySQL.

• The client-side scripting was implemented with JavaScript. Especially for the form
validation process on the client side. It is a scripting language that allows the system
components to be continuously changed.

• • JQuery was used to improve the JavaScript development process and to provide
various effects on webpages.

• Bootstrap – It’s a free framework for developing websites and online apps. It includes
design templates that are based on HTML and CSS. With a single code base, Bootstrap
easily and efficiently scales the application. Bootstrap speeds up and simplifies frontend
web development.

5.3 System Testing

The planning of a testing phase is critical for both the development and completion of a system.
The test plan should be able to test the overall system's functionality. By extensively testing a
system, it is possible to identify and fix errors that occur as a result of the system. Multiple test
scenarios were used to evaluate the implemented system. The test plan has continued to test

38
the system units since the development began. Upon completing the system, it was thoroughly
evaluated to determine whether it could execute as planned. As a result, this testing stage

assisted in the early detection of errors.

Following the system unit testing, integration testing was conducted, which allowed for the
detection of errors. To evaluate the functionality of the fully developed web-based application,
system testing was performed as the final stage.

5.4 Testing Methods

In software engineering, a number of software testing methodologies and styles have been
introduced to test various features of various systems. The major testing methodologies utilized
widely in the software testing process are Black Box testing and White Box testing. In Black Box
testing, the function is evaluated by comparing the output to the input without taking into
account the inner structure of the function, whereas in White Box testing, each of the
function's logical routes is evaluated while taking into account the inner structure of the
function.

Various styles of testing were utilized at various stages of the web-based system's development.
During the design phase, unit testing was performed on each individual function of each
module to check that they were correct. Following the completion of unit testing, integration
testing was performed to check that the functionality of the modules when they interacted
with one another was correct. Following the conclusion of the integration testing, system
testing was performed on the entire system to guarantee its reliability.

Do refer the results on Appendix A – Output Screenshot below.

39
5.4.1 Purchase Module

The following table list a relevant test case for the Purchase Module.

Test No. Test Description Testing Procedures Expected Result

1. View purchases / Navigate to Orders section. Display the sets of recent

orders purchases and placed
orders.

2. Delete purchase Click ‘Delete Order’ button in Update the placed order
order particular placed order. as deleted.

3. Complete purchase Click ‘Update’ button in particular Update the purchase

order placed order. Fill the relevant details order as confirmed.
in the dropdown bar as pending or
completed and click ‘Update’
button.

5.4.2 Stock Module

The following table list a relevant test case for the Stock Module.

Test No. Test Description Testing Procedures Expected Result

1. Add new book Go to Products, add details and click Book is added and
‘Add Book’ button. confirmed.

2. Edit book Click the ‘Update’ button in front of Update the details and
the particular book record, edit confirm.
relevant fields and confirm.

40
 3. Delete book Click the ‘Delete’ button in front of Book is deleted from the
the particular book record and record.
confirm.

5.4.3 Financial Module

The following table list a relevant test case for the Financial Module.

Test No. Test Description Testing Procedures Expected Result

1. View transactions Navigate to Dashboard section. Display most recent set

of transactions.

5.4.4 Web Module

The following table lists the most relevant test cases for the Web Module.

Test No. Test Description Testing Procedures Expected Result

1. Main menu Click each menu item of the main Load the relevant page.
navigation menu.

2. Place inquiry Fill in the form in the contact page. Add the inquiry entry &
display confirmation.
Press send button.
3. Customer / admin Enter id and password of the customer / admin is
login customer / admin. Click login. able to login.

4. Add books to the Clicks ‘Add to Cart’ button of the Update the shopping
shopping cart particular product. cart.

5. View shopping cart Click the shopping cart button. Display the shopping
cart.

41
 6. Remove books from Click delete button in front of the Remove the particular
the shopping cart particular book. book from the shopping
cart.

7. Clear shopping cart Click ‘Delete All’ button of the Remove the entire books
shopping cart area. in the shopping cart.

8. Place order Click ‘Proceed to Checkout’ button. Add the new order entry,
redirected to the orders
page & display
confirmation.

9. View order history Login to the customer account. Click Display the orders
orders menu item. placed by the customer.

5.4.5 Administration Module

The following table lists the most relevant test cases for the Administration Module.

Test No. Test Description Testing Procedures Expected Result

1. User login Enter valid user ID and password. Load the relevant default
section according to the
Click login button.
user role.

2. Delete user Click ‘Delete User’ button in user Deleted particular user
entry. For admin purposes only. in the user entry.

5.5 Test Data and Results

42
Test data is a collection of information that is used in the testing process. When preparing test
data, some of the requirements were carefully followed, such as collecting not only valid but
also invalid datasets to cover all parts of the testing process and selecting the smallest data set
possible to reduce extra complexity. In unit and integration testing, dummy datasets were
utilized, but in Web-Based system testing, datasets retrieved from the current system were
used. The test results generated during the execution of the test cases were also documented,
which will come in handy for future review and maintenance. Do refer to appendix B – Coding
Lists.

5.6 Acceptance Testing

After the system testing was completed, the users were chosen to reflect the WB's whole
business operation. After that, all of the input was collected and analyzed, and slight changes
were made in response to the users' requests.

User Acceptance Testing was entered into the developed system to begin testing. There were a
few small changes that needed to be made to the system. The client tested the entire system
by modifying the user's rights. Following the system's testing, it was requested that the system
be tested with staff members. Under the instruction of the Administrators, they had tested the
system by logging onto their user accounts. The admin pointed up a few minor changes that
needed to be made. When they finished their session, they expressed satisfaction with the
system. All of the users who recommended minor changes after completing the user
acceptance testing gave a positive response. Rather of continuing to use the old way, the client
indicated that the newly designed system would allow the business to operate more efficiently
and smoothly.

Chapter 6: CONCLUSION AND FUTURE WORK

43
6.1 Conclusion

Online shopping has gained importance not only from the standpoint of the entrepreneur, but
also from the standpoint of the customer, since the Internet has become a vital resource in
modern business. Electronic shopping opens up new business prospects for the entrepreneur,
and it allows customers to compare prices. According to a report, most online shoppers are
impulsive and decide whether or not to stay on a site within the first few seconds. "Website
design is similar to the interior design of a store." If the shop appears to be run-down or similar
to hundreds of other shops, the customer is likely to move on to the next site." As a result, I
created the project to give the user as much ease of navigation, data retrieval, and essential
feedback as possible. The user is given with an ecommerce web site that can be utilized to
purchase books online in this project.

I utilized PHP to make this a web application. PHP (XAMPP) has a number of advantages,
including improved performance, scalability, security, and simplicity. To create a web
application with PHP, I'll need a programming language like JAVA, HTML, or anything similar.
The language used to develop this application was JAVA. PHP connects with the database using
the MySQL server because it offers in-memory caching, which reduces the need to visit the
database server frequently, and it is simple to deploy and manage. MySQL was chosen as the
back-end database because it is one of the most widely used open-source databases, with rapid
data access, ease of installation, and simplicity.

A user-friendly shopping cart functionality must match a solid shopping cart design. Viewing the
contents of the customer's cart and being able to remove or add items to the cart should be
easy.

44
This project's shopping cart application includes a variety of features aimed at making the
customer's experience more pleasant. This project will help me understand how to make an
interactive web page and the tools that go into making it. The project's architecture, which
contains a Data Model and a Process Model, shows how the database is constructed with
various tables, as well as how data is accessed and processed from the tables. The project's
development has provided me a thorough understanding of how PHP is utilized to develop a
website, how it connects to a database to obtain data, and how the data and web pages are
modified to provide a shopping cart application to the user.

6.2 Recommendation for Future Work

Software development is a never-ending process that maintains the software's life based on the
changing needs of the user throughout time. The project will undoubtedly be designed with
easy modification and enhancement in mind, which may be required from time to time. This
project, on the other hand, can be modified in a variety of ways. Because of limited a time
frame, I am unable to incorporate many things here. But I will attempt to cover all of the
existing system that the Online Book Store should consist.

During the development phase, various improvements were found that would be considered in
future versions of the Web-Based Online Book Store System:

• Introduce the Barcode System

Adding an effective Bar Cord Reader helps to improve data capture reliability at the
operational level. The accuracy of data entry for sales and purchasing activities can be
improved by employing system-generated barcodes for items' SKUs.

• To manage the business in the future, integrate application and back-office operations
connected to the technology of the existing website and internal system as Enterprise
Resource Planning (ERP).
45
 • Provide an SMS service when orders are processed and for special jobs. By
implementing this recommendation, users will be able to acquire relevant information
from the system without having to enter the system or their email account.

• As the Intranet deals with a considerable amount of sensitive information, improve

security by putting in a standardized Firewall and Gateways methods to tighten security
even more.

• Obtain an SSL Certificate to ensure that all transactions are conducted over a secure
channel using https.

• Make plans to secure an Intellectual Property (IPR) for the company's website.

6.3 Lessons Learnt

As a student participating in a degree program, this was a fantastic opportunity for me to put
what I had learned in class into practice. Because the domain area was so extensive, it allowed
me to get experience in a variety of business strategies and broadened my understanding of
how to map connected business operations into a computerized system. It also gives me an
excellent opportunity to put everything I've learned into practice. The creation of the Web-
Based Online Book Store System helps in gaining valuable knowledge in system development
throughout the SDLC.

Various software engineering approaches, such as requirement collecting techniques, OOD

techniques, and designing systems using UML, are practiced during the analysis and design
phases, which will be useful in my future job. This phase also assists me in improving my
knowledge of PHP, AJAX, JQuery, and other programming languages. The evaluation phase
provided a great opportunity for me to practice evaluating systems, particularly on the user
side. A better understanding of how to communicate with a real customer was gained. In
addition, the working environment included web-related languages.

46
APPENDIX A – OUTPUT SCREENSHOT

View purchases / orders

47
Edit purchases

Add new book

48
Edit book

49
 Delete book

Add books to the shopping cart

50
 View
shopping
cart

APPENDIX B - CODING LISTS

51
This part contains several Web-Based Book Store System codes that has been explained in the
design and implementation chapter.

Solution Explorer

52
 AppSettings.json

Category Model

53
 Product Model

54
 _Layout.cshtml

Index.cshtml(Home)

55