Date: Fri, 29 Mar 2024 12:07:15 +0100 (CET) Message-ID: <789297072.1954.1711710435282@nm-docs> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1953_2055590578.1711710435282" ------=_Part_1953_2055590578.1711710435282 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
=
R= eleased on: July 2, 2018
<= br>
Cameo Systems Modeler version 19.0 focuses on enterprise level scalabili= ty, integrations with other engineering products, and usability. No Magic, = Inc. always supports the latest standard versions. UML 2.5.1 and SysML 1.5 = will be supported in the upcoming version of the modeling tool and related = plugins, along with enhanced support of the ISO 80000 standard. For some ti= me now, No Magic has presented the MagicGrid method for MBSE. In this relea= se, MagicGrid will be available out o= f the box in our products. Dow= nload Cameo System Modeler today at nomagic.com, or co= ntact your sales representative. And please don't forget to give us = your feedback on LinkedIn, Twitter= or Facebook. Also, please check the documentation&= nbsp;and additional resources.
Methods and standards
Usability and infrastructure
We are proud to announce that our tools support the new Sys=
ML 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 concep=
t and base it on any kind of model element.=
For an example, download the new Property Based Requirements.mdzip sample model.
No Magic, Inc. always supports the latest standards. As of th= is version, modeling tool supports the new UML 2.5.1 specification<= /strong>! Several minor enhancements include:
Two new project templates are available in this version. They both accom=
pany MagicGrid, a new approach for MBSE developed here at No Magic, Inc.
MagicGrid supports performing problem domain analysis as well as building =
the solution for the logical system design, from stakeholder needs elicitat=
ion and capturing to the logical system design verification and technical r=
equirements specification for manufacturing. The approach is thoroughly des=
cribed in the MagicGrid Book of Knowledge, which will be available=
with the final version of 19.0.
The MagicGrid QuickStart template will guide you =
through the entire modeling process, starting with the problem domain defin=
ition and finishing with one or more solutions of the logical system design=
.
The MagicGrid Blank template will give y=
ou the predefined structure of packages for modeling with MagicGrid to use =
your time more efficiently.
Lea= rn how to create MagicGrid projects >>
No Magic is proud to present the Teamcenter Integration plugin. It = complements Teamcenter (Siemens product lifecycle management (PLM) software= ) with UML/SysML modeling capabilities provided by MagicDraw. The Teamcente= r Integration plugin includes the following features:
Teamcenter Integration plugin 19.0 LTR documentation >= >
Team= center Integration plugin 19.0 LTR version news >>
Beginning with version 19.0, Cameo Systems Modeler will be able to link = and share data using Open Services for Lifecycle Collaboration (OSLC) = integration. This means:
Please note, Cameo Dat= a Hub is required to use OSLC integration.
= Learn how to link elements >>
Learn how to&= nbsp;link model elements with OSLC resources >>
The Excel/CSV synchronization mechanism ensures continuous work between = Excel/CSV files and Cameo Systems Modeler tables. As of Version 19.0, you c= an manually sync data between Excel/CSV files and tables. Simply drag the Excel or CSV file in any table to= link it. You can map columns of Excel/CSV files and Cameo Systems Mod= eler tables and specify other synchronization options.
Learn how to sync with Excel or CSV files >>
The renewed mechanism of hyperlinks to model elements brings the ability= to embed live model hyperlinks in do= cumentation or other texts, numeric values into requirements, and ke= ep various expression and constraint texts up to date. Hyperlinks are updat= ed automatically or with your control after changing the referenced element= name. Additionally, it is now possible to embed hyperlinks to model elemen= ts in plain text fields, including constraint text, value expressions, etc.= Wherever you see this button , you can insert a hyperlink to element i= n the text.
This is very important for simulation. For example, in State Machines or= Activities, parameters are usually referenced. Once these parameters chang= e their names, Guards are updated automatically. This allows you to maintai= n model consistency.
Le= arn more about defining hyperlinks >>
Cameo Systems Modeler 19.0 provides the ability to search for textual&nb= sp;information in all types of diagrams, including tables, matrices and map= s. Open the search bar by clicking in a diagram toolbar, or simply press Ctrl+F. U= se this feature to find the desired text displayed in a large diagram and q= uickly navigate the search results.
Learn = more about searching in diagrams >>
Legends have been improved to allow a wider range of usage options. Now = you can:
Learn more about cre= ating and using Legends >>
All new SysML projects use:
L= earn more about model libraries >>
You can now represent Association Block usages in the Internal Block Dia= grams. Simply drag the Association Block from the model onto a Connector to= set it as its type and automatically create a Connector Property symbol wi= th a dashed line attached to the Connector.
Learn more about Connector Property >>
The implied Connectors functionality is improved as follows:
Learn= more about Implied Connectors >>
When creating a new SysML Allocation Matrix, you can choose Defi= nition or Usage mode. Accordingly, these modes di= splay Allocate relationships either between Activities and Blocks or Action= s and Part Properties. By default, the Create SysML Allocation Matr= ix dialog (see the figure below) appears each time you create a ne= w SysML Allocation Matrix in SysML projects. Differently, when creating a n= ew SysML Allocation Matrix in the MagicGrid project, the usage allocation m= atrix is created by default. You can change that by specifying the = SysML Allocation Matrix Mode option value in the Project O= ptions dialog.
Lear= n more about SysML Allocation Matrix modes >>
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 ten= d to get a library type or reusability flavor. A new cross project refactor= ing feature allows you to simply drag-and-drop selected elements from the m= ain project to a project residing in Project Usages. = All of the relationships that the elements have had still remain. This= new feature is also beneficial for users who need to move elements from the main project to a used on= e frequently.
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. F= or 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, c= omplete the immediate task and commit the changes, and then resume your wor= k on the previously suspended changes= et.
Managing project usages
You can now configure project usages for one or several selected used pr= ojects 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 Hi= dden Packages model cutting utility is presented. This utility lets = you specify which model Packages (and elements within them) should be hidde= n. Once specified, the non-hidden/public version of the model will be creat= ed by cutting/deleting the hidden parts. As a result, the stripped model wi= th only visible model elements is stored in a dedicated branch, which is co= upled with the main project branch. You can reuse projects with only visibl= e elements according to your needs.
Whenever you need to use a stripped model in other projects, the dedicat= ed branch is suggested by default so that you can select your project to re= use. Also, there is no need to worry about making changes to the main proje= ct. 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 c= hanges of the main project to the server. Learn more how to hide packages >><= /a>
Disconnected team collaboration
Disconnected teamwork collaboration is dedicated for multiple contractor= s without the ability to work on the same Teamwork Cloud installation to co= ntribute 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= em> file and send this file to another contractor for modification. After t= he file is sent back, you have the ability to update the same server projec= t from the local project. This life cycle may continue between any amo= unt 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 proje= ct. You can use the project being clo= ned as a "template" to create a new project or use it as an ind= ependent 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 us= ed projects (if there are any) are maintained.
Other enhancements and changes
In the current release, the collaboration working environment has been s= ignificantly improved. These include:
The Comment path is now displayed after dragging the Comment element= from the Model Browser to the diagram pane when enabling the Displ= ay Paths on Element Drop option in the Environment Option<= /strong> dialog. Learn more about displaying paths >>
The Automatic Behavior= Creation (renamed to Behavior Creation M= ode) and Type Selection Mode buttons now work sep= arately for each project. Le= arn more about Behavior Creation Mode >> Learn more about Type Selection Mode >>= ;
Development of the Cameo SOA+ plugin is= discontinued. However, you will still be able to load projects created in = earlier versions with this plugin in your modeling tool. The maintenance of the SoaML profile is continue= d and SoaML diagrams have been moved to the SoaML profile resource.<= /p>