[845] in I/T Delivery
July Status Report - Java Architecture Group
daemon@ATHENA.MIT.EDU (Charles Shubert)
Tue Aug 6 14:15:23 2002
Date: Tue, 6 Aug 2002 14:15:13 -0400
Mime-Version: 1.0 (Apple Message framework v482)
Content-Type: multipart/alternative; boundary=Apple-Mail-1-958390186
From: Charles Shubert <cshubert@MIT.EDU>
To: delivery@mit.edu
Message-Id: <73EDC9A2-A968-11D6-A0BB-00039384A12E@mit.edu>
--Apple-Mail-1-958390186
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
format=flowed
Java Architecture for Infrastructure Services
Team Name: Java Architecture
Project Leader: Scott Thorne
Report Date: 8/5/2002
Submitted by: Chuck Shubert
Accomplishments:
In July we hosted the OKI Developers Meeting. During that meeting we
presented and discussed our thinking on issues associated with the
Course Administration and Content Management APIs. As part of our
presentation at that meeting we showed demonstration applications for
the hierarchy and filing APIs.
We have made considerable progress in system integration of the OKI
APIs. Our demonstration applications have focused our efforts on
creating and testing implementations of the dbc, filing, hierarchy, and
romi APIs.
We have been able to structure the development activities to effectively
integrate the development efforts of both programmers located at MIT and
at remote sites. This is an important side-effect of the OKI API
approach to developing software.
Goals:
There continues to be plenty to do: documentation, common service,
utility, and application layer API creation, implementation, testing,
documentation, and so on.
The work on the demonstration applications will continue in August with
a focus on integrating the authentication and authorization APIs.
We will be consolidating what we have learned in building the Snowmass
demonstration applications during August.
We will be adding a demonstration application and an implementation of
the user messaging API to test OKI system performance. The intent is to
use this demonstration application as well as the augmented existing
demonstration applications at the Educause meeting at the end of
September and the beginning of October.
Issues:
Structuring OKI work to handle the large number of activities currently
under way is the biggest current issue.
Team Dynamics:
The OKI team has moved from doing primarily individual effort work to
working in small groups to integrate the individual contributions.
There continues to be a lot to do. Developing the demonstration
applications continues to be fun.
--Apple-Mail-1-958390186
Content-Transfer-Encoding: 7bit
Content-Type: text/enriched;
charset=US-ASCII
<fontfamily><param>Arial</param>Java Architecture for Infrastructure
Services
Team Name: Java Architecture
Project Leader: Scott Thorne
Report Date: 8/5/2002
Submitted by: Chuck Shubert
Accomplishments:
In July we hosted the OKI Developers Meeting. During that meeting we
presented and discussed our thinking on issues associated with the
Course Administration and Content Management APIs. As part of our
presentation at that meeting we showed demonstration applications for
the hierarchy and filing APIs.
We have made considerable progress in system integration of the OKI
APIs. Our demonstration applications have focused our efforts on
creating and testing implementations of the dbc, filing, hierarchy,
and romi APIs.
We have been able to structure the development activities to
effectively integrate the development efforts of both programmers
located at MIT and at remote sites. This is an important side-effect
of the OKI API approach to developing software.
Goals:
There continues to be plenty to do: documentation, common service,
utility, and application layer API creation, implementation, testing,
documentation, and so on.
The work on the demonstration applications will continue in August
with a focus on integrating the authentication and authorization APIs.
We will be consolidating what we have learned in building the Snowmass
demonstration applications during August.
We will be adding a demonstration application and an implementation of
the user messaging API to test OKI system performance. The intent is
to use this demonstration application as well as the augmented
existing demonstration applications at the Educause meeting at the end
of September and the beginning of October.
Issues:
Structuring OKI work to handle the large number of activities
currently under way is the biggest current issue.
Team Dynamics:
The OKI team has moved from doing primarily individual effort work to
working in small groups to integrate the individual contributions.
There continues to be a lot to do. Developing the demonstration
applications continues to be fun.
</fontfamily>
--Apple-Mail-1-958390186--
