Database Design for Art Gallery Management System

The given assignment presents a comprehensive database design for an art gallery management system. The system includes various entities such as customers, employees, artists, paintings, orders, and genres. The design features normalized tables, user-friendly forms for data entry and modification, and reports for quarterly/annual customer, order, and painting details. This setup aims to streamline information gathering, storage, and processing for the gallery's smooth functioning.

Database Design Concepts 1
Database Design Concepts
Student's Name:
Instructor's Name:
Date:

Database Design Concepts 2
Contents
Task 1..........................................................................................................................................................3
1.1- Analyze the key issues and application of databases within organizational environments [1]....3
Issues with database management systems........................................................................................3
Applications for database management systems....................................................................................4
Sharing Information.............................................................................................................................4
Eliminating Duplicates.........................................................................................................................5
Ensure Security....................................................................................................................................5
Backups...............................................................................................................................................5
1.2- Critically evaluate the features and advantages of database management systems. [1][2]........6
Concurrent Use....................................................................................................................................6
Structured & Described Data...............................................................................................................6
Here is a simple example of how data can be structured into tables:.................................................7
Clean Layers.........................................................................................................................................7
Data Integrity.......................................................................................................................................7
Atomic Transactions............................................................................................................................8
Data Persistence..................................................................................................................................8
Data Views...........................................................................................................................................8
Task 2..........................................................................................................................................................9
2.1- Analyze a database developmental methodology for the given case study. [3]...............................9
Database development involves three important stages....................................................................9
2.2-Discuss entity-relationship modelling and normalization for the given case study. [1][2][3][4]......13
Entity Relationship Diagram..............................................................................................................14
Normalization....................................................................................................................................15
Task 3........................................................................................................................................................17
Design of Tables.....................................................................................................................................17
Sample queries to extract data from the system...................................................................................22
Form Design...........................................................................................................................................23
Evaluation of Design..............................................................................................................................28
Support Documentation........................................................................................................................29
References.................................................................................................................................................31

Database Design Concepts 3
Task 1
1.1- Analyze the key issues and application of databases within organizational
environments [1]
Issues with database management systems
Many organizations face serious issues with respect to data management. They find it difficult
to manage huge volumes of data efficiently. To be more precise, it is quite difficult for
organizations to handle multiple tasks at ease. When it comes to data management, serious
hassles are seen with data organization, storage and maintenance. Some companies struggle
because data serves as the backbone of their operations. They spend loads of money on
business operations that take care of mission critical data.
Without the right kind of data management systems, organizations and businesses are not able
to generate upright results. They find it hard to synchronize and manipulate data productively.
For example, businesses are unable to gather data from various systems like project
management, student information, list of library books, payroll and inventory. These are
scenarios with versatile business operations cannot be carried forward.
Without proper data management methods, organizations tend to perform tasks manually. This
means, tasks require more time and effort to be completed. In fact, data cannot be structured
or categorized to suit the needs of an organization or company.
In places where database management is done manually, the following issues are seen:
1) It is difficult to maintain the integrity of information
2) It is difficult to share data efficiently.

Database Design Concepts 4
3) It is difficult to judge the accuracy and validity of information.
4) It is not possible to reuse information effectively.
5) It is difficult to maintain data quality.
6) It is difficult for upper management to track the overall performance of their business.
Indeed, it needs lots of organization and structure to ensure sound business
performance.
In very simple terms, both big and small organizations face issues in connecting five major
components. This includes people, data, procedures, software and hardware. When these
components are not in sync, it can be difficult to focus on better and revenue generating
aspects of a business. That is where database management systems come into the picture.
Applications for database management systems
There are plenty of applications for database management systems in an organization. First of
all, organizations can use database management systems to store huge volumes of information.
It is essential for companies to focus on data. Customers can be attracted only with the right
kind of information. Data is valuable for organizations of all sizes. It has to be handled precisely
and with lots of care. Information present in a company’s database should be flawless.
Sharing Information
Database management systems prove to be useful when you wish to share information. Based
on user privileges, you can share information. Even if your business is located in different
countries, you don’t have to worry about data sharing. Multiple users can access data
simulataneously from different business spots. This is a unique feature that sets relational

