Transcript Introducing a New Product

SSWG Preliminary
Recommendations for Application
Platforms
David Walker
Information & Educational Technology
University of California, Davis
[email protected]
Purpose

Interoperability


Alignment and agility to address business needs
Sharing and Reuse

Effective use of resources

Common implementations of business rules
What Is a Platform?

The “stack” required to run an application:

Hardware

Operating System

Database server

Middleware

Programming language

Etc.
When Does Platform Matter?

Often not a major factor for interoperability
and sharing.


Interface protocols and formats
Reuse, however, requires:

Infrastructure

Expertise (operation and development)

Sufficient human resource
Platforms Considered

Java

.NET

ColdFusion

PHP

Oracle Forms

Chosen because they are in common use at
UC Davis. We did not do a technical or
business evaluation
Contexts Considered




Core administrative systems of record, such
as Banner, DaFIS, or PPS
Applications that are shared among multiple
colleges and departments
Applications that are reused among multiple
colleges and departments
Applications that are local to a single college
or department
Summary of Recommendations
Scope of Application
Platform Recommendation
Core Administrative Systems of
Record
Java
Shared among Multiple Colleges Java, .NET, PHP, or ColdFusion
and Departments
Reused among Multiple Colleges Consider the platforms in use or supported
and Departments
by recipient departments
Local to a Single College or
Department
Any platform acceptable, but UCDsupported platforms still
recommended.
A Couple More Comments

Oracle Forms

Application Complexity and Platform
Future Work

Recommended platform configurations

Relative costs

(Non-technical) barriers to sharing and reuse

Interoperability standards

Process for vetting SSWG statements
Questions?

https: //confluence.ucdavis.edu/confluence/x/ogZxAQ

[email protected]