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. Role-based tables
1.2. Measurement value display
1.3. Library of industrial symbols
1.4. The Complete Step-By-Step Modeling Guide
1.5. Inheritance of Exchanges
1.6. Possibility to decompose State Machine and Sequence diagrams
1.7. Notification Window
1.8. Multilevel selection in Display Parts dialog
1.10. Predefined relation maps
1.11. Synchronized deletion from BPMN diagrams and models
1.12. Reply and Initiating messages support in Collaboration diagram
1.13. Parallel Event-Based Gateway
1.14. Quick specification of property values
1.15. Business Architecture Report
1.16. Choreographies export to BPMN2 XML
2.1. Easier relationship creation and property value assignment
2.2. New spreadsheet reports
2.3. Simplified Print dialog
2.4. Possibility to transform customized Activity diagrams into Business Process diagram
2.5. Enhancements for Generic Table
3.1. Project Usage Map
3.2. Automated tracking of usages
3.3. Ability to approve automatically used module
3.4. Data synchronization between Teamwork Servers on different sites
3.5. Template for structured projects
3.6. Project Integrity Correctness suite
The OV-3, NOV-3, SV-6, NSV-6, and SvcV-6 tables now can be role-based as well. A role-based table represents exchanges between roles (nodes or resources).
You can now display and edit measurement values in the note or comment as well as in the compartment of an element.
As of this version, you can apply industrial symbols to your nodes, performers, and conceptual roles.
As of version 17.0.3, a new set of completeness rules is introduced. These rules are to guide you step-by-step while you create your UPDM model. If you are an advanced user, you can simply switch off this capability.
Starting with this version, the Operational Exchanges and Resource Interactions are inherited.
You will be able to see the inherited exchanges in
- Operational Exchange or Resource Interaction Manager
- Role-based tables OV-3, NOV-3, SV-6, NSV-6, and SvcV-6
Earlier versions of Cameo Enterprise Architecture 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, Cameo Enterprise Architecture 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.
The Display Parts dialog has been enhanced to support infinite levels of the composition tree, enabling quick selection and displaying of any deep-nested parts in IBD and Parametric diagrams.
Moreover, automatic pathname dot notation will be generated when deep-nested parts are selected without also selecting their owning blocks / parts.
“SysML-Lite is a simplified version of the language to help people get started modeling with SysML, but is not part of the SysML standard. It includes six of the nine SysML diagrams, and a small subset of the available language features for each diagram kind. SysML-Lite provides a significant modeling capability.” -
A Practical Guide to SysML, 2nd Edition, Chapter 3.3.
The standard mode of the System Engineer perspective has been simplified according to the SysML-Lite description to reduce the learning curve of new system engineering team members.
Note: To enable the full set of SysML concepts, open the Select Perspectives dialog (click Options > Perspectives > Perspectives on the main menu), and switch the System Engineer perspective to the Expert mode.
The predefined set of relation maps to increase traceability of system requirements and design elements.
The relation map is a special kind of diagram that automatically updates and renders an elements dependency tree according to predefined dependency criteria.
Cameo Enterprise Architecture version 17.0.3 adds predefined maps for:
- Activity Decomposition analysis
- Instance Tree traversal
- Nested and derived Requirements
- Structure decomposition (alternative to the Structure tree in the Model Browser)
The following figures depict two examples of the predefined Relation map: the Activity decomposition map and the Subsystem decomposition map.
One of the most beneficial features in this version of Cameo Enterprise Architecture is the synchronized deletion that applies to both BPMN diagrams and their models. When the last element symbol is deleted from a diagram, the element data are automatically deleted from model without interrupting dialogs. This enhancement allows the user to therefore save the time required to delete extraneous elements from model manually. Also, this improvement will prevent incompatibilities between model and diagram, which is very important when the model is exported to BPMN2 or XPDL formats.
It is now easier to indicate initiating and reply messages in the Collaboration diagram. Initiating messages are white-colored, while reply messages are in grey.
To change the message type, change the Message Type property value in the Message Specification dialog.
Starting with version 17.0.3, the Parallel Event-Based Gateway notation is supported.
To change an event-based gateway type, change the value of the Event Gateway Type property in the event-based gateway Specification dialog.
Starting with Cameo Enterprise Architecture version 17.0.3 you can use drag-and-drop operations for more quick modeling:
- Dragging Resource Role on Task, SubProcess or CallActivity adds Resource Role to Task, SubProcess or CallActivity property Resources values list.
- Dragging BPMN Process on Call Activity assigns BPMN Process to Call Activity property Called Element value.
- Dragging Global Task on Call Activity assigns Global Task to Call Activity property Called Element value.
- Dragging Class on Data Object assigns class as Data Object type.
- Dragging Choreography on Call Choreography assigns Choreography to Call Choreography property Called Choreography Ref property value.
- Dragging Global Choreography Task on Call Choreography assigns Global Choreography Task to Call Choreography property Called Choreography Ref property value.
In this version, Cameo Enterprise Architecture adds a new report template Business Architecture Report. This report provides business data, organization structure, participants, and BPMN2 diagrams export to a document file. The report consists of the following sections:
- Business Data
Business data classes descriptions with a class name, documentation, and class attributes are listed in this section.
- Organization Structure
Organization structure diagram images are displayed in this section and involved participants, organizations, posts, and persons are described after each diagram.
All the processes’ descriptions are provided in this section. A process description includes a list of involved participants, performed activities and used data elements shown in a tabular form.
This section contains a Collaboration diagram with a table of participants, message flows, and the messages used between pools. Conversation node descriptions are also included in the report.
Choreographies’ descriptions with diagrams, involved participants, and choreography activities descriptions are provided in this section.
In Cameo Enterprise Architecture version 17.0.3, you can export BPMN choreographies as BPMN2 XML files. The BPMN2 XML is a format for interchanging BPMN2 models between tools in order to perform any further model simulation, execution, or deployment.
The drag-and-drop enhancement allows for creating relationships or assigning property values by dragging one element onto another right in the diagram pane. There is a number of predefined rules to create relationships or assign property values automatically. You may also set up your own drag-and-drop specifications between any elements.
From now on, all active OV-3, NOV-3, OV-6a, NOV-6a, AV-2, NAV-2. SV-6, NSV-6, SV-10a, NSV-10a, SOV-4a, StV-5, CV-5, SvcV-10a, SV-7 Actual, SV-7 Typical, NSV-7 Actual, NSV-7 Typical, SvcV7-Actual, and SvcV-7 Typical tables can be exported into the spreadsheet report.
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 usable functionality is now available on one dialog.
The transformation capabilities of the Activity diagram have been expanded. Now not only UML Activity diagrams, but also customized Activity diagrams can be transformed into BPMN Process diagrams.
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.
The Architectural Framework option was moved to the Project Options dialog.
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.
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 Cameo Enterprise Architecture runs on Mac OS X Mountain Lion. Just click the button on the upper-right corner of the Cameo Enterprise Architecture window.
Attributes of ValueType are available in the Specification window and BDD diagram allowing quicker creation of complex data types.
Enumeration as ValueType is added into the BDD diagram toolbar.
A Nested Requirement diagram with the parent requirement displayed can now be created from the New Diagram shortcut menu.
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 find out 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 Cameo Enterprise Architecture 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 - Cameo Enterprise Architecture 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 Cameo Enterprise Architecture, you will need to refactor your module structure to reap the benefits of this feature.
In earlier versions of Cameo Enterprise Architecture, 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 Cameo Enterprise Architecture. 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 new 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.
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.
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 Cameo Enterprise Architecture 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.
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.
QUDV library is updated according to http://www.omg.org/spec/SysML/20120401/ISO-80000-1-QUDV.xmi
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 Cameo Enterprise Architecture versions. The performance has been increased as follows:
- Loading a project - up to 5 %
- Saving a project - up to 20 %
The latest version of Cameo Enterprise Architecture 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 Cameo Enterprise Architecture versions.
Earlier versions of Cameo Enterprise Architecture 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 Cameo Enterprise Architecture 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 Cameo Enterprise Architecture 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.