tag:blogger.com,1999:blog-4325801270893684209.post4572600592263782174..comments2008-10-14T10:27:34.006-05:00Robert G. Howardhttp://www.blogger.com/profile/05109738152842611690noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4325801270893684209.post-36913282565079158512008-10-14T10:27:00.000-05:002008-10-14T10:27:00.000-05:00Fred,<BR/><BR/>Thanks for the comment! I agree there are a lot of different context diagrams that people have used to get the message across, and being able to tie them back to established frameworks such as UML and Zachman are important. It&#39;s a fairly straight-forward approach - but I&#39;ve found it to be very effective in facilitating sessions in both the Strategy &amp; Planning Phases, as well as Detailed Design.<BR/><BR/>Keep the comments coming!<BR/><BR/>Robert HowardRobert G. Howardhttp://www.blogger.com/profile/05109738152842611690noreply@blogger.comtag:blogger.com,1999:blog-4325801270893684209.post-80164288587814041022008-10-14T10:20:00.000-05:002008-10-14T10:20:00.000-05:00Hello Robert,<BR/><BR/>I agree in principle with the PAID approach. This is similar to other context diagrams that I have created to help clients understand the proposed solution architecture (either at an enterprise level, or with just a customer experience focus). This approach aligns quite nicely with architecture frameworks like Zachman <A>www.zifa.com</A>.<BR/><BR/>Thanks,<BR/><BR/>Fred BlueYYYGuyhttp://www.blogger.com/profile/01959475819546265317noreply@blogger.com