Cradle from 3SL, the complete Model Based Systems Engineering Toolsuite, specialising in requirements management, requirements capture, model based systems engineering and for systems engineering software, support and consultancy, the logical choice: Cradle from 3SL.
login Register forgot password or username?
Search:         

Welcome to 3SL Reference Section

Entity Relationship Diagrams

Purpose

Entity Relationship Diagrams (ERD)s may be considered as graphical representations of data definitions. Information modelling is concerned with the definition of data within the system in terms of its meaning, composition and relationships. One of the methods within Cradle that can be used to represent information modelling is the use of an ERD. ERDs show graphically how different pieces of information are related.

Example

Here is an example Entity Relationship Diagram.

Example ERD

Description

DFDs show the flow of information through the system but play no part in defining the information, apart from being a useful place from which to access data definitions. Flows and stores on DFDs are essentially representations of information that is defined elsewhere.

While the DFD models the active processing of information by the system, the ERD models the static relationships amongst this information that are preserved and maintained by the system. The ERD shows how items of data relate, statically, to each other. ERDs cannot exist in a hierarchy, instead, either a single ERD is produced for the entire system analysis or design (when the ERD is considered to relate to the entire DFD hierarchy), and/or ERDs can be produced as companions to specific DFDs that contain a large quantity of stored data, and contain the processes that create, update, or otherwise maintain the stored data.

Diagram Conversions

None.

Characteristics

APPEARS IN DOMAIN

Essential and Implementation

NUMBERING

Cradle does not restrict the numbering of ERDs, so they can be used in whatever manner is appropriate.

HIERARCHICAL

No

Symbols

Symbol

Name

Description

Definition

Expansion

ERD Comment

Comment

Makes a note anywhere in the diagram. Are always surrounded by * characters.

None

None

ERD Data Object

Data object

An item of data operated upon by the system.

data definition

None

ERD Relationship

Relationship

A relationship between one or more Data Objects , as one of: one-to-one, one-to-many, many-to-many.

data definition

None

ERD Subtype/Supertype Relationship

Subtype/Supertype relationship

A relationship between (normally) three or more Data Objects , used in the situation where one Data Object contains data elements common to two or more other Data Objects (such as an object machine containing data items price , weight , and size , and two other Data Objects , lathe and drill , containing data elements unique to each machine type).

None

None

ERD Picture

Picture

Allows you to choose the location of a GIF or JPEG image to be displayed as a diagram symbol or to be embedded in an existing diagram symbol.

None

None

ERD Connection Symbol

Connection symbol

A link between a Data Object and a Relationship .

None

None

ERD Subtype/Supertype Connection

Subtype/Supertype connection

A link between Data Objects and Relationships or Sub/Supertype Relationships .

None

None

ERD Associative Connection

Associative connection

A link between an unnamed Relationshop and a named Data Object that indicates that the Relationship contains data in addition to the relationship between the Data Objects .

None

None

Back to top