Exam 4: Entity Relationship Er Modeling

The entity relationship model (ERM) is dependent on the database type.

The notation of entity-relationship modelling can be used for both conceptual and implementation modelling.

When using the Crow's Foot notation, the associative entity is indicated by relationship lines between the parents and the associative entity.

The entity relationship model uses the associative entity to represent a(n) relationship between two or more entities.

The existence of a(n) entity indicates that its minimum cardinality is zero.

A relationship exists when an association is maintained within a single entity.

An entity in the entity relationship model corresponds to a table in the relational environment.

A relationship is difficult to establish if only one side of the relationship is known.

Composite attributes make it easier to facilitate detailed queries.

Ideally, an entity identifier is composed of attribute(s).

When indicating cardinality, the first value represents the number of associated entities.

In the entity relationship diagram (ERD), cardinality is indicated using the notation, where max is the maximum number of associated entities and min represents the minimum number of associated entities.

The decision to store attributes in database tables depends on the processing requirements and the constraints placed on a particular application.

The concept of relationship strength is based on how the of a related entity is defined.

In organizations that generate large number of transactions, are often a top priority in database design.

A(n) attribute is an attribute that must have a value.

A relationship is an association between .

A derived attribute is indicated in the Chen notation by a that connects the attribute and an entity.

A(n) attribute need not be physically stored within the database.

In the Chen and Crow's Foot notations, an entity is represented with a rectangle containing the entity's name.