An IT Architecture for Emory University
Adopted by CIRT
Document 2: Designing Emory’s IT Architecture
February 20, 2002
ITA Version 2.6.1
© 2000 Emory University
Page 3
TABLE OF CONTENTS
1.
Preface
..........................................................................................................................................
4
2.
Conceptual architecture
............................................................................................................
5
3.
Enterprise-wide IT architecture design principles
...............................................................
7
4.
How the design principles support the requirements
.........................................................
9
5.
Configuration and implementation principles.....................................................................
10
6.
Enterprise-wide technical architecture domains
................................................................
11
7.
Next steps...................................................................................................................................
13
Appendix 1.
Justification and implications of the principles
..................................................
14
A.1.
Manage the IT architecture as a unity
...............................................................................
16
A.2.
Manage Enterprise IT infrastructure as an Emory asset..................................................
17
A.3.
Manage the evolution of the architecture
..........................................................................
18
B.1.
Deploy systems that are prepared for change
..................................................................
19
B.1.1.
Deploy scalable infrastructure
........................................................................................
20
B.1.2.
Make it easy to integrate new technology
.....................................................................
21
B.1.3.
Deploy modular, loosely coupled components..............................................................
22
B.1.4.
Enable as much reuse as is feasible
.............................................................................
23
B.2.
Reduce overall complexity
..................................................................................................
24
B.3.
Standardize judiciously
.......................................................................................................
25
B.4.
Use process-event driven systems
....................................................................................
26
B.5.
Provide a common security layer
.......................................................................................
27
B.6.
Facilitate access to IT resources........................................................................................
28
B.7.
Document flows of information
...........................................................................................
29
B.8.
Provide access controls for IT resources.
.........................................................................
30
C.1.
Costing and pricing should promote desirable behavior
..................................................
31
C.2.
Develop staff competencies in areas of strategic importance
.........................................
32
C.3.
Consider outsourcing in the context of risk to Emory’s future
.........................................
33
C.4.
Use industry standard solutions when feasible.................................................................
34
Appendix 2.
Technical Architecture Requirements
...................................................................
35
Appendix 3.
Glossary
......................................................................................................................
37
 |
 |
 |