...
Syndeia 3.2 made it possible for users to define custom mappings between artifacts types and attributes in different repositories, and use those mappings to govern model transformations, comparison, and synchronizations.
Syndeia 3.3 has now introduced the ability to define relationship mappings in addition to artifact mappings and attribute mappings. As a result, users can now map SysML relationship types (e.g. Containment, Part Property/Associations) to relationship types in other repositories (e.g. Jira link types - Blocks, Relates).
A general approach for using the mapping capabilities is presented below, followed by a list of hands-on step-by-step tutorials to get started with the mappings.
...
The mapping capabilities in Syndeia 3.2 3 are simple to set up and use. A general approach is presented below. Users are requested to review the tutorials available at Tutorials - Syndeia for Rhapsody for detailed step-by-step instructions.
Mapping Authors and Users
...
- Source Artifact Type and Target Artifact Type - Artifact types, originaing from two different model / repository types, that are being mapped. For example, SysML Activity is mapped to JIRA Task in the exampel shown below. It is mandatory to specify source and target artifact types in each mapping.
- Structure Level - Option to generate structure when transforming an artifact of source artifact type to the target model (and vice versa). In the example shown below, CHILDREN_RECURSIVE is selected. This implies that when a SysML Activity element (artifact) is used to generate JIRA Task artifact, the activity structure (call behavior actions) are used to generate linked JIRA issues recursively. The following options are available for Structure Level.
- NO_CHILDREN - Indicates that no children will be generated
- CHILDREN_IMMEDIATE - Indicates that only immediate children will be generated
- CHILDRENT_RECURSIVE - indicates that children will be generated in a recursive manner
- Attribute Definition Mappings - Mapping of attribute definitions of the source and target artifact types. In the example shown below, assignee, info, priority, and summary attribute definitions (tags originating from multiple stereotypes) on a SysML Activity artifact type are mapped to Assignee, Status, Priority, and Summary attribute definitions for JIRA Task artifact type respectively.
- Stereotypes - List of stereotypes to be applied to SysML artiact types participating in the mapping. The list of SysML stereotypes is used to derive the attribute definitions for the SysML artifact type (e.g. Activity) that can be mapped to attribute definitions of other artifact types (e.g. JIRA Task), as shown in the Attribute Definition Mappings.
- Relationship Mappings - Mapping of relationship types of the source and target artifact types. In the example shown below, assignee, info, priority, and summary attribute definitions (tags originating from multiple stereotypes) on a SysML Activity artifact type are mapped to Assignee, Status, Priority, and Summary attribute definitions for JIRA Task artifact type respectively.Attribute Definition Mappings - Mapping of attribute definitions of the source and target artifact types. In the example shown below, the Derived Requirement and Verified by relationship types in SysML are mapped to Derived from and Verified by relationship types in Jama.
...
- Jama (Part 7 - SysML-Jama Capabilities.),
- Jira (Part 8 - SysML-JIRA Capabilities.),
- DOORS-NG (Part 5 - SysML-DOORS NG Capabilities.),
- TM4J (Part 17 - SysML-TM4J Capabilities.), and
- TestRail (Part 15 - SysML-TestRail Capabilities)
- Teamcenter (Part 11 - SysML-Teamcenter Capabilities)
Limitations
There are 2 main limitations in the mapping capability in this version of Syndeia. We are actively working to expand the mapping capabilities and address these limitations in the next version of Syndeia.
...