Read the following description, and draw BY HAND an Extended Entity Relationship Diagram based on what you read. The diagram must use the symbols and methods from the lecture. Turning in a UML diagram from a software package is not valid. If the diagram is not handwritten or is not in the correct form, the quiz will be thrown away and given a grade of zero. Your diagram must include a weak entity, and must include at least one class specialization/generalization.

Mini-world Description:

Jacob Marley was going about his day, wishing everyone he met good wishes and prayers and positive energy. One day Jacob realized that he was always offering energized chakras or sending armies of angels to his acquaintancesbut he never really did stop to meditate or pray for anyone. Mr. Marley decided he needed a database to track all his promises so that he could actually spend time honoring his promises, instead of just talking. Something that could tie into his HeadTome and Quicker social media accounts. For the database, he envisioned the following description of a mini-world called Marleys Petition, that would record the interactions of the users, the acquaintances, and the social media platforms used.

"Marley's Petition"

Every user in the mini-world has a name and a unique user id. Each user can socialize with one or more acquaintances. Each acquaintance has a name and a unique contact id. Many different users may activate many different kinds of mobile phones. Every mobile phone has a unique telephone number and a brand name. Each individual mobile phone tracks one or more communication events. Every communication event has a unique event id. Communication events also have three distinct types. The first type of communication event is HeadTome, which has a set of tracking cookies. The second type is called Quicker, which always includes an image. The third type is face-to-face communication with a fellow human being (even with social distancing) and has a user comment. Each communication event may or may not have a follow-up record. A follow-up record always has a communication event. Follow-up records have four fields: the date of the event, the time of the event, the promise made, and a flag to show the promise was kept.