3.

Business goal a d functionality

This part of documentation explains the rules, calculations, validations and transformations our
database performs on our data. To support this functionality let's see some points.

1. Tables: Tables are used to organize data that is too detailed or complicated to be described
adequately in the text, allowing the reader to quickly see the result. So according to our data
the table we proposed will be asfollows.

- Art: It involves art piece information which includes artist ID, art gallery ID, price and status.

- Artist: It comprises artist details such as name, ID, contact details and commission rate.

- Gallery: It holds data concerning specific art galleries like Gallery code location and total
revenue.

- Manager: It contains information about each art gallery’s manager including their name and
contact details.

- Customer: This table carries customer’s personal data such as their names,Id and contacts.

- Total income; It includes Rno,sum of price of sold arts, the award for the artist from the
income and the total income that the ArtGallery can afford .

-Receptor- this table includes the name ,Id, task and general information of the receptors who
greet customers.

2. Relationships: To support the business functionality our documentation includes the

relationship set which helps in storing and sorting data efficiently and easily. Data analysts and
managers can then specify data with queries and filters to make the process of finding
information much easier.In our project the relationship set established is asfollows.

1.One-to-One relationship between Art and Artist (each art has one artist only).

2.One-to-One relationship between Artist and ArtGallery (one artist can be in just one art
gallery).

3.One-to-Many relationship between Customer and Art (there are customers who buy more than
one artwork).
4.One-to-One relationship between ArtGallery and Manager (each art gallery has only one
manager).

3. Calculations: For the ArtGallery database management system we used simple basic
calculation types to calculate the total income for the gallery and income for the artist who
works in the gallery .
At every sale, automatically calculate 25% to go to the artist which is subtracted from total
gallery revenue for this medium. We also integrate Triggers to automatically calculate these
informations when some updates done on the existing data and when new artworks sold.

4. Permissions: To limit user access to databases and limit the kind of operations
users can perform on those databases we included privileges in our project.
- This will allow the manager to execute changes in columns of each table and delete
tables when necessary.The manager should have access to modify entries about art
gallery, available art types, sold arts, and own personal .More also, given room to
artists who may want to change their details regarding artwork or works done by them
as well as access information on sales done for the different categories of paintings,
drawings etc. Let's explain the proposed privilege briefly as follows.

4.Design Decision and trade-offs

4.1 Design Decision

1. Database Organization:

- Tables: Maintain separate tables for Art, Artist, ArtGallery, Manager and Customer to store
relevant information.

- Relationships: Establish relationships between Art and Artist, Artist and

ArtGallery,ArtGallery and Manager. Establish a one-to-many relationship between Customer
and Art.

- Primary Keys: Have primary keys for each table to ensure integrity of data plus uniqueness

- Foreign Keys: Use foreign keys to create links between tables enforcing referential integrity.

2. Calculations:

- Implement a trigger or stored procedure that will automatically calculate the 25% paid to the
artist for a sale as well as updating the total revenue of an art gallery.

- Create a function that calculates the total revenue from sales in the art gallery while deducting
the amount paid to artists.
3. Access Control:

- Give full access to update columns of each table and delete entire table when necessary by
manager.Use appropriate access control mechanisms to restrict user access rights.

- Specify roles and permissions for manager, customer and artist so that their access is limited
only to specific tables or columns within those tables.

4.2 Trade-offs:

1. Performance:

- Automatic calculations implemented with triggers and stored procedures are used to enhance
the performance of the system.
2. Data Integrity:Using database logic to enforce complex relationships and
calculations may make the system more complicated and increase the chances of
mistake. Therefore, data integrity is maintained thorough testing and validation.
3. Security: Since we limit user access to databases and limit the kind of operations
users can perform on those databases using privileges by allowing the manager to
execute changes in columns of each table and delete tables when necessary.The
manager should have access to modify entries about art gallery, available art types,
sold arts, and own personal .More also, given room to artists who may want to change
their details regarding artwork or works done by them as well as access information
on sales done for the different categories of paintings.This will help the security of our
data.Giving full access to updating and deleting tables for a manager can be a security
threat.

4. Scalability:

- As more artists, customers and artworks are added to the system, scalability may
demand optimization of database structure and calculations. So to solve this problem
we considered some points as follows
1.To make the system adaptable to new technologies, making it easier to incorporate
emerging trends like cloud computing, microservices, and IoT without disrupting the
entire system.
2.To enhance the performance of the system using automatic operations is what we
suggested and included for this system.