Neville Prinsloo
this would be brilliant
Ł
Łukasz Madej
This would be super helpful for Deployment Diagrams
R
Richard
I stumbled upon the need for this feature the last weeks. I think this allows a lot of additional use cases for communicating the landscape in more viewpoints. We want to show how our business capabilities are realised by software systems. Using groups (and sub groups) we can visualise our capability structure with the actual software which is realising them. Also being able to have the nesting allows great usability to model the sub structure and have this inherited. This would then really lead to a lot of usability improvements (e.g. filter the model by a group/sub group).
R
Richard
And to have a "category" for a group would allow these viewpoints to be grouped. So, deployment groups, capability groups, product groups, market groups etc....
Antonio Pugliese
would objects then be part of all super groups?
if group B is nested in group A, and object C belongs to group B, does object C belong to group A atutomatically?
the current way to do this is to add object C to group A and group B. currently there is no direct relationship between the two groups, but the representation still works
Jacob Shadbolt
Antonio Pugliese The idea is that it would inherit in the hierarchy yes, similar to components in an app are automatically in the system also.
M
Matias Pavez
+1, We would like to use this for deployment diagrams, to nest "groups" like OS, PCs, hardware equipment, and docker containers.