Final answer:
An EER diagram for the parking management system should include entities like Parking Space, Staff, and Visitor, with sub-entities for Covered and Uncovered Parking. Cardinalities will define the relationships, such as a Staff member being able to book multiple Parking Spaces, and up to twenty Covered Parking Spaces being available for Visitors.
Step-by-step explanation:
To create an Enhanced Entity-Relationship (EER) diagram for the described parking management system, we need to identify the key entities, sub-entities, and their cardinalities.
Entities and Sub-Entities:
Parking Space: This can be a covered or uncovered space.
Staff: Members of staff who can book a covered parking space.
Visitor: Individuals visiting the company who can have a parking space booked for them.
Sub-Entities:
Covered Parking: A subtype of Parking Space with attributes like monthly rate.
Uncovered Parking: A subtype of Parking Space without additional attributes.
Cardinalities:
A member of Staff can book multiple Parking Spaces, but each Parking Space can only be booked by one Staff member at a time.
Up to twenty Covered Parking Spaces can be designated for Visitors; however, a member of Staff must book the space.
The connections between entities and sub-entities would reflect these requirements, and each entity would have its own attributes such as a staff member's ID, visitor's license number, and parking space details.