[637] in I/T Delivery
October/November Status for Java Architecture Team
daemon@ATHENA.MIT.EDU (Charles Shubert)
Tue Dec 4 18:05:17 2001
Message-ID: <3C0D5617.E3F50BA0@mit.edu>
Date: Tue, 04 Dec 2001 18:02:47 -0500
From: Charles Shubert <cshubert@MIT.EDU>
MIME-Version: 1.0
To: delivery@mit.edu, Bob Ferrara <rferrara@mit.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Java Architecture for Infrastructure Services
Team Name: Java Architecture
Project Leader: Scott Thorne
Report Date: 12/3/2001
Submitted by: Chuck Shubert
Accomplishments:
The primary activity for October and November has been to create Service
API definitions and Java code. The definition work was expected to be
complete by the November meeting of the OKI Developers, but was delayed
by the absence of Chuck Shubert during late October and early
November. The impact of this has been a schedule slip of one week in
the development of the Java code for the Service APIs.
The November OKI Developers meeting in Palo Alto focused on a number of
Service API issues, the Learning Asset architecture, and was a working
session of the OKI technical development team. A general consensus was
reached on a large number of API issues. The earlier prototype Learning
Management Prototypes created at Stanford and MIT will become test beds
for Service API implementations. Extensive discussions were held on the
EALP output particularly in the area of Content Management.
Bibo Lai, a volunteer has joined the team and is currently writing
software that will both test the implementation of the Roles and Sql
APIs and serve as examples for future OKI developers. We are delighted
to have Bibo working with the team.
The CVS machine has been set up for OKI and now contains some initial
APIs and some implementations.
Goals:
This month we will be completing the OKI Service APIs. This work is
casting the APIs into Java. Several implementations have been built and
example programs are being written for both testing and as examples.
The focus of the development work will shift to implementation of all
the Service APIs and definition of the OKI APIs and Objects. The OKI
APIs and Objects are in the layer above the Service APIs and use the
Service APIs to implement their functionality.
Issues:
We are now structuring the work in anticipation of additional
development help coming from our OKI partners.
Key learnings:
The November OKI Developers' Meeting has reinforced our in our
architectural approach to OKI.
Team Dynamics:
The dynamics of the OKI team are very positive and continue undergo
change as we add people to the team. These changes continue to be
positive.
