Aspect

General Information

The workspace area for the management of Aspects can be accessed via menu Aspects. Information on the graphical user interface and basic functionalities can be found on page Graphical User Interface and Basic Functions. This workspace offers users different functionalities described in brief in the following table as well as in more detail in the next chapters.

Toolbar in Tabular View

Details Page

In order to view more details related to an Aspect, users may open the Aspect in view mode by clicking on it from the list view. Note: opening an Aspect in view mode is also possible from the tree view of Aspects.

The details page of an Aspect is subdivided into different tabs. The visibility and order of the displayed tabs is configurable by users with configuration rights. Furthermore, custom tabs can be created. The custom tabs allow customers to organize the standard and extended attributes as required by their business use cases.  

Tabs which do not contain any information are grayed out.

The following table gives an overview of the tabs available for an Aspect:

Export

Users may export all or a selection of Aspects in one of the available export formats. The export are available in Aspects tabular view and have following formats:

• DIN 4002

• Spec Sheet XLSX

After defining the export options in the graphical user interface, the user may press the export button and the export will be started in the background. The exported file will be sent per e-mail to the specified e-mail address.

Export Options DIN 4002 Export Format

Through a redesign of the eptos export pages, the external appearance of the exports has now been fully adapted to the defined Usability Guidelines.

This has significantly improved the look and feel of these pages.

In a harmonized DIN 4002 Export dialog the user can save and load favorite dialog settings in tab “Selection of attributes” to access those settings faster instead of selecting them again for each new export.

Spec sheet XLSX Export Format

Note: in case the exported structure contains Elements that form a loop in the structure, the export detects this infinite loop and, instead of running endlessly, it considers the loop as a content error, highlights the export row in red and indicates to user the message that 'An infinite loop was detected'.

Create

With this functionality, users can create new Aspect. The Create functionality has two options:

• Create: allows users to create new Aspects in the hierarchy of Aspects. An assignment of the newly created Aspect to an Application Class (if needed) is done in a later step.

• Create Aspect directly assigned to Application Class: Allows users to create new Aspects that are directly assigned to an Application Class in the Application Class hierarchy. The Aspects are also visible in the hierarchy of Aspects.

Since Aspects are hierarchical structures, the first step when creating an Aspect is the selection of its placement in the hierarchy. The new Aspect can be placed in the Aspect hierarchy or assigned directly to an Application Class.

After the placement of the Aspect was defined, the user may continue with filling in the attributes of the new Aspect in the Create graphical user interface displayed in the next step. In the Create graphical user interface, mandatory attributes are marked with an asterisk and non-editable attributes are displayed as read-only. 

When the work is finished, the user may save the new Aspect as Change Request (using button Save) or directly as structure element (using button Save and Release).

Change Requests usually undergo an approval process before they are released and become effective. 

Change Text

This functionality allows users to edit the textual attributes of an Aspect. After selecting the Aspect to be changed, the user can proceed with changing the textual attributes of the Aspect in the Change text graphical user interface, which is displayed after clicking the Change text button. In the Change text graphical user interface, mandatory attributes are marked with an asterisk and non-editable attributes are displayed as read-only. 

When the work is finished, the user may save the changed Aspect as Change Request (using button Save) or directly as structure element (using button Save and Release). 

Change Requests usually undergo an approval process before they are released and become effective.  

Delete

This functionality allows users to delete existing Aspects.

Note: on deletion, the Aspect will be marked as deprecated, meaning that it is withdrawn from further usage. Deprecated elements are displayed grayed out in the system and they cannot be worked on or used anymore. 

On pressing the Delete button, the system displays the details page of the Aspect selected for deletion. User may check the attributes/relations of the Aspect before proceeding with the deletion. 

The user may confirm the deletion by pressing button Save or Save and Release. 

On Save, a Change Request for the deletion of the Aspect will be created. Change Requests usually undergo an approval process before they are released and become effective. 

On Save and Release, the Change Request for the deletion of the Aspect will be automatically executed (released). As a result, the Aspect is immediately withdrawn from further usage and is displayed as inactive within a given release (grayed out). 

Copy

This functionality allows users to create assignments of Aspects to Application Classes by means of copy and paste. 

The user may select an Aspect in the tabular view or in the tree view and press button Copy. In the tabular view or tree view of Application Classes, the user may select an Application Class where the copied Aspect should be assigned.

Note: The Paste button will appear only if the copied element type is compatible with the selected item (i.e. only if the selected Application Class allows an assignation of the copied Aspect).

On pressing the Paste button, the system will lead to the Assign Aspect page where user may confirm the assignment by pressing button Save or Save and Release. 

On Save, a Change Request for the assignment of the copied Aspect to the selected Application Class will be created. Change Requests usually undergo an approval process before they are released and become effective. 

On Save and Release, the Change Request for the assignment of the copied Aspect to the selected Application Class will be automatically executed (released). As a result, the Aspect is immediately connected to the Application Class.

Reactivate

This functionality allows users to reactivate (i.e. to make them available for usage within a certain release) the following elements:

• a deprecated Aspect

• a deprecated assignment of a Property to the selected Aspect

The options in the drop-down button are active only if the selected Aspect meets certain conditions:

• Aspect → the selected Aspect is deprecated

• Property assignment → the selected Aspect has at least one deprecated Property assignment

Reactivate Aspect

In order to reactivate a deprecated Aspect, the user needs to select a deprecated Aspect in the tabular view or tree view and press button Reactivate / Aspect

The system displays the Reactivate graphical user interface, which consists of the detailed view of the selected Aspect. Therefore, user can first check the detailed information of the Aspect before confirming the reactivation by pressing button Save or Save and Release. 

On Save, a Change Request for the reactivation of the Aspect will be created. Change Requests usually undergo an approval process before they are released and become effective. 

On Save and Release, the Change Request for the reactivation of the selected Aspect will be automatically executed (released). As a result, the Aspect is immediately activated and can be used.

Reactivate Property Assignment

In order to reactivate deprecated Property assignments for a specific Aspect, user has to first select the Aspect in the tabular view or tree view and press button Reactivate / Property assignment.

Note: the button is active only if the selected Aspect has deprecated Property assignments.

In the next step, the system displays a list of Properties having a deprecated assignment to the selected Aspect. The user can select one or more Properties and then proceed with the reactivation. 

For the reactivation of Property assignments, the Reactivate graphical user interface consists of the details page of the Aspect and the details page of the Property to be reactivated (in case one single Property assignment is re-activated) or the list of Properties to be reactivated (in case multiple Properties were selected for reactivation).

The user may confirm the reactivation by pressing button Save or Save and Release. 

On Save, a Change Request for the reactivation of the Property assignments will be created. Change Requests usually undergo an approval process before they are released and become effective. 

On Save and Release, the Change Request for the reactivation of the Property assignments will be automatically executed (released). As a result, the connection of the Aspects to the Properties is immediately activated.

Assign

The connection between Aspect and their generic set of Properties is called assignment. The Properties forming the generic set can be:

• assigned directly to the Aspect

• grouped in Blocks and then assigned to the Aspect via the Block. Note: the assignment of Blocks to Aspect is done via Block References. 

The Assign functionality (Button Assign) groups together these two options.

Assign Block Reference

This functionality allows users to assign one or more Block References to a selected Aspect. 

The starting point of this functionality can be the tabular view or the tree view, where the user can select the Aspect. In the next step, the user can select the Block References to be assigned from the tabular view of available Block References (tabular view filtered on Properties with datatype Reference). 

For the assignment of Block References, the graphical user interface consists of the details page of the Aspect and the list of Block References to be assigned.

The user may confirm the assignment(s) by pressing button Save or Save and Release. 

On Save, a Change Request for the assignment of the Block References will be created. Change Requests usually undergo an approval process before they are released and become effective. 

On Save and Release, the Change Request for the assignment of the Block Reference(s) will be automatically executed (released). As a result, the connection of the Aspects to the Block References is immediately available.

Assign Property

This functionality allows users to assign one or more Properties to a selected Aspect. 

The starting point of this functionality can be the tabular view or the tree view, where the user can select the Aspect. In the next step, the user can select the Properties to be assigned from the tabular view of available Properties. 

For the assignment of Properties, the graphical user interface consists of the details page of the Aspect and the list of Properties to be assigned.

The user may confirm the assignment(s) by pressing button Save or Save and Release. 

On Save, a Change Request for the assignment of the Properties will be created. Change Requests usually undergo an approval process before they are released and become effective. 

On Save and Release, the Change Request for the assignment of the Properties will be automatically executed (released). As a result, the connection of the Aspect to the Properties is immediately available.

Withdraw 

The connection between Aspects and their generic set of properties is called assignment. The properties forming the generic set can be:

• assigned directly to the Aspect

