E-MailHow to Talk to Architects, Part II: Business and Information
In the first two Advisors in this series (see "How to Talk to Architects, Part I: The Enterprise," 28 May 2008, and "How to Talk to Architects, Part II: Business and Information," 18 June 2008), we discussed the issues involved in communicating with architects; how to relate to their issues and concerns and to understand their perspective and vocabulary. In this final part of the series, we address application- and technology-domain architects. Recall that, for each particular architectural domain, there is an associated set of concerns, goals, or concepts. Each set can be described by some kind of conceptual model and perhaps documented in a commonly used formal model or other architectural artifacts. These artifacts define the vocabulary used within that architectural role. Another important factor is the scope of responsibility of a particular architect. The concerns at the enterprise level are different than those at a project level.
Cutter Consortium clients, please log in:
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com.