Question

I need the solution very urgent please try to solve earlier

Draw the ER Diagram of the below case study

Case Study:
Little Corp., a bicycle manufacturer located in Burlington, Ontario was a medium sized business that consisted of just over 200 employees. Of these employees, approximately 50 worked in the office while the remaining 150 employees worked in the manufacturing and warehouse facilities. Little Corp. designed, manufactured, assembled and shipped high-end bicycles (both road bikes as well as mountain bikes) both directly to end consumers as well as to retailers across North America. In the last year, Little Corp. sold over 30,000 bicycles at an average price of $1,000. When Little Corp. was first starting out, employees kept track of most of their work on Excel spreadsheets. Sales and Marketing kept spreadsheets on customers, both individual consumers who purchased bicycles directly from Little Corp. as well as retailers. Customer Service kept spreadsheets on all customers, including end-users who bought directly from Little Corp. as well as those who registered their bikes after purchasing them from retailers. Employees in the Customer Service department were finding it increasingly difficult to maintain these spreadsheet records, which also included all customer inquiries related to problems with their bicycles and warranty part replacement and repair. Sales kept spreadsheets with invoice information and then manually created invoices based on the spreadsheet data. In the manufacturing and assembling facility, employees maintained spreadsheets that included all of the bicycle parts Little Corp. purchased from suppliers as well as the specialized parts that Little Corp. manufactured inhouse. The design team kept spreadsheets that listed all of the parts used in each of the models of bicycles that Little Corp. manufactured. They also kept spreadsheets noting the model number and serial number of each bicycle produced, and sent this once per week to Sales and Marketing as well as Customer Service, but they did not know if Sales and Marketing used this information when bicycles were sold or if the Customer Service department used this information when they tracked customers. Over time, as employees came and went from Little Corp., multiple versions of many of these spreadsheets were evident in all of the departments, with employees often not knowing which were the latest and correct versions of the data. To make matters worse, employees did not keep these spreadsheets on the corporate servers, but rather kept them on their own computers and emailed them to other employees when the files were needed. Some employees backed up their data onto USB flash drives, while others did no backups at all. Approximately 6 months ago, an employee had their laptop stolen, and along with it, the most recent version of the customer database. Fortunately, they were able to recover most of the data, but it was unknown how much data was not recovered (i.e., data that had been entered on the stolen laptop after the last backup). Finally, with multiple versions of the spreadsheet files and multiple employees entering and maintaining the data, many different spellings of supplier and retailer names were evident in the different spreadsheets, making reporting tremendously difficult. Catherine Kuijpers, the founder of Little Corp. realized that something drastic needed to be done to solve their data problems, but was unsure of what to do and where to start. She realized that they needed a better way to keep track of customers, parts, suppliers, retailers, bikes and all of the data associated with these things, but how could she do this, and how could she ensure the successful transfer of the data they currently had in spreadsheet form, as she did not want to lose this and be forced to re-enter all of the information again.

Answer 1

Below is the EER diagram of the given scenario. Based on the description I tried to include all the entities. Attributes are indicative. More attributes can be added to the entities based on the requirement.

The EER diagram consist of 9 entities including one super entity and its 3 sub entity. All entities are connected to each other via 8 relationship. Primary key in each entity is underlined.

Cardinality is shown using crow's foot notation.