Summary


Confused by all the acronyms? Don't forget the glossary!

Don't feel that you need to use all of these techniques. Just use the documentation techniques that work well for you, feeling free to invent others. Here is a reminder of the techniques that I find useful:

  • FAD (fortress “ally diagram), which shows all of the enterprise fortresses and their allies with drawbridges and treaties labeled.

  • TAD (treaty “ally diagram), which shows the subset of a FAD that is relevant to a particular treaty.

  • SAD (sequence “ally diagram), which shows the sequence of interactions between fortresses necessary to implement a particular treaty.

  • FAR card (fortress “ally “responsibility card), which shows, for a given fortress, all of its responsibilities and the allies with which it collaborates directly.

  • TAR card (treaty “ally “responsibility card), which shows, for a given treaty, all of the participating fortresses and the responsibilities each has in relationship to this treaty.

  • FOD (fortress overview document), which gives a detailed look at a fortress from an outsider's perspective.

  • TOD (treaty overview document), which gives a detailed look at a treaty from the perspective of a fortress participant.



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