Bancos de Dados - Aula 04 – Modelo Entidade - Relacionamento estendido

Understanding Extended Entity-Relationship Model

Introduction to the Extended Entity-Relationship Model

• The session is led by Sara, focusing on the extended entity-relationship model in database systems for computer engineering at Univesp.

• The extended model allows for more precise expression of complex real-world contexts, serving as a logical structure for data storage.

Specialization and Generalization

• Specialization is defined as creating subtypes from a general entity type, where these subtypes are referred to as subclasses.

• Conversely, generalization involves forming a supertype from established subtypes to better describe the modeled situation.

Example of Specialization

• In an organizational context, the entity "Employee" can be specialized into subtypes such as "Secretary," "Technician," and "Engineer."

• Each subtype has unique attributes: Secretary has 'technical level,' Technician has 'degree,' and Engineer has 'type.'

Disjointness Constraint

• The disjointness constraint indicates that an employee can belong exclusively to one subtype (e.g., either Secretary or Engineer), preventing dual classification.

Additional Subtype Example: Manager

• A new subtype called "Manager" is introduced, which relates to another entity called "Project" through a management relationship.

• Managers do not have specific attributes but possess behaviors associated with managing projects; this highlights another motivation for specialization.

Salary vs. Hourly Employees

• Employees can also be classified into two categories: salaried or hourly workers. Salaried employees have a salary attribute while hourly workers have an hourly rate and may associate with a union.

Generalization Process in Entity-Relationship Models

Understanding Generalization and Specialization

• The generalization process is the inverse of specialization, where common attributes are identified across different entities.

• Example: Both "car" and "truck" entities share attributes like license, identification, and price, but have unique attributes as well.

• A super entity called "vehicle" is created to encapsulate shared attributes, enhancing model readability.

Disjunction and Overlap Constraints

• It's crucial to specify disjunction constraints indicating that a vehicle can either be a car or a truck, not both simultaneously.

• Introduction of overlap constraints allows an entity to specialize into two lower-level entities; for instance, parts can be either manufactured or purchased.

Attributes of Manufactured vs. Purchased Parts

• Common attributes for both types include identification and description; however, they also possess specific attributes.

• Manufactured parts have project-related information while purchased parts include supplier details and pricing.

Aggregation in Entity-Relationship Models

Concept of Aggregation

• Aggregation is an abstraction that enables the construction of objects from their components within the entity relationship model.

Example of Aggregation with Interviews

• An example illustrates how interviews connect companies with candidates; multiple candidates can interview at various times.

• By creating an aggregation between company and candidate through interviews, it forms a single entity that can relate to job offers.

Relationship Between Entities

• Job offers are associated with interviews which represent relationships between two distinct entities (company and candidate).

Conclusion on Entity Relationship Model Extensions

Final Thoughts on ER Model Complexity

• The discussion concludes by emphasizing the need for comprehensive understanding of the entity relationship model's complexities.

Suggested Further Study