IBM Support

PI40063: Dependencies from Autosar to SysML model elements cannot be created.

A fix is available

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Abstract:
    Dependencies from Autosar to SysML model elements cannot be
    created.
    
    Error Description:
    Customer is trying to create links from an Austosarcomponent to
    a sysml block in the component diagram. The Drawing Toolbar does
    not offer to draw dependencies (the only linking/connecting
    elements offered are AssemblySwConnector, DelegationSwConnector,
    portType and trace).
    
    The attached example
    (?Linking_Autosar_to_SysML_with_Rhapsody_8.1.2.zip?)
    ? focuses on linking (?dependency? type)
    o from a Software Architecture elements modeled in Autosar
    o to  System Architecture elements modeled in SysML
    ? consists of two projects; SysML_System_Architecture and
    Autosar_Software_Architecture (which includes a reference to the
    content of SysML_System_Architecture)
    ? is made with Rhapsody 8.1.2
    
    Using Rhapsody 8.1.2, it is not possible
    ? to create these links
    ? to let these links be graphically displayed diagrams
    in a straightforward way. It is possible by using some
    workarounds, which are described in the following.
    Step 1 Linking Autosar Components to SysML Blocks
    In a Software Components Diagram, the Autosar Components and
    SysML Blocks (and/or their instances; i.e. Parts) are  added.
    In the browser, select ?anAutosarComponent? and choose the
    context menu item ?Add new / Relations / Dependency?. In the
    ?Add Dependency? dialog, choose ???Select??? and select
    ?aSysMLblock? or ?aSysMLpart?. The dependencies will be created
    and displayed in the browser.
    
    
    Step 2: Displaying the component/block dependencies in a diagram
    
    The Drawing Toolbar does not offer to draw dependencies (the
    only linking/connecting elements offered are
    AssemblySwConnector, DelegationSwConnector, portType and trace).
    But the dependencies created in the previous  step can now be
    displayed in the diagram using the populate function.
    
    Step 3: Linking Autosar Ports to SysML Flow Ports
    When invoked for an Autosar Port, the ?Add Dependency? dialog
    will not show SysML FlowPorts.
    But it does, when invoked for a Autosar Component! This allows
    us the following workaround:
    ? create a dependency link from an Autosar Component to the
    SysML FlowPort and then
    
    ? move (drag?drop or cut?paste) the dependency from the Autosar
    Component to the Autosar Port.
    
    
    Step 4: Displaying the component/block dependencies in a diagram
    
    The Drawing Toolbar does not offer to draw dependencies (the
    only linking/connecting elements offered are
    AssemblySwConnector, DelegationSwConnector, portType and trace).
    But the dependencies created in the previous  step can now be
    displayed in the diagram using the populate function.
    
    
    Local Fix:
    Adding the dependencies from the browser and then displaying it
    using the populate function.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of version 8.1.2                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Dependencies from Autosar to SysML model elements cannot be  *
    * created.                                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed in 8.1.4
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI40063

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    812

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-04-29

  • Closed date

    2015-12-22

  • Last modified date

    2015-12-22

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    TLOGIC RHAPSODY

  • Fixed component ID

    5724V74RP

Applicable component levels

  • R813 PSY

       UP



Document information

More support for: Rational Rhapsody

Software version: 8.1.2

Reference #: PI40063

Modified date: 22 December 2015