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

• Introduction
• Objectives
• Logistics
• Participants
• Program

Introduction  

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'.

Objectives  

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 ?).

Logistics  

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 *

Participants  

- 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]

Program  

1. [Sunday 15 January 2006]

   • Preparatory work - LimSee2/3 meeting between Daniel Weck and Romain Deltour: status update and identification of areas of collaboration for development of authoring tools for accessible motion pictures.

2. [Monday 16 January 2006]

   • Day 1 of Architecture face-to-face meeting.
   • 09:30-09:40 Hiroshi - welcome speech.
   • 09:40-09:45 Dipendra - introductory speech.
   • 09:45-10:00 Daniel - introduction: presentation of meeting agenda and review of expected outcome. Selection of a scribe to take the meeting minutes.
   • 10:00-10:15 Daniel - current status: project infrastructure (team members, websites, CVS repository, mailing-lists), modeling activity (use-cases/functional requirements, UML, other diagrams).
   • 10:15-10:20 Coffee/Tea/Cigarette break.
   • 10:20-10:25 Jack - update on CWI's Ambulant Annotator design and use-cases. Anything (concept, functional requirement) the Urakawa team should consider using/doing ?
   • 10:25-10:35 Romain - update on INRIA's LimSee3 design and use-cases. Same as above.
   • 10:35-10:50 Marisa, Julien - update on Urakawa use-cases, and the XML format currently in CVS.
   • 10:50-12:00 Daniel - proposal of high-level architecture diagram (unified functional-blocks). Then collective brainstorming: analyze use-cases, make a list of functional requirements (navigation, selections, etc.), and find a place in the diagram that describes the system (toolkit). Discussion about defining software modules that target each requirement, and about their mutual interaction (input/output, etc.).
   • 12:00-13:00 Lunch Break.
   • 13:00-14:00 Collective work - continue discussion on use-cases and functional requirements, but with a focus on object classes (concepts) rather than just functions. Identify and form groups to work on preliminary detailed design (draft of course) of the concepts raised during the discussion. The aim is to look at the time model in greater detail and see how it fits with navigation and core model.
   • 14:00-14:05 Coffee/Tea/Cigarette break.
   • 14:05-14:15 Collective work - determine groups for brainstorming on UML designs targeting specific business logic domains.
   • 14:15-15:30 Group work - modeling activity: produce UML designs, diagrams, brainstorming notes.
   • 15:30-16:30 Collective work - analyze integration issues between the various types of business logics involved: what types (and object classes) need to be shared between the independent models created by the groups ?
   • 16:30-16:40 Hiroshi, Dipendra, Daniel - close session, announce logistics and plans for dinner.

3. [Tuesday 17 January 2006]

   • International Workshop on Disaster Preparedness of Persons with Disabilities
   • 10:00-10:10 Opening of the workshop
   • 10:10-10:50 Report on WSIS: outcomes and follow-up, Hiroshi Kawamura
   • 10:50-11:10 Coffee break
   • 11:10-12:00 Session 1: Development of Accessible Multimedia I: Presentation of Urakawa Project and demonstration of DAISY Production and AMIS, Marisa DeMeglio and Mayu Hamada
   • 12:00-13:00 Lunch
   • 13:00-13:50 Session 2: Development of Accessible Multimedia II: SMIL 2.1 and SMIL authoring: Jack Jansen and Daniel Weck
   • 13:50-14:40 Session 3: Presentation of Reaerch on Attention Sensitive Disaster Preparedness Applications: AIST Research Team
   • 14:40-15:00 Coffee break
   • 15:00-16:30 Session 4: Needs of persons with autism spectrum disorders with special reference to Power Cards and other multimedia applications, Stephen Shore

