Can you help me express the following situation with an ER diagram： On a large online retail platform, different users can log in using their unique identifiers and shop for various items. Each of these items comes with a unique identification code, name, price, and detailed description. Users, apart from their unique identifiers, also provide their name, email, and shipping address. These users can make multiple purchases on different dates, with each transaction assigned an identification code unique to the user, along with recording the date of the transaction and the total cost. Each transaction can consist of one or more items, and the same item could be part of various transactions made by the same or different users.

This question contains a brief UoD that provides contextual information regarding a system or organisation. You will need to create an Entity Relational (ER) diagram, or Extended Entity Relational (EER) diagram based on the UoD. If the UoD is unclear regarding specific aspects of the brief you may note assumptions on your ER diagram. However, please beware that your assumptions must not conflict with or violate any aspects of the UoD. On a large online retail platform, different users can log in using their unique identifiers and shop for various items. Each of these items comes with a unique identification code, name, price, and detailed description. Users, apart from their unique identifiers, also provide their name, email, and shipping address. These users can make multiple purchases on different dates, with each transaction assigned an identification code unique to the user, along with recording the date of the transaction and the total cost. Each transaction can consist of one or more items, and the same item could be part of various transactions made by the same or different users.

Assuming Mr. Moi only wants a database system that would keep records of medicine{names ofmedicine, amount in grams in stock}, purchase{medicine bought, amount in grams bought, whoattended to customer, when it was sold, contact and name of customer that bought the medicine}a. Draw a normalized ER diagram with only the most important data from question 1 bearing in _mind the information that Mr. Moi wants.

The constraints that cannot be modeled on the ER diagram should be handled by:Choose one answer. a. Listing them on the separate document to be coded b. Always let the network architect handle them c. Explain to the user so they can enforce them d. All constraints must be modeled and shown on the ER diagram

Question 1: Draw the ER model for the basic information given below. Use the Chen Notation for cardinality and participation constraint. (10 points) All Pakistan Software association holds workshops in collaboration with different software houses. They wish to record detailed information regarding the following aspects. • Intellect delivering workshop – They wish to record complete details about the person who delivers lectures in workshop. Record ID, Name, Email, Address (street, city, state, zip code), Contact number,current job, and qualification details. • Workshop – Record workshop ID, Year, Theme and Venue. • Venue – The venue can be some university, hotel or conference room in a software house. We need to record LocationID, Name, Address (street, city, state,zip code) and Contact number. • Participants – For a participant, record ParticipantID, Name, Designation, Affiliating Institute and Charges. The participating entities have come up with the following rules: • A total of 200 participants are allowed in each workshop each year on a first come, first served basis. • Charges vary with the designation of the participant. • Accommodation is not provided by any host and other expenses are also not entertained.

DHL System Entity Relationship Diagram (ERD):Entities:ShippedItem:Attributes:itemNumber (unique identifier)weightdimensionsinsuranceAmountdestinationfinalDeliveryDateCardinality:1 ShippedItem is processed at 1 RetailCenter1 ShippedItem participates in many TransportationEventsRetailCenter:Attributes:centerID (unique identifier)type (e.g., airport, service center)addressCardinality:many ShippedItems are processed at 1 RetailCenterTransportationEvent:Attributes:scheduleNumber (unique identifier)type (e.g., flight, truck)deliveryRouteCardinality:many ShippedItems participate in 1 TransportationEventRelationships:Processes:Connects ShippedItem and RetailCenterCardinality: One-to-one (1:1)Indicates that a single ShippedItem is processed at one and only one RetailCenter.Participates in:Connects ShippedItem and TransportationEventCardinality: Many-to-many (M:N)Indicates that a single ShippedItem can participate in multiple TransportationEvents, and a single TransportationEvent can involve multiple ShippedItems.Identifiers:Each entity has a unique identifier:ShippedItem: itemNumberRetailCenter: centerIDTransportationEvent: scheduleNumberConstraints:Primary Key: Each entity's unique identifier is its primary key.Foreign Key:Processes relationship: RetailCenter.centerID references ShippedItem.retailCenterID (foreign key)Participates in relationship:ShippedItem.itemNumber references TransportationEvent.shippedItemIDs (foreign key, assuming an identifier list for participating items)TransportationEvent.scheduleNumber references ShippedItem.transportationEventIDs (foreign key, assuming an identifier list for participating items)This ERD captures the essential information about the DHL system, including shipped items, retail centers, transportation events, and their relationships. The cardinality constraints and identifiers ensure data integrity and efficient tracking of shipped items within the system.