Database Design Concepts 5
database management systems apart! You will have quick access to all necessary information.
With right data at the right time, you can offer better customer service. This is a way of
facilitating better work.
Eliminating Duplicates
The talk about database management systems will remain incomplete without the elimination
of duplications. Database management systems should be used in places where data
duplication has to be eliminated. DBMS centralizes information. Centralization removes the
need for duplicate information. This is a common problem faced by many business owners. As a
company adopts to DBMS systems, they don’t have to be concerned about duplicates.
Ensure Security
Another important application for database management system is to ensure security. An
organization is bound to have different levels. Employees at each level will have unique
privileges and requirements. Database management systems can be used to handle these
requirements and privileges. You can decide and assign access to users based on their role. This
will improve confidentiality and security of data. In fact, it is very easy to maintain employee
data too. That is because everything can be digitalized, protected and accessed from anywhere.
Backups
Database management systems can be backed up easily. This is another critical reason to use
DBMS. Organizations have the freedom to store data with “availability” in mind. That way, the
organization will never lack or lose information. Even when hardware devices fail, they will have
a way of regaining important data.

Database Design Concepts 6
On the whole, database management systems are necessary to support all internal operations
of an organization. When data has to be used and shared safely, database management
systems prove to be handy. An efficient database can handle specialized information easily. It is
required to ensure and improve business operations.
1.2- Critically evaluate the features and advantages of database management systems. [1]
[2]
Database management systems offer a unique set of advantages. These benefits help
organizations like Shoengalleric with easy data management and smooth business operation.
Concurrent Use
Concurrent use is an important benefit in using database systems. For organizations like
Shoengalleric, concurrent use improves the economy of the entire system. Database storage
and capture will not be redundant. This means, the system can be operated from a central
location. All control will be handled centrally. This is when data manipulation becomes efficient.
A very good example of concurrent data use would be:
Imagine a travel database of a huge transport agency. Employees are bound to be
located in different branches. They will access the database concurrently for gathering and
booking journeys. Each travel agent should be able to access and work on the database without
any hassles. When they make a booking, cancelation or an update, everyone else should be able
to see the changes.

Database Design Concepts 7
Structured & Described Data
Structured and described data is the fundamental benefit of database management systems.
Every data column in your database will have a complete description and definition.
Additionally, you can control the way data is related to one another. Data in DBMS systems are
divided systematically and are linked carefully. There is a way to store and access data from the
DBMS.
Here is a simple example of how data can be structured into tables:
Id [number] Name [string] DOB [date] City [string]
1 Tom 12/12/2012 New Town
2 Jane 01/01/2013 Grande Road
Clean Layers
Efficient database management systems separate applications and data. The application
doesn’t have to worry about physical data storage. It doesn’t have to be concerned about data
format, storage, encoding or anything that is related to the physical part of a system. Most
companies like Shoengalleric can rely on communication languages like SQL to interact and
process data. Because data and applications are neatly separated, internal reorganization and
improvements become easy. The changes will have no influence on the application software.

Database Design Concepts 8
Data Integrity
DBMS became famous for data integrity. This is a byword for qualities like reliability and quality.
In the broader sense, integrity ensures the protection of data from unauthorized usage. Any
unauthorized changes will not be allowed too! Data in systems is a reflection of real world facts.
Logically, data has to be accurate to a good extend. Database management systems tend to
support tasks and bring only consistent data. All transactions can be controlled to maintain
consistency.
Atomic Transactions
Database operations are known as transactions. By definition, transaction is a collection of
actions that can be carried out in a database to ensure consistency. One transaction translates
data from one particular state to another consistent state. All transactions in a database should
be atomic. That means, you will not be able to break transactions into smaller groups. Likewise,
transactions should not result in an inconsistent database. Here is an example to demonstrate
this feature and its benefits.
Image a bank transfer, where money goes from one account to another. Money has to
be debited from one account and credited into another account. This is an example of a
consistent transaction. The transaction is atomic too. If money was only debited or credited
from a single end, the transaction will result in an inconsistent state. Database management
systems perform transactions in a similar fashion.

Database Design Concepts 9
Data Persistence
Database management systems ensure data persistence too. This is a feature that makes sure
data is not destroyed unless the user has programmed or manually wants to. The overall
lifetime of data in a database management system depends on the user. It doesn’t depend on
the system. All changes that are carried out in the database should be persistent too. When a
transaction makes a change to a database, it should not crash or increase the risks in using the
system.
Data Views
Data views play an important role in database management system. A single database can have
numerous users. Each user is bound to have desires, requirements and access rights. The
individual view of data can differ from one user to another. Data view is treated as a subset of
stored information. Here is an example to demonstrate data views in a system:
A school handles data about teachers and students. Apart from personal information,
there can be administrative details too. And, the administrative details will not be shown to
everyone. Database management systems will give you the freedom to display views based on
the rights and needs of users.
Task 2
2.1- Analyze a database developmental methodology for the given case study. [3]
Database development begins with requirements gathering. To begin with, the needs of
Shoengalleric should be understood. The proposed system, necessary documents and

Database Design Concepts
10
functional needs will be gathered. By the end of this step, Shoengalleric’s requirements will be
detailed and properly established. Data requirements are very important because it pictures
the overall database. The requirements don’t have to describe how data would be processed.
But, it should identify what the data items can be, the kind of attributes involved, relationships
and possible constraints.
Database development involves three important stages. The stages are:
1) Conceptual data modeling
2) Logical database design
3) Physical database design
Conceptual data modeling
Once the requirements of Shoengalleric is clear, data analysis would happen. During this step, a
conceptual data model is developed. The ultimate aim of data analysis is to produce a
descriptive outline of data. This data should meet all user requirements. It should take care of
low level and high level data properties. For example, in Shoengalleric’s database, the
employee details, customer details and gallery details should be identified. Possible attributes
for an employee table would be id, name, address, location and contact number. Conceptual
data model provides a formal and acollective representation of what is shared between
developers and Shoengalleric. This stage of development focuses only on what is needed and
not on how to achieve it.
During conceptual data modeling, the focus is on Shoengalleric’s data. It doesn’t stress on the
eventual use of data in various processes. Or, how data is going to be showcased in

Database Design Concepts
11
Shoengalleric’s galleries. The entire model is concerned on the structure and meaning of data.
Without a proper conceptual model, it will be difficult to move to the next stage of
development.
Logical database design
The next step in developing Shoengalleric’s database would be logical design. Logical design
focuses on the development of a logical schema. It determines the kind of database system
involved. It revolves around object-oriented, relational and network systems. The relational
representation is independent of the database management system. Relational representation
serves as an input to the logical design phase. The output of logical design would be a detailed
relational specification alias logical schema. It has all the tables and constraints requested by
Shoengalleric. The tables and constraints should satisfy the organization’s data description.
During the design stage, the right tables must be created to represent the database. The tables
should control duplication, ensure flexibility and represent all constraints in the best possible
way. The tables will describe how data should be stored and manipulated in Shoengalleric’s
database management system. Many novice database designers believe that relational
databases like SQL can be used to implement the conceptual data model immediately.
However, it is wrong and rather inefficient to translate the conceptual model to SQL tables
directly. You should have a logical schema to ensure integrity, usability, completeness, flexibility
and efficiency in Shoengalleric’s database. Throughout the process, tables will be flexed! Flexing
is the process of capturing ideas simultaneously and bending into something that can serve the
purpose. The output of logical database design serves as an input for the next stage. The output
consists of a global logical data model. This includes the entity relationship diagram, supporting

Database Design Concepts
12
documents, relational schema and data dictionaries. All these sources of information are
required for the physical design process. If Shoengalleric’s logical design is efficient and reliable,
the final database management system would be spotless. It can be used for long periods of
time without any changes. That is because a good logical design can resolve performance
issues, physical considerations and meet user requirements.
Physical database design
The next stage of development is physical database design. This is where the implementation of
secondary storage is understood. During the physical design phase, all file organizations, basic
relations and indexes are identified. This phase is important because it results in efficient data
access, takes care of integrity constraints and manages all security concerns. The logical
database design of Shoengalleric focuses on “what”. On the other hand, the physical database
design of Shoengalleric focuses on the “how” part. In this phase, the designer makes important
decisions on how a database would be implemented. The final outcome would be tailored to a
specific database management system. Feedbacks from Shoengalleric ‘s logical and physical
design is required to improve performance. The physical database design model can affect the
logical data model too!
Steps in designing the physical database of Shoengalleric.
1) The global logical data model should be translated carefully. This model involves
operations, derived data and enterprise constraints.
2) The physical representation of data should be identified. This includes the selection of
offline organization, disk space needs, transaction flows and selection of indexes. This is

