Below is the relational schema for an art exhibition database in its 1NF (primary key: exhibitionCode + locationCode + artObjectID).

ARTEXHIBITION(exhibitionCode, exhibitionName, exhibitionStartDate, exhibitionEndDate, locationCode, locationName, locationAddress, artObjectID, artObjectName, artObjectType, artistID, artistName, artistCountry, boothNo)

Basically, an art exhibition has a name, e.g., Voyage to ancient Egypt, will be exhibited at several locations at different date for certain duration. A same name art exhibition will display the same art objects, but depending on the location, the objects might be located at different booth no. Furthermore, an object was created by an artist. The artists of course can create many art objects. The art objects can also appear in many exhibitions.

1. Create a table with each attribute in the schema as column headers.

2. Fill up the table with at least 5 lines of data. Note that, the data inserted should be able to represent the description given above (try to repeat some components of a line into another so that it will be easier for you to identify the functional dependencies later. For example, do same exhibition but at different locations).

Sample data: E01, Voyage to ancient Egypt, 12/6/19, 11/7/19, L01, Dewan Tun Hussein Onn, PICC Putrajaya, AO01, Potrait of Monalisa, painting, A01, Leonardo de Vinci, Italy, 10.

3. Based on the data, identify all functional dependencies that exists.

4. Normalize the relational schema into its 2NF (based on partial dependencies) and ultimately into 3NF (based on transitive dependency).