IT ArchitectureOverview :: Getting Started :: PoliciesEmory's Enterprise-wide IT Architecture (EITA) explains how Emory envisions using Information Technology to the meet its needs now and in the future. The ability to build or change a system to meet a set of requirements quickly enough that the result is still useful when it is done is increasingly a challenge due to the rapid pace of change. The goal of the IT architecture is to create an IT environment that can respond quickly enough. To achieve this, the architecture provides general principles, called the Conceptual Architecture, that apply no matter what IT topic is involved. The principles include the use of tested and successful srtrategies and practices to create a flexible IT environment that can be quickly adapted as needs change. Examples of such strategies are reduction of complexity using standardization, standby capacity to quickly handle an increase in load, and the use of building blocks and reusable components. The architecture then organizes the various aspects of information technology into major topics, called "Domains", such as Directory, Security, Network, etc. For each domain, it provides design principles, configuration principles, standards, products and configurations. The architecture can then be used as a set of guidelines for acquiring new IT resources and deploying them in a consistent and cost-effective way across Emory. The approved IT Architecture documents to date are the following:
The above documents are all available at the legacy Emory's IT Architecture site in multiple formats that allow linking to principles from other web pages, printing of the documents, and reuse of their content. An abstract and a summary of each document are also provided. One further document, that is still in draft but has not undergone any change for over a year, is the document:
For more information, see the legacy Emory IT Architecture web site. © 2003 Emory University |