ArchiMate Grouping and Alternatives

[Viking]

Hi, I am afraid that I asked a similar question before decided for Grouping. But I cannot find it anymore.

Currently I use ArchiMate Grouping to group several independent components that could potentially even run on different computers, so that it can be easier managed in Enterprise Architecture Management (see also https://www.archimetric.com/exploring-composite-elements-in-archimate-unveiling-grouping-and-location). In my case these components are frontend, server, and database. I like Grouping, but I am having trouble to use it with EA. For example, Time Aware Modelling does not support Grouping. So, following alternatives come into my mind:

• Composite Element: for EA, this is Grouping, see https://sparxsystems.com/enterprise_architect_user_guide/17.0/modeling_languages/composite_elements.html
  
• Application Collaboration: a collaboration is as an aggregate. The collaboration has normally aggregation relationships to its aggregated components. The database has been modelled as a system component and does not support aggregation between Collaboration and Database. But that does not really matter. I would leave the relationships away. The Collaboration still “groups” the elements, meaning if I put them inside the component, they are all moved together.
  
• Application Component Stereotyped: an additional element as a stereotype that inherits from Application Component and maybe has no color (like grouping) and a symbol like grouping. Rem.: Application Component supports the same realtionships as Application Collaboration.

What are the advantages and disadvantages of the approaches? What do you recommend?

[Viking]

After investigating I think I should stay with Grouping, because the grouped elements / components spread over different layers of an application architecture.

Better ideas are still welcome.