Skip to content

UML diagrams lack primitive-valued properties for subclasses #53

@jakebeal

Description

@jakebeal

The UML diagrams that we are generating are have all of the subclasses and have their object-valued properties, but are missing the primitive-valued properties for the subclasses in the hierarchy.

For example, consider the attached ValueSpecification diagram:

  • Identified correctly shows no properties
  • ValueSpecification correctly shows its type property
  • LiteralIdentified correctly shows its identifiedValue property
  • LiteralString is missing its stringValue property

ValueSpecification_abstraction_hierarchy.pdf

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions