1 / 10

Interoperability Goals A US Higher Ed Perspective

Interoperability Goals A US Higher Ed Perspective. Brad Wheeler Assoc VP for Research & Academic Computing and Dean of IT Indiana University 22 September 2003 Ann Arbor, Michigan. Three Types of Inter-Op. Data Specifications, real standards Software Code Code mobility among institutions

lee
Download Presentation

Interoperability Goals A US Higher Ed Perspective

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. Interoperability GoalsA US Higher Ed Perspective Brad Wheeler Assoc VP for Research & Academic Computing and Dean of IT Indiana University 22 September 2003 Ann Arbor, Michigan

  2. Three Types of Inter-Op • Data • Specifications, real standards • Software Code • Code mobility among institutions • Business Process • Mix/match participants in a business process

  3. ‘Code Mobility’ is the essential economic bet for higher education

  4. CMS as one Example Textbook Integrationw/ Publishers Special Character Sets Math/Languages/Sciences Sophisticated Assessment Integration/Leverage w/Enterprise Services Research/CommitteeSupport Current CMSOngoing Maintenance Streaming Multi-media Self-pacedTutorials Workflow Library Integration Direct Manipulation User Interfaces E-Portfolio IMS/SCORM Greater Personalization How will Higher Ed meet these growing requirements for CMS functionality in a period of relatively flat resources?

  5. UI Rendered Via Portal JSR 168 UI Rendered Via Silo’d App App Tool 1 App Tool 2 App Tool 3 App Tool … Towards Code Mobility Interop Framework + Data Standards OKI OSID Local Implementations Heterogeneous local systems

  6. Action to Achieve

  7. Application Development Guiding Principles 1. Standards: • IU will enhance our opportunities for code mobility among universities by architecting on a common layer of OKI services (OSIDs) as our baseline infrastructure for new IU applications. The complementary data standards will be based on IMS specifications (or other applicable data standards groups) whenever applicable. J2EE, AIX/Linux, and Oracle are the standards for enterprise-scale application development. 2. Sourcing: • For in-house developed systems, whenever possible, IU will participate in open source approaches – both importing existing solutions and exporting IU solutions. IU will partner with like-minded institutions whenever goals and resources align to share costs.

  8. Application Development Guiding Principles (cont.) 3. Delivery: • IU will focus on personalized delivery of information services and activities via the OneStart Portal through an unbundled, Web services approach to application development. 4. Leverage: • IU will aggressively seek efficiencies in consolidation of redundant application services whenever feasible.

  9. Code Mobility…Unlikely • Local project passions • Tactics over strategy • Xyz…is better …unless higher ed leaders choose to embrace the economic win of code mobility

  10. Interoperability GoalsA US Higher Ed Perspective Brad Wheeler Assoc VP for Research & Academic Computing and Dean of IT Indiana University 22 September 2003 Ann Arbor, Michigan

More Related