An original painting is a painting that is actually painted by the artist. These original paintings are for display alone and are not for sale. An original painting is painted by exactly one artist and an artist might have painted many such original paintings. There can be many copies of an original painting, and there would at the least be one copy of an original painting available for sale. BGAG has a customer base consisting of art enthusiasts and collectors from across the region. A customer can purchase many copies of original paintings from BGAG, however, at the least must have purchased one copy. A copy can be purchased only by one customer. BGAG also wants to keep track of customer interest (admiration) in artists. A customer may be interested in many artists; however, some do not have an interest in any artist. An artist may have many customers interested in them; however, less popular artists may not have any customers interested in them.

You are required to design an E-R diagram that reflects the BGAG operating environment described above. Your E-R design must have the following four entities/tables: ARTIST (contains records of artists) PAINTING (contains records of original paintings) COPY (contains records of copies of original paintings) CUSTOMER (contains records of customers)

Your design must reflect all relationships depicted in the BGAG operating environment. There should be at least three attributes per entity(table) including the primary key (the same applies for intersection/bridge tables if any). You can use surrogate primary keys for all entities, and you can use your imagination to come up with other suitable attributes (for example, the PAINTING entity could have a PK field called PaintingNo and two other attributes called PaintingName and PaintingDate; the COPY entity could have a PK field called CopyNo and two other attributes called CopyType and CopyPrice).

1. The E-R design should depict the minimum and maximum cardinality relationships between the entities.

2. The maximum cardinality relationships should be implemented using appropriately positioned foreign keys.