Which of the following is true of the components of an entity-relationship data model?

Section 1

Inhaltsverzeichnis Show

Entity Relationship Diagrams in Enterprise Architect
ERD and ERD Transformations
Entity Relationship Diagram Toolbox Page
A typical Entity Relationship diagram
Tagged Values
Learn more
Which of the following statements is true of relational database management systems Rdbms?
Which of the following is the term for data about the structure of a database?
Which of the following is true when implementing a one
Which of the following gives an accurate description of a data model?

1. Entity Relationship model is independent of the hardware or software used for implementation. True or False? Mark for Review

(1) Points

True (*)

False

2. The purpose of an ERD is to document the proposed system and facilitate discussion and understanding of the requirements captured by the developer. True or False? Mark for Review

(1) Points

True (*)

False

3. Which of the following statements are true about ERD's? (Choose Two) Mark for Review

(1) Points

(Choose all correct answers)

A piece of information can be shown multiple times on an ERD.

A piece of information should only be found one place on an ERD. (*)

You should not model derivable data. (*)

All data must be represented on the ERD, including derived summaries and the result of calculations.

4. A well structured ERD will show only some parts of the finished data model. You should never try to model the entire system in one diagram, no matter how small the diagram might be. True or False? Mark for Review

(1) Points

True

False (*)

According to the online Wikipedia:

An entity-relationship model (ERM) is an abstract and conceptual representation of data. Entity-relationship modeling is a database modeling method, used to produce a type of conceptual schema or semantic data model of a system, often a relational database, and its requirements in a top-down fashion. Diagrams created by this process are called Entity-Relationship Diagrams, ER Diagrams, or ERDs.

Entity Relationship Diagrams in Enterprise Architect

Entity Relationship diagrams in Enterprise Architect are based on Chen's ERD building blocks: entities (tables) are represented as rectangles, attributes (columns) are represented as ellipses (joined to their entity) and relationships between the entities are represented as diamond-shape connectors.

ERD technology in Enterprise Architect assists you in every stage from building conceptual data models to generating Data Definition Language (DDL) for the target DBMS.

ERD and ERD Transformations

Enterprise Architect enables you to develop Entity Relationship diagrams quickly and simply, through use of an MDG Technology integrated with the Enterprise Architect installer.

The Entity Relationship diagram facilities are provided in the form of:

An Entity Relationship diagram type, accessed through the 'New Diagram' dialog
An Entity Relationship Diagram page in the Diagram Toolbox
Entity Relationship element and relationship entries in the 'Toolbox Shortcut' menu and Quick Linker

Enterprise Architect also provides transformation templates to transform Entity Relationship diagrams into Data Modeling diagrams, and vice versa.

Entity Relationship Diagram Toolbox Page

You can access the 'Entity Relationship Diagram' page of the Diagram Toolbox by specifying 'Entity Relationship Diagrams' in the Toolbox 'Find Toolbox Item' dialog

Entity is an object or concept that is uniquely identifiable; the property of 'Multiplicity' in the SourceRole and TargetRole definitions for the Relationship connector can be used to define the cardinality of an Entity that participates in this relationship
Attribute is a property of an entity or a relationship type
N-ary Association represents unary (many-to-many recursive) or ternary relationships and can also be used to represent relationships that have attributes among the entities; the N-ary Association element should always be at the target end of a connector
Connector is a connector between an Entity and an Attribute, and between two Attributes
Relationship is a diamond-shape connector, representing the meaningful association among entities
Disjoint and Overlapping represent the relationships between the super-class Entity and the sub-class Entity

A typical Entity Relationship diagram

Tagged Values

Some of the Entity Relationship diagram components can be modified by Tagged Values, as indicated:

Component	Tagged Value / Notes
Entity	isWeakEntity Notes: If true, this entity is a weak entity.
Attribute	attributeType Notes: There are four valid options: 'normal', 'primary key', 'multi-valued' and 'derived'
Attribute	commonDataType Notes: Defines the common data type for each attribute.
Attribute	dbmsDataType Notes: Defines the customized DBMS data type for each attribute. This option is only available when the commonDataType tag is set to 'na'. You must define the customized type first through the 'Settings > Reference Data > Settings > Database Datatypes' ribbon option.
N-ary Association	isRecursive Notes: If true, the N-ary Association represents the many-to-many recursive relationship. For one-to-many and one-to-one recursive relationships, we suggest using the normal Relationship connector. Sometimes you might want to limit the stretch of the diamond-shape Relationship connectors; simply pick a Relationship connector, right-click to display the context menu, and select the 'Bend Line at Cursor' option.
Relationship	isWeak Notes: If true, the Relationship is a weak relationship.
Disjoin Overlapping	Participation Notes: There are two valid options, 'partial' and 'total'.

Notes

Entity Relationship diagrams are supported in the Corporate, Unified and Ultimate Editions of Enterprise Architect

Learn more

Wikipedia Entry on Entity Relationship diagrams (Online Resource)

Which of the following statements is true of relational database management systems Rdbms?

Which of the following statements is true of relational database management systems? They can be used to combine tables to deliver data only if two tables share a common data element.

Which of the following is the term for data about the structure of a database?

Explanation. The correct answer is schema. The schema describes the structure of the database.

Which of the following is true when implementing a one

17) Which of the following is true when implementing a one-to-many relationship? The file on the many end has a foreign key consisting of the primary key on the one end.

Which of the following gives an accurate description of a data model?

Which of the following gives an accurate description of a data model? It is a logical representation of the data in a database that describes the data and relationships that will be stored in the database. Which step is NOT required in transforming a data model into a relational database design?