Develop an entity-relationship diagram (ERD) using Chen notation for the case study described below.You are to clearly:-- identify entity sets, relationship sets, all attributes, and primary keys; ·-- specify connectivities for relationship sets;-- specify overlapping/disjoint constraints, if there is a specialization/generalization hierarchy. To simplify ERD, assume that phone numbers, addresses, and names are atomic attributes (no need to replace them by a set of atomic fields). Case Study "Baker's Choice" is a company providing bakery equipment and services associated with the equipment. Its customers may buy or lease the equipment for their needs and request maintenance or repair services from time to time. The company needs to design a database to improve its operations. A customer buys or leases a piece of equipment which can be a single machine or a series of machines combined together into one unit called cell. Each piece of equipment is described by unique ID, title, and category. Individual machine is presented in the database by its hourly capacity and price. A cell is described by a product the cell can make and its discount. It is necessary to recode all individual machines included into a given cell. A machine can be included into one cell only. Customers are assigned customer ID, Company name, address, and contact phone number. A customer may lease more than one piece of equipment. When a customer leases a piece of equipment a lease contract is signed. It includes unique contract number, first and last dates of the lease. It is important to know who leases which piece of equipment. Each piece of equipment can be leased by more than one customer over its lifetime. The same customer may re-lease the same piece. In this case a new lease contract is issued. When a customer buys a piece of equipment, an invoice is issued. The invoice is described by its unique number and the date of the purchase. It is necessary to know the buyer of the equipment. The invoice can include one or more pieces of equipment. For each piece, the sale price is recorded. After the customer pays the invoice, there is no return. However, on customers' request, "Baker's Choice" provides technical support which includes one or more maintenance or repair services. Customers may request services on both bought and leased equipment. Company's employees implement these services. Each employee is described by employee ID, name, phone, and occupation. For each service provided by the company, service ID, its title, and the cost of labor must be recorded in the database. A service may cause one or more other services, e.g., maintenance may require a part replacement. Each service can be caused by many other services. This information is to be included in the database. Each service may require materials which can be parts, tools, or chemicals. Each material is described by a unique id, title, and its price. Machines may fail from time to time. If a problem is encountered, it must be recorded in the database. A problem is described by its sequential number for each machine, description, and date. If a machine is no longer in use, its record is removed from the database along with the records about associated problems. Each problem is associated with a service. This association must be recorded. A request for a service on a particular piece of equipment results in an appointment scheduled on a certain date. An appointment is described by ID, date, and time slot. An employee is assigned to each appointment. Each appointment can be associated with more than one service. This assignment must be recorded in the database. Reference:Rodina, D. (2021). Chen ER Diagram - Entity-Relationship Diagram in Chen Notation - Software Ideas Modeler. Retrieved 23 January 2021, from https://www.softwareideas.net/chen-er-diagram-erd Please anyone can help me out with this question to answer with step by step explanation......

Question

Develop an entity-relationship diagram (ERD) using Chen notation for the case study described below.You are to clearly:-- identify entity sets, relationship sets, all attributes, and primary keys; ·-- specify connectivities for relationship sets;-- specify overlapping/disjoint constraints, if there is a specialization/generalization hierarchy. To simplify ERD, assume that phone numbers, addresses, and names are atomic attributes (no need to replace them by a set of atomic fields). Case Study &#34;Baker's Choice&#34; is a company providing bakery equipment and services associated with the equipment. Its customers may buy or lease the equipment for their needs and request maintenance or repair services from time to time. The company needs to design a database to improve its operations. A customer buys or leases a piece of equipment which can be a single machine or a series of machines combined together into one unit called cell. Each piece of equipment is described by unique ID, title, and category. Individual machine is presented in the database by its hourly capacity and price. A cell is described by a product the cell can make and its discount. It is necessary to recode all individual machines included into a given cell. A machine can be included into one cell only. Customers are assigned customer ID, Company name, address, and contact phone number. A customer may lease more than one piece of equipment. When a customer leases a piece of equipment a lease contract is signed. It includes unique contract number, first and last dates of the lease. It is important to know who leases which piece of equipment. Each piece of equipment can be leased by more than one customer over its lifetime. The same customer may re-lease the same piece. In this case a new lease contract is issued. When a customer buys a piece of equipment, an invoice is issued. The invoice is described by its unique number and the date of the purchase. It is necessary to know the buyer of the equipment. The invoice can include one or more pieces of equipment. For each piece, the sale price is recorded. After the customer pays the invoice, there is no return. However, on customers' request, &#34;Baker's Choice&#34; provides technical support which includes one or more maintenance or repair services. Customers may request services on both bought and leased equipment. Company's employees implement these services. Each employee is described by employee ID, name, phone, and occupation. For each service provided by the company, service ID, its title, and the cost of labor must be recorded in the database. A service may cause one or more other services, e.g., maintenance may require a part replacement. Each service can be caused by many other services. This information is to be included in the database. Each service may require materials which can be parts, tools, or chemicals. Each material is described by a unique id, title, and its price. Machines may fail from time to time. If a problem is encountered, it must be recorded in the database. A problem is described by its sequential number for each machine, description, and date. If a machine is no longer in use, its record is removed from the database along with the records about associated problems. Each problem is associated with a service. This association must be recorded. A request for a service on a particular piece of equipment results in an appointment scheduled on a certain date. An appointment is described by ID, date, and time slot. An employee is assigned to each appointment. Each appointment can be associated with more than one service. This assignment must be recorded in the database.  Reference:Rodina, D. (2021). Chen ER Diagram - Entity-Relationship Diagram in Chen Notation - Software Ideas Modeler. Retrieved 23 January 2021, from https://www.softwareideas.net/chen-er-diagram-erd Please anyone can help me out with this question to answer with step by step explanation......

Accepted Answer

About the case   study:

You are to clearly: -- identify entity sets, relationship sets, all attributes, and primary keys; · -- specify connectivities for relationship sets; -- specify overlapping/disjoint constraints, if there is a specialization/generalization hierarchy.