Develop an Er/EER model for the database based on the scenario below. If you discover while drawing the diagram that the scenario is incomplete, make up reasonable explainations to complete the story. Supply your explanations along with the diagram.

The ER/EERD should be fully specified with :

• Entities and supertype/subtype entities: the proper number of entities and their name
• All needed attributes of each entity
• Primary key and foreign key
• Relationship:
  • Max and min connectiviities: if needed you can put your justification on your answer
  • Make sure that each M:N relationship should be decomposed into two 1:M relationships
  • Description (text) of realationship between entities (takes, advises, etc)
  • The correct number of relationships between entities
• Disjoint/overlapping constraints
• Subtype discriminators
• Partial/total completeness

In drawing the model, use crows foots model (notation

In drawing the diagram, you can use any diagraming software such as DRAW.io, Microsoft visio, lucis chart or Microsoft word

ABC, INC a factory manufacturing automobile parts, wants to implement a database to manage its data. Your task is to design the database to capture the data specifications through the ER/ERR modeling. The factory has several departments. A department may have many employees, but at least three. Every employee works for one and only one department. Every department has a manager-only one manager per department. Clearly, a manager is an employee of the company; but, all employees are not manager. A department may have many machines, and every machine is assigned to a specific department. Products are producted on machines. Every product goes through one or more machines for appropriate production operations. Likewise, everal products may to through a particular machine for some standard proess. Designers design the products. Some well-qualifies designeers may deisgn more than one product. All designers are employees of the factory. Operatiors, who are also employees of the facory, operate these machines. Due to multiple shifts, several operators operate the same machine. All operators are routinely assigned to work on only one machine and no operator is kept idle. A machine is never kept idel either. An employee cant be both a designer and an operator.

The database should capture an employees name, gender, address, and salary. Social security number uniquely identifies an employee. Likewise, department number, department name, type, and location, must be captured. Every machine will have a unique machine number. It will also consist of other details like the name of the machine, type, and vendors name. a product is identified by its product ID, product name, and description must also be recored. When a product goes through machining, the starting time, completion time, and hours of machining for each product on every machine must be capture. The information about a designer includes his or her qualification, specialization field, and experience in years. Operators, who are responsible for operating machines, belong to a labor union and have certain kill sets associated with them.