MagicDraw UML Changelog

What's new in MagicDraw UML 2021x LTR Refresh2

Jul 1, 2022

The 2021x Refresh2 introduces performance improvements to both the client-side and Teamwork Cloud-side as well as integration, general modeling, and collaborative modeling enhancements.
On the integrations side, ReqIF Import/Export improvements come into effect. For general modeling, this release presents improvements to Structured Expressions.
Finally, collaborative modeling has been extended to enable users to automatically clone used projects together with the main project.

New in MagicDraw UML 19.0 LTR SP4 (Jun 30, 2020)

New in MagicDraw UML 19.0 LTR SP2 (Apr 25, 2019)

New in MagicDraw UML 18.5 SP3 (Dec 19, 2017)

Performance related issues:
Solved the memory leak issue concerned to Mac OS X.
A drop-down menu for choosing commands in the Find and Find and Replace dialog text boxes now works in Mac OS.
Fixed the issue of text in shapes of images exported in the .svg format not shown correctly in Chrome or Firefox browsers.
Fixed the issue causing collapse of expanded elements in the Model Browser while switching between projects.
Fixed the issue related to selecting several elements in the Validation Results window to apply the same solver.
Created a passive validation rule to check if a Member of an Index is from the same table.
Solved some critical program issues related to stability of common operations and general performance while working with server projects in Teamwork Cloud server, including:
Enhancing performance of updating Used Projects by optimizing element-level operations.
Clearing the local cache more effectively now by removing unused server projects and their earlier versions.
Solving issues related to selecting symbols on diagrams and causing performance degradation of the modeling tool.
Fixing the issue related to losing references when a project is selected to be used in other project.
Diagramming related issues:
After a State Machine is copied, the references from original substates now remain to the original State Machine and not to a copy.
Relation properties can now be copied and pasted in MagicDraw tables.
Handled unexpected expanding of symbol labels on State symbols after changing the property Show Element Properties. Labels are displayed correctly on the diagram now.
When reconnecting the Connector to another Port using API, checking the arbitrary nested Port depth, full property path, and Part with Port are now performed to ensure correct visualization on the diagram.
Provided proper navigation information for Message labels in the Sequence diagrams images generated during publishing to Cameo Collaborator.
Fixed the issue causing an incorrect Type being set for an element in cases when the element has a colon : sign(s) in its name.
Fixed the issue of a Connector type not being displayed on the diagram after selecting not to show a name of the Connector.
There was an issue - table columns represented by stereotype tags became invalid after setting the stereotype customization. Now it fixed, and all columns represented by tags as properties are available just after setting the customization property HideMetatype to true.
Report Wizard related issues:
Added a new function $report.filterClassName(elementList, classNames) for retrieving a list of desired elements by specifying class names while generating reports. It solved an issue of some customized elements not being added to the report.
Other issues:
After a stereotype is applied to an element, newly added stereotype properties are now ordered the same way as specified in the stereotype.
Recursive child elements are numbered from a defined initial value correctly now.

New in MagicDraw UML 19.0 LTR Beta (Dec 11, 2017)

MagicGrid Template:
Two new project templates are available in this version. They both accompany MagicGrid, a new approach for MBSE developed here at No Magic, Inc.
MagicGrid supports performing problem domain analysis as well as building the solution for the logical system design, from stakeholder needs elicitation and capturing to the logical system design verification and technical requirements specification for manufacturing. The approach is thoroughly described in the MagicGrid Book of Knowledge, which will be available with the final version of 19.0.
The MagicGrid QuickStart template will guide you through the entire modeling process, starting with the problem domain definition and finishing with one or more solutions of the logical system design.
The MagicGrid Blank template will give you the predefined structure of packages for modeling with MagicGrid to use your time more efficiently.
Please note, the SysML plugin is required in MagicDraw to use MagicGrid templates.
Support of Latest Standards:
No Magic, Inc. always supports the latest standards. As of this version, MagicDraw supports the new UML 2.5.1 specification! Several minor enhancements include:
States are redefinable; and
Executable State Machines (PSSM) are supported
For systems engineers, we are happy to announce that SysML 1.5 (officially released as ISO/IEC 19514:2017 standard) is also supported via the SysML plugin. The updates in standard are related to adding the new AbstractRequirement concept, which allows you to define and implement any property-based requirement that could be inherited from the AbstractRequirement. Learn more about SysML 1.5 >>
For systems engineers, it is easy to use the ISO 80000 library now. About 50 of the most useful units are suggested in the list,100x less than introduced earlier.
For enterprise architects, the UAF standard (formerly known as the UPDM 3 standard) is introduced via the UAF plugin.
Search in Diagrams:
MagicDraw 19.0 provides the ability to search for textual information in all types of diagrams, including tables, matrices and maps. Open the search bar by clicking in a diagram toolbar, or simply press Ctrl+F. Use this feature to find the desired text displayed in a large diagram and quickly navigate the search results.
Live Hyperlinks to Elements in Text:
The renewed mechanism of hyperlinks to model elements brings the ability to embed live model hyperlinks in documentation or other texts, numeric values into requirements, and keep various expression and constraint texts up to date. Hyperlinks are updated automatically or with your control after changing the referenced element name. Additionally, it is now possible to embed hyperlinks to model elements in plain text fields, including constraint text, value expressions, etc. Wherever you see this button Insert Hyperlink , you can insert a hyperlink to element in the text.
Live hyperlinks are very important for simulation. For example, in State Machines or Activities, parameters are usually referenced. Once these parameters change their names, Guards are updated automatically. This allows you to maintain model consistency.
Legends:
Legends have been improved to allow a wider range of usage options. Now you can:
Generate legends automatically by creating them from stereotype tags.
Use legends in tables to adorn entire rows or the specific cells of these rows, as shown in the figure below.
Specify diagrams in which a legend is used without displaying the legend.
Rank legend items by priority.
Collaboration:
The following new features have been added for collaborating using the Teamwork Cloud server.
Cross project refactoring:
This feature allows you to move elements from the main project to a used one without losing references. When you work on a project for a long time, it's usual for the project to evolve to the stage when some components tend to get a library type or reusability flavor. A new cross project refactoring feature allows you to simply drag-and-drop selected elements from the main project to a project residing in Project Usages. All of the relationships that the elements have had still remain. This new feature is also beneficial for users who need to move elements from the main project to a used one frequently.
Change Sets:
A change set is a set of locally made changes to a server project. You may specify several sets for your project and commit sets one by one. For example, this feature is useful when you are working on a server project and get a request for an immediate change. You can suspend your changes, complete the immediate task and commit the changes, and then resume your work on the previously suspended changeset.
Managing project usages:
You can now configure project usages for one or several selected used projects at a time. In only one dialog box you can:
Control notifying users about new used projects versions
Add new projects
Remove used projects
Start directly using indirectly used projects
Change the version of a used project
Review the information of a selected used project.
Reset changes to a selected used project.
Additionally, in this dialog you can preview any changes applied to your project without closing the dialog.
The Advanced Project Usages Configuration dialog.
Hidden packages:
Starting with version 19.0, the Hidden Packages model cutting utility is presented. This utility lets you specify which model Packages (and elements within them) should be hidden. Once specified, the non-hidden/public version of the model will be created by cutting/deleting the hidden parts. As a result, the stripped model with only visible model elements is stored in a dedicated branch, which is coupled with the main project branch. You can reuse projects with only visible elements according to your needs.
Whenever you need to use a stripped model in other projects, the dedicated branch is suggested by default so that you can select your project to reuse. Also, there is no need to worry about making changes to the main project. Every change affecting the visible (or stripped) project part is synced with a project stored in the dedicated branch. You can do this manually or automatically after committing the changes of the main project to the server
Disconnected team collaboration:
Disconnected teamwork collaboration is dedicated for multiple contractors without the ability to work on the same Teamwork Cloud installation to contribute to projects. This feature allows you to export a server project as a local one, modify it, and import back while updating the server project. This means you can simply save your project locally as a .mdzip file and send this file to another contractor for modification. After the file is sent back, you have the ability to update the same server project from the local project. This life cycle may continue between any amount of contractors. This feature works even when multiple contractors work with separate Teamwork Cloud installations, as well as with Teamwork Server or local installations.
Cloning projects:
Now you can clone your latest server project version as a separate project. You can use the project being cloned as a "template" to create a new project or use it as an independent base for new development. IDs of a cloned project and elements are reset automatically. Project permissions are reset as well; the project is available only for a user who has cloned the project. All references to used projects (if there are any) are maintained.
Other enhancements and changes:
In the current release, the collaboration working environment has been significantly improved. These include:
Adding a comment for the package when exporting it to a new server project.
Displaying a progress bar with data about project changes while retrieving the content of element history. You may stop the collection process if you need to.
Viewing changes in the model in a particular scope at the element level in the package, as well as in a classifier element in a composed element such as a Block or Requirement.
OSLC:
Beginning with version 19.0, MagicDraw will be able to link and share data using Open Services for Lifecycle Collaboration (OSLC) integration. This means:
The modeling environment works smoothly in the IBM Jazz ecosystem.
Easy linking between different project lifecycle artifacts residing in different tools.
The ability to see detailed information of linked artifacts without switching between different tools.
Excel/CSV Synchronization:
The Excel/CSV synchronization mechanism ensures continuous data exchange between Excel/CSV files and MagicDraw tables. As of Version 19.0, you can manually sync data between Excel/CSV files and modeling tool tables. Simply drag the Excel or CSV file in any table to link it. You can map columns of Excel/CSV files and MagicDraw tables and specify other synchronization options.
Siemens Teamcenter Integration:
No Magic is proud to present the Teamcenter Integration plugin. It complements Teamcenter (Siemens product lifecycle management (PLM) software) with UML/SysML modeling capabilities provided by MagicDraw. The Teamcenter Integration plugin includes the following features:
Possibility to reuse UML/SysML models in Teamcenter.
MagicDraw integration with Active Workspace, allowing you to open and browse Teamcenter models in the MagicDraw modeling environment.
Importing/exporting bill of materials (BOM) to/from MagicDraw.
Bidirectional data traceability and synchronization.
Complementing Teamcenter models with functional analysis results from UML/SysML behavior models.
Other:
The Comment path is now displayed after dragging the Comment element from the Model Browser to the diagram pane when enabling the Display Paths on Element Drop option in the Environment Option dialog.
The Automatic Behavior Creation (renamed to Behavior Creation Mode) and Type Selection Mode buttons now work separately for each project
The Edit Compartments command is now accessible directly from the shortcut menu of the classifier compartments (such as Properties, Operations, Receptions, Ports, etc)
You can now specify the custom column and row query in all matrices, when you need to collect more than just owned elements. Simply click [Specify Row/Column Query (optional)] next to Row/Column Scope box in the the Criteria area
You can now specify the custom column and row query in all matrices, when you need to collect more than just owned elements. Simply click [Specify Row/Column Query (optional)] next to Row/Column Scope box in the the Criteria area
You are able to specify one more outside label position of a Port. This shows the Port label inside a shape, with the Port created on the shape boundary.
You can choose an existing model element when creating a relation in the relation map.
When creating a new Composite Structure Diagram for a Package, you can specify whether to create a diagram context element automatically or not by selecting an appropriate value for the Diagram Context property in the Project Options dialog.
As of this version, the Tooltips Style option is located in the Project Options dialog.
You are able to select an additional Show Both or Behavior Name value of the Name Display Mode symbol property for the Call Behavior Action. This allows you to show only the behavior name instead of both if the action name is not specified or the action name matches the behavior name.
When dragging or selecting an image from the Image Library or other resources, you can specify whether to apply an image to the property or to its type in the Project Options dialog > Apply Image To
When specifying a new type for a Activity Parameter Node or Pin in the Activity diagram, you can select the element kind created in the model with a specified name and set as a type.
The new project option Use different Fork/Join and Decision/Merge notations allows you to draw different notations for the Fork, Join, Decision, and Merge.
The Note anchored to the diagram frame can now represent the information of the diagram context element (for example, Activity or State Machine). To switch the representation to the diagram information, right-click the Note, and in the shortcut menu clear the selection of Represent Diagram Context.
You can now define your own documentation server. For that purpose, the new Environment option documentation.server is added to the Path Variables property group. Learn more about working with path variables >>
The filter mechanism includes the following improvements:
The Exclude Auxiliary Resources replaces the Exclude Used Projects filter option. Learn more about Filter Options >>
The elements from used projects are included in the search results list by default.
The new Exclude Auxiliary Resources filter option reduces the search results list by excluding elements contained in auxiliary resources, except elements with the new «ignoreAuxFilter» stereotype applied.
If you clear the Apply Filter check-box once, your selection is remembered for the next time.
A number of new operations have been added to the built-in operations library.
Now Mac OS X now supports the mdel:// links and *.mdzip files opening.
The new documentation layout, including the new home page, is introduced. On the new homepage, you can easily navigate through the menu or simply use the search.
Enhancements in Report Wizard:
You can now include the Attached File element to the main template by using #include, #includeSection, $import.include(), and $import.includeSection(). You can also use the Attached File element as a template of $file.create(), $file.silentCreate(), and $file.createAndWait() to generate reports.
The DOCX template can now dynamically import the content of other DOCX documents by using $import.include() and $import.includeSection() at runtime, as an alternative to existing RTF, HTML, and text template support.
There is now a more convenient, flexible way to generate reports through a command line prompt by specifying element IDs of single or multiple elements in MagicDraw projects as the report scope.
The dialog tool API is now equipped with a select method to create more customized Selection dialog boxes. You can select elements during runtime through the user interface.
Discontinued Integrations and Editions:
The Personal edition is discontinued for all modeling tools.
For business process modeling, only the Cameo Business Modeler plugin is supported. The development of Cameo Business Modeler tool is discontinued.
For Cameo Enterprise Architecture, only the Enterprise edition remains. Support of other editions is discontinued. We assure you that the modeling features will not be affected by this change.
Integration of Eclipse, Rational Application Developer (RAD), openArchitectureWare (oAW), and AndroMDA are no longer supported.
Development of the Cameo SOA+ plugin is discontinued. However, you will still be able to load projects created in earlier versions with this plugin in your modeling tool. SoaML diagrams are converted to pure UML diagrams and maintenance of the SoaML profile is continued.

New in MagicDraw UML 18.5 SP2 (Aug 29, 2017)

