ER Modeling

You will need it to draw Entity-Relationship Diagram (ERD).

(2) Consider a fictional We Meet (WM) social media for meetings as described below. WM has been drastically (and somewhat unrealistically) simplified, with very limited functions. Construct a reasonable ERD to capture the data requirements of the project. List the entities, relationships with multiplicities, and attributes. Specify the primary key of an entity whenever possible. Note that you should use the Crow's Foot notation as supported by ER Assistant v2.1. ER Assistant supports attributes for relationships and your ERD may have relationship attributes

We Meet (WM)

WM is a web-based social media supporting members to form groups to meet. You may get some ideas by taking a look at meetup, such as: (Of course, meetup is a $400+ million company and this assignment is a drastically simplified one only worthy of 3.75% of your grade.) WM in this project supports very limited functionality of a very small portion of the application.

Any people can join to become a member of WM. They will need to provide a first name, a last name, an email address, and an optional phone. WM stores the time a person joins to become a member. A WM member has a unique id. A member must have an account to access WM member pages. An account contains a unique id serving as the key, a unique username, and a password for logging on. There are many types of accounts (such as for administrators, managers, staff, mavens, etc.) These other types of accounts need not be modeled in this assignment. WM stores previous old passwords for all accounts and the times these passwords were created. This is used to ensure that account holders do not reuse old passwords.

For example, the account with id 109828198 and username benhui_2020 may have the following history of passwords (encrypted when stored):

A WM member may follow any number of other WM members. This follower and following information need to be stored.

WM Members can form groups of interests for meetings. A group has a unique id, a name, a purpose, and a creation time. It may have a description. For example, here is a group:

Id: 110982

Name: ABC Explorers

Purpose: ABC current students and alumni to meet and explore the XYZ area together.

Creation Time: 01/16/2019 09:34.11pm

Description: Have fun together as ABC students and alumni.

A group must have one or more administrators. A WM member can serve as an administrator of multiple groups. When a WM member serves as an administrator of a group, the start date time, a description and an indicator when the WM member is also a creator of the group should be stored.

Any WM member can join any number of groups. When a member joins a group, the join time, an optional comment and an optional note of the role are stored.

A group may belong to a number of group categories. For example, the group 110982 ABC Explorers may belong to the categories of university, City,

regional and learning.

A group administrator of the group may post meet events on WM. For example, the group 110982 may have three administrators and 634 group members. One of the administrators may be benhui_2020. He can post an event:

Meet Time: ABC Spring Break Celebration

Date: 3/18/2021

Start Time: 4:00pm CST

End Time: 5:30pm CST

Location: Garden Room, first floor, Bayou Building, 111 Boulevard, XYZ, GH 7777.

Description: A social meet up for ABC students. Coffee will be served. Bring your own cookies to share.

Once a meet event is posted in a group, any group member can post comments on the event, such as asking questions. A comment may be a response or follow-up of another comment. The comment's body and time should be stored.