What element to use to represent groups of components?

[Modesto Vega]

This is perhaps a question for the UML forum, happy to move it there.

What is the best element to use to represent groups of components with similar functionality but handling different types of data?

[qwerty]

I would say a package (though that's not an element).

q.

[Modesto Vega]

I would say a package (though that's not an element).

q.

Well, in Sparxian, it is an element, a dual personality element. In fact, I considered using Packaging Components but hesitated after reading this 11 year old thread - https://sparxsystems.com/forums/smf/index.php/topic,7175.0.html - and having difficulty correlating packaging components to the UML 2.5.1 specification.

Edit: I forgot to add that a package, including a Packaging Component, does not work very well as the same component can be in multiple groups depending on the role they play in the transaction.

[qwerty]

You should probably define a component extension in a profile that has a stereotype property to define its grouping.

q.

[adepreter]

Indeed,, if you are mixing levels of detail then you can't generate meaningful charts and
reports.

You need precise semantics and the ability to manage levels of detail, like in Labnaf.

A.

[Modesto Vega]

In labnav this could be covered by the Application Group or the Application Function.

By the way, I have the bad habit of using applications and components almost interchangeably.