IT Architecture

Overview :: Getting Started :: Policies

You can get started understanding and using Emory's IT Architecture by following these steps.

1. Read the documents
   Read the architecture documents on Emory's IT Architecture web site.
2. Appreciate the principles
   Note how the IT Architecture is intended to help Emory and you use Information Technology to meet mission, goals and objectives. Appreciate the IT staff's use of the IT Architecture principles to keep systems flexible so they can respond quickly enough.
3. Apply the principles
   In the Conceptual Architecture, for each of the principles in turn, ask yourself how that principle applies to your project.
4. Design with adaptability and flexibility to change in mind.
   See if you can think of any other principles that will make the result of your project able to more easily respond to changing needs.
5. Allow for growth and expansion
   Your application or service might be more popular than anticipated. You might need to upgrade your web server or move your project to a server with more capacity. Just make sure your project design does not prevent handling unexpected, overwhelming demand. When purchasing equipment, note that a server with no room for growth might be less expensive than one with room to add additional capacity, but the full server could require replacement if you have to grow it faster than anticipated.
6. Use components
   Seek to identify parts of your work that could be reused by yourself or others in other projects. Package them for that purpose. These are called "reusable components. " Be sure to document how to use them, and make their details available so that others can assess their quality and suitability. Also look for existing work that you can reuse, giving credit where credit is due, unless doing so violates laws (such as copyright) or academic rules.
7. Standardize
   Use only as many different types of computers and software as are distinctly useful. The fewer things you have to test when making a change, the faster you can implement the change.
8. Reduce complexity
   The simpler a system is, the easier it is to understand the impact of a change.
9. Use the classification scheme
   Categorize your data and documents for security and disaster recovery using the guidelines of the Security Classification Model.
10. Look for non-IT applications
    Many of the principles outlined in the first two architecture documents are timeless and of wide applicability. See if you can apply them to your benefit outside Information Technology.
11. Let us know
    Please let Peter Day (ospwd, 404-727-7678) know how you make use of the IT Architecture documents and their ideas.

For more information, see the legacy Emory IT Architecture web site.

© 2003 Emory University