Database & Design, Entity Relationahip model, ERD, SQL

The Full description is attached. 1a) Entity-relationship model mapped to a relational database Produce an Entity-Relationship Model using UML notation for the above case. Convert to a relational model by specifying the primary and foreign keys, mapping any one-to-one relationships into relations, and decomposing any many-to-many relationships. This is the Relation diagram and the diagram which you should submit. Note that there is no need to include the type of each attribute. State any assumptions that you may need to make particularly about optional and mandatory relationships. Note that assumptions are about how you have interpreted the scenario, not about the E-R modelling process. The ERD is not trivial – it involves at least 10 entities. I suggest you start by each member of your group concentrating on different parts of the ERD and then coming together to discuss. 1b) Validate the model Checking for connection traps Examine your model and identify one potential trap (fan trap or chasm trap) - if present. Consider whether this may cause a problem to your model and re-draw if necessary, arguing your case either way. Supporting the functional requirements Validate the model to check it can support the following functional requirement i.e. specify the access path by listing the appropriate relations (taking into account the correct relationships) from your diagram: ‘List all members by name who have ever belonged to the Science group, who have a talent for music and have attended an event with Goldie as the outside speaker.’ Will pay $50