Enterprise Architect Role


The primary goal of the Enteprise Architecture Initiative is to establish a process which is focused on building and maintaining an enterprise-wide technical architecture that best enables the priority business activities of AdCom and facilitates the adaptation of technology to the changing business needs of the campus.

In a typical IT organization, there usually are several "architectures" at work. Architecture spans data, network, application, and security. Moreover, architecture can and should involve business strategy decisions, financial analysis, and business process analysis and design.

The role of an Enterprise Architect is to output from the process of architecture a set of design drawings and possibly models for aiding in visualizing the final result of an extended construction process. As is evident in the previous paragraph, in terms of IT, the output can be quite complicated and situation dependent.

The Enterprise Architect typically produces a high level design which can be used by an enterprise to manage information more effectively. This design is then used by network engineers, application designers, database designers and so forth to drive detailed functional designs in each of these areas. It is clear that the Enterprise Architect must be versed enough in the details of each specialty to realize the possible and impossible.

As quoted from a Commplexus article on Enterprise Architecture:

Enterprise Architecture is by its very nature interdisciplinary. The successful practitioner, while he may specialize in one particular area, must always maintain currency in each of the disciplines. Without this broad general knowledge, he will be unable to design effectively, as problems and opportunities will not be evident. The disciplines most crucial to the Enterprise Architect are:



Ideas for this document where taken from: Commplex Enterprise Role Document
Maintained by Marina Arseniev / Last Modified 10/23/2001