Diagram

Diagrams are a useful tools for visualizing and exploring your project. They demonstrate visual connectivity and relationships including associations, compositions and semantic paths. For convenience, they can be saved and exported for future re-use.

Diagram interface overview

Interface overview

The Diagram interface is composed of 5 parts:

1. Main top menu for the most used features of diagrams
2. Stencils for creating new diagram content
3. Details and Usages panels on the right
4. The center canvas to visualize and arrange diagram content
5. The NavTree on the far left

General menu actions

IMAGE

The first set of actions in the menu allows:

• Clear Diagram: Removes all objects from the canvas
• Auto layout: Rearranges all objects on the canvas
• Zoom: Custom zoom levels for the canvas area

Interface modes

A diagram can be used in one of two modes (1) Modeling (2) Projection:

• Modeling mode: This is the standard entity diagramming mode that allows for the editing of entities and associations. This includes the creation of composition and association relationships.

IMAGE

• Projection mode: This mode is specifically designed for the creation and editing of Views. This includes the creation, editing and displaying of the semantic projection paths making up that View.

IMAGE

Managing elements on a Diagram

Adding elements to the diagram

Elements can be added to the diagram canvas from different locations:

• From the stencil panel: Dragging an object from the stencil panel will create new entities, associations, and views. These elements are not committed to any model, but can be found in the NavTree under the UncommittedEntities package.
• From the NavTree: Dragging an existing object from the Navtree will add those objects to the diagram canvas where they can be directly edited and saved within the diagram.

Once the desired objects are on the diagram, compositions and associations can be created between them using the respective icons IMAGE and IMAGE When dragging a connector from one object to another, various anchor point options are provided to customize the diagram.

Note: An Association must have at least 2 connections to be valid.

IMAGE

Interacting with elements on the diagram

Most components on the diagram have a right-click contextual menu allowing the user to interact with them.

Below is a table detailing how mouse clicks interact with the elements on the diagram.

IMAGE

When hovering over an entity, a tooltip displays its description.

When an entity or an association is selected, the right-side panel can display its details and usages:

• Details: Displays editable Name and Description fields for the entity.
• Usage: Displays usages of and relationships to that object throughout the rest of the model including Compositions, Associations, Specializations and Views.

IMAGE

Deleting and removing elements

The option to "Remove" exists for all diagram objects. This means that they are removed from the diagram but they still exist in the model or in the UncommittedEntities list.

The option to "Delete" a diagram object exists for only some objects. This means that they will be permanently removed from the model or the UncommittedEntities list.

An option located in the Gear menu on the far right of the menu bar allows the user to switch off the Delete/Remove confirmation messages for convenience.

IMAGE

Diagram management

There are 3 actions that can be performed on a diagram:

IMAGE

• Upload: Allows the loading of a saved diagram and also the ability to delete saved diagrams.
• Save: Saves the current diagram. Everything that is displayed on the diagram (committed entities, uncommitted entities, connections, drawings...) will be saved in the diagram.

Note: if a diagram is not saved, then all changes made to it will be lost when the page is refreshed

• Export: Exports the diagram as a PNG image

Committed and uncommitted entities

Uncommitted entities

Uncommitted entities are created by dragging an Entity, Association or View block from the stencil panel. Once on the diagram canvas, they can also be found in the NavTree under the UncommittedEntities package.

Note: If uncommitted entity is not saved in a diagram or committed, when the diagram page is refreshed, they are lost.

IMAGE

An uncommitted entity can be reused in all the diagrams that the user has open, but in order to be used within a View path, they must be committed first.

Commit entities

When an entity is created or updated from the diagram, the changes are not stored in any model until the user commits them.

IMAGE

IMAGE

When the user clicks the "Commit" button, a dialog appears listing all the entities that have been created or updated. The user can chose to commit all or some of them to a specific model.

Note: If a diagram was saved with uncommitted entities, when they are committed, the diagram is re-saved to account for the change and keep the data synchronized.

Building view paths

To build, a new path for a view:

• Add a new field to a view. The rolename can be added later and the measurement will be added automatically when the path is built.
• Click on the IMAGE icon
• Select the 1st hop in the path which will be either an entity or a path. The available elements are highlighted in green

IMAGE

• For the next hops, the possible subsequent hops are highlighted in green. They are either an attribute within the current hop selected or within associations that contain the current hop

IMAGE

IMAGE

• To complete a path. the last hop has to be types as an Observable

IMAGE

Paths can be shown/hidden using the eye icon. By using the show/hide eye icon repeatedly, the View paths will randomly change colors for convenience.

IMAGE