no magic catia logo

1. SysML 1.2 Specification Support

MagicDraw family products have always been known for supporting the latest versions of standards and MagicDraw SysML plugin version 16.8 is no exception.

As MagicDraw 16.8 version introduces UML 2.3 specification support, SysML 16.8 plugin is capable of supporting the latest SysML 1.2/UML 2.3 specification changes of Conjugated Flow Ports metamodel and notation (see figure below).




All other new SysML 1.2 specification features that are not related to UML 2.3 specification are already supported in MagicDraw SysML 16.6 version.

2. Standard SysML Notation Cleanup

More and more books, papers and even OMG SysML specification diagram samples are done using MagicDraw SysML tool. It produces high quality scalable graphics, but contains several tool-specific notations that should not be used in vendor-neutral publications and requires manual post-editing.

MagicDraw SysML 16.8 version eliminates or changes all tool-specific notations:

  • <<elementType>> is now used instead of an element type icon in non-standard "Call Out" notation for Allocations.
  • Different property kinds of custom Block are now visually separated in compartments.
  • Solid lines of Control Flows in SysML Activity Diagram have been changed to dashed ones.
  • By default, diagram icons are invisible on the diagram frames.
  • By default, the Visibility attribute of each Role on an Association is not displayed on SysML diagrams.
  • SysML template now comes with the "OMG SysML" style. Use this style to create new SysML projects for publications.
  • "OMG SysML" style file (OMG SysML style.stl, located in /templates/SysML/ folder) is provided. To prepare SysML diagrams in an existing SysML project for publications, import this style into the project and then apply the style to such diagrams. Additional layouting may be required.

See the same SysML Block Definition diagram depicted below. The first picture shows the original diagram and the second picture shows the one ready for publication.






3. Improvements for Requirements Management

MagicDraw SysML version 16.8 makes requirements management even more effective:

  • New buttons for quick nesting-level of row(s) change in Requirements Table are added (for example, by simply clicking the button, you can change the level of requirement and make it a “child” of the requirement above). If automatic requirement numbering is enabled, the requirement's ID will also be re-assigned accordingly.



  • The whole content of each HTML-based Text cell is now displayed in Requirements Table.
  • Create a sub-requirement of a requirement directly in the table using the table toolbar or row shortcut menu.



  • Quick requirement search by ID is supported. See user guide for the instructions.
  • Automatic solvers for Requirements with invalid IDs (redundant) are provided.
  • Use the smart manipulator menu of a requirement when you need to create a new SysML Requirement diagram to provide more details on existing requirements.



4. Item Flow and Item Property Improvements

  • The GUI for adding an ItemProperty onto a Connector is redesigned to be more intuitive.
  • You can directly navigate from each Connector to the corresponding Item Flow(s) / Item Property(ies) through the "Go To" shortcut menu.

5. Traceability

Traceability is a new feature supported in MagicDraw SysML 16.8 version, including new derived properties, Relation Map, etc. Note, that the Relation Map is a very powerful tool for visualizing traceability (select Analyze > Create Relation Map in the main menu).

Important derived properties include:

  • Forward traceability properties.
  • Backward traceability properties.

5.1. Forward Traceability – Realization

Property nameDescriptionApplied forReference through…Value elements typeExample
Derived Requirements All requirements that are derived from the requirement, directly and indirectly. Requirement Relation: DeriveReqt Requirement
Traced From Requirements All requirements that the requirement is traced from, directly and indirectly. Requirement Relation: Trace Requirement
Refined By Requirements All requirements that the requirement is refined by. Requirement Relation: Refine Requirement
Contained Requirements Derived from all requirements directly and indirectly owned by the considered requirement. Requirement Ownership Requirement
Realizing Requirements,
All Realizing Requirements
Realizing Requirement(s) in one / all lower level(s) of abstraction showing how the Requirement is realized. Requirements are connected through one of the relations: Refine, DeriveReqt, Copy, Ownership. Requirement Relation: Refine, DeriveReqt, Copy
Ownership
Requirement -

5.2. Backward Traceability – Specification

Property nameDescriptionApplied forReference through…Value elements typeExample
Derived From Requirements All requirements that the requirement are derived from, directly and indirectly. Requirement Relation: DeriveReqt Requirement
Traced To Requirements All requirements that the requirement is traced to, directly and indirectly. Requirement Relation: Trace Requirement
Refine Requirements All requirements where the requirement refines them. Requirement Relation: Refine Requirement
Containing Requirements Derived from all requirements directly and indirectly owning the considered requirement. Requirement Ownership Requirement
Specifying Requirements, All Specifying Requirements More specific Requirement(s) in one / all higher level(s) of abstraction showing why Requirement exists. Requirements are connected through one of the relations: Refine, DeriveReqt, Copy, Ownership. Requirement Relation: Refine, DeriveReqt, Copy
Ownership
Requirement -
For more information or a quote
please contact
sales@nomagic.com
or call +1-214-291-9100.