Modeling related issues:
Fixed the issue in the Activity Diagram where several Output Pins to call a Behavior are created instead of one.
You can select properties of a custom type element to display as columns of the Generic table.
Users are warned about the limitation of reversing the flow direction if the flow source and target are the same elements.
In tables, you can simply select a cell when pasting a group of words, instead of pasting a cursor in it.
The size of Requirement shapes no longer changes to default if you align the Requirement diagram in the Grid Layout type and set the Make Preferred Size option to false.
Eliminated he ability to add Entry/Exit Point to State or Transition. To meet UML specification, you can add an Entry/Exit Point to the Composite or Orthogonal State.
Fixed the issue related to losing the Sync Element property value after converting an Input Pin to a Value Pin in the Activity Diagram.
In Object Diagram, you can assign several classifier types to one Instance Specification.
DSL related issues:
Evaluating expressions in JRuby language: a parameter THIS is always available.
Derived properties defined as an Integer type: the Long type value returned by the JRuby script of the derived property expression is converted to Integer.
Automatic numbering of custom elements: the continuity of unique IDs for every new instance of the custom element is correct in all numbering schemes.
Collaboration related issues:
Enhanced performance of updating Used Projects by optimizing diagram-related operations.
Connectors can no longer be locked without their classifiers while mapping port types. This prevents automatically locking irrelevant connectors.
Fixed displaying dates of the Norwegian, Bokmal (Norway) format in server project dialogs.
Updated the locking mechanism to prevent lock-stealing related issues after saving a model containing locked elements as an offline project.
Fixed the issue related to opening a server project after it was saved and edited offline and thus treating it as outdated.
Added the progress bar to show indexing progress when importing a server project with a deep hierarchical structure to the DataHub.
Fixed issue with potentially failing commits after changing package permissions.
Model validation issues:
Updated the No Type for Parameter UML completeness validation rule.
Fixed the spell check issue for validating tagged values.
Enhanced validation rules to detect issues related to invalid item flow direction.
Other issues:
Full element names (without ellipsis) are visible in the column names while printing matrices in PDF. The issue appeared depending on the screen resolution. Now it is solved.
You can generate an html report from thousands of files with the Web Publisher 2.0 template from the command line.
Z ordering of dialog windows issues are fixed in the native full screen mode in Mac OS X.

New in MagicDraw UML 18.3 Beta (Nov 13, 2015)

More Reasons to Choose CEDW for Collaborative Modeling:
Now you can inspect the detailed history of the model at element level. Check who and when modified the particular element easilly. Also, compare any two versions of the element and see what properties were added, modified, and deleted.
Another great feature is the possibility to restrict access to selected packages for different users without splitting the project. You can select who can modify the contents of the package and who can only review it.
In addition to these features, the performance of updating changes has increased significantly, compared to Teamwork Server and CEDW 18.2.
Requirements Change Management and Impact Analysis:
Working on a server project requires an up-to-date knowledge of all relevant project changes. While some of them may be visible simply by taking a look at the diagram, modified requirements are harder to track.
For this, we introduce a new set of validation rules for suspect link analysis.
These rules help you track changes in requirements, that are linked to design elements (such as SysML Blocks, Test Cases, Use Cases, etc.) by satisfy, derive, refine or verify relationships, as well as allow tracking deprecated requirements and requirements that are not linked.
Improved Scope Management
Custom Buttons on Diagram Pallet
Image Library
More Options in Dependency Matrices
Easier Swimlane Manipulation
Quick Filter Improvements in Options Dialogs
Nested Properties and Parts in Instance Table
Smoother Work With Images
New Validation Rule to Ease the Model Clean-Up
Automatic Detection of Prefixes
No More Gaps in Numbered Sequences
Related Actors in the Use Case Specification
New Drag Operations
Changes in Model Browser:
Relationship directions are now displayed directly in the Model Browser. You no longer need to open the Specification window of the relationship to identify its direction.
Text in brackets now indicates classifier behaviors and behaviors with context.
Miscellaneous:
Default name of the root package in all new projects is Model, not Data.
A newly created diagram is now named after its owner by default.
Now when you edit Call Behavior name in its text editor, a new behavior is automatically created with the new name.
Assigning Signals to Messages is now more convenient: typing a Message name is the only thing you need to do, and a Signal is automatically created with the same name as the Message name.
Now when you add Ports to Classes, Ports don't overlap the compartment elements as the margins are automatically adjusted to create distance from a Port.
Line width of a Separator or Rectangular Shape can now be easily modified by editing the Line Width property of the appropriate symbol. Learn more >>
The multiplicity [0…1] is no longer limits the default value creation of instance slots when creating Instance Specification from the diagram toolbar or in the Instance Table.
Enumeration attributes are now read-only by default.

New in MagicDraw UML 18.2 (Nov 13, 2015)

New in MagicDraw UML 18.2 Beta (Jul 24, 2015)

