952 research outputs found

    prototypical implementations ; working packages in project phase II

    Get PDF
    In this technical report, we present the concepts and first prototypical imple- mentations of innovative tools and methods for personalized and contextualized (multimedia) search, collaborative ontology evolution, ontology evaluation and cost models, and dynamic access and trends in distributed (semantic) knowledge. The concepts and prototypes are based on the state of art analysis and identified requirements in the CSW report IV

    A multi-user collaborative BIM-AR system to support design and construction

    Get PDF
    This is an accepted manuscript of an article published by Elsevier in Automation in Construction on 29/11/2020, available online: https://doi.org/10.1016/j.autcon.2020.103487 The accepted version of the publication may differ from the final published version.Augmented Reality (AR) is fast becoming an established tool for the construction industry. Previous research reports on the conversion of BIM geometric models and the implementation of these with marker-based AR, or the use of more wide area AR taking positional input from GPS. Much of this focused on the use of AR in an individual context, so there is need to align AR with the more collaborative nature of BIM. By implementing marker-based AR, and connecting to a cloud-based database, the presented BIM-AR system provides the ability to view, interact and collaborate with 3D and 2D BIM data via AR with geographically dispersed teams. An Agile Scrum Method was used to develop the prototype system including a mobile AR application and a Large Touch Screen application based on and a Model, View, Controller (MVC) approach. Finally, the system was tested and verified using a focus group of construction practitioners.Accepted versio

    Human Machine Interaction

    Get PDF
    In this book, the reader will find a set of papers divided into two sections. The first section presents different proposals focused on the human-machine interaction development process. The second section is devoted to different aspects of interaction, with a special emphasis on the physical interaction

    Defining usability heuristics for adoption and efficiency of an electronic workflow document management system

    Get PDF
    Usability heuristics have been established for different uses and applications as general guidelines for user interfaces. These can affect the implementation of industry solutions and play a significant role regarding cost reduction and process efficiency. The area of electronic workflow document management (EWDM) solutions, also known as workflow, lacks a formal definition of usability heuristics. With the advent of new technologies such as mobile devices, defining a set of usability heuristics contributes to the adoption and efficiency of an EWDM system. Workflow usability has been evaluated for various industries. Most significantly research has been done for electronic healthcare records (EHR). In other areas such as the financial sector and educational institutions there is also some literature available but not as abundant as for EHR. This was identified as a possible research limitation. The general purpose of this research was to establish and validate an overarching set of usability heuristics for EWDM in general. This was approached by conducting a literature review and a survey on 32 workflow consultants from Hyland Software, Inc. Quantitative and qualitative data was collected focusing on the study’s main research question: “what usability heuristics should be defined to ensure the adoption and efficiency of a workflow implementation? Findings based on regression testing and expert opinions have suggested a proposed set of usability heuristics. The final list consists of: adaptability to diverse platforms, user control, system feedback, intuitive interfaces, visibility on mobile devices, error management, help, and documentation

    Advances in Streamlining Software Delivery on the Web and its Relations to Embedded Systems

    Get PDF
    Software delivery has evolved notably over the years, starting from plan-driven methodologies and lately moving to principles and practises shaped by Agile and Lean ideologies. The emphasis has moved from thoroughly documenting software requirements to a more people-oriented approach of building software in collaboration with users and experimenting with different approaches. Customers are directly integrated into the process. Users cannot always identify software needs before interacting with actual implementations. Building software is not only about building products in the right way, but also about building the right products. Developers need to experiment with different approaches, directly and indirectly. Not only do users value practical software, but the development process must also emphasise on the quality of the product or service. Development processes have formed to support these ideologies. To enable a short feedback-cycle, features are deployed often to production. A software is primarily delivered through a pipeline consisting of tree stages: development, staging and production. Developers develop features by writing code, verify these by writing related tests, interact and test software in a production-like 'staging' environment, and finally deploy features to production. Many practises have formed to support this deployment pipeline, notably Continuous Integration, Deployment and Experimentation. These practises focus on improving the flow of how software is being developed, tested, deployed and experimented with. The Internet has provided a thriving environment for using new practises. Due to the distributed nature of the web, features can be deployed without the need of any interaction from users. Users might not even notice the change. Obviously, there are other environments where many of these practises are much harder to achieve. Embedded systems, which have a dedicated function within a larger mechanical or electrical system, require hardware to accompany the software. Related processes and environments have their limitations. Hardware development can only be iterative to a certain degree. Producing hardware takes up front design and time. Experimentation is more expensive. Many stringent contexts require processes with assurances and transparency - usually provided by documentation and long-testing phases. In this thesis, I explore how advances in streamlining software delivery on the web has influenced the development of embedded systems. I conducted six interviews with people working on embedded systems, to get their view and incite discussion about the development of embedded systems. Though many concerns and obstacles are presented, the field is struggling with the same issues that Agile and Lean development are trying to resolve. Plan-driven approaches are still used, but distinct features of iterative development can be observed. On the leading edge, organisations are actively working on streamlining software and hardware delivery for embedded systems. Many of the advances are based on how Agile and Lean development are being used for user-focused software, particularly on the web

    Persuasive by design: a model and toolkit for designing evidence-based interventions

    Get PDF

    A human factors perspective on volunteered geographic information

    Get PDF
    This thesis takes a multidisciplinary approach to understanding the unique abilities of Volunteered Geographic Information (VGI) to enhance the utility of online mashups in ways not achievable with Professional Geographic Information (PGI). The key issues currently limiting the use of successful of VGI are the concern for quality, accuracy and value of the information, as well as the polarisation and bias of views within the user community. This thesis reviews different theoretical approaches in Human Factors, Geography, Information Science and Computer Science to help understand the notion of user judgements relative to VGI within an online environment (Chapter 2). Research methods relevant to a human factors investigation are also discussed (Chapter 3). (Chapter 5) The scoping study established the fundamental insights into the terminology and nature of VGI and PGI, a range of users were engaged through a series of qualitative interviews. This led the development of a framework on VGI (Chapter 4), and comparative description of users in relation to one another through a value framework (Chapter 5). Study Two produced qualitative multi-methods investigation into how users perceive VGI and PGI in use (Chapter 6), demonstrating similarities and the unique ability for VGI to provide utility to consumers. Chapter Seven and Study Three brought insight into the specific abilities for VGI to enhance the user judgement of online information within an information relevance context (Chapter 7 and 8). In understanding the outcomes of these studies, this thesis discusses how users perceive VGI as different from PGI in terms of its benefit to consumers from a user centred design perspective (Chapter 9). In particular, the degree to which user concerns are valid, the limitation of VGI in application and its potential strengths in enriching the user experiences of consumers engaged within an information search. In conclusion, specific contributions and avenues for further work are highlighted (Chapter 10)
    • …
    corecore