In this version, we continued improving the performance with a major focus on compliance mode, reports, and UAF metrics.
Compliance Modes
Turning on the BPMN or SysML compliance modes in large projects now takes less time than in earlier versions.
Feature
2021x
2021x Refresh 1
BPMN Compliance Mode (UAF)
> 60 min
9 min 27s
SysML Compliance Mode (UPDM)
> 60 min
3 min
Image Removed
Report
The report generation was optimized so it takes less time for large projects. In the optimization process, the tables, matrices, and relation maps were excluded from the scope of the Used in Diagrams column. MS Word supports files only up to 512 MB, therefore we do not recommend generating a report with the entire project as its scope.
The following table shows the testing, performed with the scope of ~ 5000 elements, results.
Feature
2021x Refresh 1
All views report (XL project)
5 min 30s
Dictionary report
31s
Summary and Overview report
15s
Dictionary Excel Spreadsheet
2 min 11s
UAF Metrics
The metrics calculation was also optimized and runs smoothly in the larger projects. However, we do not recommend selecting the entire project as a scope for calculating metrics.
The following table shows the testing, performed with the scope of ~ 5000 elements, results.
Feature
2021x
2021x Refresh 1
UAF metrics (1M)
Low memory
21.719 s
UAF metrics (10M)
Low memory
190.35 s
UPDM2 metrics (1M)
Low memory
42.564 s
UPDM2 metrics (10M)
Low memory
56.109 s
Diagrams and Tables
The Hierarchical Typical Measurements tables were enhanced and no longer hold the status of technology preview. New hierarchical display modes were implemented. You can also generate predefined reports for these tables. Also, having the Hierarchical Typical Measurements table filled out makes it easy to create the Hierarchical Actual Measurements table by simply clicking the Evaluate Measurements button. Learn more >>
The Hierarchical Actual Measurements tables are available for all domains. The hierarchical table for actual measurements allows working with the actual measurements directly in the table. You can add new or existing Actual Property Sets and define values. When you add a Property Set to the table, all existing Actual Property Sets will be collected recursively according to the defined scope. Learn more >>
TheActualProjectMilestone SummaryTable (Pj-Rm) depicts all actual project milestones in the model. Adding the actual project milestones into the table allows you to see their name, kind, start date, project, project status, version released, version withdrawn, and actual resource information. You will also be able to add or modify the actual project milestone information directly in this table.Learn more >>
If you need to see the original name, set the Show Original Name of Measurement symbol property to true. The original name will be displayed in brackets and in gray font. Learn more >>
You can create a Model Library package for each UAF domain.
A new system property is implemented to help with the migration of server projects. There are two cases regarding the migration of UAF and UPDM projects:
If you are performing UPDM project migration from the modeling tool with the UPDM environment, only the project version will be migrated.
The UPDM project migration from the modeling tool with the UAF environment will not be performed. However, if you want to migrate the UPDM project to UAF, you need to open the magicdraw.properties (or cea.properties) file and change the value of the system property -Dmigrate.project.from.updm2.to.uaf\=false to True. By default, the value of this property is False, which means that your UPDM projects will not be migrated. Learn more >>
ArchiMate Model Import (Technology Preview)
In this version, the import of the ArchiMate model from the open exchange file into the UAF project is implemented. As it is only a technology preview for this version, the imported element mapping is only partial. The mapping of ArchiMate 3.1 to UAF 1.1 approach is based on the NATO Architecture Framework.
You can now keep your Internal Block diagram (IBD) consistent with Activities with less effort! Our brand new behavior-to-structure synchronization allows you to validate Part Properties in an IBD to check whether Proxy Ports exist and are typed by compatible Interface Blocks based on flows found in Activities. As a result, instead of manually updating IBDs to be consistent with Activities, coherence between them is ensured by automatically detecting inconsistencies and providing the user with the solvers to handle each inconsistency individually.
Contextual Relationships have undergone major improvements! From now on, you can create contextual relationships directly in structure tree view tables and represent data in table columns by considering the usage context of the row elements.
Image Removed
Creating contextual relationships in tables.
Additionally, for a more compact Internal Block Diagram (IBD) view, you can now represent contextual relationships in the Element Properties compartment of the element shape.
Image Removed
Displaying contextual relationships in the element compartment.
In earlier versions, the Show Parts filter was hard to use in larger projects: only a limited list of connectors was visible; and identifying the connectors was difficult in some cases. This version brings enhancements that will allow easy searching, identification, and selection of all connectors outgoing from the parts. Using this dialog, you can easily filter connectors and choose which ones should be displayed in the table or hidden from it. Learn more >>
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.
Image Removed
A chart comparing the opening time of Requirement Table having 7 standard columns with a different number of requirements.
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).
Image Removed
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.
Image Removed
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. Image Removed
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.
Image Removed
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.
Image Removed
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).
Image Removed
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).
Image Removed
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.
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.
Image Removed
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!
Image Removed
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.
Image Removed
Image Removed
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.
Image Removed
A chart comparing memory consumption when saving a TWC project as a local one between different modeling tool versions.
The 2021x Refresh1 release introduces further performance and scalability upgrades in key product areas: compatibility modes, report generation, metrics calculation, integration, general modeling, and collaboration improvements. Furthermore, new tables and usability improvements are here to make your modeling experience better. Additionally, this version introduces a technology preview of ArchiMate model import.
This release also comes with Behavior to Structure synchronization, Contextual Relationships enhancements, and other improvements.
Collaborative modeling has been extended to assess the impact of element modification or deletion in other projects an element is used in, enable users to conveniently organize projects into the nested categories, customize the representation of Teamwork Cloud users in the modeling tool, and quickly return to the Merge dialog to change the merge decisions.
The version and Hot Fix number of a modeling tool and its plugins must be the same. After installing the Hot Fix version of a modeling tool, select the same Hot Fix version when downloading its plugins. The modeling tool will not work correctly if you install plugins of a different version and/or Hot Fix number.
In this version, we continued improving the performance with a major focus on compliance mode, reports, and UAF metrics.
Compliance Modes
Turning on the BPMN or SysML compliance modes in large projects now takes less time than in earlier versions.
Feature
2021x
2021x Refresh 1
BPMN Compliance Mode (UAF)
> 60 min
9 min 27s
SysML Compliance Mode (UPDM)
> 60 min
3 min
Image Added
Report
The report generation was optimized so it takes less time for large projects. In the optimization process, the tables, matrices, and relation maps were excluded from the scope of the Used in Diagrams column. MS Word supports files only up to 512 MB, therefore we do not recommend generating a report with the entire project as its scope.
The following table shows the testing, performed with the scope of ~ 5000 elements, results.
Feature
2021x Refresh 1
All views report (XL project)
5 min 30s
Dictionary report
31s
Summary and Overview report
15s
Dictionary Excel Spreadsheet
2 min 11s
UAF Metrics
The metrics calculation was also optimized and runs smoothly in the larger projects. However, we do not recommend selecting the entire project as a scope for calculating metrics.
The following table shows the testing, performed with the scope of ~ 5000 elements, results.
Feature
2021x
2021x Refresh 1
UAF metrics (1M)
Low memory
21.719 s
UAF metrics (10M)
Low memory
190.35 s
UPDM2 metrics (1M)
Low memory
42.564 s
UPDM2 metrics (10M)
Low memory
56.109 s
Diagrams and Tables
The Hierarchical Typical Measurements tables were enhanced and no longer hold the status of technology preview. New hierarchical display modes were implemented. You can also generate predefined reports for these tables. Also, having the Hierarchical Typical Measurements table filled out makes it easy to create the Hierarchical Actual Measurements table by simply clicking the Evaluate Measurements button. Learn more >>
The Hierarchical Actual Measurements tables are available for all domains. The hierarchical table for actual measurements allows working with the actual measurements directly in the table. You can add new or existing Actual Property Sets and define values. When you add a Property Set to the table, all existing Actual Property Sets will be collected recursively according to the defined scope. Learn more >>
TheActualProjectMilestone SummaryTable (Pj-Rm) depicts all actual project milestones in the model. Adding the actual project milestones into the table allows you to see their name, kind, start date, project, project status, version released, version withdrawn, and actual resource information. You will also be able to add or modify the actual project milestone information directly in this table.Learn more >>
If you need to see the original name, set the Show Original Name of Measurement symbol property to true. The original name will be displayed in brackets and in gray font. Learn more >>
You can create a Model Library package for each UAF domain.
A new system property is implemented to help with the migration of server projects. There are two cases regarding the migration of UAF and UPDM projects:
If you are performing UPDM project migration from the modeling tool with the UPDM environment, only the project version will be migrated.
The UPDM project migration from the modeling tool with the UAF environment will not be performed. However, if you want to migrate the UPDM project to UAF, you need to open the magicdraw.properties (or cea.properties) file and change the value of the system property -Dmigrate.project.from.updm2.to.uaf\=false to True. By default, the value of this property is False, which means that your UPDM projects will not be migrated. Learn more >>
ArchiMate Model Import (Technology Preview)
In this version, the import of the ArchiMate model from the open exchange file into the UAF project is implemented. As it is only a technology preview for this version, the imported element mapping is only partial. The mapping of ArchiMate 3.1 to UAF 1.1 approach is based on the NATO Architecture Framework.
You can now keep your Internal Block diagram (IBD) consistent with Activities with less effort! Our brand new behavior-to-structure synchronization allows you to validate Part Properties in an IBD to check whether Proxy Ports exist and are typed by compatible Interface Blocks based on flows found in Activities. As a result, instead of manually updating IBDs to be consistent with Activities, coherence between them is ensured by automatically detecting inconsistencies and providing the user with the solvers to handle each inconsistency individually.
Contextual Relationships have undergone major improvements! From now on, you can create contextual relationships directly in structure tree view tables and represent data in table columns by considering the usage context of the row elements.
Image Added
Creating contextual relationships in tables.
Additionally, for a more compact Internal Block Diagram (IBD) view, you can now represent contextual relationships in the Element Properties compartment of the element shape.
Image Added
Displaying contextual relationships in the element compartment.
In earlier versions, the Show Parts filter was hard to use in larger projects: only a limited list of connectors was visible; and identifying the connectors was difficult in some cases. This version brings enhancements that will allow easy searching, identification, and selection of all connectors outgoing from the parts. Using this dialog, you can easily filter connectors and choose which ones should be displayed in the table or hidden from it. Learn more >>
Numbering validation. Project opening now takes less time as a result of boosting numbering validation efficiency. Image Added
A chart comparing the project opening speed in 2021x and 2021x Refresh1 SysML projects with 0.5M, 1M, 2M, and 5M elements.
Anchor
element selection
element selection
Element selection. Further improvements have been introduced to element selection (i.e., the Select Element dialog and drop-down lists) performance. The stereotyped element search is now performed approximately 20-200 times faster.
Anchor
import from another project
import from another project
Import from another project. Projects can be imported much faster as the import operation now works more like Copy/Paste rather than Merge.
Image Added
A chart comparing the sample project import speed in 2021x and 2021x Refresh1 SysML projects with 0.5M and 1M elements.
Anchor
Time consumption on large server projects
Time consumption on large server projects
Time consumption on large server projects. Report Wizard now utilizes significantly less time on large server projects using the Web Publisher 2.0 template, in comparison with the 2021x version.Image Added
A chart displaying the results of performance testing between SysML project 5M and 10M sizes in the whole elements scope.
Anchor
ignoring smart package calculation in tables and matrices
ignoring smart package calculation in tables and matrices
Ignoring Smart Package Calculation in Tables and Matrices. Depending on the complexity and the total number of Smart Packages within the specified scope in tables and matrices, significant performance degradation can be caused while building tables and matrices. Since the 2021x Refresh1, the inner Smart Packages are no longer calculated by default unless you turn on theInclude Additional Content option. Consequently, tables and matrices are now built faster. Image Added
The contents of a Smart Package that falls within the specified scope is excluded when building a table.
Anchor
freezing smart package contents
freezing smart package contents
Refreshing Smart Package contents on demand. You can now suspend the automatic Smart Package contents recalculation in the background to enhance performance by simply changing the Smart Package state to Frozen. As a result, elements are no longer automatically added to the Smart Package contents; however, the dynamic contents can still be refreshed on demand by clicking the button.
Four SysML projects in 2021x that were used to run the performance tests, ranging from 0.5M to 5M in size, are equal in size to projects of earlier versions with sizes ranging from 1M to 10M.
Import variability data to your modeling tool project directly from the 3DS ENOVIA Model Definition application on the 3DEXPERIENCE platform. The 3DEXPERIENCE ENOVIA Model Definition Integration plugin is available for your modeling tool (together with the Product Line Engineering plugin).
Tree View in Select Element Drop-Downs and Quick Find
Quick Find and Type Selection drop-downs have been enhanced with the Tree view. In cases when multiple elements share the same name, it will no longer be confusing as to which one to select: all you need to do is switch to the Tree view to identify the element's place in the model hierarchy.
Image Added
Switching between the Tree and List views to find the needed element faster.
Anchor
Other Feature Improvements
Other Feature Improvements
Other improvements
The 3DEXPERIENCE menu item groups all available integrations with the 3DEXPERIENCE platform. When you install plugins that support integration with the platform, all their available functionalities will be added under the 3DEXPERIENCE menu. Learn more about authentication with the 3DEXPERIENCE platform >> Image Added
Since the UsageInDiagrams Opaque Behavior is a time-consuming operation (it loads all diagrams - matrices, tables, and maps), it has been deprecated and replaced with the UsageInDiagramsWithSymbols Opaque Behavior that searches for symbol usages only. Learn more about built-in operations >>
The following key issues have been fixed with this version:
Improved performance - Smart Packages that fall within the tracking scope are no longer automatically calculated when the Suspect Links > Show Suspicions command is executed.
The problem with Java sign-in is solved and the modeling tool now launches on macOS Big Sur without warnings.
The project update no longer fails when the standard profile has no internal version specified.
The modeling tool no longer becomes unresponsive when the element search is in progress.
The diagram is no longer scaled incorrectly on mouse click/drag.
The filtered changes are now accepted/rejected recursively when performing the merge operation.
The information in structured expression queries is properly updated when adding projects to Teamwork Cloud.
The element refactoring no longer fails when the Legend item is applied.
The applied Legend item adornments are no longer removed after saving a Teamwork Cloud project locally.
The Diagram Info box in the diagram no longer changes its position after performing the merge operation.
Action pins no longer remain synced to Activity when the action behavior is unset.
Associations are no longer moved when centering Classes vertically.
The modeling tool no longer freezes when publishing large projects to Teamwork Cloud.
When two different custom prefixes are applied for two different sets of elements, the element renumbering no longer works incorrectly for the set of elements with one custom prefix.
CSV Import Plugin support will be discontinued from the next major version. Excel/CSV Sync or Excel/CSV Import features will be replacing the CSV Import Plugin.
No more accidental Recovered Elements and unexpected surprises when updating Used Project versions! The latest release introduces the global element usage search functionality that allows you to query for the usages of the element you are about to modify or delete. Depending on the server-side configuration, projects using the element in question can be returned either from the entire Teamwork Cloud repository or the chosen custom indexed scope.
Image Added
Searching for element usages within the Teamwork Cloud repository.
Do your projects need to be grouped hierarchically? Are you seeking to organize them in a folder-like manner? We have a solution! You can now organize your projects into nested categories so you can find them later with no difficulty.
Image Added
Organizing server projects into nested categories.
Representation of Teamwork Cloud Users
You now have the freedom to customize how individual Teamwork Cloud users are represented in the modeling tool (for example, when they lock elements) by simply changing the value of the Representation of Users environment option. It is your choice whether a User Name, a Full Name, or an Email address is shown to identify them.
Image Added
Changing the user representation in the Teamwork Cloud project.
Need to make some adjustments after finishing the merge operation? Not a problem! You can now quickly return to the previously performed merge operation if you notice that you have accepted or rejected the changes (e.g., rejected the element creation) by mistake and need to change your merge decisions.
Image Added
Returning to the Merge dialog to change merge decisions.
Filters in the Merge dialog have been redesigned to improve the user experience.
Updating a server project with local changes in disconnected team collaboration now handles the Used Project branch deletions more effectively, with no errors.
Groovy Tool now supports use of relative paths, apart from Groovy file names and absolute paths, starting from the template to the Groovy file. Learn how to deploy this feature >>
Report Wizard 2021x Refresh1 allows specifying DPIs of images in generated reports at three levels: global, template, and object. Learn more about this helpful function >>
An increasingly effective utility of the Presentation Report Designer diagram has been ultimately designed for designing and generating PPTX and ODP templates. Discover Presentation Report Designer more >>
With $report.getMetaClass($element), you are able to acquire a metaclass from a specific stereotype element. Learn about this function more >>
You can now use both the relative and absolute paths of the image file on your system to display it as a homepage image by utilizing the HomeImage variable of the Web Publisher 2.0 template. Know more about how this function works >>
The exported image scaling option for Web Publisher 2.0 reports has become available in Report Wizard 2021x Refresh1, so that you can reduce, maintain, and enlarge the image size percentage. Find out how to make use of this option >>
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.
