Tribhuvan University

Faculty of Humanities and Social Sciences

"ONLINE ART GALLERY"

A PROJECT REPORT

Submitted to:
Department of Bachelor in Computer Application
Himalaya Darshan College
Biratnagar

In partial fulfillment of the requirement for the Bachelors of Computer Application

Submitted by
Tilashma Shrestha (107302081)
Santoshi Kumari Gupta (107302089)

December, 2023

Under the Supervision of

Mr. Kamal Shah
 Tribhuvan University
Faculty of Humanities and Social Sciences

Himalaya Darshan college

Supervisor’s Recommendation
I hereby recommend that this project prepared under my supervision by Tilashma
Shrestha and Santoshi Kumari Gupta entitled “ONLINE ART GALLERY” in partial
fulfillment of the requirement for the degree of Bachelor in Computer Application is
recommended for the final evaluation.

…………………….
Mr. Kamal Shah
Project Supervisor
Himalaya Darshan College
Biratnagar-10

i
 Tribhuvan University
Faculty of Humanities and Social Science
Himalaya Darshan College

LETTER OF APPROVAL

This is to certify that this project prepared by Tilashma Shrestha and Santoshi Kumari
Gupta entitled “ONLINE ART GALLERY” in partial fulfillment of the requirements for
the degree of Bachelor in Computer Application has been evaluated. In our opinion it is
satisfactory in the scope and quality as a project for the required degree.

___________________
Mr. Kushal Niroula
Er. Sumit Kumar Shah
Internal Examiner
HOD, IT
Department of IT
Himalaya Darshan College
Himalaya Darshan college

Official Stamp

Mr. Sunil Sharma

External Examiner

ii
 Abstract

An online art gallery is a website that display artworks. Usually, the online gallery is run
as a business, with the purpose of displaying the artwork being to promote it to potential
buyers. Buyers need to login first and then proceed for buying paintings. Buyers can view
the art list as per their choices. Authentication and authorization are done. Here, all the
activities of confirmation, adding Arts and user handling activities are controlled by admin
of the system. The system is built using HTML, CSS, JAVASCRIPT, PHP and MYSQL in
front end and backend.

iii
 Acknowledgement

We would like to express our deepest appreciation to all those who provided us the
possibility to complete this report. However, it would not been possible without the kind
support and help of many individuals.
A special gratitude we give to our final project supervisor Mr. Kamal Shah, whose
contribution in stimulating suggestions and encouragement, helped us to contribute our
project specially in writing this report. Furthermore, we would also like to acknowledge
with much appreciation the crucial role of coordinator Er.Sumit Kumar Shah, who gave the
permission to use all required equipment and the necessary materials to complete our
project. Last but not the least, many thanks go to our teachers, friends, guardians who
directly or indirectly helped us in achieving the goal. We would like to appreciate all the
guidance which has improved our presentation skills thanks to their comment and advices

iv
 TABLE OF CONTENT

SUPERVISOR’S RECOMMENDATION…………………………………………………i
LETTER OF APPROVAL ............................................................................................... ii
ABSTRACT ................................................................................................................... iii
ACKNOWLEDGEMENT .............................................................................................. iv
TABLE OF CONTENTS………………………………………………………………….v
LIST OF TABLES ......................................................................................................... vii
Chapter: 1 Introduction ................................................................................................ 1
1.1 Introduction ............................................................................................................... 1
1.2 Problem Statement .................................................................................................... 1
1.3 Objectives……………………………………………………………………………..1
1.4 Scope and limitation .................................................................................................. 1
1.4.1 Scope………………………………………………………..……………….….1
1.4.2 Limitation……………………………………………………………..………....2
1.5 Methodology ............................................................................................................. 2
1.6 Report Organization ................................................................................................... 3
1.7 Roles…………………………………………………………………………………...3
Chapter 2: Background Study and Literature Review ................................................ 4
2.1 Background study ...................................................................................................... 4
2.2 Literature Review ...................................................................................................... 4
Chapter 3: System Analysis and Design ....................................................................... 6
3.1System Analysis ......................................................................................................... 6
3.1.1 Requirement Analysis........................................................................................ 6
3.1.2 Feasibility Study ............................................................................................... 7
Figure 3.3 Gantt Chart…………………………………………………………….8
3.1.3 Data Modeling (Entity Relationship)……………………………………………...9
3.1.4 Process Modeling ………………………………………..……………………….10
3.2 System Design………………………………………………………………………..
3.2.1 Architectural Design…………………………………………………………….11
3.2.2 Database Schema Design………………………………………………………..12

