How Should Manage Be Represented in an ER Diagram for a Video Rental Company?

Click For Summary
SUMMARY

The discussion centers on the representation of management in an Entity-Relationship (ER) Diagram for a video rental company. Participants agree that "Manage" should not be treated as a separate entity, as it does not fit the noun structure of other entities like Staff, Branch, and Customer. Instead, the relationship between Staff and Branch should be depicted using a direct connection that indicates management responsibilities without creating an additional entity. This approach simplifies the diagram while accurately reflecting the business requirements.

PREREQUISITES
  • Understanding of Entity-Relationship (ER) Diagrams
  • Familiarity with database design concepts
  • Knowledge of relationships in data modeling (one-to-many, many-to-one)
  • Experience with business requirements analysis
NEXT STEPS
  • Research how to create effective ER Diagrams using tools like Lucidchart or Draw.io
  • Study the principles of normalization in database design
  • Learn about different types of relationships in ER modeling, such as recursive relationships
  • Explore case studies of database designs for retail businesses
USEFUL FOR

This discussion is beneficial for database designers, students learning about data modeling, and professionals involved in designing systems for retail or rental businesses.

bloynoys
Messages
25
Reaction score
0
I am doing a ER Diagram for a class and having a lot of trouble with a specific piece of the sentence. Anyway, here is the business requirements we are diagramming:

The video rental company has several branches throughout the USA. The data held on each branch is the branch address made up of street, city, state, and zip code, and the many telephone numbers each branch has. Each branch is given a branch number, which is unique throughout the company. Each branch is allocated staff. Only one staff may manage many other staff members and may manage only one local branch. The data held on a member of staff is his or her name, position, and salary. A staff may work at more than one location. Each member of staff is given a staff number, which is unique throughout the company. Each branch has a stock of videos. A branch may not have all video titles. The data held on a video is the, video number, title, category, daily rental, cost, status, and the names of the main actors. Each video may have many actors. Before renting a video from the company, a customer must first register as a member of a local branch. The data held on a customer is the first and last name, address, and the date that the customer registered at a branch. Each member is given a customer number, which is unique throughout all branches of the company. Once registered, a member is free to rent many videos. The data held on each video rental is the rental number, the full name and number of the member, the video number, title, and daily rental, and the dates the video is rented out and date returned. The rental number is unique throughout the company.

The piece highlighted is the piece I am having trouble with. My diagram is below. I believe that manage should be a separate entity that needs to connect to both staff (that they manage) and branch (which they manage). Is this correct? Or is there a different way to diagram this that I am not thinking of. Image below.
ClassTest2-ERDAssignment1_zpsc9f0b594.png
 
Last edited:
Computer science news on Phys.org
bloynoys said:
I am doing a ER Diagram for a class and having a lot of trouble with a specific piece of the sentence. Anyway, here is the business requirements we are diagramming:

The video rental company has several branches throughout the USA. The data held on each branch is the branch address made up of street, city, state, and zip code, and the many telephone numbers each branch has. Each branch is given a branch number, which is unique throughout the company. Each branch is allocated staff. Only one staff may manage many other staff members and may manage only one local branch. The data held on a member of staff is his or her name, position, and salary. A staff may work at more than one location. Each member of staff is given a staff number, which is unique throughout the company. Each branch has a stock of videos. A branch may not have all video titles. The data held on a video is the, video number, title, category, daily rental, cost, status, and the names of the main actors. Each video may have many actors. Before renting a video from the company, a customer must first register as a member of a local branch. The data held on a customer is the first and last name, address, and the date that the customer registered at a branch. Each member is given a customer number, which is unique throughout all branches of the company. Once registered, a member is free to rent many videos. The data held on each video rental is the rental number, the full name and number of the member, the video number, title, and daily rental, and the dates the video is rented out and date returned. The rental number is unique throughout the company.

The piece highlighted is the piece I am having trouble with. My diagram is below. I believe that manage should be a separate entity that needs to connect to both staff (that they manage) and branch (which they manage). Is this correct? Or is there a different way to diagram this that I am not thinking of. Image below.
ClassTest2-ERDAssignment1_zpsc9f0b594.png
I don't believe that "Manage" should be an entity. All of your other entities are nouns (staff, branch, customers, orders, videos), and these entities interact with other entities via verbs (employs, contains, registers, etc.). You already show a "manage" connection between Staff and Branch, so why is it necessary to also have a Manage entity?
 

Similar threads

  • · Replies 42 ·
2
Replies
42
Views
9K
  • · Replies 1 ·
Replies
1
Views
3K
  • · Replies 7 ·
Replies
7
Views
10K
  • · Replies 21 ·
Replies
21
Views
6K
  • · Replies 99 ·
4
Replies
99
Views
36K
  • · Replies 4 ·
Replies
4
Views
7K
  • · Replies 3 ·
Replies
3
Views
4K
  • · Replies 8 ·
Replies
8
Views
5K
  • · Replies 65 ·
3
Replies
65
Views
11K
  • Sticky
  • · Replies 2 ·
Replies
2
Views
503K