1 / 15

ARCHEOGUIDE Augmented Reality-based Cultural Heritage On-site Guide

morrisa
Download Presentation

ARCHEOGUIDE Augmented Reality-based Cultural Heritage On-site Guide

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Archeoguide Kick-off Meeting Olympia 24-25 January, 2000 ARCHEOGUIDE Augmented Reality-based Cultural Heritage On-site Guide Application Requirements & Scenarios

    2. Objectives To identify the actors in the field. To collect, analyze, and organize the ARCHEOGUIDE requirements. To provide realistic application scenarios for the ARCHEOGUIDE.

    3. Requirements Specification Phase

    4. Archeoguide Actors - Cultural Site Visitors They wear the HMD displays in order to have access to the Archeoguide End-user application. Types of Visitors (different skills, age, education level, cultural and linguistic backgrounds): Individuals, tourists Schools Families Students Scientists, Archeologists Expectations: Personalized information User friendly interface Ease to use Easy to learn

    5. Archeoguide Actors - Site Managers They have access to all the Archeoguide tools, retrieving also information about the usage of the Archeoguide system. Expectations: Increase the number of visitors Increase the mean time of stay on site Increase the reputation and the visibility of the site

    6. Archeoguide Actors - Content Creators They use the Archeoguide authoring tools for providing content to the Archeoguide system. Expectations: Easy to Use authoring tools Easy to learn authoring tools Quick Content creation Easy Adaptation and Use of existing content

    7. Archeoguide Actors - Ministries of Culture Monitor the deployment and the usage of the system. Responsible for the archeological areas Provide Content Expectations: Reliable, friendly and exciting system Increase the number of visitors Increase the mean time of stay on site Increase the reputation and the visibility of the site Success of the system Extend the use of the system to other sites

    8. Archeoguide Actors - System Administrator S/he uses the Archeoguide administration tool in order to administer the Archeoguide system. Expectations: Easy of Installation Easy to Administer Ability to administer all the aspects of the system Rapid responds to problems System Fault Tolerance

    9. Requirements Section Outline 1. Introduction 1.1. Purpose 1.2. Scope 1.3. Overview 2. General Description 2.1. Product Perspective 2.2. Product Functions 2.3. User Characteristics 2.4. General Constraints 2.5. Assumptions and Dependencies 3. Specific Requirements 3.1. Functional Requirements 3.2. Performance Requirements 3.3. Interface Requirements 3.4. Operational/Resource Requirements Appendixes

    10. ARCHEOGUIDE Application Scenarios

    11. UML(Unified Modeling Language) a unification of Booch, OMT and OOSE methods A de facto standards in the domain of object-oriented analysis and design UML Use Case View allows to depict a usage scenario and the users (actors in UML terminology) involved. For each scenario, a typical course of events has to be provided in a tabular format. The requirements related to each scenario have to be listed by considering the priority and the relevance with respect to the project. UML tools (e.g. from Rational Software) permit source code generation and reverse engineering. UML in the requirements phase

    12. Example of Use Case

    13. Typical Course of Events

    14. Functional Requirements

    15. Action Points Actors Identification Assignment for actor-specific questionnaire preparation Assignment for technical partners that will provide technical requirements Planning of user interviews Planning of deliverables preparation

More Related