Master Conceptual Data Modeling in PowerDesigner: Entities, Attributes, and Relationships

1. Overview of Conceptual Data Model

Data model is an abstraction of real‑world data characteristics. It should satisfy three requirements: (1) realistically simulate the real world, (2) be easy to understand, (3) be easy for a computer to implement.

Conceptual data model (also called information model) is based on the Entity‑Relationship (E‑R) theory and extends it. It models information from the user’s viewpoint and is mainly used for the conceptual design of databases.

Typically, the real world is first abstracted into a conceptual world (CDM), then transformed into a physical data model (PDM) supported by a specific DBMS.

CDM consists of a strictly defined set of model elements that describe static and dynamic characteristics and integrity constraints, including data structure, data operations, and integrity constraints.

Data structure: entities and attributes.

Data operations: insert, delete, update, query on entity records.

Integrity constraints: attribute‑level constraints (type, check, rule) and referential constraints (relationships, inheritance).

2. Definition of Entity, Attribute, and Identifier

An entity (or instance) represents a distinguishable “thing” or “event” in the real world, e.g., a student or a surgery. Each entity is described by a set of attributes such as student number, name, gender, birthdate, department, enrollment year.

An entity set is a collection of entities of the same type and properties. An entity type is the common set of properties shared by entities in an entity set; the terms are often interchangeable.

An identifier is one or more attributes that uniquely identify an entity instance. The primary identifier is the chosen identifier; additional identifiers are secondary.

3. Expressing Entities, Attributes, and Identifiers

PowerDesigner is used to create conceptual data models, entities, and attributes. The following steps illustrate the process.

3.1 Create a New Conceptual Data Model

File → New → select “CDM model”.

Enter model name, code, description, creator, version, etc., in the Properties dialog.

3.2 Create a New Entity

In the CDM diagram, click the Entity tool, then click the canvas to place an entity symbol.

Double‑click the entity to open its General tab and enter name, code, description.

3.3 Add Attributes to an Entity

In the Attribute tab, add attributes. Options such as “Add Attribute” and “Reuse Existing Data Item” are related to the Data Item’s Unique Code and Allow Reuse settings.

Columns P, D, M indicate whether the attribute is a primary identifier, displayed in the diagram, or mandatory (cannot be null).

Standard checks (Minimum, Maximum, Default, Unit, Format, Lowercase, Uppercase, Cannot modify, List of Values, Label) can be defined in the Checks tab.

Additional checks can be defined using SQL variables %MINMAX%, %LISTVAL%, %RULES%, %UPPER%, %LOWER%.

3.4 Define Identifiers

Open the Identifiers tab of an entity to designate primary and secondary identifiers.

3.5 Create Data Items

Data items are the smallest units of information and can be attached to entities as attributes. Use Model → Data Items → Add a Row to create a new data item, then set code, data type, length, etc.

The “Unique Code” option enforces uniqueness within a namespace; “Allow Reuse” permits a data item to be used by multiple entities.

3.6 Add Data Items to Entities

In an entity’s Attributes tab, use “Add a DataItem” to copy an existing data item (a new code is generated if Unique Code is enabled) or “Reuse a DataItem” to reference an existing one without duplication.

4. Relationships

A relationship links instances of entity sets. Relationships can be one‑to‑one, one‑to‑many, many‑to‑one, or many‑to‑many.

To create a relationship, select the “Create Relationship” tool, click the source entity, drag to the target entity, and release.

Four basic relationship types are illustrated, along with special types such as Identify (dependent), Non‑Identify, and Recursive relationships.

Identify relationships occur when the identifier of one entity becomes part of the identifier of another entity, creating a dependency.

Recursive relationships connect instances within the same entity set (e.g., employee‑manager hierarchy).

Relationship properties include role names, mandatory/optional flags, and cardinalities (e.g., 1,1 or 0,n).

5. Additional Relationship Attributes

After drawing a relationship, double‑click the line to open its properties window, where you can set role names, mandatory flags, and cardinalities for each direction.

Understanding these elements enables accurate translation of a conceptual model into a physical database schema.