|
What distinguishes Enterprise Architecture is what people choose to do, to
meet strategic goals. Solution Architecture is what people must do, to
deliver systems that work. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||
|
Enterprise Architects and Solution Architects address the same
architecture domains, at different levels of abstraction and with different
goals. |
||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
|
Common architect roles |
Architect job survey |
|||||||||||||||||||||||||||||||||||||||||||||||||
|
·
·
Solution
Architects: are more likely to be
found working for IT service providers than enterprises. They shape specific
solutions. Their goals relate to the pressing time, cost and quality
objectives of the solution they have to deliver, of which they need to
develop a deep understanding. ·
Software
Architects: work at a lower level of
detail, and often specialise in a software development technology (web apps,
database apps, J2EE, .Net). See also where
agile meets enterprise. All of the above require technical knowledge, but the design and
operation of technical infrastructure is usually the responsibility of technical
architects: These often specialise in one area of infrastructure
technology (hardware configuration, CISCO, MS Exchange etc.). Some spend more
time managing and fire-fighting than designing. Some choose to call
themselves enterprise architects for the simple reason that they work on
infrastructure technologies that support an enterprise, but they are not
enterprise architects of the kind that TOGAF and Zachman frameworks are
designed for. Other roles: I have surveyed over two thousand IT job
adverts with architect in the title. The survey (opposite) is not fresh. If I
did it again, no doubt other job titles like SOA architect would be high up
the scale. |
|
|||||||||||||||||||||||||||||||||||||||||||||||||