v
 3.2.3 Interface Design………………………………………………………………....13
3.2.4 Physical DFD…………………………………………………………………...15
Chapter 4: Implementation and Testing .................. ………………………………….18
4.1 Implementation ....................................................................................................... 18
4.1.1 Tool Used .................................................................................................... 18
4.1.2 Implementation details of modules…...………………………………….19
4.2 Testing……………………………………………………………………….……….19
4.2.1 Unit Testing……………………………………..………………….………..19
4.2.2 System Testing…………………………………..………………….……….19
Chapter 5: Conclusion and Future Recommendation ...................................................... 24
5.1 Expected Outcomes ................................................................................................. 24
5.2 Conclusion .............................................................................................................. 24
5.3 Future Enhancements .............................................................................................. 24
Appendices .................................................................................................................... 25
References ..................................................................................................................... 30

vi
 LIST OF FIGURES
Figure 1: Waterfall Model ................................................................................. 2
Figure 2: Use-case Diagram ............................................................................. 6
Figure 3: Gantt chart. ........................................................................................ 8
Figure 4: ER Diagram ....................................................................................... 9
Figure 5: Context Diagram .............................................................................. 10
Figure 6: Level 1 DFD. ................................................................................... 10
Figure 7: Architecture Design ......................................................................... 11
Figure 8: Database Schema Design ................................................................. 11
Figure 9: Context Diagram .............................................................................. 14
Figure 10: Level 1 DFD of Online Art Gallery…………………………………………15

vii
 LIST OF TABLES

Table 4.1: Test Case 1-Registration Form ....................................................... 19

Table 4.2: Test Case 2-Login Form ................................................................ 20

Table 4.3: Test Case 3-Adding product/category by admin ………………….20

Table 4.4: Test Case 4-checking user message and respond it ............. ………20

Table 4.5: Test Case 5-user checking out ....................................................... 21

Table 4.6: Test Scenario 01-User ordering product (with no login) ................. 12

Table 4.7: Test Scenario 02-User ordering product (with login) ...................... 23

Table 4.8: Test Scenario 03- Add/deleting product by admin (with login)…...24

vii
i
 Chapter 1: Introduction
1.1 Introduction
Art gallery management system is the selling and purchasing of art of different
varieties. This system will store the information of each painting. The purchase is just
click away with the help of this system, you don’t have to go to some shops and buy
from selected stuffs. This application will be able to available you a wide range of arts.
With the rapid modernization of the world, we are introduced to advances in all areas
of human activity.

People don’t even have time for themselves and their hobbies because of their works.
By considering these facts, online art gallery system is going to be developed. The
system can help the user to see the varieties of arts and add to their carts.

1.2 Problem Statement

The problem of Online Art Gallery is listed below:

• Absence of proper return and refund facility.

• Extra charges for the paintings to the customer through the agents.

1.3 Objectives
The objective of this project is to study how the Online Art Gallery works and process of
running in present world.

• To maintain the authenticity of the products (arts).

• To provide customer service with timely response to any queries they have for an arts.

• To provide genuine art to the customer.

1.4 Scope and limitation

1.4.1 Scope

This project consists of the following scopes:

• Product range: It offers a wide variety of genuine arts to customers.

• Website design and user experience: It provide a user-friendly and visually

appealing website that allows customers to browse products and make purchases
easily. The website design can also incorporate search functionality, customer
reviews

1
1.4.2 Limitation

The limitations of the system are:

• Technical issues: Online art gallery are reliant on technology to operate, which
can lead to technical issues such as website downtime or other glitches. This can
be frustrating for customers who are trying to make a purchase or access
information.

• No online payment: Our system is built just for the buying and selling of arts
online. There is no any feature of online payment, we go through cash on delivery
(COD) process. If necessary we will update this feature in future.

1.5 Methodology

Figure 1: Waterfall model

In this model, the life cycle is divided into phases where one phase can be started only after
the completion of the previous phase. We choose waterfall model is suitable for small type of
project and it is simple to understand and use

2
  Requirement Analysis: In this phase, all the possible requirements of the systemto be
developed are captured and documented.

 System Design: In this phase, the requirement specification are studied and thesystem
is designed. It helps in specifying hardware and system requirements.

 Implementation: With inputs from the system design, the system is developed intoa
small program called unit, which are integrated into the next phase.

 System Testing: all the units developed are tested for any error and faults and then
