[584] in I/T Delivery
September Status for Java Architecture Team
daemon@ATHENA.MIT.EDU (Charles Shubert)
Sat Oct 6 11:16:47 2001
Message-ID: <3BBF1FE2.9BD441D0@mit.edu>
Date: Sat, 06 Oct 2001 11:14:42 -0400
From: Charles Shubert <cshubert@MIT.EDU>
MIME-Version: 1.0
To: delivery@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: 10/5/2001
Submitted by: Chuck Shubert
Accomplishments:
The primary activity this month was the OKI Developers Meeting. A large
amount of effort was spent on looking at Roles as a model for the OKI
Rules Engine. This pre-Meeting effort yielded a mechanism for defining
the key element of the next layer of OKI. This key element currently
uses the name "OKI Asset". The OKI Developers meeting was a working
session of the OKI technical development team. The sessions were
focused on the definition of the OKI Common Services. A general
consensus was reached on the principle issues of a variety of common
services. Assignments were distributed to the participants and groups
formed to develop Java APIs for each of the Common Services. Extensive
discussions were held on the OKI Asset and how it might address a
variety of educational application needs. Giri Swarminathan, the new
member of this team, participated in the pre-meeting work as well as the
meeting itself and is now fully integrated into the team. The CVS
machine is being set up for use by the OKI developers.
Goals:
This month we will be working on a variety of OKI APIs. This work
includes defining the API, casting it into Java, and in a number of
cases building implementations. Existing APIs and implementations will
be reviewed and tested. In addition to the API work a significant
amount of effort will be spent on further development of the OKI-Asset
concept. The EALP meeting during the second week of October will focus
on defining 2 or 3 applications that would use OKI-Assets and OKI Common
Services. The output from this meeting will frame the development work
for the rest of the month and until the next OKI Developers Meeting in
mid-November.
Issues:
The output of the EALP meeting will serve as a reality check for the
current OKI work.
Key learnings:
We continue to gain confidence 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. We anticipate that these changes
will also be positive.
