IBM Support

PI96831: DEPENDENCY LOST AFTER COPIED REQUIREMENTS FROM USECASE DIAGRAM TO SEQUENCE DIAGRAM

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Dependency lost after copied requirements from Usecase Diagram
    to Sequence Diagram
    
    Reproduce Steps:
    1. Create a new model
    2. Create 2 new requirements
    3. Create a new usecase diagram, drag these requirements onto
    it, add dependency between the requirements.
         a dependency relation appears under the requirement in
    explorer.
    4. Create a new sequence diagram.
    5. Select and copy these requirements and dependency from
    usercase diagram, then paste onto the sequence diagram.
    6. As the result, the dependency relation appears on the
    sequence diagram, but disappears from usecase diagram and
    explorer.
    7. Save and Reopen the model, the dependency relation disappears
    entirely.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Rhapsody                                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Dependency lost after copied requirements from Usecase       *
    * Diagram to Sequence Diagram                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed by preventing the Dependency from disappear.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI96831

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    820

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-04-17

  • Closed date

    2018-06-17

  • Last modified date

    2018-06-17

  • 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

  • R820 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
17 June 2018