1 / 8

IT Architecture @ UW–Madison

IT Architecture @ UW–Madison. Lessons from the first four years Keith Hazelton (hazelton@doit.wisc.edu) IT Architect, Division of Information Technology. IT Architecture @ UW–Madison: Lessons from the first four years. IT Architecture ver. 1.0, 1995 Typical products What hasn’t worked

andres
Download Presentation

IT Architecture @ UW–Madison

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. IT Architecture @ UW–Madison Lessons from the first four years Keith Hazelton (hazelton@doit.wisc.edu) IT Architect, Division of Information Technology

  2. IT Architecture @ UW–Madison: Lessons from the first four years • IT Architecture ver. 1.0, 1995 • Typical products • What hasn’t worked • What has worked • 1999 activities and plans • Questions for those without IT architects... CSG: IT Architecture @ UW-Madison

  3. IT Architecture ver. 1.0, 1995 • Architects (1. – 2.5 FTE) and advisory group, Committee on Information Technology Architecture (CITA) • Process: CITA prioritizes issues, teams formed, guidelines drafted, reviewed, approved • All processes, work in progress and results documented on web site (http://www.wisc.edu/arch) CSG: IT Architecture @ UW-Madison

  4. Typical products • Guidelines on shared authentication, directory services • Campus forums on PeopleSoft, MS & Novell Contracts, E-forms/workflow • Interoperability info: quick lookup guides, research reports (E-commerce, E-mail) CSG: IT Architecture @ UW-Madison

  5. What hasn’t worked • Limited impact on applications development • “Big book of standards” a pipe-dream • Some non-converts see as a budget-cut target • Big IT changes often happen outside the architecture process • Consensus-based standards-like efforts take lots of time and resources CSG: IT Architecture @ UW-Madison

  6. What has worked • Growing recognition that architects & friends represent a valuable and rare global perspective • Architects have become trusted colleagues of some key planners and decision-makers • Flexibility to redefine tactics as landscape shifts • From authors of “building code” to JIT honest info brokers • Adjustable mix of slow crafting of infrastructure guidelines and quick results for low-hanging interoperability fruit. CSG: IT Architecture @ UW-Madison

  7. 1999 activities and plans • Bring CITA & architects into policy arena as advisers • Target info brokering at the groups and individuals making the big decisions • Web-based learning systems guideline • Secure server best practices • Rollout of architecture-shaped directory and authentication services CSG: IT Architecture @ UW-Madison

  8. Questions for those without IT architects... • Who represents the interests of the whole versus the interests of the pro-activist dept. or unit with money? • Who mediates between central IS and departmental IT? • By what processes are institution-level IT issues resolved? • Who is charged to look over the horizon, over the wall? To whom do they report? CSG: IT Architecture @ UW-Madison

More Related