Kuali on Campus ITANA Screen 2 Screen May

  • Slides: 10
Download presentation
Kuali on Campus ITANA Screen 2 Screen May 28, 2009 David Walker Curtis Bray

Kuali on Campus ITANA Screen 2 Screen May 28, 2009 David Walker Curtis Bray Eric Westfall

Multi-Campus Vision Interoperable strategies that encourage and facilitate sharing and reuse of technology resources

Multi-Campus Vision Interoperable strategies that encourage and facilitate sharing and reuse of technology resources among campuses, while enabling consolidation of business processes and functions

Definition: Interoperable A software component is interoperable with another component if it is able

Definition: Interoperable A software component is interoperable with another component if it is able to use the other's services as part of its own, particularly over a network. The prerequisite for interoperability is common semantics, but interoperability is facilitated when network protocols and data formats are also common. When two different organizations provide the two components, common organizational trust is also required.

Definition: Sharing A software component is shared by two or more organizations when a

Definition: Sharing A software component is shared by two or more organizations when a single instance of that component is operated to provide services to those organizations.

Definition: Reuse A software component is reused by two or more organizations when those

Definition: Reuse A software component is reused by two or more organizations when those organizations each install a copy of that component to provide services to themselves.

Business Processes and Technology • Process consolidation results in shared software • Processes that

Business Processes and Technology • Process consolidation results in shared software • Processes that share common practices can result in sharing or reuse • Processes that do not share common practices might result in reuse

Use Cases for Sharing and Reuse - 1 • UC Irvine reuses a time

Use Cases for Sharing and Reuse - 1 • UC Irvine reuses a time sheet application that was written at UC Davis – – – UCD instance will use UCD middleware UCI instance will use UCI middleware Needs similar runtime and middleware at each campus

Use Cases for Sharing and Reuse - 2 • UC Irvine reuses a time

Use Cases for Sharing and Reuse - 2 • UC Irvine reuses a time sheet application, written and operated at UC Davis – UCD instance will use UCD middleware – UCI instance will use UCI middleware – Needs a common middleware API; UCD provides runtime platform for both instances

Use Cases for Sharing and Reuse - 3 • UC Irvine shares a financial

Use Cases for Sharing and Reuse - 3 • UC Irvine shares a financial system with UC Davis that is operated by UC Davis – • Needs a “common” middleware layer What do we mean by “common” here? – – – UCI and UCD do not share middleware. For example, workflow items need to flow between UCD and UCI workflow engines Also service bus and IAM

Potential Topics for Discussion • • More information about Rice Interoperability and multi-enterprise middleware

Potential Topics for Discussion • • More information about Rice Interoperability and multi-enterprise middleware Identity management integration Middleware governance