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

14.2. First-Pass Design

I will start by trying to identify some possible fortresses. Because customers will be using browsers, I know that I will have at least one presentation fortress. Vendors will be coming into my system programmatically, so I know I will need a Web service fortress. I also know that I will have at least one business application fortress to process the requests. So far, I am up to three fortresses. But how many business application fortresses should I have? And what about treaty management and service fortresses?

Let me start by identifying the functionality that I think needs to be in the system someplace:

  1. Customer gateway: sending catalog information, accepting browser requests, and preparing the order information

  2. Vendor ...

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