Release date: 10th December 2012
For the description of the FR (Feature Release) and LTR (Long-term Release - Gibraltar),
please read the article No Magic Introduces New Gibraltar Long-Term Releases.
1.1. Project Usage Map
1.2. Automated tracking of usages
1.3. Ability to approve automatically used module
1.4. Data synchronization between Teamwork Servers on different sites
1.5. Possibility to decompose State Machine and Sequence diagrams
1.6. Notification Window
1.7. Template for structured projects
1.8. Spreadsheet reports for generic tables
1.9. Project Integrity Correctness suite
The Project Usage Map is a live visual graph that represents Teamwork Server project usages as well as identifies potential problem areas.
The Project Usage Map allows for representing projects and their dependencies in two views:
- The All Projects view that shows all projects and all the dependencies among them.
- The Individual project view that shows a particular project along with other directly and indirectly used modules.
Using the Project Usage Map you can easily do the following:
- Identify, analyze, and validate dependencies among projects (for example, you can easily discover all the projects, wherein a particular module is used).
- Identify cyclic dependencies among projects.
- Identify and fix inconsistent dependencies among projects.
In earlier MagicDraw versions, rearranging the module composition (i.e., removing submodules, merging their content, etc.) caused usage problems in the projects that used the module and directly referenced to the content of its submodules (even in the read-only mode; more so in the read/write mode). The owner of the project had to solve these problems manually by retargeting the usages of submodules whenever the module owner had changed the module composition.
As of this version, in most cases retargeting of usages is done automatically while loading or reloading the project and it is transparent to the user. Thus the module owner can now refactor the composition of his complex module without worrying that this will break all the other projects using the module - MagicDraw will automatically update usages and project owners will not have to do any additional work!
Note: If you already have projects with complex composition (having modules / submodules) that are prepared in any earlier version of MagicDraw, you will need to refactor your module structure to reap the benefits of this feature.
In earlier versions of MagicDraw, upon editing a module with read / write permissions, additional usages were created automatically and without any approval by the user. So there was a risk that some unneeded inter-module usages might have been added by accident, causing such problems as cyclic module usages, references back to private project parts, unexpected expansion of the scope of other projects, and so forth.
In the latest version, the user is prompted to approve or reject any automatically created module usage.
The automatically created usage is now considered unapproved, if it is unsubstantiated by any real module usage path. These kinds of usages are captured by a special validation rule that has been predefined in MagicDraw. The user can then choose whether he / she wants to approve the usage and make it a real one or reject it by changing the underlying model reference.
The latest version allows synchronization of data among several Teamwork Server deployments. Projects available on one Teamwork server can now be accessed as read-only replicas by other Teamwork Servers that are deployed on remote sites.
This is extremely useful for a multinational organization that has departments all around the world. One server can be set up per each department with synchronization among them. Employees of each department can access (read or link to their projects) projects created by other departments on their local server (giving the LAN-level access performance).
Data synchronization between servers can be performed periodically at intervals specified by the Teamwork Server administrator.
The following figure depicts an example of data synchronization between two distant Teamwork Servers.
Note: The data synchronization can be performed only on the Native repository type.
Earlier versions of MagicDraw only supported extracting in Activity and Composite Structure diagrams. With the new version, this kind of refactoring is supported in two more UML diagrams. You can now extract any selected part of a State Machine* or Sequence diagram into a separate one, which represents a new state machine or interaction appropriately.
We expect that exploiting this kind of refactoring will improve the reusability and readability of your model since:
- Some parts that often appear in many diagrams (for example, a part of a Sequence diagram describing the user logging on) can now be extracted into a separate diagram for further reuse.
- Large diagrams can now be easy simplified by extracting their most complicated parts into separate diagrams.
Note: This feature is available only in Enterprise and Architect editions.
* Including a Protocol State Machine diagram.
As of the new version, MagicDraw introduces the Notification Window (to open it, select Window > Notification Window from the main menu), which is designed to store the history of all environment and project specific messages as well as messages received from other team members.
You can now create a structured project template in order to jump-start the creation of structured project.
Creating a structured project from a specific template takes less time since you do not need to worry about its structure. Additionally, the brand new project already has all the required modules. This is especially handy for organizations that work with many projects with the same structure.
You can now export your active table to a Microsoft Excel Workbook (an .xlsx file) and have a WYSIWYG style spreadsheet report.
This new validation suite allows for detecting integrity issues in your project composition, such as the following:
- Cyclic dependencies among modules
- Mount location inconsistencies in used modules
- Required version inconsistencies in used modules
Inspect your projects with this suite and discover even more by using the all-new Project Usage Map.
Changes of a Teamwork Server project can be either saved locally or committed as a new project version to the Teamwork Server using two separate actions via:
- The Collaborate menu
- The Collaboration toolbar
- The File toolbar
With this enhancement, it is now more convenient to save a Teamwork Server project locally in the so-called offline mode than is was in earlier versions. Moreover, saving intermediate project changes locally and committing all changes at once (for example, once per day at the end of the work) instead of committing each intermediate modification to the server can significantly help to decrease traffic that is generated on the network.
From now on, any recent Teamwork Server project can be opened by one click in one of the following ways via:
- The Collaborate menu
- The Welcome screen
- The File menu
Two dialogs have been reorganized in order to simplify adding and committing projects to the server.
As of the new version, the Commit Project to the Server dialog allows for:
- Reusing any comment from recent commits
- Keeping locks for further modifications
- Saving your project locally
The Add Project to the Server dialog has also been changed in order to be consistent with the Commit Project to the Server dialog.
In earlier versions, the user could reconnect to the server after MagicDraw had stopped responding only when the time-out period was over. Moreover, he / she was unable to reconnect to the server from one workstation by closing his / her own already-existing session from another workstation.
From now on, you can close any session of your own when attempting to create a new connection. There is also a possibility to close any user session via the Teamwork Administrator's Console.
You will no longer need to open other dialogs, when you have to change various printing options (for example, select another printer or choose different page orientation and format). All the most used functionality is now available on one dialog.
You can now do the following:
- Search either in the scope of the whole table or in the scope of a single column. This is especially useful for large projects wherein generic tables can contain more than a thousand elements.
- Set element type automatically by dragging the element to the table.
- Display the fully-qualified names in cells.
You can now add any address (not only HTTP addresses) as a hyperlink to an element by using the Edit Hyperlink dialog. Note, that the appropriate tab name has been changed from Web page to Address.
The Display Parts dialog was enhanced to display any depth of a structure. You can select parts either individually or recursively. To select a part recursively, hold down SHIFT while selecting the part.
All symbol styles from loaded modules are now listed in the Project Options dialog. You can now see the exact locations where symbol styles are defined and can be modified.
You can now display the related elements for all the selected elements at once.
You can now turn on the diagram full screen mode, if your MagicDraw runs on Mac OS X Mountain Lion. Just click the button on the upper-right corner of the MagicDraw window.
From now on, you can select one from the list of existing pins or a pin will be automatically created when drawing a new object flow. This enhancement allows for easier modeling in Activity diagrams as well as helps to maintain the consistency of the entire model.
You can now easily show or hide stereotypes on a symbol. All that needs to be done is to add them either to the Selected list or to the Hidden list in the newly created Stereotypes tab on the Compartment Edit dialog.
With this enhancement, you can now display on a diagram
- Links created between instance specifications (the Display Paths command on the instance specification shortcut menu).
- Instance specifications at the other end of a link (the Display Related Elements command on the instance specification shortcut menu).
Links can now be represented in the Relation Map and Dependency Matrix.
You can easily show or hide slot values. The following figure briefly illustrates the way this can be done.
Deletion from Activity diagram and model is now synchronized. An element, such as Activity Node, Activity Group, Activity Edge, or Expansion Node, is now removed from your model, when its last symbol is deleted from the diagram.
Element properties can now be displayed on the element shape. As shown in the following figure, you can select properties to be displayed on the element shape via the new Element Properties tab on the Compartment Edit dialog.
As of the new version, the enhanced DSL customization profile allows for specifying
- Custom drag-and-drop operations. You can now set up your own drag-and-drop specification either to create relationships between various elements or assign one element as a property value of another.
- DSL stereotype visibility on symbols.
Projects having a lot of tagged values are now saved and loaded significantly faster than in earlier MagicDraw versions. The performance has been increased as follows:
- Loading a project - up to 5 %
- Saving a project - up to 20 %
The latest version of MagicDraw can detect equivalent changes when merging so that the changes that depend on the equivalent changes can now be accepted. This new capability of the merge algorithm significantly increases the merge usability as you can accept more changes than in earlier MagicDraw versions.
Earlier versions of MagicDraw could not display exact changes of textual values when merging or comparing models. You could only see if a value has been created, modified, or deleted. In order to find the exact changes, you had to read both texts and identify conflicts manually. So it was rather complicated task to compare long texts in element properties (for example, element documentation, comments, pre and post conditions of a use case and so forth).
The latest version of MagicDraw solves for the problem. You can now see the differences between compared texts in a single dialog, where inserted and deleted parts of the text are appropriately highlighted.
- Jython has been upgraded to version 2.5.3 in MagicDraw Open API.
- Java code engineering model libraries and project templates have been upgraded to support Java SE 6, Java SE 7, and Java EE 6.