Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

Use below to create a UML diagram. Include all one-to-many relationships in the

ID: 3743172 • Letter: U

Question

Use below to create a UML diagram. Include all one-to-many relationships in the diagram with matching primary and foreign keys in the attribute list of the entities linked by each relationship.

Certification incident responce Employess Vehicle fire sation Certification ID (PK) High-rise toxic-waste level 2-DIL emt Employee iD (FK) emt-2 paramedic Last name firts name Branch ID (PK) name location phone Branch NAme (FK) ID (PK Report ID (PK) date address depart return details Vehicle ID (FK) Branch ID (FK) Employee ID (PK) Firstname last name address DOB address Ssn pay rate certifications ID (FK) milage accidents maintainace Level 2- DL (FK)

Explanation / Answer

If you have any doubts, please give me comment...

Certification(CertificationID) - Employees(EmployeeID) : Many to 1

incidence response(Vehicle ID) - Vehicle(ID) : Many to 1

Incidence response(Branch ID) - fire station(Branch ID) : Many to 1

Employees(certifications ID) - Certifications(Certification ID) : Many to 1

Vehicle(Level 2-DL) - Certification(Level 2-DL) : Many to 1

fire station(Branch NAme) - fireStation(name) - Many to 1

Both Many to 1 and Many to 1 are equal. If we change order of entities, then we will get 1 to Many.

Here Last two are violating regarding to foreign key constraint. according to foreign key rule references attribute must be primary key