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

8.2. Treaty Considerations

The Starbucks example illustrates the two main considerations of treaty design:

  1. Workflow. How does work flow from one fortress to another?

  2. Error management. How does one fortress report an error to another fortress?

You might expect security to be part of the treaty. In the Starbucks/Roger collaboration, I had to hand over my American Express card to prove I was authorized to make a charge on that particular account. It is reasonable to think of security as part of the treaty, but I think of it as a feature of the drawbridge rather than of the treaty, and I recommend documenting the drawbridge in the fortress documentation. Either approach is fine, though.

Treaties are spelled out in treaty overview documents (TODs), ...

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