IT Architecture Home || Provost Home || Emory Home | Search | Index | Help

IT Architecture Documents

Presentations and Articles

Old IT at Emory pages

Give Feedback (closed)

IT-ARCH Discussion List (closed)

Other Sites on IT Architecture

Get a free copy of Acrobat® Reader

 

Domain Architecture Task Forces Cont'd.

Architecture Domains

This architecture is one of a set of architecture "domains" that define reusable building blocks of technology infrastructure. A domain architecture provides a logically consistent set of principles to guide the engineering of a domain infrastructure that can change as quickly as required to meet Emory's needs now and in the future. The domain principles are derived from Emory's priorities, goals and strategies by applying the Conceptual Architecture Principles to the domain. The domain architecture also provides guidelines to facilitate the process of selecting and applying industry standards, selecting standard products, and designing standard configurations of technologies within the domain.

A list of Emory's architecture domains and their definitions and the Conceptual Architecture Principles (CAPs) can be found in Document 2: Designing Emory's IT Architecture. Additional information to facilitate the architecture creation process will be supplied once the team is formed. See also "Responsibility" below.

Organizational Scope

The architecture addresses the needs of the "University" and its community, that is, the enrolled students and the employed faculty and staff of Emory University no matter where they reside, keeping in mind that education and research involving faculty and students of the Health Sciences also occur at Emory Hospital, Crawford Long Hospital, Emory Clinic, satellite clinics, the V.A. Medical Center, Grady Hospital and its buildings, and Emory West. The term "Emory" alone includes all its sites. Healthcare clinical priorities and architectural requirements will need to be addressed elsewhere. Both architectures will need to address issues of interoperability between the University and Healthcare insofar as University Health Sciences are concerned.

Level of applicability

The IT Architecture, including the conceptual architecture and the domain architectures, applies to the enterprise-wide IT infrastructure. It is applicable to all changes to that infrastructure and to all parts of the enterprise-wide solution life cycle, including system design, construction, deployment, management, product selection, systems integration, database development, standards, and configurations relating to enterprise-wide information technology at Emory. Unit IT decisions that are of local benefit and do not adversely affect university resources are normally at the discretion of the unit. However, local decisions should consider the effect on the overall system. To the extent that Emory units adapt the enterprise-wide architecture for local use, the enterprise-wide architecture can provide a basis for common local architecture across the units of Emory.

Responsibility

The responsibility of this domain architecture Task Force is to collaboratively create a document that defines an architecture for this domain to recommend for Emory to the University Information Technology Architecture (ITA) committee. A template specifying the required content and format will be supplied by the first meeting of the Task Force. The Task Force may include other information in its document that it deems necessary.

The Task Force should obtain approval from the ITA for each component of the document before proceeding to the next. The Task Force is encouraged to request clarification regarding its work from the ITA as needed. It may also request from the ITA assistance and access to additional expertise, including coaching by the Enterprise Architecture Strategy analyst assigned to Emory by the consulting company (META Group) that Emory has retained.

Length of Service

Each Architecture Domain Task Force has a limited life. When a Task Force's deliverable is accepted, the work of the Task Force is done, and the task force disbands. Architecture Task Forces may be created and recreated as needed when there is work to do.

IT Architecture Home || Provost Home || Emory Home | Search | Index | Help

©2002 Emory University
Legacy Site for reference