Diagram

A diagram is a graphical representation of Atomic Warehouse Model (AWM) elements and their relationships that shows in a graphical form how model elements are related to each other. A diagram is also used to represent the AWM elements that belong to a project scope. In CA ERwin, the diagram construct is supported by a subject area.

IBM Industry Models are delivered with predefined diagrams.
Note: no predefined diagrams exist for project scopes.

Properties

Name (mandatory)
A textual name that identifies this diagram. The name is based on the names of parent packages of the model elements that are represented in this diagram.
  • e.g. diagram Involved Party Hierarchy
  • e.g. diagram Arrangement Overview
Members (mandatory)
The model elements that belong to this diagram.

When the diagram represents a project scope, all entities in the diagram are part of the scope and all attributes in scope are highlighted with a color.

Parent package (mandatory)
The parent package, to which this diagram belongs. Diagrams illustrating AWM elements sit in the package of the entities on which the diagram focuses. Diagrams representing project scopes have the <<Scopes>> package as parent package.
  • e.g. package Arrangement is parent package of diagram Arrangement Overview
Entities
Entities that are shown in these diagrams use a color coding scheme that is described in Entity.

Project scope diagrams

AWM includes many thousands of entities and attributes. Data model implementers typically want to work with a subset of these when they are developing a data model for a specific project. This subset is referred to as a scope.

When scoping a data model, create a diagram to hold all the elements that are part of your scope. The diagram represents a view of your scope. Attributes that are part of the scope can be highlighted with a color. Attributes that are not part of the scope are set as nonpersistent.

Package diagrams have the following properties:
  • Name identifies the diagram and is based on the name of the modeling project or business requirement.
  • A parent package e.g. <<Scopes>>, is used as the parent package.
  • When the diagram represents a project scope, all entities in the diagram are part of the scope.
  • Attributes that are part of the scope can be highlighted with a color. Attributes that are not part of the scope are set as nonpersistent.