The latest version of MagicDraw supports the latest version of the UML specification. For a summary of changes brought by the UML 2.4.1 standard including both UML metamodel and notation changes, click here.
Models which have been created using any MagicDraw version older than 17.0.1, can be opened up with this MagicDraw version as well. To update older models, simply open them with MagicDraw 17.0.1 and then save them. Models will be automatically converted and next time will be opened as UML 2.4.1 models. All the property values of these models will persist after the conversion.
Matrixes represent relationships between elements in a very compact way which allows for quick overview and analysis of the system being built. Matrixes display whether two model elements are related or not, and what kind of relationships they have.
From now on, relations and element properties can be directly edited in matrixes. Simply clicking on the selected cell allows for:
- Creating or deleting relationships between elements.
- Defining or removing element properties or tags.
This feature not only facilitates management of ordinary relationships between elements, but also allows for a faster creation of traceability links between elements, for example, between requirements and the architecture or requirements and test cases. Such an improvement saves huge amounts of time in comparison to linking elements in diagrams. It significantly increases applicability and usability of matrixes.
The validation results for relationships are now visualized in matrixes. Matrix cells are highlighted whenever relations violate validation rules. This feature is useful, for example, to check which test cases for requirements verification fail, to check if dependencies are valid or up-to-date when doing gap analysis.
The following figure depicts an example of an active validation results visualization on a diagram and dependency matrix.
QVT (Query/View/Transformation) is a standard defined by the Object Management Group for specifying model-to-model transformations. Model-to-model transformation is a key aspect in a model-driven development, and QVT is one of the most popular transformation languages.
The new QVT plugin significantly increases MagicDraw usability while working with model transformations. There is no need to export your model to EMF UML2 XMI in order to run a QVT transformation. From now on, you can run model transformations directly in MagicDraw - the QVT plugin uses the Operational QVT implementation that is provided by the Eclipse M2M project.
With this free plugin applied to MagicDraw you can run a QVT transformation script in one of the following ways:
- Via the Create Macro dialog (see the following figure), as the plugin supports the JSR 223-compliant QVT script engine.
- As a session in the Cameo Simulation Toolkit plugin.
- As a script or programming language that is supported in MagicDraw.
The new plugin supports transformations between models that are based either on the same metamodel or on different metamodels.
Note: For more information about the QVT plugin, please visit here.
TOGAF (Open Group Architecture Framework) is an open standard providing a comprehensive approach to the design, planning, implementation, and governance of enterprise information architectures.
In order to implement this standard, No Magic has developed and introduces for MagicDraw users a new free TOGAF plugin which provides:
- Fully featured enterprise architecture metamodel for content
- TOGAF diagram for content representation
- TOGAF project template
- Sample project
Note: For more information about the TOGAF plugin, please visit here.
Starting with version 17.0.1, MagicDraw provides you with a new and flexible generic numbering mechanism that can be applied to any DSL elements created in MagicDraw. The generic numbering mechanism allows you to:
- Automatically assign a unique number to the elements in the model when they are created, moved, or your model is refactored.
- Easily identify and find an element in the model when communicating with colleagues or stakeholders.
- Show an element's place in a hierarchy.
With this new feature you can easily:
- Customize currently applied numbering formats (schemes).
- Create and apply your own numbering formats.
- Change the numbering format while creating numbered elements.
As of MagicDraw version 17.0.1, the following new Open APIs are available:
- New APIs allow for accessing and working with the following functionality:
- Merge Plugin. APIs for standard and advanced project merging and differencing are provided.
- Selecting elements via the element Selection dialog. This allows creating, initiating, displaying, and using this dialog in custom plugins.
- Refactoring model elements. This allows converting an element to another one or replacing an element with another one.
- Displaying Related Elements in a diagram. Now MagicDraw plugins can display symbols that are related to a given symbol via relationships.
- Copying elements and symbols. Model elements and symbols can be copied either to another location in the same project or to another project now.
- Listening for all changes in a diagram using a single adapter. MagicDraw provides an API to listen to all diagram changes in a single adapter that receives events from all opened diagrams and delegates these events to your own listener.
- Adding custom environment options. This allows for adding custom environment options for MagicDraw.
- API for extending the Eclipse main menu with an additional command provided by a MagicDraw plugin.
- API for creating automatic test cases. This functionality allows users to create automatic tests to test custom MagicDraw plugins.
MagicDraw Open API User Guide and samples.
No Magic has released a new standalone MagicDraw Project Converter for customers who use MagicDraw version 9.x or earlier. This software is used to convert those versions' files to 17.0 format.
In MagicDraw version 17.0.1, performance of the project saving operation has been improved. Unless the project contains a lot of reversed code, users will see a performance improvement of 20%-800%.
- New actions for element locking in diagrams. When locking a symbol on a diagram in a Teamwork Server project, now you can:
- Lock both the diagram, which contains the symbol, and all its elements.
- Lock both the corresponding element and the diagram, which contains the symbol.
- Ability to view locked elements. Now you can manage, view, and filter project locks by user in the new Locked Elements tab on the Model Browser.
- Restricting automatic creation of user accounts in the server when it is integrated with LDAP. In earier versions, a user account in Teamwork Server was automatically created after the user had logged in to the server using LDAP. Starting with this release, you can choose whether or not user accounts should be created automatically via the LDAP Integration tab in the Teamwork Server Administrator's Console.
- Discarding project changes. In Teamwork projects, MagicDraw no longer freezes if a user has added new elements and decided to discard changes after that.
- Locking on a Mac operating system. From now on, modules of Teamwork projects can be locked without causing an exception on a Mac operating system.
- Authority of diagrams. In details of newly created Teamwork project diagrams, the project author logged on Teamwork is defined, not the person who is logged on the computer.
MagicDraw version 17.0.1 implements two major changes related to diagrams:
- The Object, Package, Component, Deployment, and Profile diagrams are now displayed in the MagicDraw GUI as separate diagrams. In earlier versions these diagrams were presented to the user as parts of other diagrams.
- Non-UML diagrams have been moved from the Custom Diagrams group into two newly created groups: Analysis Diagrams and Other Diagrams. User-created diagrams remain in the Custom Diagrams group.
Note: The Generic DDL and Oracle DDL diagrams as well as the Business Process diagram are not included in the latest version of the MagicDraw GUI. The Generic DDL and Oracle DDL diagrams have become a part of the Cameo Data Modeler plugin. Starting with this release, the Business Process diagram is available only in the Cameo Business Modeler plugin.
The new MagicDraw version introduces a significantly updated editor for multiline textual values. The enhancements include the following:
- It can be easily opened. All that needs to be done is either double-clicking a multiline textual value or clicking a specific button.
- All values are displayed and can be managed in a single place, i.e., the multiline textual values editor.
- A new value can be created / removed in a single click.
- Each value can be separately edited in the HTML mode.
- Values can be easily reordered.
- Spell checking is supported.
- Long values can be stripped for easier reading.
The Quick Start perspective from now on provides a much more simplified user interface than in earlier MagicDraw versions.
So if you are a new MagicDraw user and / or UML modeling beginner, do not miss the chance to learn basic modeling features in the improved Quick Start perspective, because:
- Only commonly used UML diagram buttons are displayed on the Diagrams toolbar.
- Only commonly used commands are displayed on menus (for example, main menu, shortcut menus).
- Only commonly used element buttons are displayed on diagram pallets.
Note:All UML diagrams and more commands on menus are available in the Expert mode of this perspective.
- A new option of the $image tool for automatically reducing size of an image to the paper size has been added.
- A lossless image transformation option has been added to the $image tool.
- A new template variable for retrieving a template name has been added.
- A new template variable for retrieving a use case number has been added.
- Report templates now also support Groovy Script.
- Content diagram hyperlink support in Web Publisher has been added.
- Permanent link URLs have been added to elements in Web Publisher.
- Generating a DOCX document of which the <a> HTML tags contain no href attribute will no longer create any error.
- Generating a DOCX document of which field code contains a VTL syntax will no longer create any error.
- The use case table section in the Use Case (Modern) template has been updated.
You can now choose what type of UML model elements will be used for CORBA Interfaces modeling. Either the UML Interface or the UML Class can now be selected as a base element for CORBA Interfaces in a model. In earlier MagicDraw versions, only the UML Class could be used as a base element for CORBA Interfaces modeling.
You can now be more specific when setting options for displaying not applied stereotype's properties in the Specification window of a model element. Displaying of these properties can now be configured to depend on:
- Profile application. Properties will be available only when a parent package of the model element has a corresponding profile application.
- Another stereotype and / or metaclass. Properties will be available only when some other stereotype is already applied on the model element.
Note: This is valid when usage by derived properties is ignored.
|Argument type||Parameter type|
|Literal Unlimited Natural||Unlimited Natural|
Because of this automation you will no longer need to change argument types manually after creating a call message.
There is no need for browsing to the desired location in the dialog twice anymore.
You are welcome to read option descriptions and save your time!
- A stereotype must be directly or indirectly contained in a profile.
- A signal reception must have a signal that handles it.
From now on, flows between input pins of structured nodes and owned actions are allowed in activity diagrams.
As of MagicDraw version 17.0.1, tooltip visibility has been improved. Word wrapping is now used when the text is long.
- Slot values can be created in a link specification without any exceptions.
- Operands for Alternative Combined Fragments can be created without any exceptions in sequence diagrams.
- In State diagrams, no additional signal events nor any redundant space are added after the guard expression has been modified.
- In a project, you can now move over opened diagrams using shortcut keys ALT + → or ALT +← without any exceptions.
As of version 17.0.1, information about code engineering sets with inner objects of these sets and code engineering options are stored in the MagicDraw project file *.mdzip, not in the separate *.mdr file as it was in earlier MagicDraw versions.
If DDL or XML Schema code engineering sets were used in projects created in earlier versions of MagicDraw, the Cameo Data Modeler plugin should be installed. From now on, the Cameo Data Modeler plugin supports these data modeling features in MagicDraw. For more information about data modeling, see Section 4.2.
Note: For more information about new features and improvements in the latest version of Cameo Data Modeler plugin, please visit here.
In the new MagicDraw version, C++ code engineering has been improved:
- Explicit macros defined for C++ code engineering now are project-specific only, rather than specific to the whole environment. You can easily share your projects on different computers as your defined macros will be saved with the particular project.
- While reversing your models to C++ code, HTML tags are parsed and stored as HTML documentation for the element in the model.
As of version 17.0.1, attributes and methods are CORBA stereotyped by default in CORBA IDL diagrams.
As of version 17.0.1, business process modeling is available only in the Cameo Business Modeler plugin. BPMN 1.x Business Process diagram has been removed from MagicDraw. To continue using your BPMN 1.x Business Process diagrams, convert them to BPMN 2.0 Business Process diagrams with the Cameo Business Modeler plugin.
Note: For more information about the Cameo Business Modeler plugin, please visit here.
As of version 17.0.1, data modeling features (DDL and XML Schema diagrams as well as their associated code engineering features and transformations), have been transferred from MagicDraw to the Cameo Data Modeler plugin which until now provided users only with the ER modeling features. If any DDL (renamed to SQL in a new version) and/or XML Schema features were used in earlier versions of MagicDraw, the Cameo Data Modeler plugin should be installed when upgrading MagicDraw to version 17.0.1.
From now on, this plugin is free of charge only for existing customers of MagicDraw Architect and Enterprise editions.
Note: For more information about new features and improvements in the latest version of Cameo Data Modeler plugin, please visit here.
MagicDraw is always compliant with the newest standards and the newest technologies. As of version 17.0.1, MagicDraw is compatible with Eclipse 3.7. Earlier Eclipse versions are not supported as well as products based on earlier Eclipse versions. Support for Embarcadero JBuilder integration has been discontinued.
Watch the new Generic Numbering Feature demo!