integrated into a system.

 System Deployment: After all the testing is done, the product is deployed into themarket

 System Maintenance: After deployment, there may arises issues in the system. To fix

this, maintenance is done to bring changes in the product.

1.6 Report Organization

Chapter 1: This chapter introduce the system and the problems, given an overview about
the study.

Chapter 2: This chapter covers the literature review which is the previous related work that
has been done before.

Chapter 3: This chapter explains the selects methodology that we are going in this project
planning through the methodology.

Chapter 4: This chapter discuss about the implementation and testing.

Chapter 5: This chapter discusses the conclusion, recommendations and future works to
improve this study.

1.7 Roles

Name Specific Task

Santoshi kumari Gupta System design , front end development

Tilashma shrestha System analysis , back end development and

testing

3
 Chapter 2: Background Study and Literature Review
2.1 Background study
Software keeps changing during its life cycle. It must be created to adapt to the current
requirements to change the trends and problem. Previously, the buying and selling of
art was on the shop in the market through face to face interaction which consume lots
of time and effort. Currently, there are some few system existed now. Our system is
solely focused on selling of arts in online processes. It provides capabilities for
selecting a particular painting and have them for use.

2.2 Literature Review

There are many Art Gallery System project conducted previously by many researchers.
However most of them are outdated or involve manual system. Some of the previous
researches are:

Art Gallery System by Cloud

art Attendant is a cloud-based collection management system, which enables galleries, art
dealers, and institutions to upload, organize, and publish artworks. Artists can maintain a
private collection and sell or rent studio archives through an online marketplace. [1]
Features include secure data storage, remote access, activity tracking, categorization,
digital asset management, and bulk image uploads. Artists can create a catalog of art
inventory with details such as availability, value, location, acquisitions, and collections. It
facilitates quick searches by letting users sort collections by title, status, cost, inventory
number, and more.
Art Gallery System by Tamzin Lovell-Miller

Artfundi is an inventory management solution that helps collectors, artists, and galleries
track and manage artworks across locations. It enables users to create a database of all
artworks with information such as artist details, corresponding images, categories,
locations, status, creation date, and more.

It also provide features for cataloging artworks, managing collections, organizing

exhibitions, and facilitating communication between artists and galleries. These platforms
may also offer tools for marketing, sales, and documentation. [2] It would be beneficial to
explore the official website or contact the creator directly for detailed information. To get
the most accurate and current information, consider checking the latest updates on the
official Artfund website, reviewing any press releases or announcements, and exploring
4
related articles or reviews. If Artfundi has gained popularity or recognition within the
art community, you might find articles or discussions that provide additional insights into
its functionalities and impact on the art world.

Additionally, users can sort artworks into multiple categories such as print, mixed media,
paintings, textiles, photography, film/video, drawings, and more

5
 Chapter 3: System Analysis and Design
3.1 System Analysis
System analysis is a process of gathering and interpreting facts, diagnosing problems and the
information about the Online Art Gallery System to recommend improvements on thesystem. It
is a problem solving activity that requires intensive communication between the system users
and system developers.

3.1.1 Requirement Analysis

Functional Requirements
The functional requirements are the requirements that describe what the system does
i.e. the functioning or behavior of the system. It explains what has to be done byidentifying the
necessary task, action or activity that must be accomplished.

 Admin will be able to control, insert, delete and update the art-works.

 User will be able to login.

 User can check the art-works available.

Use Case Diagram

Figure 2: Use Case Diagram

6
 Non-Functional Requirement
Non-functional requirements are the criteria for evaluating how a software system should
perform and a software system must have certain quality attributes in order to meet
nonfunctional requirements .

• Security
User will only be able to access the system using authorized username and password.
Only the authorized user can change their profile content and password.

• Performance
It handles and supports multiple users at a time.

• Availability
It will be available to all the registered users.

3.1.2 Feasibility Study

A feasibility study is an analysis that takes all of a project's relevant factors into account
including economic, technical, legal, and scheduling considerations to ascertain the
likelihood of completing the project successfully..

Technical feasibility
Technical feasibility focuses on gaining an understanding of the present technical
resources of the organization and their applicability to the expected needs of the
proposed system. It is an evaluation of the hardware and software and how it meets the
needs of the purpose system.

Operational feasibility

Operational feasibility is an important aspect of a feasibility study for an online art

