Model-based requirements engineering brings the value of:
With this plugin you can:
For more information, visit the Cameo Requirements Modeler Plugin page.
Glossary saves time by ensuring consistent usage of terminology in the organization. It also improves the communication between team members since terms are understood in the same way and definitions become visible everywhere the terms are used.
Creating a term is quick and easy. Just do one of the following:
After terms are defined in the glossary, it is easy to use them in your project. Just press Ctrl+spacebar while typing to get a list of available terms.
For your convenience, a term description becomes visible when you move the pointer over this term.
Publish your project as interactive web portal and share it with stakeholders, including even those who are incapable of reading models in MagicDraw!
The published web portal eliminates less needed elements from the model tree and proposes the most relevant views of software engineering project, such as Glossary, Requirements, Architecture, and Implementation. So you can discover your project in user-friendly and easily browsable environment.
Use quick search to find elements and diagrams for viewing their custom contents and share this information with colleagues. Provide feedback on any element or diagram.
Publishing the project as a web portal is as easy as generating any report. On the main menu, click Tools > Report Wizard, select the Software Engineering Portal template, and follow the steps of the report wizard. Then place the output in a shared directory or on web server to make it available for colleagues.
IMPORTANT! The Software Engineering Portal template is only available in MagicDraw Enterprise edition. In other editions, MagicDraw provides a demo version of this web report template, which can contain, at most, 10 symbols per view.
NOTE. This is a technology preview of the software engineering portal. Please explore this new portal, experiment with it, and get back to us at support@nomagic.com with your feedback and suggestions about possible improvements or features you are missing. We seek to create as serviceable tool as it could be, so we are thankful and very appreciative of your contributions!
With this new approach you can
Creating a new elementary metric suite is as simple as creating a new class with a couple of stereotyped attributes: one for parameter definition and one for metric definition.
The parameter definition can be any model element or a primitive type, such as real or integer. The metric definition, that is, a formula for calculating metrics, can be easily specified either as a structured expression (by using the operations of the expression evaluation engine) or as a script operation written in any script language supported by MagicDraw (for example, JavaScript, Jython, Groovy). Moreover, one metric definition can use the results of other metric definitions.
Once the metric suite is created, you can calculate the metrics for a selected element. Analyze the results of the calculations, that is, metrics, in a metric table, which is automatically created for these metrics representation. You can easily reorganize the columns of the table, calculate new metrics, and recalculate the existing metrics with other parameters.
The recent enhancements for modeling efficiency saves time, which allows focusing on what to model, but not how to model and keep the result well-formed:
Now you can get professional-looking diagrams quickly, without the need to adjust the path layout manually. When drawing new paths, reconnecting or moving paths, or resizing connected shapes, the automatic layout does most of the work in optimizing the routes for these paths, so you can focus on model creation.
Here are the rules of the new path behavior:
Also, now you can make the route of a single path or the routes of all the paths connected to a selected shape rectilinear with just one click.
Got lost between open diagrams? In earlier versions, every diagram could open only in a new tab. Now you can choose to open diagrams either in the same tab or in a new tab – just like in the most popular Internet browsers.
Here are the benefits of using the tabbed browsing:
Different aspects of the system (for example, requirements, architecture, test cases, domain models) can now be analyzed in separate tabs. Both backward and forward navigations are supported for each aspect (tab) separately. Navigation does not open new tabs by default, which greatly helps in limiting the number of open tabs.
Spending too much time searching for the specific diagram to create? Now you can create any diagram you want in just a few seconds despite the number of diagrams! Simply click the Create Diagram button (or press Ctrl+N), type the first letters or a part of the diagram type name, and press Enter.
The enhanced Camel Case mode in Search engine makes the diagram creation even faster, as it allows:
Simplified and unified UI for symbols manipulation makes the symbols customization easier and intuitive:
Now you can see how your shapes or paths changes immediately after modifying their symbol properties without closing the Symbol Properties dialog. Also, while the dialog is open you can still work with diagrams or other dialogs. The ability to group the properties by display modes (Standard, Expert, All) allows the hiding of unnecessary properties, thus making the dialog simpler and faster to use.
Now you can define any package as scope for your table. All the elements in this package will be automatically added to the table; subsequent elements created in this package will also be added to the table.
Nodes are movable and branches are expandable even in read-only Relation Maps.
Inherited members, such as attributes, operations, signal receptions, ports, literals, and extension points, can be easily identified on element's shape. They are now denoted with the caret "^" sign.
The main toolbar and the diagram toolbar have been reorganized and minimized:
On the main toolbar, the single Create Diagram button has replaced the cumbersome diagram toolbars thus minimizing distractions.
On the diagram toolbar, rarely used buttons have been removed and the groups of buttons have been moved under a single button.
Less used option buttons became commands of the new grouping toolbar button and are now by default hidden.
Drawing several symbols of same type consecutively has been simplified. Now instead of clicking the Sticky button, you can press the Shift key. While holding the Shift key, click the element button on the diagram pallet and then click the diagram pane – with each click, the new symbol of the same type will be created.
Cannot see the Make Preferred Size smart manipulator on big shapes? Now the smart manipulator is always displayed on any of the visible borders. Just select the shape, and the manipulator appears at the right of the shape’s horizontal border or at the bottom of the vertical shape’s border.
Element shape can now display the image of the element type, such as Activity Parameter Node, Call Behavior Action, Collaboration Use, Instance Specification, Lifeline, Part, Swimlane, or Object Node.
The illustration displays concepts from SysML Plugin.
Two connected shapes of the same type can now be easily swapped in Activity or State diagrams.
A new option has been added to enable the automatic ports display.
The illustration displays concepts from SysML Plugin.
Forget the long workflow when assigning an already created behavior to operation! Now you can now easily create and assign an operation to any owned behavior directly from the Specification window.
Tracing between the related elements is now easier, since you can navigate:
Dragging an Interaction to an Interaction Use on diagram pane makes the specification of the referred Interaction for this Interaction Use easier.
With the help of an instance table you can easily:
All that needs to be done is creating an instance table, adding the instances, and then choosing the slots to review and edit. This form of reviewing and editing data will definitely save a lot of time, as opening the Specification window of each instance is no longer required.
The illustration displays concepts from SysML Plugin.
No Magic, Inc. presents a technology preview of Document Modeling Plugin, which the main purpose is to assist in the modeling of the document structure. This plugin is familiar to system engineers as concepts from the OMG SysML standard are used. However, it is designed not only for systems engineers, but also for systems analysts, systems architects, and other persons who need to model a document structure for the specific project.
Document Modeling Plugin allows reviewing the prepared document structure in the document preview dialog and saving the document as a .pdf, .html, or .xml file. This plugin also allows you to:
Document Modeling Plugin provides:
NOTE. This is a technology preview of the document modeling functionality. It is not intended for use in the production environment. Please explore this new technology, experiment with it, and get back to us at support@nomagic.com with your feedback and suggestions about possible improvements or features you are missing. We seek to create as serviceable tool as it could be, so we are thankful and very appreciative of your contributions!
Administrative tasks, such as users, projects, and permissions management, can now be performed by using a new command line utility - teamwork_console.exe.
The ability to access the server administration functions in this new way facilitates the scriptable management of Teamwork Server. This enables the automation of routine administrative tasks, such as permission management, and improves integration with external identity sources. For example, it is now possible to retrieve group information from LDAP servers and set permissions accordingly in MagicDraw Teamwork Server.
MagicDraw 18.0 is not compatible with OS X Leopard and Snow Leopard, nor with Java SE 6. Although, Java SE 6 based code engineering is still supported.
MagicDraw 18.0 and Eclipse integration is not supported for OS X. The integration fails to run because of technical issues related to Java SE 7, which is the only Java version compatible with MagicDraw 18.0. Although, the standalone MagicDraw 18.0 runs on OS X with no problems.
MagicDraw 18.0 integration with NetBeans IDE is not supported. If you need this integration, you are welcome to use MagicDraw 17.0.5 or earlier.
The obsolete use case numbering is no longer supported, and all the use cases are now numbered using the approach, which is based on the generic numbering mechanism.
Executable files of MagicDraw and Teamwork Administrator's Console are no longer stored in the same location. All the files of Teamwork Administrator's Console have been moved to the collaboration folder in the MagicDraw installation directory. Developers of MagicDraw extensions will no longer be confused trying to determine the right path to the MagicDraw executable file!
File format has been adopted to UML 2.5 support related changes:
Stored elements format has been changed to reflect minor changes in the metamodel. See Metamodel Changes for details.
URIs have been changed for profiles. The new URIs are as follows:
StandardProfileL2 and StandardProfileL3 have been merged into StandardProfile. All references to any element from these profiles now uses the xmlns:StandardProfile URI.
UI of diagrams' windows management, symbols' compartments management, and elements creation in compartments have been refactored. As a consequence, some actions have been removed from the com.nomagic.magicdraw.actions.ActionsID interface and new actions have been added.
IDs of the removed actions are as follows:
Types of parameters have been changed from Set to Collection, because of performance related improvements in methods of the following interfaces:
The com.nomagic.magicdraw.expressions.ExpressionHelper class has been added. It provides utility methods to use in queries defined with the StructuredExpression language (used by smart packages, derived properties in DSL, and so forth).
The com.nomagic.uml2.ext.jmi.helpers.InteractionHelper class has been added. It provides utility methods to access Interactions part of UML metamodel.