Enterprise setup

[nick-ikigai]

Our overall setup consists of multiple independent teams who are assigned separate subdomains/bounded contexts and who are empowered to make arch decisions within these boundaries.

While these bounded contexts are loosely coupled, there are still a number of east west dependencies, i.e. software system A in BC1 (modelled as workspace1) is subscribing to a topic/container which belongs to software system B in BC2 (modelled as workspace2).

My understanding is that there is currently no way to reference model elements from other workspaces, but the external software system B needs to be part of both workspaces in order to model that A -> B relationship.

Which creates the problem of duplication if I try to establish a holistic system landscape view that integrates all workspaces.

The other option (as described here) is to pre-define all common top level entities (i.e. users and software systems) centrally first, and then let the teams extend those with more detail. That approach avoids duplication, but it also takes decision authority away from the individual teams.

Essentially, software systems are now owned by the EA team not the empowered product team anymore.

Are there any other option than those two (bottom up vs top down) ?

[simonbrowndotje]

That approach avoids duplication, but it also takes decision authority away from the individual teams.

Why?

Essentially, software systems are now owned by the EA team not the empowered product team anymore.

Again, why?

It sounds like you're assuming that the EA team needs to own the central definition of people and software systems.