Skip to content

Dependency Ownership Inconsistent with UML Specification #3467

@pbrown12303

Description

@pbrown12303

Describe the bug

The Gaphor implementation of Dependency (and its sub-classes) makes the client the owner of the dependency. In the UML specification a Dependency is a subclass of PackageableElement, whose owner must be a Package.

To Reproduce

Here's the Gaphor definition:
image

Here's the UML Specification:
image

Note that in the Gaphor implementation, the owner property is derived from the client property.

Expected behavior

According to the UML specification, the Dependency must be owned by a Package. This makes some sense, as the Dependency (or its subclasses may be declared in other contexts and not necessarily be a part of the NamedElement.

In MagicDraw, the default behavior when creating a Dependency (or any of its subclasses) in a diagram is to make the package owning the diagram the owner of the Dependency.

Screenshots

If applicable, add screenshots to help explain your problem.

OS

  • Linux (Please put in notes the specific distro)
  • macOS
  • Windows

Version

Version of Gaphor: 2.26.0

Additional information

Add any other context about the problem here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugAn issue in the application

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions