Page History
Content layer | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Content layer | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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 How to use the Find feature in diagrams and navigate the search results.
Legends have been improved to allow a wider range of usage options. Now you can:
In this example, a legend is used to adorn Requirement table cells by Requirement status.
We are proud to announce that our tools support the new SysML 1.5 specification as of 19.0 LTR! The main change is the new concept of Abstract Requirement, which allows you to extend the Requirement concept and base it on any kind of model element. For an example, download the new Property Based Requirements.mdzip sample model.
|
Anchor | ||||
---|---|---|---|---|
|
You will be able to represent Association Block usages in the Internal Block Diagrams. Simply drag the Association Block from the model onto a Connector to set it as its type and automatically create a Connector Property symbol with a dashed line attached to the Connector.
Anchor | ||||
---|---|---|---|---|
|
All new SysML projects use:
Anchor | ||||
---|---|---|---|---|
|
You can now represent Association Block usages in the Internal Block Diagrams. Simply drag the Association Block from the model onto a Connector to set it as its type and automatically create a Connector Property symbol with a dashed line attached to the Connector.
Anchor | ||||
---|---|---|---|---|
|
The implied Connectors functionality is improved as follows:
Anchor | ||||
---|---|---|---|---|
|
When creating a new SysML Allocation Matrix, you can choose Definition or Usage mode. Accordingly, these modes display Allocate relationships either between Activities and Blocks or Actions and Part Properties. By default, the Create SysML Allocation Matrix dialog (see the figure below) appears each time you create a new SysML Allocation Matrix in SysML projects. Differently, when creating a new SysML Allocation Matrix in the MagicGrid project, the usage allocation matrix is created by default. You can change that by specifying the SysML Allocation Matrix Mode option value in the Project Options dialog.
Anchor | ||||
---|---|---|---|---|
|
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.
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:
Additionally, in this dialog you can preview any changes applied to your project without closing the 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. Learn more how to hide packages >>
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:
Anchor | ||||
---|---|---|---|---|
|
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:
For system engineers, it is also important that the ISO 80000 library is simplified for usability purposes. About 50 of the most useful units are suggested in the list,100x less than introduced earlier. Learn more about updates in basic units >>
Anchor | ||||
---|---|---|---|---|
|
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. Learn more about displaying paths >>
The Automatic Behavior Creation (renamed to Behavior Creation Mode) and Type Selection Mode buttons now work separately for each project. Learn more about Behavior Creation Mode >> Learn more about Type Selection Mode >>
Content block | ||
---|---|---|
| ||
Content block | ||
---|---|---|
| ||
Content block | ||
---|---|---|
| ||
Content block | ||||||
---|---|---|---|---|---|---|
| ||||||
News of earlier versions |
No Magic, Inc. Copyright © 1998 – 2025 No Magic, Incorporated, a Dassault Systèmes company – All Rights Reserved.