Create a Entity Relationship Diagram.

Company ZZZ organizes workshops where its trainers give tutorials on different programming languages, systems, platforms, etc. ZZZ wants to maintain a database about its employees, their jobs, and workshops organized by the company. In addition, for every workshop ZZZ creates food orders that will be submitted to caterers so that the workshop participants can have breakfast, coffee breaks, lunch break, etc.

Each ZZZ employee has an SSN, first name, last name, email address. The company has many job types (e.g., trainer, lecturer, senior lecturer, intern, etc.) and every job type has an ID, title, salary level, and the description of the duties. Every company employee has a specific job type assigned to her; many employees can have the same job type. Every job type has at least one employee that has this job type.

A workshop is identified by the workshop ID, description, location, start and end dates, number of participants. A workshop is organized by one or more ZZZ employees and an employee can be assigned to zero, one, or many workshops.

For every workshop, depending on the workshop length, ZZZ submits food orders, where every order is identified by the caterer name, food type (e.g., breakfast, coffee break, lunch, etc.), money amount paid. For some workshops (for example, short 2-hour tutorials), ZZZ does not submit any food orders, for other workshop (for example, 2-day workshops), ZZZ submits multiple food orders. As ZZZ employees are self-proclaimed foodies, ZZZ never submits multiple orders to the same caterer during one workshop. If a workshop is cancelled, ZZZ cancels the corresponding food orders and deletes the information about these orders from the database.