4. [Wednesday 18 January 2006]

   • [[ IN PARALLEL: 09:00-17:00 Study visit to Keyakino Sato, etc. (without the Urakawa team) ]]
   • Day 2 of Architecture face-to-face meeting.
   • 09:30-09:40 Daniel - introduction to the agenda. Reminder of objectives.
   • 09:40-10:30 Collective work - restart brainstorming on integration between the different business-logic domains (Time, Filesystem I/O, Navigation, Selection, etc.). What data types are exchanged between the software modules ? What are the challenges involved ?
   • 10:30-10:35 Coffee/Tea/Cigarette break.
   • 10:35-11:00 Collective work - modeling activity: distribution of tasks according to the identified domains to cover.
   • 11:00-12:00 Group work - continue UML modeling.
   • 12:00-13:00 Lunch Break.
   • 13:00-14:00 Group work - continue UML modeling.
   • 14:00-14:30 collective work - wrap-up modeling activity. Explain/compare models. Be critical but constructive. Remarks will be used to determine action items and work assignments.
   • 14:30-14:35 Coffee/Tea/Cigarette break.
   • 14:35-15:30 Collective work - Decision making: identify the independent software modules that need to be designed in priority and then developed by the Implementation team. Propose a sequence of deliverables and estimate dates for major milestones. Decide on a start date for the Implementation team, and an end date for the Architecture team. Verify people's availability !
   • 15:30-15:50 Collective work - Tests, validation, quality: functional tests specifications can be defined by Architecture team at a cost (test reviews are even more time consuming). The minimum required should be pre and post conditions for the various processes involved in the model (input/output entities). Unit-testing is part of the Implementation team's activity: if test-driven development is the adopted paradigm.
   • 15:50-16:20 Collective work - discuss synchronization between Architecture, Implementation and Application. What process suits Marisa and Daniel for delivering models and implemented software modules, and for integrating these discrete productions into the global system (toolkit). Any best practice recommendation/experience ? Milestones for deliverable, review, integration and tests results: how many ? Setup a flexible formal process that meets the requirements of the various team members involved.
   • 16:20-16:30 Daniel - wrap-up: propose next meeting (location, date). Review work assignments, remind deadlines and checkpoints (teleconference, etc.).
   • 16:30-16:40 Hiroshi, Dipendra, Daniel - close session, announce logistics and plans for dinner.

5. [Thursday 19 January 2006]

   • 09:30-11:00 Session 4: Support/Training Center Scenario of Disaster Preparedness of persons with ASD, John Burke
   • 11:00-11:20 Coffee break
   • 11:20-12:50 Session 5: Family Support Scenario for Disaster Preparedness of children with autism, Mayer Max
   • 12:50-14:00 Lunch
   • 14:00-15:30 Session 6: Class Room Scenarios of Disaster Preparedness of Students with Disabilities, Judith Marco.
   • 15:10-15:30 Coffee break
   • 15:30-16:50 Session 7: Presentation on GIS based Inclusive Evacuation Training in Urakawa, NRCD Research Team

6. [Friday 20 January 2006]

   • 09:30-11:00 Session 8: Trends in Web Services and Web Accessibility, Judy Brewer
   • 11:00-11:20 coffee break
   • 11:20-12:50 Session 9: Observation and contribution from psychological point of view, Helen Sullivan
   • 12:50-14:00 Lunch
   • 14:00-15:00 Session 10: Concluding discussion and closing of the Workshop
   • 15:00-16:30 Study tour of NRCD including meeting with the President of NRCD

7. [Saturday 21 January 2006]

   • International Forum on Disaster Preparedness of Persons with Autism Spectrum Disorders and other Disabilities (NRCD College Auditorium)
   • 13:00-13:10 Opening, Tokutarou Sato, President of NRCD
   • 13:10-13:20 Welcome Message, Hatsue Suda, Vice President of Japan Autism Society
   • 13:20-13:40 Disability Inclusive ICT Development for Disaster Preparedness as an Outcome of WSIS, Hiroshi Kawamura, NRCD Research Institute
   • 13:40-14:40 Needs and Seeds to Support Persons with Autism be Well Prepared for Disasters, Stephen Shore, US Autism Society.
   • 14:40-14:50 break
   • 14:50-15:30 Support for Persons with Autism in the Community, John Burke, Kentucky Autism Training Center
   • 15:30-16:10 Support for Persons with Autism in Schools, Judith Marco,
   • 16:10-16:25 Comments by Mayer Max and Kohei Yamane
   • 16:25-16:30 Closing remarks, Motoi Suwa, Director of NRCD Research Institute
   • Stephen, John and Judith will be requested to limit their presentation not longer than 30 minutes and give rest of the time for Q&A and discussion.

8. [Sunday 22 January 2006]

   • Urakawa-admin meeting including Dipendra Manocha, Julien Quint, Marisa DeMeglio, Daniel Weck, and maybe other members. (To be refined)

9. [Monday 23 January 2006]

   • AMIS-related meeting including Jun Ishikawa, Julien Quint, Marisa DeMeglio and Daniel Weck. (Localization framework, Japanese IME, Porting). (To be refined)

10. [Tuesday 24 January 2006]

    • LimSee2 Japanese localization meeting with Koichi Yokota, Mayu Hamada and Daniel Weck.

End of document