Package vs Domain

[Thomas Mercer-Hursh]

I have been having a discussion with someone who seems to think that the term "package" is legacy UML from pre 1.5 and who is equating it with Package Diagram, which has been effectively replaced by Component Diagram.   Yet, from what I see "package" is a generic UML term for any grouping of things.

This focuses specifically on classes, where I was happy to call the lowest level Package and any higher levels Domain, but he prefers Domain for all levels.

[qwerty]

Is he some kind of person that has eaten wisdom with a spoon? Then call it a day. In German we call that "splitting hairs". I'd also prefer to look at Domain as something high level, but would not really start arguing with someone.

q.

[Geert Bellekens]

Package is a valid UML construct, even in 2.5 spec.
"Domain" on the other hand is not know as a construct in UML.

To be precise in v 2.5 Package is defined as:

A Package is a namespace for its members, which comprise those elements associated via packagedElement (which are said to be owned or contained), and those imported.

A package can contain any and all UML elements, so not at all limited to Classes.

You can also tell this someone that
- A Package Diagram still very much exists in UML 2.5 and so it not at all legacy
- The types of diagram really are not important at all, they are not even really a part of the UML specification, but merely a guideline on how to represent your model in a sensible way. (more ranting about that on UML is NOT about diagrams!

Geert

[Eve]

A package can contain any and all UML elements, so not at all limited to Classes.

Actually, a package can only contain anything that inherits from PackageableElement. Noteable exceptions are: Operation and Property (owned by a classifier), State and Action (owned by a behavior).

[Geert Bellekens]

A package can contain any and all UML elements, so not at all limited to Classes.

Actually, a package can only contain anything that inherits from PackageableElement. Noteable exceptions are: Operation and Property (owned by a classifier), State and Action (owned by a behavior).

Yes indeed, that is more precise then my explanation.

Geert

[Eve]

Sorry, I can be a pedant sometimes.

[Thomas Mercer-Hursh]

Still, the existent of PackageableElement itself says a lot.