Template Type: Connectors

Data Relation

A DataRelation shows the relation between two data entities.

At each end of a DataRelation there is a DataEntity, which automatically appears in the ‘From’ and ‘To’ fields in the DataRelation dialog. The roles of the DataEntities can be described and the cardinality. If a one-to-many DataRelation is created, QualiWare Lifecycle Manager will automatically update the relevant DataEntity with a foreign key.

Node Relation

Used for connecting the symbols in a deployment diagram.

NodeRelation properties

The NodeRelation tab

Property  Metamodel name Description
Show on diagram ShowOnDiagram Initial value is on.
Short description ShortDescription

The Extensions tab

Property  Metamodel name Description
Stereotype Stereotype Links to: Stereotype.
Constraints HasConstraints Links to: Constraint.
Tagged values HasTaggedValues Links to: TagDefinition.

The Ext From tab

Property  Metamodel name Description
Stereotype FromStereotype Links to: Stereotype.
Constraints FromConstraints Links to: Constraint.
Tagged values FromTaggedValues Links to: TagDefinition.

The Ext To tab

Property  Metamodel name Description
Stereotype ToStereotype Links to: Stereotype.
Constraints ToConstraints Links to: Constraint.
Tagged values ToTaggedValues Links to: TagDefinition.

Data Flow

A DataFlow is connection on a DataFlowDiagram through which information flows. A DataFlow must always be connected to a Process in one end.

Data Entity

A DataEntity represent a logical group of information – a category of information.
In the early phases of a system analysis or even a business analysis a DataEntity is used to describe physical objects like ‘Customer’, ‘Order’ or ‘Product’. Or it is used to describe important concepts in the modelled system or its surroundings.

In a later phase a DataEntity will represent a smaller normalized informationgroup.

One of the most important characteristics of a DataEntity is, that it can be uniquely identified using a relation to a Key, and that it has got non-key Attribute describing its information content.

In QualiWare Lifecycle Manager the concept of a DataEntity includes a description of the operations performed on the DataEntity during its lifecycle – i.e. from it is created for the first time in the system, until it is deleted. This is accomplished by letting the user relate a DataEntity to a series of operations – here called Methods. This object oriented approach makes it possible for the designer to separate into small reusable groups related information and functions.

When a DataEntity is created it is good practice to give it a primary key. When this is done and the OK-button on the DataEntity dialog is pressed, the key attributes is automatically transferred to the attribute link list.

Object Association

Object association refers to the relationship between different objects or components within a system, where one object is associated or linked to another object. Object association can be used to represent various types of relationships, such as ownership, collaboration, or interaction between different objects or components.

For example, in a system where a customer places an order for a product, the object association might be illustrated through a line connecting the customer object to the order object, and another line connecting the order object to the product object. The lines would represent the associations between the objects, since the customer is associated with the order, and the order is associated with the product.

The ObjectAssociation tab

Property  Metamodel name Description
Show ShowShortDescription Check to show short description on diagram
Initial value is on.
Short Description ShortDescription Short verbal description of this relation
Role FromRole Verbal description of the role of the starting InformationConcept.
Show ShowFromRole Check to show role on diagram.
Initial value is on.
Group
Role FromRole Verbal description of the role of the starting InformationConcept.
Show ShowFromRole Check to show role on diagram.
Initial value is on.
Cardinality FromCardinality Min. and max. cardinality for the starting InformationConcept for each ending.
Choices are:
0:1
1:1
0:M
1:M
Role ToRole Verbal description of the role of the ending InformationConcept.
Show ShowToRole Check to show role on diagram.
Initial value is on.
Group
Role ToRole Verbal description of the role of the ending InformationConcept.
Show ShowToRole Check to show role on diagram.
Initial value is on.
Cardinality ToCardinality Min. and max. cardinality for the ending InformationConcept for each starting.
Choices are:
0:1
1:1
0:M
1:M

Object Decomposition

Object decomposition refers to the process of breaking down a complex object or system into smaller, more manageable components or sub-objects. Object decomposition is used to simplify the representation of complex systems by dividing them into smaller, more easily understood parts.

For example, a line might connect a process to a module to represent how the process is made up of smaller modules. Similarly, a line might connect a module to a function to represent how the module is made up of smaller functions.

The ObjectAggregation tab

Property  Metamodel name Description
Short Description ShortDescription Short verbal description of the object aggregation

Object Dependency

Object dependency refers to the relationship between different objects or components within a system, where the behavior or functionality of one object is dependent on the behavior or functionality of another object.

For example, in a system where a database is used to store customer information, the object dependency might be illustrated through a line connecting the customer information object to the database object. The line would represent the dependency of the customer information object on the database object, since the customer information cannot be retrieved or stored without the use of the database.

The ObjectDependency tab

Property  Metamodel name Description
Short Description ShortDescription Short verbal description of the dependency
Label Box LabelBox Label for this dependency
Initial value is on.
Dependency type DependencyType The type of object dependency

Object Generalization

Object generalization in a business diagram refers to the process of creating a more general class or category of objects or components that share similar characteristics or behaviors. Object generalization is used to simplify the representation of complex systems by grouping similar objects or components together.

For example, a line might connect a specific product to a product category to represent how the product belongs to a more general category of products. Similarly, a line might connect a specific customer to a customer type to represent how the customer belongs to a more general category of customers.

The ObjectGeneralization tab

Property  Metamodel name Description
Short Description ShortDescription Short verbal description of the generalization