Versions Compared

Old Version 21

changes.mady.by.user Fiona Sargeant

Saved on

compared with

New Version 22

changes.mady.by.user Fiona Sargeant

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page is for data modellers or application designers. It explains how to use a relationship diagram to understand how your system's data is connected.

TODO - Possibly bugs or possibly me...

To Jira relationship

Raise a Jira if you see these again. They currently look OK.

  • Relationship end points can be drawn a long way from the mouse when you are selecting an attribute. 
  • When entities are below each other PhixFlow gets confused about which one you are selecting.

Overview

Use a relationship diagram to represent the information that your application will use and how it is connected. If you want to show a processIt is important to understand the connections between data when you start to create relational views, which display data from different streams.

Relationship diagrams do not show changes over time, responsibilities or processes. To represent this type of information, use a workflow diagram.

PhixFlow's relationship diagrams are simplified entity-relationship diagrams (ERD).  An ERD is commonly used to show the relationships between database tables. If you are not familiar with ERDs for databases, the concepts are explained in this article: ER Diagram Tutorial in DBMS.  


Panel
borderColor#7da054
titleColorwhite
titleBGColor#7da054
borderStylesolid
titleSections on this page

Table of Contents
indent12px
stylenone



Key concepts
Entity-Relationship DiagramPhixFlow Relationship DiagramExamples
A database table represents a thing or entity.

A stream represents a thing or entity.

Tip

Choose a stream name that reflects the entity it represents.


Entities:

  • Company
  • Employee
  • Department
  • Product
The column headers of a database table are the data attributes.

The stream attributes are the data attributes.

Employee attributes:

  • EmployeeID 
  • Name
  • Address
  • Phone
  • Department

A stream must include at least one attribute that has unique values.
This is usually an identifier, so has ID or UID in the name.
The unique attribute is the primary key.

Primary Keys

  • Employee stream: EmployeeID
  • Department stream: DepartmentID
When the data from one stream's primary key also appears in a different stream, it is a foreign key.

Employee attributes:

  • EmployeeID (primary key)
  • Name
  • Address
  • Phone
  • Department = DepartmentID - foreign key

Department attributes

  • DepartmentID - primary key
  • Department Name
  • Purpose
  • Department Manager = foreign key

Tables or attributes can have various relationships to each other

Tip

By convention, a relationship is expressed as an action (verb) that follows the left-right flow of the diagram.


Attributes can have relationships. On the diagram the relationship is shown as an arrow.
The relationship must have a unique name.

Relationships can only be one-to-many, from primary key to foreign key.

Relationships

  • one company → employs → many employee
  • one employee → manages → several departments
  • one department → makes → many products


Note

We recommend that a primary key attribute should be set as an integer. , because PhixFlow can automatically generate a unique integer value for each new data record.


More About Relationships

The name for the relationship should reflect its direction. For example:

  • either company → employs → people
  • or people→ work for → company
  • but not company → work for→ people

PhixFlow imposes no restrictions on the names for relationships, but it must be unique in the repository.   (Todo - May change)

One to One Relationships

In a PhixFlow relationship diagram, it is not possible to create a one-to-one relationship. 

Many-to-Many Relationships

You can show a many-to-many relationship by using an intermediate stream, called a resolution entity. This stream has attributes that are foreign keys from the two streams you want to connect, with a one-to-many relationship into the foreign keys. For example

  • A customer buys many products
  • And a product can be bought by many customers
In this case the resolution entity could be the customer purchase record
  • The intermediate stream is a Customer Purchase Record, which has both the CustomerID and ProductID as foreign keys.

Example

In a relationship diagram, a stream and its attributes are displayed as a box. You can expand or collapse the  box using the icon in the top left. PhixFlow shows all the attributes when the stream is expanded, and only the primary and foreign keys when it is collapsed.

The following diagram shows some relationships between streams that represent a company, its employees and departments, the products it makes and the customers who buy them.

(Todo - update with a final version)

