No abstract

No abstract

No abstract

Navigating Augmented Reality (AR) environments with a handheld device often requires users to access digital contents (i.e. Points of Interests -POIs) associated with physical objects outside the field of view of the device's camera. Halo3D is a technique that displays the location of off-screen POIs as halos (arcs) along the edges of the screen. Halo3D reduces clutter by aggregating POIs but has not been evaluated. The results of a first experiment show that an enhanced version of Halo3D was 18% faster than the focus+context technique AroundPlot* for pointing at a POI, and perceived as 34% less intrusive than the arrowbased technique Arrow2D. The results of a second experiment in more realistic settings reveal that two variants of Halo3D that show the spatial distribution of POIs in clusters (1) enable an effective understanding of the off-screen environment and (2) require less effort than AroundPlot* to find POIs in the environment.

Background: Within the current organization of design activities it is difficult to fully realize the potential of BIM (Building Information Modelling). In BIM processes, it is necessary to identify and exchange the specific information that is relevant in the exchange information requirements of each project. The concept of level of detail of the information is a tool for describing and quantifying the information that should be exchanged. But the existing definitions of level of detail of information are not easily usable. Precise definitions of methodology, tools and principles are needed to redefine this concept and to use it in order to define the elements of information that are relevant to be exchanged. Methods: The authors propose the use of System Engineering and Requirements Engineering to define BIM uses and the relevant level of detail of information and its modelling concerned by each BIM use. The authors first explain why, in this context, the existing definitions of LOD, which can mean level of detail, level of development, level of definition, etc., are not sufficient and not always coherent. They demonstrate through real use cases that System Engineering and Requirement Engineering are a part of this methodology and propose, using formalisms, to describe each BIM use in detail. Results: The authors apply two different approaches to defining the relevant information to each BIM use. Using a top-down conceptual approach they show that Level Of Detail (LOD) is a crucial element in defining the content of a BIM use. They then verify the practicality of their proposal using a bottom-up approach based on three use cases (acoustic studies, safety audit, sizing drainage system). These cases studies allow the authors to address different kinds of systems and objects within a whole infrastructure project. They represent domain use cases (acoustic and drainage) and coordination use cases (safety audit). This part of the work is based on the L2 project in Marseille, which is a Public Private Partnership for expressways. As a result, a methodology is proposed both to redefine the level of detail of information concept and to describe how this concept is used to complete the BIM uses definition. The system engineering and requirement engineering methods are partially adapted to infrastructure projects. These elements facilitate the description of BIM uses expected in BIM Execution Plans. It was necessary to change the definitions of LOD in order to make them compatible with the methods of requirement management.