Summary


I said at the beginning of this chapter that you are probably already using something close to a software fortress architecture. I even had you take a quiz to prove it. Let's go back and score your yes answers.

  1. If, in the quiz, you said that your systems are developed inde pendently, this is exactly how software fortresses are built. You just need to learn to apply some design discipline to this independence.

  2. If you said that your systems are interrelated in complex ways, then I have good news. This is the assumption of the software fortress model. You just need to start thinking of the interrelationships as treaties among allies , apply a little methodology, and start making better choices about how you connect these systems.

  3. If you said that your organization often gets into religious wars about technologies, perfect! The software fortress model gives permission for people to disagree .

  4. If you said that departments within your organization don't trust each other ”for technical, political, or organizational reasons ”then you are well on your way to understanding the basic trust boundaries that form the heart of the software fortress architecture.

  5. If you said that your databases are not coordinated at the enterprise level, no problem. In the software fortress model, we expect each fortress to be responsible for the organization, maintenance, and administration of its own data strongbox.

  6. If you said that you are concerned about connecting your systems to the Internet, you are well on your way to understanding why we are so careful to separate the functionality of a presentation fortress from that of a business application fortress.

  7. If you said that you have critical legacy systems that you don't want to touch, voil  ! Welcome to the world of the legacy fortress!

The major points you should remember from this chapter are these:

  • The software fortress is a trust boundary of like systems developed by a cohesive group of individuals, kind of an atomic unit of trusted processing.

  • The software fortress architecture builds enterprise systems as a collection of software fortresses held together in treaty relationships.

  • All software fortresses have walls, guards , drawbridges , and data strongboxes. If they send messages to other fortresses, they have envoys as well.

  • The main fortress types (at least so far) are presentation, Web service, business application, legacy, treaty management, and service fortresses.

  • Fortresses are quite different from either objects or components .

Now we're ready to start looking at software fortresses in more detail.



Software Fortresses. Modeling Enterprise Architectures
Software Fortresses: Modeling Enterprise Architectures
ISBN: 0321166086
EAN: 2147483647
Year: 2003
Pages: 114

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net