[572] in I/T Delivery
Java Architecture Team Status
daemon@ATHENA.MIT.EDU (Robert Ferrara)
Thu Sep 13 18:16:50 2001
Message-Id: <5.0.2.1.2.20010913180840.0280b0c0@po9.mit.edu>
Date: Thu, 13 Sep 2001 18:16:33 -0400
To: delivery@mit.edu
From: Robert Ferrara <rferrara@MIT.EDU>
Cc: Charles Shubert <cshubert@mit.edu>, repa@mit.edu
In-Reply-To: <3BA11FB8.CC9F5E87@mit.edu>
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="=====================_29485878==_.ALT"
--=====================_29485878==_.ALT
Content-Type: text/plain; charset="us-ascii"
Hello,
Here's a report from the Java Architecture Team from Chuck Shubert. Since this was the first, I reformatted it slightly. This team's team work will figure very largely in future application development. So thanks to Chuck for this report. Cheers, Bob
-----------------------------------------------------
Team Name: Java Architecture
Project Leader: Scott Thorne
Report Date: 9/7/2001
Submitted by: Chuck Shubert
Accomplishments:
The Java API approach to making existing services available is firmly established. Roles API has be available for some time for review. Roles API implementation is complete and being tested. Modifications have been made to the Sql (database) API as a result of its use in the Roles API. A skeletal API for Workflow has been created and is under active construction. Early discussions of the OKI Learning Object have been held and the overall OKI architecture is starting to emerge.
Goals:
Plans are being made for an OKI workshop in late September in which we will extend development of the Common Services APIs. The will be a working session with invited architects. The intent of this session is to firm up the basic set of API for Common Services.
Issues:
Equipment: Timely installation of a CVS machine as a repository for API source code and other OKI documents is important as is the acquisition of a test machine. The OKI CVS machine will need to address the issue of access by developers from outside MIT.
Personnel: The addition of a new senior Java development person and possible redeployment of Stellar some personnel to OKI will require some attention.
Key learnings:
Presentations of the API expression of Common Services and OKI components to various professional organizations indicate that we are firmly in a leadership role and we are picking up a large amount of support from major players in this arena.
Team Dynamics:
Team dynamics are very positive and will undergo change as we add people to the team. We anticipate that these changes will also be positive.
--=====================_29485878==_.ALT
Content-Type: text/html; charset="us-ascii"
<html>
Hello, <br>
<br>
Here's a report from the Java Architecture Team from Chuck Shubert. Since
this was the first, I reformatted it slightly. This team's team
work will figure very largely in future application development. So
thanks to Chuck for this report. Cheers, Bob <br>
<br>
<font size=4>-----------------------------------------------------<br>
</font>Team Name: Java Architecture<br>
<br>
Project Leader: Scott Thorne<br>
<br>
Report Date: 9/7/2001<br>
<br>
Submitted by: Chuck Shubert<br>
<br>
Accomplishments: <br>
<br>
The Java API approach to making existing services available is firmly
established. Roles API has be available for some time for
review. Roles API implementation is complete and being
tested. Modifications have been made to the Sql (database) API as a
result of its use in the Roles API. A skeletal API for Workflow has been
created and is under active construction. Early discussions of the
OKI Learning Object have been held and the overall OKI architecture is
starting to emerge. <br>
<br>
Goals:<br>
<br>
Plans are being made for an OKI workshop in late September in which we
will extend development of the Common Services APIs. The will be a
working session with invited architects. The intent of this session
is to firm up the basic set of API for Common Services.<br>
<br>
Issues:<br>
<br>
Equipment: Timely installation of a CVS machine as a repository for
API source code and other OKI documents is important as is the
acquisition of a test machine. The OKI CVS machine will need to
address the issue of access by developers from outside MIT.<br>
<br>
Personnel: The addition of a new senior Java development person and
possible redeployment of Stellar some personnel to OKI will require some
attention.<br>
<br>
Key learnings:<br>
<br>
Presentations of the API expression of Common Services and OKI components
to various professional organizations indicate that we are firmly in a
leadership role and we are picking up a large amount of support from
major players in this arena.<br>
<br>
Team Dynamics:<br>
<br>
Team dynamics are very positive and will undergo change as we add people
to the team. We anticipate that these changes will also be
positive.<br>
<br>
<br>
<br>
</html>
--=====================_29485878==_.ALT--
