Packages for classes

[alkock]

Is your feature request related to a problem? Please describe.
USE already has a wonderful possibility to create UML diagrams via classes and associations, which can be exported. Particularly with larger systems, a structure according to packages is desirable.

Describe the solution you'd like
A possibility to structure classes into packages that are also displayed in the class diagram view.

Describe alternatives you've considered
A current workaround would be to manually trace the packages with the help of an image editing program. ;)

[ChuckLutz]

This would be a tremendously helpful enhancement; I am interested in building models to capture other OMG specifications, which inevitably are divided into packages and often make references to other models' content, e.g. to MOF::Element.

An undesirable current workaround would probably be to encode package names into class names, e.g. "MOF__Element" or similar.

[h-man2]

This one is a big one, because we want to solve more than just packages in the long-run.

Plans are currently:

• Add support for defining data types, i. e., side-effect free types that don't change the system state (comparable to primitives in Java or structs in C#).
• Add support for a packaging mechanism including versioning, and a package manager
• Add support for "import" statements to be able to access package elements without the need to fully qualify them
• Support visibility definitions (public, private, ...)

Students of mine work on some of these topics at the moment.

If you like, feel free to post ideas about a package mechanism here. So we can discuss a solution, espacially for using packages).
Like for example:

model Shop
import de.haw.hamburg.types.Date

class Invoice
  attributes
    date:Date
...
end