Integration with Cameo Enterprise Data Warehouse:
We are proud to offer our users the integration with Cameo Enterprise Data Warehouse (CEDW), a new server for collaborative development and versioned storage of models. CEDW is envisioned and architected to provide significant future improvements in the areas of model-governance, model-analysis, and integration with third-party tools.
What are the differences between working with CEDW and MagicDraw Teamwork Server:
Faster project opening*.
Scalable server performance (server can be expanded to a cluster).
Faster commitments and updates of project changes.
Faster team collaborations when server is located at MAN/WAN.
Redesigned project composition of used projects.
Model versioning with the built-in database.
User authentication against LDAP server (multiple directories supported).
Role-based access control (RBAC) with predefined set of roles for the server and project access management.
Easier administration of the server and in-the-sever-stored models via the web browser.
Completely Reworked Model Comparer and Upgraded Merge:
New look:
Due to the new appearance, model comparer is now more user-friendly, and provides more explicit information about changes without causing confusion.
A single difference tree, instead of the previous two, helps the comparer to provide a clearer visual structure of the changes made. An easily readable legend provides the number of differences for quick overview, and more detailed information is provided in the Change Details panel.
Reviewing diagrams:
Forget looking at diagrams for hours without actually knowing what has changed in a model or trying to track the minor symbol movements – that is now in the past. The improved diagram Difference Viewer window was introduced into both model comparer and merge to enable users to notice, distinguish and filter modifications instantly.
Recognize the nature of each modification – color coded lines and flags allow quickly distinguishing between addition, modification/move or deletion changes. Too many colors, lines and flags in one place? Filter to show only model or symbol changes, or a certain type of modifications. Each model change in a diagram is marked with a flag and by simply clicking it you can instantly navigate to the model tree to review the changed details.
No more switching between different diagrams versions – a new slider provides an animated view of how your diagrams changed with every modified version.
Extensive reporting:
Finished reviewing changes and wish to see them on paper? We made it easy – simply export all the diagrams with visible changes to a Microsoft Word document using one of two predefined templates – Diagram View or Full View for a more detailed overview, including the full tree with all dependent changes. Need less information? Create your own customized template and generate reports of any desired depth and scope.
Merge upgrades:
A minimized toolbar, more comprehensive legend, and a simplified two-way merge appearance give the Merge window a nice make-over. Improved representation of changes in diagrams and reporting options provide even more power to the project merge.
Scrum project template:
A bundle of MagicDraw project templates was extended with a new item for software engineers, who use the Scrum methodology! In this template you can find brief guidelines and predefined artifacts for all phases of Scrum-based software development process recommended by No Magic, Inc.: user stories, requirements specification, architecture design, sprint planning, and publishing the model. Analyze the predefined information and adapt it to your needs - modify or delete existing elements, add your own ones – to jump start the creation of your Scrum model.
The Scrum project template appears in the New Project dialog under the Software Engineering category.
Increased Modeling Efficiency:
Validation enhancements:
Visible diagrams validation mode:
Feel like validation of your model runs too slow? Going to stop it? Then switching to the visible diagrams validation mode is what you need! As a result, the active validation starts running only on elements displayed in one or more visible diagrams, which significantly increases the performance of the modeling tool.
Validation results marker bar:
When your diagram is too large to be displayed all-over, it may become quite challenging to notice all annotated symbols it contains. In this case the new validation results marker bar is your true helper! It appears on the right side of a diagram pane, if the diagram contains annotated symbols.
The markers are shown even for the items that are not currently visible on the screen (you may need to scroll down to see them). The marker bar is shrunken to fit the screen and displays relative positions of annotated symbols on the axis of ordinates. Every marker is colored according to the violation severity.
You can click a marker to select the annotated symbol or move the mouse over the marker eye (at the top-right corner of the diagram pane) to see the summary of the diagram validation results.
Diagram validation button:
Need to validate only a small portion of the model you just have modified in a diagram, table, matrix, or relation map? Click the new button on the toolbar of this diagram, table, matrix, or relation map to run the validation only there.
New rules and specifications:
From now on:
Validation reports an error if an Opaque Behavior or Activity Parameter Node contains more than one return Parameter.
The warning message “Too few tag values” indicates which tagged values failed the procedure. You no longer need to look for the particular undefined tagged values manually.
Automated management of Use Case subjects:
From now on, dragging a Use Case onto a Class in a diagram sets that Class as the subject for the Use Case.
Having a Use Case with the subject jump-starts the creation of Swimlanes in the Activity diagram owned by that Use Case. In this case, you can select the subject properties you wish to be represented by the Partitions of that Swimlane.
Smarter diagram layout:
Our enhanced Composite Diagram Layout makes working with composite diagrams even more hassle-free – a dynamic shape spacing approach within layers has been implemented, label layout has been improved and support for conveyed labels added.
Port placement on diagram frames has been improved to better satisfy your modeling needs when using Composite Diagram Layout.
Parts no longer overlap each other after you choose to display them.
The new Shape Order option coming with the Hierarchic Layout allows you to specify the order of laid-out shapes, thus making the creation of Requirement diagrams more convenient and time-effective. Now you can arrange your shapes by name or by numbering.
A new, separate Grid Layout has been created to enable you to layout elements in a COMPACT grid. Its options allow ordering elements by a defined comparator, and also the definition of aspect ratio that the layouter can work on . The Grid Layout has the Make preferred size option; if true, elements are resized to the smallest possible sizes, if false, elements remain of the same sizes they are. The Minimal shape distance option determines the distance between shapes.
Transparent unconnectable shapes:
Forget about considering which shape is suitable for connection! From now, on all the shapes that cannot be connected with the selected shape become less visible on the diagram pane.
You can specify the transparency of unconnectable shapes by changing the Transparency of Unconnectable Shapes property value in the Environment Options dialog, the Diagram property group.
Relation Map enhancements:
The Relation Map can now display:
Element numbers after you click the Option button on the Relation Map toolbar and then select Show Element Numbers.
Standard and custom subtypes of the selected element type after you choose the element type and then select the new Include Subtypes check box in the Select Element Type dialog.
Plus, you're welcome to use the zoom buttons directly from the relation map toolbar!
Classifier Behavior in Classifier's specification:
Use the Behaviors property group not only to create or delete owned Behaviors, but also to manage the Classifier Behavior! Change it simply by clicking the new Set Classifier Behavior button.
Activity Parameter Node enhancements:
We improved the Activity Parameter Node creation and placing, to make it more intuitive and automated. Now, when you create an Activity Parameter Node by dragging it, the trajectory of how you do it defines parameter‘s direction; dragging towards the right/bottom border or inside the node creates an out direction, dragging towards left/upper border creates an in direction.
Managing an Activity Parameter Node properties is now more convenient with the updated Specification of Activity Parameter Node window and shortcut menu. You can now set a parameter's direction by simply right-clicking the Activity Parameter Node instead of opening the Specification window. Other activity parameter properties are easily configured and displayed in the Parameter property group in the Specification window.
Miscellaneous:
A new Display Parts button has been added to the smart manipulator toolbar, making access of the command quicker.
Due to the newly introduced symbol property Inner Elements Sort Mode, you can now choose how to arrange your Package inner elements. Keeping the default selection No Sorting leaves the elements sorted by the date of their creation, whereas selecting By Name sorts Package inner elements alphanumerically.
Converting a State to a Composite State no longer requires you to manually create a Region inside that simple State. The conversion is carried out by simply dragging a vertex on a simple State symbol.
Now you can adjust the position of labels of several Port shapes at once. In earlier versions this was possible only for a single shape.
Now all the relations that can be connected to a property can be directly connected to the Association name label as well.
Finding your diagrams in the Containment tree is quicker and easier due to the changed sorting – now they‘re displayed right after the Relations group and Packages, so you can access them in seconds whenever you need to.
We have updated the Project Options and Environment Options dialogs for your convenience – now when you open either of them, you see the General options grouped into sub-categories with links in the right side of the dialog. This saves you time from guessing where a certain option is, also it makes access to those options easier – simply click the link, and the chosen option sub-category will be selected in the tree and opened in the right pane.
Other News:
Online documentation:
It's our pleasure to announce that as of 18.2 FR, we are starting to move all our actual documentation online – to a single, user-friendly platform with advanced searchability.
For a limited time, you might notice this migration is in progress. This means that:
At first, only 18.2 new features' documentation will be available in the new site.
Temporarily, there will be no offline documentation for the 18.2 FR.
Offline documentation accessible via MagicDraw is up to 18.1.
Context-sensitive help (F1) will reference to 18.1 documentation.
We plan to provide the complete online documentation until the release of the next LTR.
We'd like to apologize for any inconvenience this migration may cause. Your patience and trust in us is what inspires us to look for even better solutions for our clients!
Optimization for high resolution displays:
Now OS X users can take full advantage of a long-awaited Retina display support, allowing those who work with higher resolution screens to see more detail in diagrams and enjoy sharper icons in the interface.
Those who use MagicDraw for Windows and Linux with high resolution screens will definitely notice the initial steps taken towards full HiDPI support – you can now benefit from a significantly better overall visual quality, including proper scaling and increased sharpness of icons.
Discontinued compatibilities and dropped integrations:
Windows XP is no longer supported. You may still use MagicDraw with Windows XP, however, full functionality of the tool is not ensured.
MagicDraw 18.2 integration with CVS is not supported.
EMF-based UML v1.0 projects are no longer supported.
If you need to continue using these file formats or deploying these integrations, you are welcome to use MagicDraw 18.1 or earlier.
Eclipse UML 2.5 model data export:
The Eclipse UML 2.5 model data export from and import to MagicDraw is now fully supported.
All available Eclipse UML 2 XMI formats – Eclipse UML 2 v2.x/v3.x/v4.x/v5.x/ XMI – are now listed under a single File > Import From / Export To command group Eclipse UML 2 XMI File.
Open API changes:
OSGi framework:
From now on, MagicDraw uses the Eclipse OSGi framework. MagicDraw and all plugins are wrapped into a single OSGi bundle. This change in most cases has no impact for MagicDraw plugin development, since development principles remain the same as before.
However, there are some changes in starting MagicDraw.
Changes in starting MagicDraw from the command-line
com.nomagic.magicdraw.Main was deprecated. Use com.nomagic.osgi.launcher.ProductionFrameworkLauncher to start MagicDraw in this case. Additional java properties must be passed to this new launcher.
Changes in starting MagicDraw from another Java application:
To make MagicDraw classes accessible, run this Java application inside the OSGi framework too. Use com.nomagic.magicdraw.core.Application#start(java.lang.String[]) to start MagicDraw in this case.
Integration with CEDW and changes in project structure:
Due to MagicDraw integration with a new server, Cameo Enterprise Data Warehouse (CEDW), a new type of project was added. From now on, we have three types of projects: local project, Teamwork Server project, and CEDW project.
There is a great chance that plugins won't work correctly with CEDW projects, since this type of project (in contrast to local and Teamwork Server projects) can have many root elements. The root element of each used project becomes a root element in the main CEDW project. Thus, please review the existing plugins.
For working with multiple root models, a new API was added into the com.nomagic.magicdraw.core.Project:
public java.util.List getModels ()
public com.nomagic.uml2.ext.magicdraw.classes.mdkernel.Package getPrimaryModel ()
public com.nomagic.uml2.ext.magicdraw.classes.mdkernel.Package getModel () was deprecated.
HiDPI monitors support:
Since the loading of different resolution icons by monitor DPI was implemented, the new class is introduced for loading multi-resolution icons:
com.nomagic.magicdraw.icons.IconsFactory
Element lookup API:
Elements lookup API was refactored and cleaned. Two new utility classes were added:
com.nomagic.magicdraw.uml.Finder - provides the API for element lookup by simple name, qualified name, metatype, scope, and level of depth in the model structure.
com.nomagic.magicdraw.uml.ClassifierFinder - provides the API for UML Classifiers lookup and creation by simple or qualified name and metatype.
com.nomagic.magicdraw.uml.ElementFinder was deprecated.
UML metamodel changes:
Multiplicity of the following member ends of meta-associations in UML metamodel was changed from [1] to [0..*]:
Association.get_clearAssociationActionOfAssociation
Classifier.get_readExtentActionOfClassifier
Property.get_readLinkObjectEndActionOfEnd
Property.get_readLinkObjectEndQualifierActionOfQualifier
Trigger.get_replyActionOfReplyToCall
UML metamodel API was changed according to these changes.
File format changes:
The "parameter" reference was removed from xmi:Extension for Pins and ValueSpecifications. It does not exist in UML metamodel.
The "syncElement" reference was added to xmi:Extension instead of standard reference. It is not a part of UML standard metamodel.

New in MagicDraw UML 18.1 (Jul 24, 2015)

New in MagicDraw UML 18.0 (Jul 24, 2015)

New Features:
Operation signatures can now be suppressed on State shapes and Transition paths thus making the symbols look good even if they contain numerous operations with many parameters. For this, open the Symbol Properties dialog of the State or Transition and set the Show Operations Signature property value to false.
The Keep locks check box on the Commit Project to the Server dialog now remembers the last choice of the user. Thus, if you want to release the locks every time when committing changes, you don't need to unselect the Keep locks check box each time you do this, once you make your choice during the first commit.
Removed Features:
The ability to lock elements without update, which was a part of 18.0 LTR, has been removed from MagicDraw functionality. Updating elements that have been locked without update may result in data loss.
UML Metamodel Changes:
Multiplicity of the following member ends of meta-associations in UML metamodel was changed from [1] to [0..*]:
Association.get_clearAssociationActionOfAssociation
Classifier.get_readExtentActionOfClassifier
Property.get_readLinkObjectEndActionOfEnd
Property.get_readLinkObjectEndQualifierActionOfQualifier
Trigger.get_replyActionOfReplyToCall
UML metamodel API was changed according to these changes.
Main Issues Fixed in this Service Pack:
Search:
A single element selection dialog improperly opens, when you attempt to specify the search scope for gathering the contents of the smart package.
An unhandled error occurs when trying to open the Select Properties dialog from the Find dialog.
Symbols cannot be selected on the diagram pane, if that diagram is opened from the quick search results list by pressing Enter.
Save, load, modules:
In certain cases, unconfirmed module usages and recovered elements are unexpectedly found in the project.
Reloading a module in certain cases may cause an unhandled error.
When MagicDraw runs on Windows, changes made in a read-write module are lost after saving and re-opening the recovered project, where that module was manually loaded.
When MagicDraw runs on OS X Mountain Lion, the custom fill color of a stereotype’s symbol does not persist, after you reopen the project, if the Alpha option value of that fill color is other than 255.
Diagram layout:
Moving shapes connected in a tree-like structure causes their paths to cross each other and breaks up the tree.
Modeling/Diagramming:
Dragging a Class to an Activity diagram creates a Swimlane instead of Central Buffer Node.
An Association cannot be moved to the Package, if there is another Association with the same name in that Package.
Deleting an Extension relationship of the stereotype via its Specification window causes an unhandled error.
Numbering of Requirements created in a Package starts from 2.
Selecting Related Elements > Display Related Elements on the shortcut menu of an Instance that has usages to Enumeration, causes an unhandled error.
The kind of Aggregation cannot be changed from Composite to Shared for the Association that was created by importing a .csv file.
Color tags of the Operation are unduly displayed, when that Operation is selected on the Transition path.
Operation signature checker does not include return parameter type into the signature (important for Ada uers).
When MagicDraw runs on OS X Mountain Lion, fill color transparency of the diagram legend item can not be set, if the Alpha option value of the fill color is other than 255.
Generic Table:
Check boxes are incorrectly displayed as editable in the cells of the Generic Table.
The description of the Glossary term is not shown, when the pointer rests on that term in the Name column of the Generic Table.
When a Generic Table that contains a column with collection is exported to an .xlsx file, a new line is added in the spreadsheet. When such Generic Table is exported to a .csv file, incorrect separators are used.
Relation Map:
MagicDraw stops responding during the creation of multiple directed Compositions, when a Relation Map is loaded.
There is a great chance of deadlock on any change in the model (new element creation in the Model Browser, element rename, and so forth), while any Relation Map is open.
Teamwork Server integration:
After you cancel the local save of a server project before closing MagicDraw, changes made in that project are lost.
Model Merge:
A message about locked elements unduly appears and the Merge stops, if the project contains a read-only module with inner lock on its shared package.
Retina displays:
Trying to select symbols with a Selection Rectangle tool (click and drag) causes diagram distortion.
Text is distorted in the tree of the Select Element dialog.
Symbol properties and styles:
The Use Advanced Member Coloring symbol property of the Protocol Transition to Self is missing.
The Show Operations Signature and Use Advanced Member Coloring symbol properties of Protocol Transition are wrongly set to false by default.
When a Stereotype has the Class and Property metaclasses, the Stereotype Style is not applied to it.
DSL engine:
A DSL stereotype does not appear in the list of types under Refactor > Convert To, if that DSL stereotype has the same name as another stereotype.
Inherited tags of a customized stereotype are not shown in the Select and Define Properties Used as Criteria dialog.
The Structured Expression dialog misleadingly states that it is in the Standard mode after you switch to the Expert mode and reopen the dialog.
Miscellaneous:
Element ID is displayed in a Document Modeling report instead of a textual element representation.
After trying to set the Working Package for the C++ code engineering set, MagicDraw stops responding.
Exporting model to an EMF Ecore file causes an unhandled error, and the EMF Ecore file is not created.
Updating a transformed model after the Any to Any transformation causes a model inconsistency error.
Generating a Software Engineering Portal report using generate.bat does not work.
When MagicDraw runs on OS X Mavericks or Yosemite, it is impossible to add the external .jar as the External Libraries property value in the Project Options dialog.

New in MagicDraw UML 17.0.5 (Jul 24, 2015)