Database Design Concepts
13
a very important step in the physical design of databases. Optimal file organization is
required to improve the performance of Shoengalleric’s DB. All base relations and
indexes should be optimized to improve performance.
The ultimate aim of physical database design is to store and retrieve data efficiently. Several
factors govern the way you produce data. This includes the following:
1) Transaction throughput time – the total number of transactions users can perform in
the Shoengalleric database within a specific time interval.
2) Disk storage – the total amount of disk space required to store Shoengalleric’s database
files. Disk space should be optimized carefully.
3) Response time – the total amount of time required to complete a transaction in
Shoengalleric’s database. From an end users point of view, response time should be as
low as possible.
Once physical database design is done, Shoengalleric’s database will be ready for usage. It will
have all necessary tables for storing and retrieving data. Additionally, table updates can be
done without any concerns.
2.2-Discuss entity-relationship modelling and normalization for the given case study. [1][2][3]
[4]
Entity relationship data modeling is a very old technique. It has been around for three decades.
The ER model is essential for modeling the overall structure of Shoengalleric’s database
management system. It is an abstract outline that explains the relationship between each
entity. ER models translate to relations easily.

Database Design Concepts
14
Entity relationship diagrams revolve around two major concepts:
1) The entities are nothing but things. In Shoengalleric’s database, the customers, galleries,
paintings and artists are entities.
2) Relationships describe the associations and interactions between entities. For example,
the artist draws paintings and sells it at the gallery. This is a simple relationship upon
which the entire Shoengalleric database can be built.
There are several different types of entities in a database system. Independent entities are also
known as kernels. These entities serve as the backbone of the database. In the Shoengalleric
database, the galleries, artists and employees are independent entities. These entities have the
following qualities:
1) The entities have composite or simple primary keys
2) Independent entities are the building blocks of any database
3) Primary key of independent entities cannot be foreign keys
4) The independent entities don’t depend on other entities for existence. These entities
can function without any dependencies.
The next type of entity would be the dependent entities. These entities depend and can be
derived from other tables. They have the following qualities:
1) Dependent entities can be used to connect two independent entities together
2) These entities depend on two or more tables
3) Databases with dependent entities have associative tables that can carry at least 2
foreign keys.

Database Design Concepts
15
4) Dependent entities may contain other attributes.
5) The primary key of dependent entities is not simple.
Entity Relationship Diagram
The entity relationship diagram produces lots of information. It can be used to understand
more about entities, its relationship and characteristics. Once the entity relationship diagram is
drawn, tables for Shoengalleric’s database can be gauged. The tables are formed after
normalization.
Normalization
Normalization is required to eliminate data redundancy, ensure easy access and integrity. With
normalization, Shoengalleric’s database will have carefully arranged attributes that have
dependencies between attributes in such a way that all database integrity constraints are
satisfied. Rules for normalization are formal and standardized. It is possible to create databases
with optimal structure after normalization. There are three important types of normal forms.
1) The first normal form doesn’t have multi valued attributes. No table can have columns
with multivalued attributes.
2) The Second normal form eliminates partial dependencies.
3) The third normal form eliminates all non-key dependencies. A database in 3NF will be
void of insertion, deletion or update anomalies.
After normalization, the third normal forms for Shoengalleric’s database will be as follows:
Employee(id, name, contact number, address, location, role id)

Database Design Concepts
16
Role(id, title, description)
Gallery(id, title, location)
Employee-Gallery(emp-id, gallery-id)
Exhibition(id, gallery-id, title, organizer, date)
Customer(id, name, age, preferences, birth location)
Artists(id, name, location, type)
Paintings(id, category, gallery id, price)
Artist-painting (artist id, painting id)
Artist-genre(artist id, genre id)
Genre (id, title, description)
Buyer (id, painting id, date, quantity, total cost, status)
Task 3
Planning

Database Design Concepts
17
The aim of this design to develop a database management system that can manage the art gallery’s data
and functions. The design has to take care of common problems like data redundancy, security,
reporting and validity.
System Definition
The Shoengalleric’s database has many departments. Here is a simple outline of the
departments and functions performed:
No Department Function
1 Visitor This department is responsible for handling all visitors who enter
into the galleries. They gather information about the visitors, and
their interests. If a visitor intends to buy a painting, they help them
with the procedure.
2 Gallery This department is responsible for handling Shoengalleric’s very
many galleries. As a new gallery is opened, modified or closed, this
department handles it all!
3 Painting Shoengalleric is famous for its paintings. This department is
responsible for tackling all paintings. It keeps track of every
painting, its value and age. When new paintings are added, sold or
replaced at the gallery, this department is involved.
4 Artist This department is responsible for managing artists who are
involved with the gallery. When an artist wishes to display their
paintings at the gallery, they must come in touch with this
department.
5 Employee-Admin This department is responsible for handling all administrative
tasks. This includes: hiring of new employees, opening a new
gallery, organizing events and more.
6 Events This department is responsible for organizing events at
Shoengalleric’s gallery. Tasks like adding, modifying and improving
events are done by this department.
Requirements gathering and analysis
Details of all entities, attributes and relationships for the gallery would be as follows:

