Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Objectives

The new learning objectives of this exercise are to use a Data Map connection to create a SysML block from an existing JIRA issue and to use it to update block attributes. This exercise uses the default SysML-JIRA mapping; greater flexibility may be achieved using custom SysML-JIRA mappings (see Exercises 8.4 and above).

Preparation

This exercise assumes the student has

  • IBM Rational Rhapsody 8.2 installed correctly on his or her machine with a valid license for use, and

  • Syndeia 3.3 installed as a plugin for Rhapsody with a valid license for use

  • Syndeia JIRA interface, correctly installed with a valid license for user.

We will use the provided Rhapsody project Syndeia_JIRA_Mapping_Tutorial.rpy (Get it here - SysML Models, Profiles and Mappings.). The user can use any JIRA repository they have available with the ability to create and edit issues within a JIRA project. It is generally advisable to carry out these exercises in a non-production repository, a "sandbox", set up for training and practice purposes.

Exercise

  1. If not already open from the last exercise, open Syndeia_JIRA_Mapping_Tutorial.rpy (Get it here - SysML Models, Profiles and Mappings.) and launch the Syndeia dashboard. Select a Syndeia Cloud project, if needed.

  2. Go to the Settings tab (Figure 1). Set Default Issue Type to New Feature and check Sync block name with JIRA issue summary. Under General, make sure Use mapping is unchecked. Click Apply and close Syndeia dashboard to apply new settings.

    Figure 1 Settings tab, Syndeia dashboard

  3. Re-launch the Syndeia dashboard, Connection Manager tab, from the package JIRA Tutorial and select Data Map under Connection Type in the central pane. Open the SysML model in the left column and the JIRA repository in the right. Drag a JIRA issue from the right pane onto the JIRA Tutorial package in the left pane (the SysML model). We use SDB-1844 in this example. Click Yes to confirm. A new block appears in the left pane under the JIRA Tutorial package named UAV Issue A (the issue Summary field) as shown in Figure 2.

    Figure 2 Dragging SDB-1844 into SysML to create block UAV Issue A

  4. Go to the Connection Search tab and click Get All. A new connection of type BLOCK_JIRA_ISSUE_DATAMAP_CONNECTION appears as in Figure 3, in addition to the three created in the previous exercise.

    Figure 3 Connection Summary tab after creating Data Map Connection

  5. Return to Rhapsody. Create a new block definition diagram under the JIRA Tutorial package and drag the new block (e.g. UAV Issue A) into the diagram (see Figure 4). Note that an applied stereotype of <<JIRA_Issue>> is displayed along with <<Block>>. The default values of the value properties are determined by the contents of the corresponding JIRA properties.

    Figure 4  Rhapsody BDD

  6. Change one of the default values in the SysML block. In our example, we changed the priority to Major.

  7. In the Syndeia dashboard, Connection Browser tab, load and expand the SysML Repository. Right-click the UAV Issue A row and select Compare Source & Target, as in Figure 5.

    Figure 5 Connection Browser tab comparing across Data Map connection

  8. A difference table will be displayed automatically in the Comparison Result tab (Figure 6) showing the discrepancy between the SysML block and JIRA issue.

    Figure 6 Comparison Result shows difference in status between SysML block and JIRA issue

  9. In the Syndeia dashboard, Connection Browser tab, right-click the UAV Issue A row again and select Sync Target → Source. The default value of the priority property of the SysML block will be reset to its value in JIRA, Major.

  • No labels