leased on: January 15, 2015
Review all owned and inherited flow properties and directed features of the Proxy Port using new Direction property! You can find it in the Specification window of the Proxy Port.
The directed features are not included into combined direction of the Proxy Port by default. To include it set the Include Directed Features into Combined Direction of Proxy Port property value to true in the Project Options dialog.
If all features have direction "out" or "provided", the combined direction is "out". If all features have direction "in" or "required", the combined direction is "in". Otherwise the direction is "inout".
The Direction property is available in tables, matrices, criteria selection dialogs, reports, and open API.
Now directions of flow properties, Proxy and Full Ports can be easily identified in many places with help of direction prefixes.
The flow property direction prefixes are now displayed:
The Proxy Port direction prefixes are now displayed:
The Proxy and Full Port direction prefixes are now displayed:
All owned and inherited Ports and their Interfaces are now listed in one place! Manage them on the left of the Block Specification window > Ports/Interfaces. For detailed information about selected Port interfaces open its Specification window> Interface Block Properties.
Validation of Ports/Interfaces is more efficient now! It is easier to create the system with compatible connections between Ports because of additional validation of Ports/ Interfaces compatibility rules. They check if:
Invalid connectors are highlighted in red. Click on the smart manipulator toolbar and choose one of the suggested solutions.
The traceability of the Block, Signal, and Instance elements is much easier now! There are two ways to inspect those element usages in your model:
- On the left of the Block or Signal Specification window, click Usage In.
- From shortcut menu of the Block or Signal, choose Go To > Usage In.
- On the left of the Block Specification window, click Instances.
- From shortcut menu of the Block, choose Go To > Instances.
Block usage traceability
You can trace the Signal when it is used:
Trace all direct and indirect Instances of your Block.
Follow and double-click on the symbol with rake icon for faster navigation in the model! According to the SysML specification, the decomposition of model elements can be represented by the rake icon. It means a reference to a more elaborated diagram.
The rake icon automatically appears on:
The rake icon is shown by default on the symbol in the new SysML projects. To hide the rake icon set the Show Rake Icon value to false in the Symbol Properties dialog.
Indirect Part connections via Ports are now collected in the Connectors property group of the Part's Specification window. Inspect the list of connectors and modify their properties.
Now the Relation Map works like a Mind Map! You can use it not only to browse through a model, but also to create new elements with single click. The Structure Decomposition and Activity Decomposition maps became the fastest model creation tools.
TIP! To create elements faster and more easily:
When you copy a listed text, each item of this list becomes a new named element in your model (to simplify the creation, basic numbering and bullets are not reproduced in the model).
Elements can be created either in the Containment tree or on the diagram pane, as you can see in the following figures.
When you copy a table, each row becomes the corresponding element with its properties. If elements already exist in the model, the information updates.
You can create element groups and add or remove group elements quickly and easily.
When the Test Case is created, its return parameter for the verdict is created automatically.
In addition to newly created Usage In, Instances, and Ports/Interfaces property groups, the UML-oriented Attributes property group in the Block Specification window is now replaced with the SysML-oriented Properties property group. All owned and inherited Block properties are grouped as in the Block compartments.
Integrating custom MATLAB functions into the model is much easier now! Just drag the m-file icon to the diagram to create a Constraint Block, Constraint Property, or Call Behavior Action with corresponding function name and parameters.In earlier versions you could only drag the m-file on existing Constraint Block in Block Definition diagram.
NOTE. M-file must contain function declaration.
Appropriate layouts are applied for displaying parts on a structured classifier shape, if the Layout Parts check box is previously selected in the Display Parts dialog.
Changing search options in the Quick Find and Element Selection dialogs as well as in autocompletion lists is now easier and more efficient due to the following changes:
Keep your model valid and synchronized with your changes! The new synchronizations are introduced and the main element properties are now synchronized. In addition, the solving of the broken synchronization has been enhanced.
The Instance table UI was improved to allow easy and fast creation of composite Instances. Just click the Create Instance Specification button in the slot value cell and create an instance of the slot type instantly or choose from available subtypes.
Now the results of validation rule failures are marked in tables.
Starting from this version, module is referred as a used project. Keywords "used project" and "project usage" replace the keyword "module" everywhere in MagicDraw UI.
File format reflects changes made in UML metamodel.
The com.nomagic.magicdraw.sysml.util.SysMLUtilities class was added to the open APIs. It provides utility methods for easier work with SysML projects. For more information, see <MagicDraw installation directory>\openapi\docs.
An IntelliJ IDEA project with modules for developing two sample plugins was pre-configured and can be found in <MagicDraw 18.1 installation directory>/openapi/ide.
Now adjunct properties can represent State entry/do/exit behaviors and Transition effect behavior. From the State or Transition shortcut menu, select Tools > Adjunct Property > Create Adjunct Property for <...> to create adjunctProperty representing entry/do/exit behaviors or Transition effect behavior.
UML metamodel related changes
You can check the following lists of publicly available or your own reported issues fixed in version 18.1 FR:
Note: You will be required to login. Use same credentials as to your account.