You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Released: June 4, 2021 



UAF Features

2021x Refresh1 Version News#SysML Features

2021x Refresh1 Version News#Client-side Performance Improvements

2021x Refresh1 Version News#Teamwork Cloud-related Performance Improvements

2021x Refresh1 Version News#System Requirements

2021x Refresh1 Version News#Discontinued Products

2021x Refresh1 Version News#Modeling and Infrastructure

2021x Refresh1 Version News#Collaboration

2021x Refresh1 Version News#Other Features


SysML Features

Back to top

Client-side Performance Improvements

Partial Data Loading in Tables

Experience enhanced table loading and scrolling performance! Thanks to the newly-introduced Load Partially mode, data is now loaded in only visible rows. There is no longer a need to wait until data is calculated in the entire table. Additionally, fast scrolling has improved; it is now considerably smoother.

A chart comparing the opening time of Requirement Table having 7 standard columns with a different number of requirements.

Learn more about partial loading in tables >>

Increased Excel and CSV files Import Speed

The import performance of data from an Excel or CSV file into the modeling tool adds a great experience while managing a large scope of data. The data import time using the table sync feature is significantly faster compared with the previous version (19.0 SP4).  Also, the data import using the new Excel/CSV Import dialog is even better in comparison to Excel/CSV Sync feature. The import of 61k elements takes only 2 minutes (see the chart below).

A chart comparing data import from Excel and CSV files using the Excel/CSV Sync and Excel/CSV Import dialogs.

Common Operations

  • Copy/Paste. Now you can copy and paste data 2-4 times faster depending on the specific scenario. 

A chart comparing the copy&paste operation time in various scenarios.
  • Find. The search speed in all texts has increased by 70-150% compared to 19.0 SP4.
A chart comparing the Find operation speed in 19.0 SP4 and 2021x projects containing 1M, 2M, and 5M elements (including used projects).
  • Numbering. Creating the first numbered element, copying/pasting numbered elements, renumbering elements recursively, and updating the last element ID is now 30-840 times faster. 

A chart comparing the Numbering operations speed in 19.0 SP4 and 2021x projects containing 10M elements (including used projects).

  • Element Selection. Now you can search and select the needed elements (e.g., in the Select Element and Quick Find dialogs as well as drop-down lists) approximately 40-50 times faster.

A chart comparing the element selection speed in 19.0 SP4 and 2021x projects containing 5M elements (including used projects).
  • Validation. The active validation of the model now takes less than a second (0.8s after 5M project load and 0.5s after diagram load). 

A chart comparing the active validation speed after the project and diagram load in 19.0 SP4 and 2021x projects containing 5M elements (including used projects).

Profiling Changes in the UML 2.5.1 Metamodel

Significant changes have been implemented in the UML metamodel for improved performance. The InstanceSpecifications, Slots, and ValueSpecifications are no longer used to store profiling data. Instead, new model element types and properties are introduced, while some have been removed (see the diagram below). 

Profiling changes in the UML metamodel.

As shown in the figure above, Element references the TaggedValue that is used to specify the Boolean, Integer, Real, String, or Element values of the applied stereotype properties. This approach uses fewer model elements to store profiling data, which leads to a decrease in the total number of elements in SysML and UAF projects by 40-80%.

Note. Expressions based on the previously implemented profiling data storing metamodel no longer work, meaning that they have to be updated manually.


Back to top

Teamwork Cloud-related Performance Improvements

Project Merge

Project Merge has undergone considerable performance improvements. The modeling tool version 2021x requires approximately 4-5 times less memory to successfully merge two server project branches, compared to 19.0 SP4. 

A chart comparing merge memory consumption in different modeling tool versions.

Furthermore, the merge operation speed has increased by 20-70% in 2021x compared to 19.0 SP4. Both frequent (between close project versions) and infrequent (between distant project versions) merges can now be performed much faster!

Charts comparing merge performance in Speed and Memory modes.

TWC Project Load 

Project load memory and speed improvements have been implemented for Teamwork Cloud. The modeling tool now requires only 2GB of heap to load a 2M SysML project (first and second time) when working with TWC projects compared to 8GB in 19.0 SP4. Additionally, as a result of the UML metamodel changes, SysML projects are now opened 2-3 times faster.

Note. Received results cover the project load only, excluding validation, diagramming, and further modeling tool feature usage.

Charts comparing project load memory and speed improvements between different modeling tool versions.
  • Three projects (sizes ranging from 1M to 2M) in 19.0 SP4 and the same projects in 2021x (sizes ranging from 750k to 1M) were used to run the tests.
  • Migration time is excluded because projects that had already been migrated were used for testing.

TWC Save to Local 

In 2021x, great attention is paid to the memory consumption improvements. Saving a Teamwork Cloud project locally now requires less memory. For example, a 2M SysML project now consumes only 4GB of RAM, compared to 20GB in 19.0 SP4. 

A chart comparing memory consumption when saving a TWC project as a local one between different modeling tool versions.

Back to top

System Requirements

Back to Top


Modeling and Infrastructure

Back to Top

Back to Top

Collaboration

Back to Top

Other Features

Report Wizard

Back to Top

Key issues fixed
  • The issues concerning the All Views report have been fixed. The matrices and Producing/Consuming OperationalActivities/Functions are now included.
  • The issue where the PartProperty stereotype instead of ReferenceProperty stereotype was applied for the role when the Aggregation relation is created has been fixed.
  • The additional stereotype is no longer applied for the element with custom stereotypes after migration from UPDM2 to UAF.
  • [UPDM2] The issue where redundant Block stereotypes were applied for specific Environment elements has been fixed. Now only Value Type is applied for Condition, Climate, and LightCondition elements in SysML Compliance mode.
  • [UPDM2] The validation rule COR2071 no longer fails in a valid situation.
  • [UPDM2] The issue where incorrect metaclass element is created with Impelemnts stereotype applied when solving validation rules COM2023 and COM2047. Now the Abstract relation with the «Implements» stereotype is created.
  • A resources tag value of Call Activity now is set when the BPMN compliance mode is ON.
  • The issue where Operational Object Flow was not keeping project settings when BPMN compliance mode is ON has been fixed.

Version news of servers and plugins

Cameo Enterprise Architecture documentation

News of earlier versions