• grouped in Blocks and then assigned to the Aspect via the Block. Note: the assignment of Blocks to Aspect is done via Block References 

If the connection of an Aspect to a Property or Block Reference is not needed anymore, the assignment can be deprecated using the Withdraw functionality.

The Withdraw functionality (Button Withdraw) groups together all these two options.

Withdraw Block Reference

This functionality allows users to deprecate (withdraw from usage) the connection between Block References and a specific Aspect. 

The starting point of this functionality can be the tabular view or the tree view, where the user can select the Aspect. In the next step, the user can select the Block Reference(s) to be withdrawn from the list of the Block References assigned to the selected Aspect. 

For the withdrawal of Block References, the graphical user interface consists of the details page of the Aspect and the list of Block References to be withdrawn.

The user may confirm the withdrawal by pressing button Save or Save and Release. 

On Save, a Change Request for the withdrawal of the Block References(s) will be created. Change Requests usually undergo an approval process before they are released and become effective. 

On Save and Release, the Change Request for the withdrawal of the Block References(s) will be automatically executed (released). As a result, the connection of the Aspect to the Block References is immediately deprecated and displayed grayed out.

Withdraw Property

This functionality allows users to deprecate (withdraw from usage) the connection between Properties and a specific Aspect.

The starting point of this functionality can be the tabular view or the tree view, where the user can select the Aspect. In the next step, the user can select the Properties to be withdrawn from the list of the Properties assigned to the selected Aspect.

For the withdrawal of Properties, the graphical user interface consists of the details page of the Aspect and the list of Properties to be withdrawn.

The user may confirm the withdrawal by pressing button Save or Save and Release.

On Save, a Change Request for the withdrawal of the Properties will be created. Change Requests usually undergo an approval process before they are released and become effective.

On Save and Release, the Change Request for the withdrawal of the Properties will be automatically executed (released). As a result, the connection of the Aspect to the Properties is immediately deprecated and displayed grayed out.

Create Range Constraint

This functionality is available in all classes lists (Application Classes, Blocks and Aspects). It allows users to define range (min/max) constraints for Integer (count) and Real (count) properties used within a Class. 

e.g. In case of cardinality structures used in the context of a specific Application Class, the customer wants to restrict the possible valuations of a block by defining a specific range (e.g. for a car, the number of doors can be for example minimum 2 and maximum 5). 

After pressing the button 'Create Range Constraint', the system displays the tree view of classes. Starting point for the creation of range constraints is a Property with datatype Integer (count) and Real (count). 

After selection of the Property the system displays the Create Range Constraint graphical user interface which consists of:

• the details page of the selected Property

• the details page of the Class in which the selected property is used 

• field for entering the Minimum Value for the Property

• field for entering the Maximum Value for the Property

After filling in the desired minimum and maximum Value and entering a Reason, the user may confirm the entered value range via button Save or Save and Release.

On Save, Change Request of type New Range Constraint will be created. Change Requests usually undergo an approval process before they are released and become effective. 

On Save and Release, the Change Request of type New Range Constraint will be automatically executed (released). As a result, the minimum and maximum values are displayed in brackets beside the name of the Property.

Manage Aspect Types

The workspace area for the management of Aspect Types can be accessed from Aspects tabular view via tollbar option Manage aspect types. Tabular view displays Aspect Types attributes e.g. ID, Dictionary, Preferred name, whether or not it is used.

This workspace offers users different functionalities described in brief in the following table as well as in more detail in the next chapters.

Toolbar in Tabular View

Create Aspect Type

In order to create an Aspect Type, user needs to select it and the select toolbar option Create. A create Aspect Type page opens and user needs to insert Preferred Name and Definition. Process is completed by selecting Save option. New created Aspect Type is immediately visible in Aspect Type tabular view.

Edit Aspect Type

In order to edit an Aspect Type, user needs to select it and the select toolbar option Edit. A edit Aspect Type page opens and user can change Preferred Name and Definition. Date of creation and Creator are also displayed grayed-out.

Process is completed by selecting Save option. Changes in edited Aspect Type are immediately visible in Aspect Type tabular view.

Delete Aspect Type

The functionality that allows users to delete existing Aspect Types is option Withdraw.

In order to delete an Aspect Type, user needs to select it and the select toolbar option Withdraw. A withdrawal Aspect Type page opens and user needs to start process by selecting Save option. After save option was selected, system informs user via console message that the selected Aspect Type is withdrawn and marked for deletion in next version.