About Implement Relations

Implement links are used to connect objects from the four RFLP tree categories (Requirement, Functional, Logical, Physical).

An implement link:

Identifies the purpose of the implementing object
Defines the context to be loaded when opening with completion an object (in case of a reference-reference implement link)

This page discusses:

Implement Links Display
Context and Subcontext Definition
Implement Links Between Objects
Implement Links List
Implement Links: Display in the 2D Graph

Implement Links Display

Implements links are displayed in the tree (in the implementing object node) and in the work area (on both implemented and implementing objects).

Tips:

In the tree, click the implement link to highlight the implementing and implementing objects.
In the work area, click the icon to display the implementing or implemented object.


Tree	Work area
	Implemented icon: Implementing icon:

Note:

In the tree, if the corresponding options are selected, the implement relations are stored in these folders:

Implement Relations: The two entities pointed by the implement relation are present in session.
Partially Loaded Implement Relations: At least one entity pointed by the implement relation is not present in session (but both extremities exist).
Broken Implement Relations: At least one entity pointed by the implement relation no longer exists.

For more information about these options, see Me > Preferences > App Preferences > 3D Modeling > Systems Architecture > Functional & Logical Design > Tree. For more information, see Native Apps Preferences Guide: Tree.

Context and Subcontext Definition

Between two references, links can be defined in the context or subcontext of the selected references.

Implement Links Between Objects

Between two categories, whatever element you first select when creating an implement link, the implement relation is always created from the lower level abstract category to the higher level abstract category.

In other words:

A physical product implements a function, a logical component or a requirement.
A logical component implements a function or a requirement.
A function implements a requirement.

Implemented Requirements

You can create an implement link between the following elements:


Implementing domain	Requirement root	Requirement
Function root
Function
Flow
Flow Exposition Instance
Logical root
Logical system type
System Type Exposition Instance
Physical root

Implemented Functional Objects

You can create an implement link between the following elements:


Implementing domain	Function	Function Port	Functional connection	Flow	Flow Exposition Instance	Logical Component	Logical port	Logical Connection	System type	System Type Exposition Instance	Physical product
Function
Functional Port
Functional Connection
Flow
Flow Exposition Instance
Logical component
Logical port
Logical Connection
System type
System Type Exposition Instance
Physical product

Implement Links List

To list implement relations on an object, you can use:

The RFLP Linked Objects panel (see Showing RFLP Linked Objects)
The Traceability Matrix (see Display Implement Relations in the Traceability Matrix)
B.I. Essentials (see Using B.I. Essentials in Functional & Logical Design).

Implement Links: Display in the 2D Graph

Mask Describing the Implement Link

On the implemented or implementing object, a mask indicates the implement link status:


Mask	Implement Link Status
	Implement links in the current context of the selected element (parent path).
	Implement links in a subcontext (child path).
	Implement links between the reference of the selected element and other references.
	Implement links that connect the selected element to other elements, in contexts different from the current one. Note: This last implement link appears only if the List the Implement links that connect the selected element in another context option is selected in Me > Preferences > App Preferences > 3D Modeling > Systems Architecture > Functional & Logical Design > Genreal.