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

Compare with Current View Page History

« Previous Version 13 Next »


Magic Systems of Systems Architect

Planned released: February 12, 2021


This release introduces significant performance and scalability upgrades in key product areas: migration, converting between frameworks, building matrices, Merge, Teamwork Cloud project load, Teamwork Cloud project saving, table loading, Excel and CSV files import, and such common modeling tool operations as Copy/Paste, Find, Numbering, Element Selection, and Validation. Additionally, this version adds support for the UAF 1.1 Profile, new diagrams and tables, and a number of usability and traceability improvements.

The released version is also packed with a few improvements that extended the usage of Simulink import and Modelica export. We introduce the new SysML 1.6 specification support, including new concepts such as Conjugated Interface Block, «AddFlowPropertyValueOnNestedPortAction» stereotype, additional Binding Connector notation, renamed compartments, enumerations, and more. 

Version 2021x adds the ability to use layers in diagrams, automatically create legends, present diagrams or predefined sequences of diagrams in full screen to stakeholders, create compositions and aggregations in matrices, and use predefined element type filters when searching for the necessary model elements. Additionally, the Excel/CSV file import functionality has been reviewed and refreshed, and numerous improvements to Excel/CSV synchronization functionality in tables have been added.

Last but not least, project merge has been extended to give users the option to show only the changes in directly modified diagrams, hide Target and Equivalent Changes by default, and choose a specific ancestor calculation algorithm depending on merge scenario and expected outcome. 


UAF Features

SysML Features

2021x LTR Version News


Modeling and Infrastructure

Collaboration

Other Features

Performance Improvements in UAF

In this version, projects containing 1, 5, and 10 million elements were tested in both UPDM and UAF scopes. After receiving the results, improvements in migration, converting between frameworks, and building matrices were made for better performance.

Migration

The migration from UPDM2 to UAF 1.1 and from UAF 1.0 to UAF1.1 has been optimized and takes less time than in earlier versions. 

The comparison of migration time depending on the project size

Converting between frameworks

The conversion between frameworks has been optimized. The following table shows the results of converting a project containing approximately 2 million elements and hundreds of framework packages, which needed to be moved or renamed:

Earlier versions

2021x version

The modeling tool stops responding after 30 min~ 1 hour


Building matrices

