Provide a separate ER diagram representing each of the following situations. They can be on the same page, but items from one should not be used in the others. For instance, Dog is used in a couple of these. There should be a separate Dog for each of the diagrams. Make sure to clearly label each diagram. (iopts each) Dog is an entity. It has two attributes, "Name and Tag Number. A given dog can be identified by its Tag Number. Person is an entity. It has two attributes, Name and ID. ID can be used to identify a person. There is a relationship, "owns, between Person and Dog. A person can own many dogs, but a dog may only be owned by a single person. Dogs, Cats, and Hamsters are types of Pet. A Pet can exist without being one of those types, but no pet exists that is more than one of these types. All pets have a name. Dogs alone have an attribute for their favorite type of bone. You're working on a simple social network and want to store information on how people are related. This will center around a (recursive) is friends with relationship between two People, and a likes relationship between a Person and some Thing (an entity). The is friends with relationship is between a single person and many people on the other side. The likes relationship is many-to-many. Each Person will have a Name and a UserID. The UserID can uniquely identify a given Person. Note: You may only use one Person entity. A is an entity. It has an attribute, a_id" as its identifier. Bis a weak entity that depends on A. It has b_id" as its discriminator. Many instances of B may belong to the same instance of A. A, B, and C are entities. There is a relationship between all three, called D. For each A and B there is one C. For each B and C there can be many A's. For each A and C, there is one B. Every time the relationship, D, is satisfied, a single value, Note, will be stored