The address of an employee in an ER diagram representing an employee database is a good example of a Composite attribute.

Here's why:

A. Derived Attribute: These are attributes that do not exist in the physical database, but their values are derived from other attributes present in the database. For example, Age can be derived from the Date of Birth. The address is not a derived attribute because it is not derived from any other attribute.

B. Hierarchical Attribute: This is not a standard term in ER modeling. Hierarchies in ER models are usually represented by relationships, not attributes.

C. Composite Attribute: These are attributes that can be divided into smaller sub-parts, which represent more basic attributes with independent meanings. An address can be broken down into smaller parts like street, city, state, and country. So, the address of an employee is a good example of a composite attribute.

D. Simple Attribute: These are atomic values, which cannot be divided further. The address is not a simple attribute because it can be divided into smaller parts.

Question

The address of an employee in an ER diagram representing an employee database is a good example of a Composite attribute.

Here's why:

A. Derived Attribute: These are attributes that do not exist in the physical database, but their values are derived from other attributes present in the database. For example, Age can be derived from the Date of Birth. The address is not a derived attribute because it is not derived from any other attribute.

B. Hierarchical Attribute: This is not a standard term in ER modeling. Hierarchies in ER models are usually represented by relationships, not attributes.

C. Composite Attribute: These are attributes that can be divided into smaller sub-parts, which represent more basic attributes with independent meanings. An address can be broken down into smaller parts like street, city, state, and country. So, the address of an employee is a good example of a composite attribute.

D. Simple Attribute: These are atomic values, which cannot be divided further. The address is not a simple attribute because it can be divided into smaller parts.

Knowee AI · Accepted Answer

The address of an employee in an ER diagram representing an employee database is a good example of a Composite attribute.

Here's why:

A. Derived Attribute: These are attributes that do not exist in the physical database, but their values are derived from other attributes present in the database. For example, Age can be derived from the Date of Birth. The address is not a derived attribute because it is not derived from any other attribute.

B. Hierarchical Attribute: This is not a standard term in ER modeling. Hierarchies in ER models are usually represented by relationships, not attributes.

C. Composite Attribute: These are attributes that can be divided into smaller sub-parts, which represent more basic attributes with independent meanings. An address can be broken down into smaller parts like street, city, state, and country. So, the address of an employee is a good example of a composite attribute.

D. Simple Attribute: These are atomic values, which cannot be divided further. The address is not a simple attribute because it can be divided into smaller parts.

in ER diagram representing employee database, address of an employee is a good example ofA Derived attributeB Hierarchical attributeC Composite attributeD Simple attribute

Question

Solution

Similar Questions

Upgrade your grade with Knowee