Personal tools
You are here: Home Corpora AMIDA corpus
Document Actions

AMIDA - Home

last modified 2008-08-23 08:30

AMIDA Scenario Data Collaction


Scenario Setup


In the remote meeting scenario, the participants are asked to take over and finish the design project after another team has carried out already the first two meetings: the kickoff meeting and the functional design meeting. All material of these two meetings is made available through the meeting browser. The participants are asked first to prepare their meeting, before carrying out the third meeting: the conceptual design meeting.

Raw media files can be downloaded by AMI partners only from the following page:

http://www.idiap.ch/mmm/corpora/amida-corpus/amida_data



Preparing the first meeting consists of:

  • Getting a personal gist
During the first meeting their task is:
  • Getting a shared gist: discussing what the project is about and formulate collectively the objective
  • Decide collectively on the role allocation: who should do what
After this meeting, the allocated User Interface Designer (UID) will move to a remote location. Preparing the second meeting consists of:
  • preparing the conceptual design meeting individually, using the meeting browser and e-mails for guidance
During the second meeting, the participants present their individual work and come to a conceptual design. The UID will announce that he can’t be available in the next meeting, but will help the ID in preparing that meeting. The ID will take over the role of the UID in that last meeting.

Preparing the third and final meeting consists of
  • the UID designer and Industrial Designer (ID) specify the form in clay. This will results in interesting communication: the UID has to explain his ideas of form from a distance.
The other participants prepare the meeting similar as in the original design project scenario.
At the third meeting: the detailed design meeting:
  • The remote UID needs to perform two important non-design tasks (we need to work out these tasks). One of those needs to be completed before s/he might be disturbed, the other only if it is very important. S/he indicates his/her availability (e.g. within Visual Nexus)
  • The other participants present their individual work
  • The clay prototype is presented and evaluated
  • At a certain point in time there is a need to consult the User Interface Designer (we need to come up with a trick to force this).

After the meeting, the Project Manager will describe the Product Specification Document.

When this scenario is used later during an evaluation, the remote participant will use the Meeting Assistant to catch up. The completion of his other two tasks will be used as a measure for the value of the catching up function.




Powered by Plone