Thinking about the worksheets and different terminologies. One thing I did note in the lecture was that it was emphasised that relationships have attributes as well, but my take on this is "Multiplicity". Would that be the correct interpretation for that concept?

If I have understood your question correctly, then I am afraid your interpretation is not correct. Multiplicity means how many times an entity can participate in a relationship. In the class we did an example on newspapers and propertyForRent as two example entities. The cost of an ad and the date of an ad can be attributes of the relationship between the two entities, while multiplicities tell you how many times the two entities can participate in the relationship (min and max constraints).

I understand that relationship attributes are a separate concept to Multiplicity, but I did find a useful video that explains this in detail: However, this takes the worksheet exercise to a new level because those attributes that we are asked to think about tend to make the ER model more complex because they are absorbed into the framework of existing entities. The gentleman that explained the concept in the video then added that if the relationship attribute cannot be added to the entity attributes themselves, then a new table is formed when there is a many to many relationship. Multiplicity, a separate concept, is in fact the guiding concept in this approach. Not so much confusing, but rather complex. If I am to summarise what he said, take the relationship attribute and add it to the entity attribute in a "one to many", add it to any entity in a "one to one" but build a new table in a "many to many", which itself would require another relationship or so. A domino effect. How de we keep it less complex or maybe simple?

Hi James, Sorry that we missed this. In the first part of the project, we are focusing on the conceptual design. Now that you have started logical modeling, we are going to create a new table where we see a *:* relationship. While dealing with concepts we are decided not to worry about the tables. In the class we did an example where I said if there are multiple newspapers and multiple properties we could not put attributes that are connection the two entities (for example date of an ad) under either of the two entities i.e., newspapers or properties. In that case we make them attributes of the relationship. You can drop by in my office on Friday morning it this is still not clear. Cheers