Database Design Concepts
18
No Entity Attributes Relationships
1 Employees Employee ID, name, contact number,
address, location, role
Works
2 Gallery Gallery id, title, location Exhibits
3 Exhibition id, gallery-id, title, organizer, date Showcases
4 Customer id, name, age, preferences, birth location Visits
5 Artist id, name, location, type Paints
6 Painting id, category, gallery id, price Displayed
7 Buyer id, painting id, date, quantity, total cost,
status
Buys
Design – Conceptual

Database Design Concepts
19
Design – Logical
Design of Tables
The art gallery’s database begins with table design. Important tables in this database are:
1) Employee table holds details of employees in the gallery. The employees are identified
using a unique “id”. They are assigned a role that is identified using another unique id.
2) The role table describes all roles in the gallery. The role table maintains a unique id
along with the role’s title and description.

Database Design Concepts
20
3) The gallery tables hold details of all galleries. The table keeps track of all branches and
its location. A unique id is used to identify the gallery tables.
4) Employees are associated to the galleries by an employee-gallery table. In this table,
both the employee id and gallery id serves as the primary key.
5) Exhibition table is a collection of all exhibitions hosted by the gallery. This is an
important table that can be accessed and modified at each branch. The exhibition table
has a unique id. It holds important details like the place of exhibition, date and
organizer.
6) The artist table holds details of all “artists” who showcase their works at the gallery. The
artists can belong to different genre. There is a separate genre table to keep track of the
artist’s area of specialization.
7) The genre table helps in managing all kinds of artwork that gets showcased at the
gallery. Each genre is identified using a unique id.
8) The gallery manages all paintings showcased at the exhibitions using a paintings table.
The paintings table links to the artist and exhibition table.
9) The Buyer table is responsible for holding details about buyers who invest on paintings
or offer donations to the gallery. The gallery entertains both buyers and visitors. Visitors
are not expected to pay any fees. The buyers are identified using a unique id.
The overall structure of tables for the gallery would be as follows:
Employee Table
Field Data Type Description

Database Design Concepts
21
Employee id Integer Primary Key
Name Short Text Hold name of employee
Address Long Text Employee’s residential or contact
address
Contact Number Number(10) Employee’s personal contact number
Location Short Text The branch at which the employee
works
Date of Birth Date The employee’s date of birth
Email Long Text Employee’s mail address
Domain id Short Text Unique domain id assigned to
employee
Gallery Table
Field Data Type Description
Gallery id Integer Primary Key
Title Short Text Hold name of gallery
Address Long Text Gallery’s official address
Location Short Text Branch location
Role Table
Field Data Type Description
Role id Integer Primary Key

Database Design Concepts
22
Title Short Text Role Name
Description Long Text Holds details about role
Employee-Gallery Table
Field Data Type Description
Employee id Integer Primary Key
Gallery id Integer Primary Key
Exhibition Table
Field Data Type Description
Exhibition id Integer Primary Key
Title Short Text Name of Exhibition
Genre Integer Foreign Key
Gallery id Integer Foreign Key
Organizer Integer Foreign Key
Date Date Date of exhibition
Artist Table
Field Data Type Description
Artist id Integer Primary Key

Database Design Concepts
23
Name Short Text Holds name of artist
Genre Integer Foreign Key
Location Short Text Current location of artist
Painting Table
Field Data Type Description
Painting id Integer Primary Key
Title Short Text Name of painting
Genre Integer Foreign Key
Artist Integer Foreign Key
Artist-Painting Table
Field Data Type Description
Painting id Integer Primary Key
Artist id Integer Primary Key
Painting-Gallery Table
Field Data Type Description
Painting id Integer Primary Key
Gallery id Integer Primary Key

Database Design Concepts
24
Genre Table
Field Data Type Description
Genre id Integer Primary Key
Title Short Text Short name for given Genre
Description Long Text Brief description about genre
Buyer Table
Field Data Type Description
Customer id Integer Primary Key
Name Short Text Hold name of customer
Address Long Text Customer’s residential or contact
address
Contact Number Number(10) Customer’s personal contact number
Date of Birth Date The employee’s date of birth
Painting-Sales Table
Field Data Type Description
Customer id Integer Primary Key
Painting id Integer Primary Key
Date Date Date of Sales
Gallery id Integer Foreign Key