New Features:
Smart packages:
Need to see all non-verified requirements of the particular version in a single view? Have all frequently used elements within the same package? Get a list of all the interfaces used in the model? Pick up elements from different places of the model, into one package, for easier scope definition when generating a report? Use smart packages!
The smart packages do not hold anything, but display elements stored elsewhere in the model and continually update to display elements that meet the search criteria specified by a query. The smart packages save your time when you would otherwise need to rebuild a search from scratch. They also help to find, track, and organize your model elements. The smart packages are treated like regular packages and can be used in Dependency Matrices, both Find and Quick Find dialogs, element Selection dialog, and other places in the application.
Creating a smart package is as simple as creating a regular package.
Once the smart package is created, you are ready to specify the query for gathering its contents. For specifying queries, use the Query dialog, which reflects numerous enhancements of the powerful expression evaluation engine. Let’s say we need to have all requirements from the package HSUV Requirements with tag value version=5.
From now on every new requirement in the package HSUV Requirements will be automatically included into the smart package if tagged with version=5.
The smart package can be selected as the row or column scope in a dependency matrix. The scope will update after any update of the smart package contents
You can also select the smart package as a search scope in both Find and Quick Find dialogs, element Selection dialog, and other places in the application.
Favorites:
Save time by marking any element that you regularly use in your model and need to access quickly as a Favorite.
Using Favorites also speeds up the scope selection in:
Quick Find dialog
Element Selection dialog
Autocompletion lists
Gradual upgrade of Teamwork Server clients:
The new version of the client application can connect to an earlier* version of Teamwork Server. This feature enables the gradual upgrade of Teamwork Server, which will make the upgrade process smoother in larger organizations.
By using the gradual approach for upgrading Teamwork Server, different teams from the organization can migrate their server projects independently of each other and still work with the same Teamwork Server. A team that has switched to the new version of the client application, and needs to work with server projects, no longer has to wait while other teams complete their work with the earlier version of the client application in order to upgrade the server. Upgrading Teamwork Server is not required to access server projects with the upgraded version of the client application. The upgrade of Teamwork Server can now be postponed until all client applications are upgraded.
An additional benefit of the feature is the ability to try out the new version of the client application with real-life server projects without upgrading the server.
Modeling / Diagramming Enhancements:
Layout enhancements:
When drawing new paths, MagicDraw automatically chooses the optimal route to avoid crossing of shapes.
When drawing a new path, the path end is connected to the shape center. Note this is valid if the shape is small enough.
Layout inside Swimlanes has been enhanced and now symbols are layed out based on the Partitions to which they belong.
Labels no longer overlap after applying the automatic layout on the diagram.
The shape no longer changes position after selecting to display related elements.
Enhanced layout for association classes.
When inserting a shape into a path in an Activity or State diagram, a space is made automatically for the new shape and shapes no longer overlap each other.
MagicDraw introduces the smart shape sizing when drawing new shapes from other shapes via paths. The size of the newly created shape is kept the same as the size of the shape from which the path is drawn.
Easier modeling in Composite Structure diagrams:
Modeling of Composite Structure diagrams is greatly simplified. Modeling in Composite Structure diagrams will be much faster now as Ports will automatically be created when drawing Connectors from other Ports. It will be possible to easily create Ports when drawing Connectors to the diagram frame. In addition, depending on the Type Selection Mode you choose, you will be able to skip the specification of Part types and set them later.
The figure illustrates the following modeling enhancements:
Draw connector to / from diagram frame. You can now draw a Connector directly to or from a Composite Structure diagram frame. As a result a Port will be created on the diagram frame.
Select compatible or create new port. You can now select from the list of existing Ports or create a new one when drawing a Connector from a Port.
Refine Type using new Type Selection list. You can now easily change the Part type using a new Type Selection list without losing data when Ports on the Part are created. Ports will be replaced with new ones of a new type and Connectors will reconnect to them.
Other enhancements in Composite Structure diagrams:
You can create a Port or a nested Part on the Part even if the Part type is not specified. In this case, MagicDraw will automatically create a type for the Part, on demand.
You can now create a Composite Structure diagram for the Part directly from the Smart Manipulator toolbar and in this way easily model the inner structure of the type and deepen the level of your model.
Connectors now display in the new Connectors group in the element Specification window. This new enhancement allows you to distinguish Connectors by their context.
The legacy “unnamed1, unnamed2 …” naming schema is replaced by more useful default naming where Ports are named the following: “p1, p2 …”.
Easier modeling in Activity diagrams:
Create behavior automatically:
MagicDraw introduces new Automatic Behavior Creation mode. When the mode is on, Behaviors are created automatically on Action creation. Furthermore, Parameters are created on Pin creation automatically. This helps to save time and to maintain consistency in your model.
Quickly display Properties as Swimlanes in Activity diagram:
To represent your Properties as Swimlanes easily, create a new Swimlane in the diagram and you will be offered the list of Parts to be displayed as Swimlanes. Note that the Activity diagram should be created under the Classifier that owns the Properties.
New drag-and-drop operations:
Drag a Class, Property, Actor or Instance Specification to an Activity diagram to create a new Swimlane.
You may also add new Partitions to the existing Swimlane, by dragging elements.
If you drag an Activity, Interaction, or State Machine to an Activity diagram, Call Behavior Action is created.
Other:
Symbols that overlap with an Activity Partition on the Activity diagram are now highlighted as invalid.
Parameter direction now displays on Activity Parameter Node shapes on diagrams.
The element name and the Element Properties compartment are now separated by a line on the element shape.
Designing of tables and trees in the User Interface Modeling diagram is now more flexible. Reorder columns or nodes and leaves simply by changing their numbers.
By using the new change type button in the Smart Manipulator toolbar, you can now quickly create or change the behavior of the Call Behavior Action, the type of the Lifeline, the classifier of the Instance Specification, the behavior of the Interaction Use, the type of the Collaboration Use, and others.
If a Property, with private, protected or package visibility is converted to a Port (Refactor > Convert To > Port), the visibility of the Port becomes public.
Behaviors are now grouped to the Owned and Inherited groups in the Behaviors property group of the element Specification window.
Diagrams look cleaner now - grid lines no longer display on diagrams by default (snapping to grid lines will still be on).
Analysis Diagram Enhancements:
Ability to easily identify different relation criteria in Relation Map:
You can now easily identify different relation criteria represented on a relation map. For this capability, the relation map has been enriched with the following enhancements:
Colors. Select the colors when specifying the relation criteria you need to see on the relation map.
Legend. Identify relation criteria by colors. The legend will be included in a report, image, or printed copy of the relation map.
ToolTips. Move the pointer over an arrow to see the relation criteria it represents.
The ability to represent colored relation criteria on relation maps will help you when performing a traceability, impact, or coverage analysis.
As the following figure shows, you can now:
Use the same or similar colors to represent different relation criteria between the elements in the same phase of a project development.
Use different colors to represent relation criteria between the elements that belong to separate phases of the project development.
Easier analysis with Dependency Matrix:
You can now sort both rows and columns either in ascending or descending order (see the following figure) or create your own order by shifting selected items (either grouped or non-grouped) from one place to another. The sort order persists after changing the row or column owner's display mode.
To shift the selected items, use either appropriate commands from the row or column shortcut menu (see the following figure) or key combinations, such as Ctrl+Arrow.
Now you need fewer clicks to create or remove a relationship.
You can now choose to select a relationship in the Containment tree or open its Specification window from the cell's shortcut menu.
One more popular option can now be specified directly in the Criteria area of the matrix. In earlier MagicDraw versions you could change the Show Elements option only in the Specification window of the matrix, but not in the Criteria area.
Relationships with stereotypes applied can now be more easily selected as dependency criteria from the Dependency Criteria dialog (in earlier versions, the Criterion Editor dialog). Now you need a single click to select a relationship with a stereotype instead of performing the whole workflow: selecting a relationship and then specifying the appropriate stereotype as the Applied Stereotype property value for the more precise filter as it was in earlier MagicDraw versions.
Open API for Dependency Matrix customization:
You can now use the open API to:
Create custom types of the dependency matrix. Customize a dependency matrix as follows:
Configure the toolbar (1), shortcut menus of the row or column element (2), cell (3), and Criteria area (4).
Assign shortcut keys for commands.
Define custom dependencies that can be created in the matrix (5).
Specify the appearance of the matrix, that is, change the default colors of the cell and both row and column headers, assign custom icons to represent dependencies, etc. (6).
Define cases when specific dependencies should be updated without rebuilding the whole matrix.
Export the data of a dependency matrix to any format (7).
No Magic, Inc. provides instructions on how to use the open API and a sample project, which can be found in \openapi\examples\dependencymatrix.
Common Usability Enhancements:
You can now start a quick search by clicking a new toolbar button on any open tab (Containment, Diagrams, etc.) in the Model Browser.
You can now see the full length of a long text that is cut off by the border of a list or a tree area. Move the pointer over a cut-off text to see the full length.
You can now easily navigate either to the previous or to the next open diagram. A toolbar for navigation has been added to all the diagrams:
In dependency matrices, relation maps, and generic tables, find the new toolbar on the toolbars area.
In another diagram, move the pointer over the bottom-left corner of the diagram pane to see the new toolbar.
A list of suggested elements can now be reduced by clicking a specific button. As a result, all irrelevant elements will be excluded from the list.
You can now lock, unlock, or discard changes of multiple elements just in one click. The appropriate commands have been added to the shortcut menu of multiple elements selected on a diagram.
The shortcut menu of an element selected in the Model Browser has been refined as follows:
The Create Symbol command has been excluded.
The Generate Code Framework and Check Syntax commands have been moved to the submenu of the Tools command.
ReportWizard Enhancements:
The capability of Web Publisher has been optimized as follows:
You can now see the details of an element that has an active hyperlink in the Specification tab by clicking the element's icon in the Containment tree.
The new Diagrams tab has been added to the Web Publisher report to allow you to easily see all diagrams that are grouped by diagram types.
You can now click an element in the Containment tree and see all diagrams that represent the element in the new Appears in tab.
A newly-added report variable allows you (when clicking a hyperlink on an element) to choose between the normal MagicDraw's active hyperlink behavior and the auto-navigation to the last active hyperlink behavior (similar to transitive behavior).
When generating a report via the command line, you can now choose whether to overwrite existing file(s) before generating the new one(s).
This release improves the DSL properties handling. You can now use any nested property in any # directive.
To retrieve slot variables and values, you can now use shortcuts instead of velocity code.
The performance of the FTP and FTPS upload function has been improved.
Report variables' values can now utilize HTML formatting.
Other Enhancements:
Automatic Java selection:
MagicDraw no longer suggests selection of a Java version on Windows OS while installing MagicDraw, as from now on the bundled Java is the default. Most testing and debugging were performed with the bundled Java version, so the use of this JVM is highly recommended.
Automatic check for updates:
MagicDraw now automatically checks for updates according to the Check for Updates option and displays a notification if updates are found.
Enhancements in expression evaluation engine:
The expression evaluation engine now allows for:
Defining reusable expressions in the model and calling them from another expression.
Calling expressions with multiple parameters, for example, calling the search operation with the following parameters: scope, search text, search options, and type filter.
Combining several expressions into a single expression. The results of calculation of one expression can be passed into another as arguments.
The redesigned Criterion Editor dialog reflects these enhancements.
Ability to create Duration, Interaction or Time Constraint:
You can now create a Duration, Interaction or Time constraint from the element Specification window.
Ability to hide Name Auto Completion list for DSL element:
You can now hide the list of already existing elements that appears when typing a name for a new element in the model. This list is typically needed only for elements which are displayed in several diagrams. To turn off this list for a specific element type, set the Do Not Suggest Name Auto Completion property to true while specifying the customization element.