The company "contains" many departments. An employee "works in" a department, and a department can have many team members. In this company, the department "makes" several products, which "ship to" many customers.

Relationship diagrams are useful because you can design relational views that use data from multiple streams. For example, you might want a view that shows the employee details by department. This will display data from the Employee stream and the Department stream. The relationship diagram shows these are connected by the DepartmentID attribute.


Relationship Diagrams and Relational Views

TODO - Add how ERDs and Relational vies interact.

Drawing Relationship Diagrams

Create a Relationship Diagram

  1. In the repository for your application, right-click on 
    Insert excerpt
    _relationship_diagram
    _relationship_diagram
    nopaneltrue
    .
  2. Click 
    Insert excerpt
    _add
    _add
    nopaneltrue
    .
  3. In the pop-up, enter its name.
  4. PhixFlow opens a properties tab on the right, and a new relationship diagram on the left. The relationship diagram has a toolbar at the top; see the Toolbar section below for details.
Tip

When you make any changes to the diagram, remember to 

Insert excerpt
_save
_save
nopaneltrue
.

Open a Relationship Diagram

To open an existing relationship diagram:

  • either, in the repository, right-click on its name and select Display.
  • or, in the properties toolbar, click the .
    Insert excerpt
    _relationship_diagram
    _relationship_diagram
    nopaneltrue
     icon.

Create a New Stream

  1. Drag the 
    Insert excerpt
    _streams_add
    _streams_add
    nopaneltrue
     icon from the toolbar into the diagram.
  2. In the pop-up, enter its name, for example "Customer" and click
    Insert excerpt
    _dialog_finish
    _dialog_finish
    nopaneltrue
    . PhixFlow opens a new Stream properties tab.
  3. PhixFlow adds a box to represent the data stream, and opens the properties tab for it.
  4. To add attributes to the stream
    • either, in the properties tab on the right, In the Attributes section, click 
      Insert excerpt
      _add
      _add
      nopaneltrue
      .
    • or right-click the stream and select Add New Stream Attribute.
  5. PhixFlow opens a Stream Attributes properties tab where you can specify details for the attribute, such as its name, data type and length. 
  6. If this is the unique identifier, tick Primary Key. Remember to include ID or UID in the name.

Add an Existing Stream

  1. In the repository, open the list of streams.
  2. Drag a stream from the repository into the diagram. PhixFlow adds the stream with a list of all of its attributes.
  3. If the stream has many attributes, click  to collapse the stream so that it only shows the primary and foreign keys.

Connect Attributes

To connect attributes in different streams, click-drag from one attribute to another. PhixFlow shows the currently selected destination in bold. Release the click to connect to the selected destination.

PhixFlow can only connect primary and foreign keys. If you connect standard attributes, PhixFlow automatically sets them to be foreign keys.

Tip

You can change which attributes are the Primary Key or a Foreign Key  using the tick boxes in the the Stream Attributes properties. TODO ADD the new properties to attributes)

PhixFlow automatically sets the type of relationship according to the keys:

  • one to one: from primary key to primary key
  • one to many: from primary key to foreign key
  • many to one: from foreign key to primary key
  • many to many: from foreign key to foreign key

Other affected pages: repository, toolbars

Properties

Insert excerpt
_standard_settings
_standard_settings
nopaneltrue

Basic Settings

FieldDescription
NameEnter the name for the entity-relationship diagram. When yo press Return or save a new properties tab, PhixFlow opens an empty diagram in the workspace on the left.


Toolbar 
Anchor
toolbar
toolbar

TODO Same as Model Window Toolbar Icons

Organise selected objects in a grid.

Align all selected objects left.

Align all selected objects right.

Align all selected objects to top.

Align all selected objects to bottom.

Distribute all selected objects horizontally. Changed ICON TODO

Distribute all selected objects vertically. Changed ICON TODO


Drag into the diagram to add a stream, or click to open the list of streams in the repository

Save TODO

Refresh TODO

Help TODO