O'Reilly logo

Software Fortresses: Modeling Enterprise Architectures by Janet Van Sickler, Roger Sessions

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

1.6. Treaty Relationships

If an organization's overall architecture could be described as a single fortress, we wouldn't need the software fortress model. We could use simple three-tier (or N-tier) diagrams to explain our architecture. The reason we need the software fortress model is that enterprises are not mono-lithic. They have many software fortresses. It is the relationship between these different fortresses that we are trying to model and understand.

When one or more fortresses work together to accomplish a higher-level activity, we say that the fortresses are allies of each other. They coordinate their work through treaty relationships.

The fact that the cooperating fortresses are allies doesn't mean that they trust each other. They still ...

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required