Database Design Concepts
25
Price Integer Cost of painting
In this design, the primary key serves as a unique field that can be used to identify a row in the
given table. And, the foreign key maps to another table that carries more information about
records.
Sample queries to extract data from the system
1. Upcoming exhibitions
Select * from exhibition where date>Sys.Date
2. List of artists involved in a particular gallery
Select * from artist where artist_id = (select artist_id from artist-gallery where gallery_id=”1”)
3. Total number of galleries
Select count (gallery_id) from gallery;
4. Managers at each gallery
Select * from employee where role_id = select role_id from role where title=”Manager”
5. Top buyers of the gallery
Select customer_id from Paintings_sales where Price=select max (price) from Paintings_sales
6. List of all buyers and location
Select customer_id, address from customer

Database Design Concepts
26
The above queries gather common information that can be requested by users of the database
management system.
Form Design
Forms serve as a front end interface for users. Users can enter and modify data using forms.
The forms are important for the following reasons:
1) Well-designed forms help in feeding information to the system.
2) The forms are required to modify existing data
3) The forms can be used to scan through existing records.
4) The forms can be used to delete entries.
5) The forms can be used to share information with users.
Exhibition Form
This form is used to gather details about the exhibition. This includes details like the location,
start date, organizer and title of exhibition. The form is built using many constraints that can
ensure integrity and avoid
duplication.

Database Design Concepts
27
The exhibition list form displays all exhibitions hosted by the gallery. It helps the upper
management keep track of all exhibitions the organization handles. The form carries details of
exhibition location, start & end date, title and description. The active exhibition list serves as a
filter from which all current and most happening events can be tracked. Details of previous or
upcoming exhibitions can be extracted using reports. The form is designed with filters that can
be used to fine-tune the data displayed and entered. It is also possible to attach files and
documents to each record. The attachments would be stored in the database.

Database Design Concepts
28
Customer form is responsible for gathering details about buyers. This form allowers users to
add, modify and delete records from the system. There are special administrative privileges on
who gets to add and delete customer details. And, data entered into the system is carefully
validated. There are different types of validations carried out on the fields. For example,
customer name can have only text characters. It doesn’t allow users to enter numbers or
special characters.
Employee details form is similar to the customer details form. It is carefully validated to ensure
data integrity and accuracy. Employee details are currently handled by the upper management.

Database Design Concepts
29
Users without add/modify privileges will be allowed to view reports. The reports produce a list
of employees enrolled in the organization. The report helps with annual audits too. Every
employee is given a unique domain id to access the system. The domain id identifies the
employee’s unique privileges. Additionally, the employee has to key in his/her email id to
access the system. Details entered by the employees (end users) are validated against data
stored in the system
Painting Order Form is used to enter details of each order placed by a customer. The form
allows users to enter details of the painting, important dates (date of order, date of delivery,
date the order was closed), customer and inventory. The form allows users to submit and order.
The sales of paintings happens in several levels. Initially, customers should place an order for
the painting. Once the order gets approved, it would be delivered and the order request would
be closed.

Database Design Concepts
30
Evaluation of Design
The use of an efficient database will make work easier and efficient for the gallery. Employees
will be able to gather, store and process information easily. Information maintenance will no
longer be a daunting task. This is a major reason why the gallery should upgrade to a database
management system. The proposed design is neatly normalized and presented with user
friendly interfaces. Apart from tables, forms and queries, end users can generate reports. These
reports will help in the following situations:
1) Quarterly sales details
2) Quarterly visitor details

Database Design Concepts
31
3) Customer information
4) Annual sales report (this is similar to the quarterly sales details)
5) Artist information (useful when the gallery wants to identify the kind of paintings that
are famous within a specific location)
With the help of a database management system, the gallery will be able to ensure smooth
functioning.
Support Documentation
Tables implemented for the gallery:
1) Employee
2) Artist
3) Role
4) Employee-Role
5) Painting
6) Gallery
7) Customer
8) Painting-Gallery
9) Painting-Customer
10) Order
11) Genre
Forms for the gallery:
1) Customer entry/modify/delete

Database Design Concepts
32
2) Gallery entry/modify/delete
3) Employee entry/modify/delete
4) Painting entry/modify
5) Artist entry/modify
6) Order entry
7) Genre entry/modify/delete
8) Role entry/modify/delete
Reports for the gallery
1) Quarterly /Annual customer details
2) Quarterly /Annual order details
3) Quarterly /Annual painting details
4) Employee details
5) Gallery Branch Sales Details