Example

The following diagram shows the elements defined in a package with a variety of "BrowserOrder" tagged values to illustrate the use of eaUtils Sort By Tagged Value feature.

Using the BrowserOrder or a custom tagged value to sort elements (eaUtils settings)

This feature uses the dedicated Tagged Value BrowserOrder value to sort elements within a package or element. eaUtils settings lets you define a different Tagged Value other than "BrowserOrder" if needed.

Sort elements within a package by tagged value (BrowserOrder)

Option 1: default settings

Right click in the Project Browser on the package where elements need to be sorted > Extensions > eaUtils > [Browser] Sort elements.

In the following dialog window, select Tagged Value as the sorting option and confirm that you would like to proceed with the default 'BrowserOrder' tag.

Note: eaUtils sort by settings are displayed. The settings can be opened and modified if needed.

Once the sorting is complete, the following confirmation is displayed:

The expected result is illustrated below (note that the option "Identify and sort integers within string values" is enabled by default).

The new sorting order is visible in Enterprise Architect project browser as illustrated below:

Option 2: "Identify and sort integers within string values" setting disabled

When the option "Identify and sort integers within string values" is disabled in eaUtils settings, there is no attempt to extract integer values and sort them accordingly. Based on the previous data set, this option will impact requirements with REQx values:

• The expected order for the requirements is REQ-02, REQ-1, REQ-100, REQ-25, REQ-5, REQ-60-TEST, REQ-9-TEST, whereas the previous result with this option enabled by default was REQ-1, REQ-02, REQ-5, REQ-25, REQ-100, REQ-9-TEST.

Option 3: Use the Case Sensitive Value setting

eaUtils can be case sensitive as managed in eaUtils Settings.

This can be useful when you need to treat values like "Requirement1, requirement2, REQUIREMENT3, requirement4, Requirement5" as within the same list or not. If you make eaUtils case sensitive, the previous list will be sorted based on 3 groups, requirement, Requirement, REQUIREMENT: "requirement2, requirement4, Requirement1, Requirement5, REQUIREMENT3".

Option 4: Sort numbering sequences setting

The following diagram illustrates a package with requirements that need to be sorted based on the BrowserOrder tagged values using eaUtils Sort numbering sequences option: 1.1, 1.10, 1.11, 2.1...

When enabled, this option leads to the following result in the project browser:

Option 5: sort sub elements

eaUtils process sub elements sorting setting is available so that not only elements within the selected package are sorted, but also elements placed within elements of that package i.e. sub elements.

With the current example model, running the sort by tagged value with the sub elements setting enabled makes it possible to sort elements within the selected package, as well the elements within the composite use case (Use Case0), illustrated in the next section.

Sort elements within an element by tagged value BrowserOrder

When an element contains sub-elements, e.g. a UML activity or use case contains activities, nodes, etc., these elements can be sorted with eaUtils addin.

Option 1: default settings

Right click in the Project Browser on the element with embedded elements to be sorted > Extensions > eaUtils > [Browser] Sort elements.

In the following dialog window, select Tagged Value as the sorting option and confirm that you would like to proceed.

The expected result is illustrated below (note that the option "Identify and sort integers within string values" is enabled by default).

Once confirmed, the elements are sorted in the selected element as illustrated below, matching the above expected results:

Option 2: "Identify and sort integers within string values" setting disabled

When the option "Identify and sort integers within string values" is disabled in eaUtils settings, there is no attempt to extract integer values and sort them accordingly.

The expected result is illustrated below.

Once confirmed, the elements are sorted in the composite element as illustrated below, matching the above expected results: