Page tree

Cameo Enterprise Architecture 2021x Documentation

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

Compare with Current View Page History

« Previous Version 13 Next »


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. 


Contact your sales representative, and don't forget to give us your feedback on Twitter or Facebook.

Performance Improvements

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 ForecastResources Forecast, and Standards Roadmap diagrams are implemented, improving the way they are created and used. The Personnel ForecastResources 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 >>


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 FlowDirectionKindFeatureDirectionKind and ControlValueKind respectively.

Learn more about SysML 1.6 support >>

Back to top

Performance Improvements

Project Merge Improvements

Project Merge has undergone considerable performance improvements. Modeling tool version 20.0 requires 3-4 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 speed has increased by 20-70% in 20.0 compared to 19.0 SP4.

Charts comparing merge performance in speed and memory modes.

TWC Project Load Memory and Speed Improvements

Project load memory and speed improvements have been implemented for Teamwork Cloud. The modeling tool now requires only 2GB of heap to load a 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 mostly, SysML projects are now opened 2-3 times faster.

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

N.B A red border on a bar chart in the image below indicates a low memory occurrence during testing.


Charts comparing load memory and speed improvements between different modeling tool versions.
  • 3 projects (sizes ranging from 1M to 2M) in 19.0 SP4 and 3 projects in 20.0 (sizes ranging from 750k to 1M) were used to run the tests.
  • Migration time is excluded because already migrated projects were used.

TWC Disk Footprint Improvements

Major TWC disk footprint-related changes are presented in this release. TWC 20.0 requires twice as less disk space for the same amount of projects with no history compared to TWC 19.0 SP4. In addition to this achievement, the disk size growth is cut nearly 5 times in TWC 20.0 compared to TWC 19.0 SP4 for those projects users work actively on.


A chart comparing TWC disk footprint between different modeling tool version
  • A database of 50 projects with 200 commits each was used to run the tests. 
  • Project sizes ranged between 400k and 2.2M elements (average project size being 700k elements).

Partial Data Loading in Tables

Experience enhanced table loading and scrolling performance! Thanks to the newly-introduced Load Partial mode, data is now loaded in only visible rows, meaning that there is no need to wait until data is calculated in the entire table. What is more, 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 >>

Enhanced Copying/Pasting Operation Speed

Recent modeling tool performance improvements have led to an increase in the copying/pasting operation speed. Now you can copy and paste data noticeably faster for maximized productivity.

A chart comparing the copy&paste operation time in various scenarios.

Profiling Changes in the UML 2.5.1 Metamodel

Significant changes have been implemented to the UML metamodel for performance reasons. 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%.

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

Modeling and Infrastructure

Layers Based on Legends

Diagrams can get extremely crowded as the model evolves. Therefore, highlighting a chosen piece of information, for example, only one specific aspect of the system becomes a great 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 >>

Presentation Mode

Direct the attention of your audience to the diagrams being presented! You can now present diagrams in full screen without showing such user interface components as 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 >>

Intelligent Legend Creation

Seems like Legend creation is a tiresome activity? Not at all! From now on, you can create Legends easier than ever before – extract them automatically from the elements displayed on your diagram instead of relying on a manual creation. What is more, 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 >>

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 to synchronize data 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 brings the ability to create and display Composition and Aggregation relationships in Dependency Matrix.

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

Learn more about Composition and Aggregation creation >>

Predefined Element Type Filters

Find the needed elements in the Select Element dialog faster! You can now filter elements by their types to narrow down the search results and thus perform your searches more effectively. That is not all! More performance-related improvements that help to find and select the needed elements faster are coming.

Performing an element search with the applied element type filter.

Learn more about predefined element type filters >>

Other Improvements

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

  • The Jython 2.7.2 version is now supported.
Discontinued Products
  • The development of the following plugins is discontinued:

  • Web portal reports are no longer available. For more effective model publishing and reviewing on the web, use Cameo Collaborator.
  • WSDL Code Engineering and WSDL diagram are no longer available.
  • C# Code Engineering and C# Professional Edition are no longer available.
  • The 32-bit installation files are no longer offered for download.

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 have to migrate their server projects to TWC 19.0 series first and then upgrade to TWC 20.0.

From Cameo Collaborator for Alfresco to Cameo Collaborator for Teamwork Cloud

From version 20.0 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 >>


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

  • No labels