- We are designing a new cloud-based software called "Warranty Central" that will be used to sell and track warranties for consumer goods that are sold through other marketplaces like Kijiji or eBay. - The system will be used by users in the US and Canada. - We have collected a series of requirements that describe the information that must be held within the system and need to develop both conceptual and logical data models that supports these requirements. Requirements Checklist (Entities and Relations) User Information Users of the system can be considered sellers (when they are listed as the seller of an item), a buyer (when they purchase an item from another user). A user does not need to have participated in a transaction in order to exist. Sale (sale of items) Each sale can consist of one or more different items that were included in the sale (i.e., a user can buy/sell more than one item as part of a single sale). Each item can optionally include a warranty. Warranty A warranty must relate to a specific item that was part of a sale. Each warranty must be issued by an Insurer. Insurer An insurer represents an insurance company that participates in the system and issues warranties for items. A single warranty can only be issued by one insurer but an insurer, of course, will issue any number of warranties over time. Claim A claim can be filed by a user of the system. The claim must reference the original sale of the item as well as the specific warranty that was issued. Claim Resolution All claims must have, eventually, one ore more resolutions A resolution to a claim describes the details of what was done to resolve the claim. Some claims may be denied, while other claims are to be resolved using one of or a combination of: a repair, a replacement item, or a refund (full or partial) of the purchase price of the item, 1. [ 10 marks ] Conceptual Model (Chen Notation) Create a Conceptual Model that meets the requirements above using Chen Notation. a. You will model only entities and relations using Chen notation (no attributes). b. You must indicate correct cardinality and any mandatory relationships. c. You do not need to model weak entities or weak relations. - We are designing a new cloud-based software called "Warranty Central" that will be used to sell and track warranties for consumer goods that are sold through other marketplaces like Kijiji or eBay. - The system will be used by users in the US and Canada. - We have collected a series of requirements that describe the information that must be held within the system and need to develop both conceptual and logical data models that supports these requirements. Requirements Checklist (Entities and Relations) User Information Users of the system can be considered sellers (when they are listed as the seller of an item), a buyer (when they purchase an item from another user). A user does not need to have participated in a transaction in order to exist. Sale (sale of items) Each sale can consist of one or more different items that were included in the sale (i.e., a user can buy/sell more than one item as part of a single sale). Each item can optionally include a warranty. Warranty A warranty must relate to a specific item that was part of a sale. Each warranty must be issued by an Insurer. Insurer An insurer represents an insurance company that participates in the system and issues warranties for items. A single warranty can only be issued by one insurer but an insurer, of course, will issue any number of warranties over time. Claim A claim can be filed by a user of the system. The claim must reference the original sale of the item as well as the specific warranty that was issued. Claim Resolution All claims must have, eventually, one ore more resolutions A resolution to a claim describes the details of what was done to resolve the claim. Some claims may be denied, while other claims are to be resolved using one of or a combination of: a repair, a replacement item, or a refund (full or partial) of the purchase price of the item, 1. [ 10 marks ] Conceptual Model (Chen Notation) Create a Conceptual Model that meets the requirements above using Chen Notation. a. You will model only entities and relations using Chen notation (no attributes). b. You must indicate correct cardinality and any mandatory relationships. c. You do not need to model weak entities or weak relations