gallery. By evaluating staffing, inventory management, order fulfillment, customer
service, supplier management, marketing and sales, and technology infrastructure, we
can ensure that our online store is operationally feasible and capable of delivering the
desired results.
Economic feasibility

Economic feasibility is an aspect of a feasibility study for an online art gallery. By

evaluating start-up costs, operational costs revenue, sale projections, pricing strategy and

market trends and competitions. We can determine whether our online art gallery store is
economically feasible and has the potential to generate profits and be sustainable in the
long run.
7
3.3 Gantt chart
Gantt chart is a management tool that shows the work completed time period over a period
of time in relation to the time planned for the work. It includes the list of task on the left
part while it includes timeline that visualize work in the right side.

Weeks 1 2 3 4 5 6 7 8 9
Work
Planning

Analysis

Data
Modelling
Process
Modelling
Database
Implementation
Coding

Testing

Documentation

Fig 3: Gantt Chart

RED > TILASHMA SHRESTHA

BLACK > SANTOSHI KUMARI GUPTA

8
3.1.3 Data Modeling

Diagramming data flows of creating a conceptualrepresentation of data objects and their

relationships to one another.

Figure 4: ER-Diagram of Online Art Gallery

9
3.1.4 Process Modeling

For process modeling of online mobile shopping, context diagram and DFD up to level 1
are as follows:

3.1.4.1 Context Diagram

In the context diagram there are two entities, user and admin. The corresponding data
flow from each entity is shown in the context diagram below.

Figure 5: Context Diagram of Online Art Gallery

10
3.1 System Design

The system design of online art gallery that consists of architectural design, database

schema design and user interface design are shown as follows: -

3.2.1 Architecture Design

Figure 7: Architecture design

11
3.2.2 Data Schema Design

Figure 8: Database Schema Design

12
3.2.2.1 Level 1 DFD

Figure 6: Level 1 DFD Diagram

13
3.2.3 Interface Design

 Registration page UI

• Login page UI

14
• Admin panel UI

15
3.2.3 Physical DFD

3.2.4.1 Context Diagram

Figure 9: Context Diagram of Online Art Gallery

16
3.2.4.2 Level 1 DFD

Figure 10: Level 1 DFD of Online Art Gallery

17
 Chapter 4: Implementation and Testing

4.1 Implementation
In this phase working of the overall system is checked. It deals with the complete process
of building and implementing it. It focuses on the technical aspects of the system starting
with identifying the necessary components and building the relevant relationship among
subsystems for the smooth and efficient operation of the system.

4.1.1Tool Used
Vs. code-It is a streamlined code editor with support for development operation like
debugging task running and version control. It supports many programming languages.
Draw.io:-It is proprietary software for making diagrams and charts. The software lets us
choose from an automatic layout. They have a large selection of shapes and hundreds of
visual elements to make our diagram or chart one-of-a-kind.

4.1.1.1 Programming Language

Client Side
 HTML
HTML is used for developing user layout
 CSS
CSS is used for designing the web pages of the system
 JavaScript
JavaScript is used for validating and creating user functionalities.
Server Side
 MYSQL
It is used as database where data are stored and retrieved from mysql is a tool used to
manage databases and servers, so while it's not a database, it's widely used in relation to
managing and organizing data in databases.

 PHP
PHP is the most widely used open source and general purpose server side scripting language
used mainly in web development to create dynamic websites and applications

18
4.1.2 Implementation details of modules

1. Admin Module:
Admin module of Online Art Gallery of the following functions.
 Login to the system

 Add product

 Response to users message

 Manage order
2. User Module:
User module of Online Art Gallery consists of the following functions.
 Register and login to the system

 View/Buy product

 Add product to wish list and cart

 Contact with admin

 Update Profile

4.2 Testing
Testing is the process of running a system with the intention of finding errors. Testing can
be done using varieties of level
4.2.1 Unit testing
Unit testing is a type of testing which is done by software developers in which the
smallest testable module of an application like functions, procedures or interfaces- are
tested to ascertain if they are fit to use.

Table 4.1: Test Case 1 - Registration form

Test Case Description Expected Result Test Result

1 Enter valid form field User get registered Successful

details

2 Enter valid form field Display validation Successful

details error

19
 Table 4.2: Test Case 2 - Login form

Test Case Description Expected Result Test Result

1 Enter valid email System should Successful

address and password redirect to respective
user page.

2 Enter invalid email Display error result Successful

address and password

Table 4.3: Test Case 3 - Adding product/category by admin

Test case Description Expected Result Test Result

