Multiple projects sharing/working on a common baseline

[Rik van der Schalie]

Isn't the root of the issue the fact that models hardly tend to be purely hierarchical, whereas the publish mechanism in EA is?
IMHO the only solution would be for EA to offer the possibility of "defining" publications, containing elements from multiple packages that do not necessarily share the same root-package, and to reuse that publish definition?

[Modesto Vega]

Isn't the root of the issue the fact that models hardly tend to be purely hierarchical, whereas the publish mechanism in EA is?
IMHO the only solution would be for EA to offer the possibility of "defining" publications, containing elements from multiple packages that do not necessarily share the same root-package, and to reuse that publish definition?

Since Sparx hierarchically "organises" the repository - please note the quotes, this thread is/was about having a discussion about how to hierarchically organise an enterprise repository in order to

• avoid projects constantly reinventing the wheel,
• contributing to and improving an enterprise body of architectural knowledge, and
• reusing this body of knowledge