The scope for predefined matrices is no longer set by default. Now all matrices will start to build after the row and column scope is selected (https://jira.nomagic.com/browse/UPDM-11385)

Earlier versions

2021x version

Load predefined matrices in the projects with 10 million elements:

~ 1-3 hours. Sometimes more.

Create a new matrix:

   instantly (~1-2s)

Methods and Standards


UAF 1.1 Profile Support

Beginning with this version, the UAF 1.1 profile is supported. Therefore the following migrations will be necessary:

Evolution of standards


Diagrams and Tables
  • New Actual Enterprise Phases Gantt Chart shows how actual enterprise phases change over time. Learn more >>
  • New Date and Time Summary Tabledepicts all dates and times specified in the ISO8601 date-time format. Learn more >>
  • New Personnel Forecast, Resources Forecast, and Standards Roadmap diagrams are implemented, improving the way they are created and used. The Personnel Forecast, Resources Forecast, and Standards Roadmap diagrams created with earlier versions of the modeling tool will be marked as deprecated and will be available only for review purposes.
  • The Deployment diagram has been enhanced. The Strategic Deployment table is renamed the Strategic Actual Deployment table and you can now create it using an Actual Resources Deployment Creation Wizard. Moreover, the Deployment Milestones wizard is renamed the Actual Resources Deployment Wizard and enhanced. Learn more >>
    • A technology preview of the Hierarchical Measurements table. Please note that if you open a project created with earlier versions, the Measurement tables of those projects will be empty. However, you can create them anew.
Usability Improvements
  • The new Personnel Gantt Chart property Display Actual Persons in Different Lines was implemented. Now you can choose to see each Actual Person in separate lines.

  • In the Gantt chart Options area, you can choose to mark a required period of time. One of the following Marking Modes are available:

    • None. Nothing will be marked.
    • Period of Time. Choose to mark a period of time. For this mode, you can select the Start and End dates to be marked.
    • Period of Actual Enterprise Phase. Choose to mark a period of the Actual Enterprise Phase. The time frame will be marked according to the Start and End dates set for the selected Actual Enterprise Phase.

  • The Create Association on Part Creation project option is set to True. This means that when you create parts in the Part compartment of the Resource and Operational performers, the appropriate association is also created in the model.

  • A new Symbol property Show Measurements Inherited Name allows you to display the inherited measurements name through the dot notation when the Property Set is applied as a type.
Traceability Improvements

The Implementation matrices have been enhanced. Now, by default, the traceability is shown according to the following criteria:

  • Mapping Using Milestone (Actual Resources and Resources)
  • Mapping Using Milestone (Resources Performers)
  • Mapping Using Milestone (Service Specification)
  • Mapping Using Milestone (Actual Resources)

You may hide some mapping rules from a Matrix by changing the Dependency criteria in the Specification window.

Learn more about working with the implementation matrices >>

Other
  • The new version of the UJTL version (20200115) is now available. You can choose the library version when creating a new project.

  • When an old project (UAF 1.0 or UPDM2) is opened with the latest version (UAF plugin), stereotypes for nonDSL'ed associations should be applied:

    • when the association is between OperationalAgent, the <<OperationalAssociation>> stereotype is applied. 
    • when the association is between ResourcePerformer, the <<ResourceAssociation>> stereotype is applied.  
  • Operational Signal/Resources Signal now applies automatically for the DSL'ed signal.
  • The derived properties of ActualResponsibleResources, ActualOrganization, ActualPost, and ActualPerson were renamed: 
    • ownsActualProject renamed to managesActualProject, 
    • responsibleForActualResponsibility renamed to ownsActualResponsibility, 
    • responsibleForActualProjectMilestones, 
    • responsibleForActualResponsibility renamed to managesActualResponsibility.

  • When working with the predefined matrices, you can make some changes to the default settings, such as changing the row or columns element type, dependency criteria, or directions. You can restore the following settings to default at any time:

    • Description
    • Direction
    • Dependency Criteria
    • Show Elements
    • Column Element Type
    • Row Element Type
    Learn more about working with matrices >>>
  • New system options are implemented. One is for setting the default plugin and the other to display which plugin is installed. Learn more >>

Back to Top

SysML Features

Proxy Ports in FMU and Simulink import

FMU and Simulink import now support Proxy Port creation. Once you have imported the external FMU/Simulink model, you can select the Proxy Port to be created in your model and then specify an existing or create a new Interface Block to be used as its type.

Selecting the Proxy Port and an Interface Block upon the external model import.

Learn more about FMU and Simulink import >>

Simulink model import to Activities

You can import the Simulink model by dragging and dropping the Simulink file (*.slx) directly onto the Activity diagram. The Activity (stereotyped by «SimulinkBlock») which is assigned as behavior for the Call Behavior Action and its Input and/or Output Pins are created in the model. 

Simulink import to Activity diagram.


Learn more about Simulink import >>

Simulink composite signals export 

You can now select how to export Proxy Port or Interface Block with multiple Flow Properties (composite signals): as bus Creators/Selectors or as bus In/Out ports. 

Learn more about Simulink export  >>

IBD-based selective Modelica export

You can now use the Internal Block Diagram to select what to export to Modelica. Only parts, ports, and connectors appearing in this diagram are exported, rather than the entire model. See whole vs partial export comparison in the image below.

The difference between whole (exporting Block) and partial (exporting IBD) export to the Modelica file.

Learn more about Modelica export >>

SysML 1.6 support

As of version 2021x the SysML Plugin supports the SysML 1.6 specification which brings the following improvements:

  • One more way to model conjugated ports is to create the Conjugated Interface Block which has the same features as its original Interface Block except that its Directed Features and Flow Properties are reversed (conjugated). Learn more about Conjugated Interface Block >>
  • The ability to change the Binding Connector notation keyword from "equal" to sign "=". Learn how to create Binding Connector >>
  • The new stereotype «AddFlowPropertyValueOnNestedPortAction» is created which enables values added to a flow property to propagate out through a specified behavioral port of an object executing the action, rather than all behavior ports exposing the flow property. It also enables values added to a flow property to propagate into objects.
  • The AdjunctProperty principal type is changed from Element to NamedElement.
  • The «PropertySpecificType» stereotype is renamed to «pst».
  • The Value Type compartment attributes is renamed to properties.
  • The initialValue compartment is renamed to initial values.
  • The signal receptions compartment is renamed to receptions.
  • The FlowDirection, FeatureDirection and ControlValue enumerations are renamed to FlowDirectionKind, FeatureDirectionKind and ControlValueKind respectively.

Learn more about SysML 1.6 support >>

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

TWC-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

RAM and disk space requirements have been updated taking into consideration different sizes of large models. Learn more about recommended system requirements >>

Project Elements Count
(including used projects)

Allocated Memory2

Disk Space
Earlier versions2021x and later1
1.5 million1 million6GB6GB
2.5 million2 million7GB10GB
5 million3.5 million11GB30GB
1 the project elements count is different due to the profiling data storing metamodel optimized in 2021x. 
  2 these memory requirements are indicative and may vary by project specifics.

Back to Top

Modeling and Infrastructure

Layers Based on Legends

Diagrams can get extremely crowded as a model evolves. For example, when highlighting a chosen piece of information, only one specific aspect of the system becomes a challenge. For your convenience, you can now filter diagrams by the selected Legend items to make only the necessary diagram layers stand out.

Filtering the diagram by the selected Legend item.

Learn more about layers based on Legends >>

Intelligent Legend Creation

Do you feel that Legend creation is a tiresome activity? Not at all! From now on, you can create Legends more easily than ever before: extract them automatically from the elements displayed on your diagram instead of relying on a manual creation. Additionally, you can now automatically extract Legend items for the existing Legends. Once the Legend items are created, you can customize their adornments representation. They can now be displayed as rectangular shapes or extended lines to represent paths and shapes in greater detail.

Extracting the Port Types legend according to the elements displayed on the diagram as symbols. 

Learn more about extracting Legends >>

Presentation Mode

You can now present diagrams in full screen without showing user interface components, such as a model browser, diagram palette, status bar, and toolbars. That is not all! You can also define the sequence of diagrams to present one after another.  

Diagram in the enabled Presentation Mode.

Learn more about Presentation Mode >>

Renewed Excel/CSV File Import

You can import data from an Excel/CSV file directly to the model without installing Excel and CSV Import Plugins (read more about discontinued products). From now on, the newly created Excel/CSV Import dialog brings an easy to use and clearly understandable graphical user interface. It allows you to import content with just a few clicks by selecting the Excel/CSV file and specifying element mapping options. Additionally, you can save your maps to reuse them, collect saved maps in groups, manage those groups, and use an entire group instead of a single map for data import. 

The Excel/CSV Import dialog with specified options for satisfy relationship import.

Learn more about Excel/CSV file import >>

Extended Excel and CSV Sync

Three improvements expanded the data synchronization between Excel or CSV files and a model:

  • Unique elements. Elements to be synchronized can now be identified not only by their name, but also by element property or tag value.
  • Direct relationships. From now on, you can import direct relationships between the source and target elements as easily as other elements.
  • Relationship ends. When importing relationships between different elements, you can select a specific property or tag to identify the source and target end of the relationship.

New mapping options in the Excel/CSV Sync Options dialog: Identification Property, Identify Relationship (end) Source by, Identify Relationship (end) Target by.

Learn more about Excel/CSV Sync in tables >>

Composition and Aggregation Relationships in Dependency Matrix

You can now define relationships between the elements in your model more accurately! The latest release gives you the ability to create and display Composition and Aggregation relationships in a Dependency Matrix.

Creating and displaying Composition, Aggregation, and Association in a Dependency Matrix.

Learn more about Composition and Aggregation creation >>

Other Improvements

  • Applying Legend items to the same element is more convenient since they are now grouped by Legend.

  • A reference from the image shape to the attached image is now created when attached images are displayed as diagram shapes.

  • The Diagram Tabs Limit is set to 20 to prevent high memory utilization. You can change this environment option at any time. 

  • The smart autocompletion command Ctrl + Space now works for the Change Event expression in a State Machine diagram.

  • In the Select Element and Quick Find dialogs, elements can now be filtered by their types to narrow down search results. 

  • The Jython 2.7.2 version is now supported.
  • The MARTE Profile version 1.2 is now supported. 
  • The Reader Edition is now available for all the 2021x version modeling tools. Contact your sales executive to request the license.

Back to Top

Discontinued Products

  • The development of the following plugins is discontinued:

    • Document Modeling Plugin (Model-based reports). For more effective model publishing and reviewing on the web, use Cameo Collaborator.
      • To create Views and Viewpoints diagrams using the modeling tool with no plugins installed, use the Cameo Collaborator Publisher plugin or  the SysML plugin instead. 
      • The DockBook Library Profile is no longer available. 
    • Methodology Wizard Plugin.
    • QVT Plugin.
    • Excel Import Plugin. We highly recommend using Excel/CSV Sync or Excel/CSV Import features instead.
    • CSV Import Plugin. We highly recommend using Excel/CSV Sync or Excel/CSV Import features instead.
    • LieberLieber Embedded Engineer plugin.
    • Project Element Counter plugin.
    • MBSE plugin.
  • Web portal reports are no longer available. For more effective model publishing and reviewing on the web, use Cameo Collaborator. You can also use Web Publisher (Simple HTML) or Web Publisher 2.0 ReportWizard templates to generate HTML reports.
  • WSDL Code Engineering and WSDL diagrams are no longer available.
  • C# Code Engineering and C# Professional Edition are no longer available.
  • CIL and CIL Disassembler Code Engineering are no longer available.

  • The News Reader (RSS) is no longer available. The notification at the right bottom corner of the modeling tool will inform you about the new version release instead.

  • The no_install_mac.zip and 32-bit installation files are no longer offered for download.
  • The Project Usage Map Profile is no longer available. 
  • The JavaScript Nashorn is deprecated with the intention of removing it. We highly recommend using JavaScript Rhino instead.  
  • The following 3rd party plugins are discontinued:
    • Cameo Workbench
    • Cameo Inter-Op
    • ParaMagic Lite
  • The following no cost plugins are no longer available in modeling tools:

From Teamwork Server to Teamwork Cloud

Teamwork Server is no longer supported in the latest release. Teamwork Cloud should be used as a product for collaborative modeling and model version control. Customers still using Teamwork Server must migrate their server projects to TWC 19.0 series first and then upgrade to TWC 2021x.

Learn how to migrate from Teamwork Server to Teamwork Cloud >>

From Cameo Collaborator for Alfresco to Cameo Collaborator for Teamwork Cloud

From version 2021x, Cameo Collaborator for Alfresco is no longer supported. We recommend using Cameo Collaborator for Teamwork Cloud instead.

Learn the benefits of Cameo Collaborator for Teamwork Cloud compared to Cameo Collaborator for Alfresco >>

Learn how to migrate your documents and comments from the Alfresco server to Teamwork Cloud >>


Back to Top

Collaboration

Detecting Changes in Diagrams During Merge

You can now specify in the Environment Options dialog whether to compare only the direct or all the changes in diagrams during the Project Merge and Project Comparison operations. By default, only the changes made by the user in loaded (open) diagrams are analyzed, leaving out unintentional diagram changes that occurred due to indirect changes in the model. This feature not only eases both merge and project comparison processes for the user since the number of diagrams with changes is considerably reduced but also optimizes modeling tool performance. 

An Environment option to specify the changes to detect in diagrams.

Learn more about diagram changes in model merge and project comparison >>

Further Merge Usability Improvements

The model merge has undergone further usability improvements. From now on, changes from the Target and Equivalent Changes are automatically hidden by default, meaning that only the Source changes are shown. As a result, fewer changes need to be reviewed by the user.

What is more, the model merge has been extended by adding a capability to select which ancestor calculation algorithm to use. You now have the freedom to choose a Branch Point as an ancestor for your merges. This is especially useful in those cases when merge results become too complex to understand and analyze due to previously rejected changes. By default, Lowest Common Parent ancestor calculation algorithm is used.

Selecting the ancestor for future merges in the Merge Project dialog.

Learn more about merge types in Teamwork Cloud >>

Other Features

Report Wizard

  • An empowering tool of the Document Report Designer diagram is now available for conveniently drafting and designing new templates of Microsoft Word Document (DOCX) format. Discover more about Report Designer >>

    Document Report Designer for drafting and designing new templates of Microsoft Word Document (DOCX) format.

  • Web Publisher 2.0 now has the Quick properties panel, at the lower left similar to MagicDraw, show the documentation settings in the Documentation tab and properties in the Properties tab of elements selected in the diagram and from the Containment tree. Learn more about the new Quick properties panel >>

    The Quick properties panel: Documentation and Properties tabs.

  • You can utilize a new sorter function for sorting elements as they appear in the Containment tree. Learn how to use this sorter tool >>

  • Reference bookmarks and their links can be created for DOCX numbered items. Learn about using these bookmark tools >>
  • Functions for displaying lists of properties in property groups for given elements and stereotypes are ready to use. Learn how to use this group of report tools >>

Back to top