Create an ER (Entity Relationship) diagram for a small social network application, where persons…
Create an ER (Entity Relationship) diagram for a small social network application, where persons can follow each other, send messages to other persons (private messages) or post messages (public messages). Each person has a name and a unique number that can be used to identify the person. A person can follow (and be followed by) multiple persons. It can be possible that ‘Jan’ follows ‘John’, but that John’ does not follow Jan! The date when a person started to follow the other person should be stored. A person can send private messages to many persons and receive messages from many persons. Notice that a person should be able to send multiple messages to the same person. A person can post multiple public messages, but a public message must be posted by exactly one person. The text of the message, the date when a message was sent or posted, and a unique identifier for the message must be stored. Draw an ER diagram with only entity sets, relationship sets, attributes, and participation and cardinality constraints. Make sure your design represents the object system accurately and is optimized to minimize redundancies and incomplete information. If you make special assumptions, make them explicit (using a textual description).
Any citation style (APA, MLA, Chicago/Turabian, Harvard)
Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.
You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.