Bug 425295 - Associations in use case diagrams are not deleted in the UML model, only in the diagram
Summary: Associations in use case diagrams are not deleted in the UML model, only in t...
Status: RESOLVED DUPLICATE of bug 335364
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: Git
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-13 12:23 UTC by Robert Hairgrove
Modified: 2020-08-13 14:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Hairgrove 2020-08-13 12:23:25 UTC
SUMMARY
When an association is created by dragging the related icon from an actor to a use case, or to another actor, two XMI elements are added to the file:

1) The element which has the tag <UML:Association> along with the owned elements <UML:Association.connection> and <UML:AssociationEnd>;

2) The element <associations>, previously empty, is given child elements with the tag <assocwidget>.

But when the associations are deleted in the diagram, only the elements under the <diagram> element are deleted; the model elements tagged <UML:Association> are left behind as zombies.


STEPS TO REPRODUCE
1. In Umbrello, create an actor and two use cases;
2. Draw associations between the actor and the use cases.
3. Save the file. Open it in an editor and verify that the elements described above were created.
4. In Umbrello, delete the associations just drawn and save the file again.

OBSERVED RESULT
Notice that the elements tagged <UML:Association> were not deleted, only the <assocwidget> elements under <diagram> were deleted.


EXPECTED RESULT
All elements corresponding to the deleted associations should have been removed from the XMI file.

SOFTWARE/OS VERSIONS
Linux Ubuntu 18.04.4
Qt Version: 5.x

ADDITIONAL INFORMATION
Comment 1 Robert Hairgrove 2020-08-13 14:22:12 UTC

*** This bug has been marked as a duplicate of bug 335364 ***