1 Enter all the details asked System should show Successful

and click submit. the data in admin table
and store in database.

2 Enter details with leaving System should show Successful

required field blank and some alert message.
click submit.

Table 4.4: Test Case 4 – Checking users message and respond it.

Test case Description Expected Result Test Result

1 Click on message Message will be sent Successful

section and check for to users and status
message and click on will be
reply button to reply automatically
the message of user. changed to replied

2 Checking user Status will remain Successful

message but not unchanged.
replying it.

20
 Table 4.5: Test Case 5 – User Checking Out

Test case Description Expected Result Test Result

1 Login to the system and User gets redirected to Successful

click checkout. checkout page.

2 Click checkout without Users get redirected to Successful

logging to the system. login/registration page

4.2.2 System testing

System testing is a type of software that is performed on a complete integrated system
to evaluate the compliance of the system with the corresponding requirements. This
testing is done to ensure that the system meet the requirement. We tested whether the
admin and user can perform their roles as per designed or not.

Table 4.6: Test Scenario 01- User ordering product (with no login)

Test Test case Test case Test Data Expected Actual output Status
scenario Id outcomes

TC 1 Load Type Home Home page Pass

Homepage URL: page loaded
home loaded

TC 2 Add Click: Cart Product Product is added Pass

Test
Product to button should be to cart.
Scenario cart. added to
cart.
01

TC 3 Click on Click a Redirect to Redirect to Fail

checkout link: checkout login/registration
button on page. page.
cart page. Checkout

21
 Table 4.7: Test Scenario 02- User ordering product (with login)

Test Test Test Case Test Data Expected Output System Status
Scenario Case output
ID

TC 1 Load Type URL: Home page Home page loaded Pass

Homepage home loaded

TC 2 Login Type URL: Redirect to Redirect to home Pass

user login Homepage if page
correct email and
password
Test
Scenario
02 TC 3 Registration Type URL: Acknowledgment Acknowledgement Pass
User link
link
registration

TC 4 Add product Click: Product should be Product is added Pass

to cart. Cart button added to cart. to cart

TC 5 Click checkout Click a link: Redirect to Redirected to Pass

button on cart checkout page. checkout page as
page. Checkout
user is already
logged in.

22
 Table 4.8: Test Scenario 03- Add/deleting product by admin (with login)

Test Test Test Test-Data Expected Output Actual Output Status

Scenario Case Case
ID
TC 1 Login Type Redirect to admin Redirected to Pass
UR dashboard if valid admin dashboard
L:admin login username and
password.

TC 2 Product Click a link on List all of the List all the Pass
dashboard: product to be product.
Product displayed.

TC 3 Enter Click a link on New form should be Product form is Pass

product product page: displayed where displayed.
Test details Add product Details aboutproduct
can beadded.
Scenario 03

TC 4 Submit Click a Redirect to product Redirected to Pass

the page and data product pageand
link:
details. should be added on data had been
Submit database. added on database.

TC 5 Delete Click a Specific product Specific product is Pass

added should be deleted Deleted from
link:Delete
product from database and Database and
frontend. frontend.

23
 Chapter 5: Conclusion and Future Recommendation

5.1 Expected Outcomes

With the help of this project opportunity, we gained real world experience in web
development and system development. In the completion of this project, we felt that
this project was very beneficial in terms of experience and skill development.
Some of the practical knowledge we have learnt can be pointed as follows.

i. Reduces the time of buyers to buy arts. ii. Importance of time management and
schedule working and how it can improve the outcome.
iii. To provide genuine arts to the customers.

5.2 Conclusion
The project is developed to buying and selling of different arts and paintings. The users will
easily select their art and submit their feedback to the administration. The administration
can view and record the feedback for future reference.

5.3 Future Enhancements

Till now, our system is developed to buying and selling of an arts of user's interest. But in future,
to enhance our project we can add changes to meet the demands of our customers.

 We can add a payment feature for online transaction.

 We can use QR code to directly pay through the system.
 We can use SMS service for receiving notification of feedback.

24
Appendices

Admin Login Page

User Login Page

25
Homepage before Login/Register

User View page After Login

26
 Order history of Admin page

ssssss

User messages in Admin page

27
28
29
References
[1] artAttendant [Online]
Available: https://www.softwareadvice.com/inventory-management/artattendant-profile/
[2] Artfundi [Online]
Available: https://artfundi.tech/
[3].ArtLY [Online]
Available: https://en.wikipedia.org/wiki/Art.

30