New in MagicDraw UML 17.0.4 (May 23, 2013)

Usability Enhancements:
Increased usability of Dependency Matrices:
No Magic, Inc. is proud to introduce significant usability enhancements for Dependency Matrices. No Magic is known industry-wide for its focus on the user experience, and our easy-to-use, fast and very powerful Dependency Matrices are a tangible example of this.
In a Dependency Matrix you can now easily:
Change the scope of your analysis at any time by expanding and collapsing data hierarchies in both row and column headers.
Specify data filters (scope, element types, and dependency criteria) by dragging selected elements directly from the Model Browser.
Hide unneeded data filters by modifying appropriate property values in your dependency matrix Specification window.
See the full name and the owner of an element as well as details of a relationship on ToolTips.
Track and create indirect (transitive) relationships between elements by specifying Meta chain, OCL, or binary expressions as dependency criteria.
Trace elements that are associated by the relationship in the selected cell since the appropriate row and column are highlighted.
From now on you can have your own custom process supporting matrices. A new custom Dependency Matrix type can now be created in the same easy way as a new custom diagram – a special wizard will guide you through the development process. Be advised that the old Dependency Matrix templates mechanism is no longer supported.
Flexible inspection of model composition:
The latest version of MagicDraw includes a new mechanism for surveillance of your model composition, which is especially handy for larger projects. The mechanism includes tracking of potential model breakdowns as well as helps to solve model integrity issues.
With this enhancement, MagicDraw will supervise your actions and notify you in case of performing an action that might cause a model breakdown, for example, unresolved reference. Less recovered elements will unexpectedly appear in your model, and it will be easier to maintain the model integrity. The following figure shows several notifications that appear in case of potentially dangerous user actions: stop sharing a package, removing the content of a shared package, and moving elements from one module to another, when both modules are used in the read-write mode.
Users can customize their own sets of actions that should be supervised by MagicDraw to prevent the creation of recovered elements. A new option group named Composition Inspection has been added in the Environment Options dialog for this customization.
Already existing model integrity issues detected by MagicDraw active validation are now represented under the Composition Integrity violations group wherein the unresolved references are grouped by recovered elements they refer to.
The model integrity issues are by default inspected only in the project, but not in the modules it uses. For the extended inspection, which includes the modules you can change the inspection level from Standard to Advanced. Change the inspection level using the Composition inspection option that can be found in the Composition Inspection options group on the Environment Options dialog.
Easier modeling in Activity diagrams:
The following enhancements allow for easier modeling in Activity diagrams as well as help to maintain the consistency of the entire model:
You can now create an Activity diagram directly from the Smart Manipulator toolbar of a Call Behavior Action .
When creating an Activity diagram for the Call Behavior Action that has one or more Pins, Parameters for these Pins are created in a new Activity. In addition, Activity Parameter Nodes are created in the new Activity diagram and displayed on the Activity diagram frame.
Double-clicking a Call Operation Action now opens the Behavior diagram.
You can now easily navigate to the associated Parameter from the Pin shortcut menu.
Pins are now always displayed on Actions. In earlier versions of MagicDraw, Pins could be hidden, but hiding them could cause modeling issues in some cases.
From now on, you can easily specify a Pin type when dragging a Classifier onto an Object Flow.
You can now draw an Object Flow directly to or directly from an Activity diagram frame. As a result an Activity Parameter Node will be created with an Object Flow connected to it.
Incoming and outgoing flows remain connected after removal of the Action between them.
You can now see Object Flows that are connected to an Action via Pins in the Action Specification window as well as under the Display Related Elements and Display Paths commands on the Action shortcut menu.
Simplified Find and Find and Replace dialogs:
The latest version of MagicDraw features an enhanced Find dialog whose simplified GUI allows for easier setting of search criteria.
You can now search elements with one or more specific property values or elements whose textual properties either match or contain any entered text.
The Find and Replace dialog has been simplified accordingly.
Validation results grouping:
Validation results are now grouped by validation suites as well as the results are linked together.
Ability to search for matching phrase anywhere:
You can now search for a matching phrase throughout the entire name of the element in the element Selection dialog and drop-down lists. Just turn the Search matching anywhere mode on, as it is shown in the following figure.
More options for data representation in Relation Map:
Cut element names, if they are too long (the text exceeds reasonable length) and make the Relation Map difficult to read. See the whole name of an element on a ToolTip.
Reorganize graphs into well-formed trees, which show duplicate nodes to avoid cyclic references.
Ability to finish entering new element names by pressing ENTER:
There is no need any longer to click a free space on diagram pane in order to finish typing an element name. Press ENTER instead!
Performance Enhancements:
Faster merge operation:
Results of the most testing cases that had been performed on large projects showed that the merge operation is now performed up to 10 % faster.
Faster opening, saving, committing, and updating of project files:
Results of the testing cases that have been performed on larger projects to compare with MagicDraw version 17.0.2 SP3 show that
Opening a local or a server project is now 10-50% faster
Saving a project is now about 20% faster
Committing a project is now 20-30% faster
Updating a project is up to 90% faster (depends on number of changes made by other users)
Performance enhancements for dependency matrices:
Even in larger matrices that represent more than 1000 elements, scrolling is smooth and remarkably faster than in earlier MagicDraw versions.
There is no longer a delay when opening the filter selection or property value specification dialogs.
After modifying your model, only the visible matrices are now rebuilt as opposite to all of them. You will not notice any performance degradation since rebuilding is done instantly and therefore will not interrupt your other work in the project.
Java heap size optimization:
Java heap size for MagicDraw since now is automatically set according to the physical memory (RAM) size of your computer during MagicDraw installation.
Merge Enhancements:
Ability to merge projects including modules:
You can now merge projects including modules in one single operation rather than merging each module and finally the main project one-by-one as was the case in earlier MagicDraw versions. From now on feel free to split your larger teamwork projects into separate parts and easily merge their different versions. The nature of accepting and rejecting changes in both projects and modules is the same, so if you are familiar with the project merge, that’s all there is to it - try the new enhancement now!
Ability to turn off order changes detection:
Now before merging your projects, you can define, which properties you wish to exclude from the order changes detection. With this enhancement you are able to skip the unnecessary information analysis and save your time.
Enhanced Support for Enterprise Deployments:
New location of MagicDraw configuration files on Windows:
Be advised that as of the new version, MagicDraw configuration files on Windows operating system (OS) are no longer stored directly in the user's home folder. The files can now are be found in the Local Application Data folder, as it should be according to Windows OS recommendations.
See new locations of both MagicDraw configuration files and Teamwork Server projects on different Windows OS versions in the following table.
User Account Control (UAC) utilization on Windows Vista / 7 / 8:
In earlier MagicDraw versions, many users could not upgrade MagicDraw, install / uninstall a resource, or change the Java heap size parameters. It was not allowed at all or the message telling that it is not possible to modify the MagicDraw installation folder was used to appear. The reason of this problem was that users did not have sufficient rights to modify MagicDraw installation folder or even if they had such rights, the confirmation was anyway required.
From now on, MagicDraw uses the UAC technology to get administrative permissions to be able to change the installation folder. For example, the following UAC dialog opens when the user has no administrator rights.
Modeling / Diagramming Enhancements:
Stereotypes, constraints, tagged values, and element properties can now be displayed as labels of a Port symbol on a diagram.
Experience the remarkably enhanced automatic layout for the Class, State Machine, Protocol State Machine, Activity, and Composite Structure diagrams.
You can now draw a vertical separator on your diagrams as well as change a separator's position from to horizontal to vertical, and vice versa.
Enhancements for Collaborative Environment:
You can now quickly access the server project history as well as the latest version information such as comments, tags, modules, and meta information.
Using the enhanced discard changes operation, all newly created elements will be removed as well as removed elements restored while discarding changes.
The locking operation is now slightly faster since read-only modules are not updated.
Since now on you must have the Administer project permission, when you need to manage (create, rename, and remove) project branches or migrate projects to a later version.
Teamwork Server service successfully keeps running after logging off the server.
Teamwork Server is now more stable when started as a Windows Service.
ReportWizard Enhancements:
The Velocity Engine has been upgraded to a more stable version 1.7. Several bug fixes, better reporting, and less performance bottleneck are some of the improvements in the new Velocity Engine.
A new query tool has been added to ease the process of querying multiple data with conditions or a complex model. With the new query tool, it is now easier to find elements in MagicDraw.
The CSS 3.0 and HTML 4.01 support has been enhanced by adding colors in rgb() format, subscript, and superscript.
A new DocBook template is now supported. You can now add the DocBook template in Report Wizard.
The diagram overview elements have been equipped with a hyperlink that allows you to open them on a Web Publisher 2.0 report.
A new method to generate a child report template process has been added in the FileTool to enable synchronous report generation.
You do not need to manually declare the #import statement in the template code to include the template tools anymore. You can choose to automatically include the template tools in a template.
Locating icon files is much easier now that icon names have been replaced by a unique filename. Each MagicDraw element icon will now have a specific generated filename and the name will remain the same regardless of how many times you export it.
Report engines now generate reports 4 times faster and use 40% less memory than earlier versions.
Profile Changes:
As the old Dependency Matrix templates mechanism is no longer supported, files "matrix_templates_module.mdzip" and "Matrix_Templates_Profiles.mdzip" have been removed from \profiles.
MagicDraw built-in "UML_Standard_Profile.mdzip" has been reorganized. Inner Standard/System profiles "UML completeness constraints.mdzip", "UML correctness constraints.mdzip", and "Traceability Customization.mdzip" are no longer used, since their content has been imported into "UML_Standard_Profile.mdzip", and the files have been removed from \profiles.
Note: All your projects that have been created in any earlier version of MagicDraw will be successfully migrated once they are opened with the latest version of MagicDraw.
DSL Enhancements:
You can now create a DSL element with already specified short name - abbreviation. Use the new Abbreviation property to enter the short name while specifying the customization element.
You can now use DSL elements in Meta chain expressions.
You can now select a name of the opposite meta association end from the drop-down list when creating a Meta chain expression.
Other:
The numerical order is now used for sorting numbered elements in the Model Browser, Generic table, etc.
The Model Extensions, Inheritance, and Structure tabs are no longer on the Model Browser by default.
Non-open API Classes and Methods will be marked as Deprecated in your IDE.
Both importers and exporters of Eclipse EMF support the UML 2.4.1 specification.
The Multiple Windows interface style is no longer available in MagicDraw.
MagicDraw no longer supports project export to BPEL, the EJB generator, nor the integrations with ProActivity, CaliberRM, and Intellij IDEA.

MagicDraw UML Changelog

What's new in MagicDraw UML 2021x LTR Refresh2

New in MagicDraw UML 19.0 LTR SP4 (Jun 30, 2020)

New in MagicDraw UML 19.0 LTR SP2 (Apr 25, 2019)

New in MagicDraw UML 18.5 SP3 (Dec 19, 2017)

New in MagicDraw UML 19.0 LTR Beta (Dec 11, 2017)

New in MagicDraw UML 18.5 SP2 (Aug 29, 2017)

New in MagicDraw UML 18.3 Beta (Nov 13, 2015)

New in MagicDraw UML 18.2 (Nov 13, 2015)

New in MagicDraw UML 18.2 Beta (Jul 24, 2015)

New in MagicDraw UML 18.1 (Jul 24, 2015)

New in MagicDraw UML 18.0 (Jul 24, 2015)

New in MagicDraw UML 17.0.5 (Jul 24, 2015)

New in MagicDraw UML 17.0.4 (May 23, 2013)

New in MagicDraw UML 16.8 (Apr 30, 2010)

New in MagicDraw UML 16.6 (Oct 27, 2009)