* This document is tentative *

Urakawa Project, Architecture Team

Face-to-face meeting [1]

Tokyo (Japan), 16-18 January 2006.

Authors : Hiroshi KAWAMURA, Daniel WECK
Editor : Daniel WECK
Last revision : 09 January 2006
(Note: some content has been copied directly from Hiroshi's draft agendas: workshop v2 and forum v1. Original content can be found in Hiroshi's email entitled 'International Workshop and Forum in January 2006 draft agenda')

Table of contents


This first face-to-face meeting for the Architecture team is taking place jointly with a workshop organized and hosted by NRCD. The workshop entitled 'International Workshop on Disaster Preparedness of Persons with Disabilities' is a major opportunity for the Urakawa face-to-face participants to identify requirements of people with autism. This is why an interactive session is organized between the specialists in technology and the experts in disabilities (full schedule can be found below, in the section called "Program").

Workshop Objectives

  1. Identify needs of persons with disabilities for disaster preparedness.
  2. Identify use cases of accessible multimedia in order to address those requirements in the multimedia standards development process.
  3. Establish a sustainable link between persons with disabilities and ICT development for disaster prevention including preparedness, early warning, evacuation, first response and recovery.

The workshop will be followed by a forum entitled 'International Forum on Disaster Preparedness of Persons with Autism Spectrum Disorders and other Disabilities'.


Note: Some of these meeting objectives may not be met immediately: the expected outcome will include work assignments to achieve these goals in the short term.

  1. Functional Requirements, Scope - Determine accurate scope for the API/toolkit (from both design and implementation perspectives), based on use-cases/requirements. What is the minimum set of independent functionality required in order to deliver a demonstration application working on top of the implemented toolkit at iteration 1 (July 2006) ?

  2. System Overview, Connected Software Modules - Unify the identified functional blocks and produce high-level architecture diagrams. Separate the different types of business logic and decompose the object-oriented world. Highlight domains (toolkit, application, or core vs "utilities", etc.).

  3. Well-Defined, Implementable Intermediate Goals - Refine the roadmap by identifying implementable sub-deliverables (such as "core", "input/output layer"), and by prioritizing some functionality (decide collectively on what criteria to use). The actual number of sub-deliverables should be sufficient for insuring realistic/achievable deliverables in the short-term, and for allowing a very responsive iterative development model (deliver model, review, implement, report back). The team should agree on the nature of interactive cycles between Architecture and Implementation teams at each milestone. (note: the original development model expressed in the current Gantt roadmap excludes interaction between Architecture and Implementation, implementation starts only at the end of the modeling activity, when a full model specification is available)

  4. Resource Planning, Time Estimates - Estimate durations of each iteration, so that the "sum" of each milestone form the full model to be delivered on due time. Collectively review the current time constraints expressed in the Gantt roadmap, and decide on a realistic end of activity for the Architecture team, based on the refined development model. Discuss the start of the Implementation team, so that it corresponds to the first milestone (model level 1). The planned date for this event is strategic, because it implies that the Architecture team looses some members who move to the Implementation team.

  5. Produce UML and other relevant Design Diagrams - Harmonize the existing UML diagrams (Core Model, Asset Manager, Selection Model, and Node Visitor Pattern), and introduce the TimeModel.

  6. Prepare Remote Collaboration, Organize Deliverables - Determine work assignments and short-term deadlines. Setup work and reporting procedures. Agree on formalized checkpoints (with or without project manager) at regular short intervals between team members. Extend/improve the current infrastructure if necessary (Skype telconfs, Wiki, Staff ?).


Participants from the Urakawa project are required (if possible) to attend the Architecture team face-to-face meeting on January 16 and 18, as well as the joint interactive session on January 17.

The rest of the event (workshop and forum) are optional, but recommended. Participants should check that sufficient funding is available to cover the extra cost of hotel accommodation.

NRCD will provide with meeting rooms including lunch, coffee or tea, and other logistical support including some social events.

The event will take place in Tokyo, Japan. The venue is the same for both the international workshop and the Urakawa face-to-face meeting, only meeting rooms will differ.

Hotel bookings will be handled by our host, the NRCD. Participants need to check in by 15th and check out on or after 19th.

* Details will be communicated as soon as possible *


- Urakawa project members

  1. Hiroshi KAWAMURA (DFA Project Manager and NRCD R&D Director, Management team member)
    [Availability: already on-site, full meeting duration]

  2. Dipendra MANOCHA (Urakawa Project Manager, Management team member, DFA)
    [Availability: Arrives 15 Jan. Leaves 23 Jan.]

  3. Daniel WECK (Architecture team head, DFA)
    [Availability: Arrives 14 Jan. Leaves 25 Jan.]

  4. Marisa DEMEGLIO (Architecture team member, Implementation team head, DFA)
    [Availability: Arrives 14 Jan. Leaves 25 Jan.]

  5. Jack JANSEN (Architecture team member, CWI)
    [Availability: Arrives 15 Jan. Leaves 19 Jan.]

  6. Julien QUINT (Application team head, NRCD)
    [Availability: already on-site, full meeting duration]

  7. Laust SKAT NIELSEN (Architecture team member, DBB)
    [Availability: Arrives 15 Jan. Leaves 22 Jan.]

  8. Ole ANDERSEN HOLST (Architecture team member, DBB)
    [Availability: Arrives 15 Jan. Leaves 22 Jan.]

  9. Romain DELTOUR (Architecture team member, INRIA)
    [Availability: Arrives 14 Jan. Leaves 17 Jan.]

  10. Markus GYLLING (Architecture team member, TPB)
    [Regrets: won't be able to attend the meeting.]

  11. Laurie SHERVE (Architecture team member, DAISY)
    [Regrets: won't be able to attend the meeting.]

- FYI: other workshop/forum experts

(this section is for information purposes only, the list may be very incomplete/inacurate)

  1. Judy BREWER (Director of the W3C's Web Accessibility Initiative (WAI))
  2. Stephen SHORE (Expert in Autism and Asperger Syndrome)
  3. John BURKE (Kentucky Autism Training Center KATC)
  4. [Mayer MAX][wwwMayerMAX] (Sharkatech Research)
  5. [Judith MARCO][wwwJudithMARCO]
  6. [Helen SULLIVAN][wwwHelenSULLIVAN]
  7. Brenda MYLES (Expert on Autism, Asperger Syndrome and special education, University of Kansas) [To be confirmed]


  1. [Sunday 15 January 2006]

  2. [Monday 16 January 2006]

  3. [Tuesday 17 January 2006]

  4. [Wednesday 18 January 2006]

  5. [Thursday 19 January 2006]

  6. [Friday 20 January 2006]

  7. [Saturday 21 January 2006]

  8. [Sunday 22 January 2006]

  9. [Monday 23 January 2006]

  10. [Tuesday 24 January 2006]

End of document

Valid XHTML 1.1Valid CSS