A Hahahaha H
A Hahahaha H
CHAPTER 1
INTRODUCTION
To manage the details of gallery, exhibition, artwork and artist. It manages all the sales and
inventory in the gallery. The purpose of the project is to build and application program to
reduce the manual work.
To tracks all the details about the sales of the artwork, the customer that bought it, etc. It
manages the information about the artwork. Provides an information and description of the
artworks left, thereby increasing the efficiency of managing the gallery. The organization can
maintain a computerized record of the artwork present in the gallery.
To helps in the utilization of the resources in an effective manner. It maintains a list of all the
customers and the various artwork that they have bought and the money that have invested in
each.
To maintain the record of exhibitions and various sales made during it. The objective of
developing such computerized system is to reduce the paper work and safe of time in art
gallery database management, thereby increasing the efficiency and decreasing the work
load.
Artwork Management: Organize and update artwork details like title, artist and medium.
Artist Profiles: Maintain comprehensive artist profiles with biographical information and
portfolio.
Customer Management: Track customer information and preferences for personalized
interactions.
Exhibition Tracking: Record exhibition details including dates, locations, and participating
artists.
Security and Access Control: Implement security measures like data encryption and role-
based access control.
Integration and Scalability: Integrate with other systems and scale for future growth.
CHAPTER 2
REQUIREMENTS
The requirements can be broken into 2 major categories namely hardware and software
requirements. The former specifies the minimal hardware facilities expected in a system
in which the project has to be run. The latter specifies the essential software needed to
build and run the project.
HARDWARE REQUIREMENTS
The hardware requirements are very minimal and the program can be run on most of
the machines.
SOFTWARE REQUIREMENTS
The software requirements are very minimal and the program can be run on most of
the machines.
Development Environment: XAMPP for PHP and MySQL.
IDE: VS code, PHP, HTML and CSS.
Operating System: Windows 11
Web Browsers: Google Chrome
AI Language Model: ChatGPT
FUNCTIONAL REQUIREMENTS
CHAPTER 3
DESIGN
GALLERY TABLE
CREATE TABLE GALLERY
(GID VARCHAR (20) PRIMARY KEY,
GNAME CHAR (20),
LOCATION CHAR (20));
EXHIBITION TABLE
CREATE TABLE EXHIBITION
(EID VARCHAR(20) PRIMARY KEY,
GID VARCHAR(20),
STARTDATE DATE,
ENDDATE DATE,
FOREIGN KEY(GID) REFERENCES GALLERY(GID) ON DELETE CASCADE);
ARTWORK TABLE
CREATE TABLE ARTWORK
(ARTID VARCHAR (20) PRIMARY KEY,
TITLE VARCHAR (20),
YEAR INT,
CUSTOMER TABLE
CREATE TABLE CUSTOMER (CUSTID VARCHAR(20) PRIMARY KEY,
GID VARCHAR(20),
ARTID VARCHAR(20),
FNAME1 CHAR(20),
LNAME1 CHAR(20),
DOB DATE,
ADDRESS CHAR(20),
FOREIGN KEY(GID) REFERENCES GALLERY(GID) ON DELETE CASCADE,
FOREIGN KEY(ARTID) REFERENCES GALLERY(ARTID) ON DELETE CASCADE);
ARTIST TABLE
The trigger is made such that when a new record is inserted into a Gallery table, it automatically
changes the lowercase name into uppercase in the backend.
CHAPTER 4
4.1 IMPLEMENTATION
The implementation of the art gallery database involves a systematic approach to design,
develop, and deploy a robust system tailored to the specific needs of the gallery. Firstly, a
comprehensive analysis of the gallery's requirements is conducted, including the types of artwork
to be cataloged, the information to be tracked for each piece, and the user roles and permissions
necessary for efficient management.
Following the analysis phase, the database schema is designed, outlining the structure of tables,
relationships between entities, and data attributes. This schema serves as the blueprint for
creating the database using a relational database management system (RDBMS) such as MySQL,
PostgreSQL, or Microsoft SQL Server.
Next, the database is populated with relevant data, including details of artworks, artists,
customers, sales transactions, and exhibition history. Data validation mechanisms are
implemented to ensure data integrity and consistency, preventing errors or discrepancies in the
database.
The frontend interface for interacting with the database is developed, providing gallery staff with
intuitive tools for adding, editing, and querying artwork information, managing customer
records, and generating sales reports. The frontend may be implemented using web technologies
such as HTML, CSS, and PHP, or through custom desktop applications.
Additionally, security measures such as user authentication and authorization are integrated into
the system to safeguard sensitive information and restrict unauthorized access.
Finally, rigorous testing is conducted to validate the functionality, performance, and reliability of
the art gallery database. This includes unit testing individual components, integration testing to
verify interactions between modules, and user acceptance testing to ensure the system meets the
gallery's requirements.
Once testing is complete and any identified issues are resolved, the art gallery database is
deployed to production environments, where it serves as a centralized repository for managing
artwork inventory, facilitating sales transactions, and analyzing gallery performance.
A database connection is a facility in computer science that allows client software to talk to
database server software, whether on the same machine or not. A connection is required to send
and receive commands.
The database connection is established using the MySQL Improved extension (mysqli).
The code defines the following variables to connect to the database:
$servername: This variable stores the hostname or IP address of the database server. In
the code you provided, it is set to "localhost", which means the database server is
running on the same machine as the PHP script.
$username: This variable stores the username for the database account. In the code you
provided, it is set to "root".
$password: This variable stores the password for the database account. In the code you
provided, it is set to an empty string (""). It is not recommended to store database
passwords directly in code as it is a security risk.
$dbname: This variable stores the name of the database that the script should connect to.
In the code you provided, it is set to "art_gallery”.
CHAPTER 5
TESTING
This chapter gives the outline of all testing methods that are carried out to get a bug
free system. Quality can be achieved by testing the product using different
techniques at different phases of the project development. The purpose of testing is
to discover error. Testing is the process of trying to discover every conceivable fault
or weakness in a work product. It provides a way to check the functionality of
components sub-assemblies and/or a finished product. It is the process of exercising
software with the intent of ensuring that the software system meets its requirements
and user expectations and does not fail in an unacceptable manner. There are
various types of test. Each test type addresses a specific testing requirement.
CHAPTER 6
RESULTS ANALYSIS
This section describes the screens of “Art Gallery Database”. The snapshots are shown
below for each module.
SNAPSHOTS
This is the main page that shows all the operations which are present in Art Gallery
Database.
Gallery page
The selection page is the next displayed as soon as the table is selected in Main Page. Gallery
table contains Insert, Search, Display and Delete tables where values can be inserted, deleted,
etc.
Exhibition Homepage
The selection page is the next displayed as soon as the table is selected in Main Page. Exhibition
table contains Insert, Search, Display and Delete tables where values can be inserted, deleted,
etc.
Contacts homepage
The selection page is the next displayed as soon as the table is selected in Main Page. Contacts
table contains Search, Display and Delete tables where values can be displayed, deleted
CONCLUSION
A database was created for a market that can use it for keeping track on art gallery
Galleries are divided into many art galleries. Galleries have different names, locations, etc.
Each gallery will have different exhibitions and each exhibition will have a start and end
date. The galleries will have different artist displaying their artwork. The model can also be
adapted to meet other purposes and thus be used for other projects. The database structure
is quite simple, which makes it easy for also other programmers to understand it. In
conclusion, a database is a far more efficient mechanism to store and organize data than
spreadsheets it allows for a centralized facility that can easily be modified and quickly
shared among multiple users. Having a web based front end removes the requirement of
users having to understand and use a database directly, and allows users to connect from
anywhere with an internet connection and a basic web browser. It also allows the possibility
of queries to obtain information for various surveys. Due to the number of users reading and
modifying student data in the department, it is an ideal use for such a system.
FUTURE WORKS
Integration with online payment gateways for seamless transactions.
Implementation of advanced search and filter functionalities for artwork and artist
discovery.
Incorporation of augmented reality (AR) features for virtual art exhibitions.
Development of mobile applications for on-the-go access to gallery information.
Integration with social media platforms for marketing and promotion.
Implementation of machine learning algorithms for personalized recommendations based
on customer preferences.
Enhancement of reporting and analytics capabilities for deeper insights into sales trends
and customer behavior.
Integration with inventory management systems for real-time tracking of artwork
availability.
BIBLIOGRAPHY
BOOK REFERENCES:
[1] Head First PHP & MySQL by Lynn Beighley & Michael Morrison.
[2] Murach's PHP and MySQL by Joel Murach & Ray Harris.
[3] Eloquent PHP: A Programmer's Guide to PHP by Steve Matthews
WEBSITE REFERENCES:
My SQL and PHP
[4] https://www.w3schools.com/php/
[5] https://www.w3schools.com/sql/