The Organization of This Book

Chapter 1 of this book is an introduction to software fortresses , discussing what they are, the terminologies we use to describe them, and how interfortress relationships work.

Chapter 2 is an overview of the various techniques we use to document fortresses, including fortress “ally “responsibility cards (based on class “responsibility “collaborator cards) and sequence “ally diagrams (based on UML's class sequence diagrams).

Chapter 3 gives an overview of transactional integrity. This is a background chapter needed to understand the many flavors of the word transaction and how different parts of software fortresses cooperate to coordinate their work.

Chapter 4 gives an overview of drawbridges. The two major subcategories of drawbridges , synchronous and asynchronous, are covered in more detail in Chapters 5 and 6, respectively.

Chapter 5 covers synchronous drawbridges, including component technologies on which they are based.

Chapter 6 covers asynchronous drawbridges, including the message queues on which they are based.

Chapter 7 discusses how security is implemented in software fortress architectures. It covers the two important aspects of security: keeping things out (wall technologies) and letting things in (guard technologies).

Chapter 8 discusses how software fortresses form partnerships and work together, through well-defined treaty relationships.

Chapter 9 gives a general overview of issues that are relevant to all fortress types.

Chapter 10 discusses the two Internet-connected fortresses: Web service fortresses, which accept programmatic requests over the Internet, and presentation fortresses, which interact with browsers.

Chapter 11 discusses the business application fortresses that run your mission-critical business systems.

Chapter 12 covers legacy, service, and treaty management fortresses.

Chapter 13 enumerates 25 important issues you should consider in a design review of a software fortress architecture.

Chapter 14 presents a software fortress architecture case study.

Chapter 15 gives a few (well, maybe more than a few) final thoughts on software fortresses.