Create a crows foot erd using only 1:1 and 1:M relationships

When a customer brings a device to PEAR for repair, data must be recorded about the customer, the device, and the repair (also referred to as repair request). Completing each repair request can involve multiple services (e.g. glass replacement, battery replacement, cleaning. Some services require parts. -For the customer, the customer's id, name, address, and a contact phone number must be recorded. -For the device to be repaired, the device serial number, and the type of device are recorded (or verified if the device is already in the system). -Each repair request is given a reference number, which is recorded in the system along with the date of the request, and a description of the problem(s) that the customer wants fixed. -For each Service, there is a service ID number, description, and charge (amount charged for the service) - Part number, Part description and Price are stored for each part. -Each repair request is associated with only one customer. A customer may submit multiple repair requests. -Each repair request is for the repair of one and only one device. It is possible for a device to be brought to the shop for repair many different times, -Completing a repair request may require the performance of many services. Each service can be performed many different times over multiple repairs. - Each service may or may not require parts. A service may require many parts. A part is used in one service. It is also possible that a part is not used in any service. When a customer brings a device to PEAR for repair, data must be recorded about the customer, the device, and the repair (also referred to as repair request). Completing each repair request can involve multiple services (e.g. glass replacement, battery replacement, cleaning. Some services require parts. -For the customer, the customer's id, name, address, and a contact phone number must be recorded. -For the device to be repaired, the device serial number, and the type of device are recorded (or verified if the device is already in the system). -Each repair request is given a reference number, which is recorded in the system along with the date of the request, and a description of the problem(s) that the customer wants fixed. -For each Service, there is a service ID number, description, and charge (amount charged for the service) - Part number, Part description and Price are stored for each part. -Each repair request is associated with only one customer. A customer may submit multiple repair requests. -Each repair request is for the repair of one and only one device. It is possible for a device to be brought to the shop for repair many different times, -Completing a repair request may require the performance of many services. Each service can be performed many different times over multiple repairs. - Each service may or may not require parts. A service may require many parts. A part is used in one service. It is also possible that a part is not used in any service