NikosFrangakis
17-03-2006, 02:57 PM
This document contains the common user requirements applicable to the VR/VE utilisation within the domains reflected by the INTUITION Cluster 2 (CL2) Working Groups (WGs).
The “URD – Common” is nominally prepared with the contribution of the overall INTUITION Consortium open also to all external entities participating to the INTUITION Forum or to the various INTUITION events, according to the procedure described in the WP 1-5 ToR (INTUITION-CL1-WP1.5-R4-V1-URDUFTToR.doc). The first issue was prepared on the basis of the experience of the partners which driven the results obtained from the VIEW Project (VIEW-of the Future; Contract N. IST-2000-26089).
This document, once CL2 activities start, will collect inputs coming from the following INTUITION organised entities:
Forum participants,
Events participants,
Network Core Group members,
Advisory Board members, and most important
CL2 WGs members.
It is WP 1.5 partners’ task to collect requirements from these different sources, to discuss them with the interested WG, and to organise and manage them as described in the WP ToR.
This document contains also generalised schematic validation scenarios that are the most representative ones that were used to identify and collect the scenario specific requirements. Presently only two of these scenarios are included: one for the generic design & development application and the second one for the generic training application; these scenarios are two of those developed during VIEW Project by partners now participating to INTUITION. Only the common requirements across all VR applications, associated with the two above mentioned scenarios, are included in this document; the requirements present in this issue are coming from VIEW Project. In the next issues of this document it is envisaged that more validation scenarios and as a consequence additional and/or modifications to the present common requirements will be included.
In the annexes of this document is foreseen to include materials or references to publications to help the understanding of the validation scenarios. In the present issue the material included is limited to the training scenario.
The “URD – Common” is nominally prepared with the contribution of the overall INTUITION Consortium open also to all external entities participating to the INTUITION Forum or to the various INTUITION events, according to the procedure described in the WP 1-5 ToR (INTUITION-CL1-WP1.5-R4-V1-URDUFTToR.doc). The first issue was prepared on the basis of the experience of the partners which driven the results obtained from the VIEW Project (VIEW-of the Future; Contract N. IST-2000-26089).
This document, once CL2 activities start, will collect inputs coming from the following INTUITION organised entities:
Forum participants,
Events participants,
Network Core Group members,
Advisory Board members, and most important
CL2 WGs members.
It is WP 1.5 partners’ task to collect requirements from these different sources, to discuss them with the interested WG, and to organise and manage them as described in the WP ToR.
This document contains also generalised schematic validation scenarios that are the most representative ones that were used to identify and collect the scenario specific requirements. Presently only two of these scenarios are included: one for the generic design & development application and the second one for the generic training application; these scenarios are two of those developed during VIEW Project by partners now participating to INTUITION. Only the common requirements across all VR applications, associated with the two above mentioned scenarios, are included in this document; the requirements present in this issue are coming from VIEW Project. In the next issues of this document it is envisaged that more validation scenarios and as a consequence additional and/or modifications to the present common requirements will be included.
In the annexes of this document is foreseen to include materials or references to publications to help the understanding of the validation scenarios. In the present issue the material included is limited to the training scenario.