Urakawa Project Report

By Dipendra Manocha
April 9, 2006

The work of the Urakawa project is clearly divided into 4 groups: architecture team which is preparing the core data model, Implementation team which is preparing the code of the SDK based on the data model, the application team which is preparing the DAISY authoring tool to demonstrate the capabilities of the SDK of the Urakawa Engine and the Management group.

The full project timeline for first iteration of the Urakawa Project (covering the period from March to August 2006) is available online at Sourceforge.net and is maintained by team coordinator, Markus Gylling.

Human resource:

The Architecture Team was officially started on 2005-December-01, with the following members:

On 2006-March-03 , the Architecture team composition was reduced to accommodate the formation of the Implementation team:

Architecture team members:

Implementation team members since March 3, 2006:

Following are the members working in the application team:

Avneesh and Suman joined the project from February 1, 2006. Markus Gylling joined the project back in February 2006 with the role of team coordination.

Meetings:

In order to check progress reports and write task assignments, the Urakawa project teams mainly used email. The mailing-list archive is hosted by DAISY. The URL for this archive is: Urakawa Archive (Note: to access this archive, authentication is required).

The modeling activity also included regular conference calls, using free VoIP software Skype (computer-to-computer calls). Weekly skype calls on every Monday are also held between team leads.

Full reports for face-to-faces and conference calls (attendance, agenda, minutes, logistics, etc.) are available on the following Urakawa WebPages: SourceForge DAISY Projects.

Deliverables

The architecture team has a schedule of three milestones in its deliverables. Two of these three mile stones have been reached.

Here is a description of the obtained deliverable:

Features highlights:

Deliverables are hosted at Sourceforge.net, under the SVN ("Subversion") Versioning Control System at SourceForge. A simple web-interface provides direct read-only access to the documents.

The UML diagrams are produced using an accessible declarative format based on the Java programming language. This provides greater flexibility in terms of the possible renderings (output formats), and ensures that the model can be hosted and managed effectively by Version Control Systems (CVS, SVN, etc.).

The tools used to convert the declarative UML specification to various output formats are:
UMLGraph
GraphViz

Note: Due to the problems at the CVS Servers, the project documents were moved from the CVS to the SBN on the source forge. This problem also caused delay in delivery of the second milestone by 3 days.

Implementation team work

The implementation team has begun its first phase of work. So far, the focus has been on the architecture team's Milestone #1 design (presented at the Cannes face to face meeting), and now is in transition to Milestone #2 (made available on April 4th, 2006). Other major implementation tasks include incorporating the validation framework and design of the XUK file format.

The next face to face meeting of the implementation group is scheduled to be held in Copenhagen. This is scheduled from May 21-25.

Application team

The DAISY Consortium is working on the contract with the NRCD to deliver an application for authoring DAISY 3 DTBs. The application team of the Urakawa project will be developing this application based on the data-model and the SDK developed by the Urakawa Project. A mock-up of this application and initial prototype of the application was delivered on April 3, 2006 to NRCD on behalf of the DAISY Consortium. Both the Mock-up of the UI and the prototype are available at following URLs:
Urakawa Prototype
Protobi

During the New York Face to face the application team developed the scope of the application and specifications for first iteration of the Urakawa project.

The development work on the final application is in progress. A Face to Face meeting with Indian programmers is scheduled on April 17-18.