Implementation of the aVOR app as a virtual patient into small instructional courses is well adopted by medical students and increases their competence in treating BPPV.

This papers describes an exploratory study into the early phase of getting to know end‐user software during which users make use of a variety of information resources, including the user interface/program itself, manuals, on‐line help, examples provided in the manuals and other sources. In particular, how do novices make use of the worked‐out examples often provided in manuals and during training? Building on earlier research on the self‐explanation effect, thinking aloud data from 10 participants were analysed to see how examples were studied and how they were used during problem solving. Important effects of self‐explaining comparable to findings in other domains were found in this study. For instance, those participants who self‐explain with the goal to discover meaning prove to be better problem solvers than those who do not self‐explain or who focus more on syntactical aspects of examples.

Abstract. Enterprise architecture (EA) management is a challenging task, modern enterprises have to face. This task is often addressed via organization-specific methodologies, which are implemented or derived from a respective EA management tool, or are at least partially aligned. Nevertheless, especially when starting an EA management endeavor, the documentation of the EA is often not likely to satisfy the level of formalization, which is needed to employ an EA management tool. This paper address the issue of starting EA management, more precise EA documentation and analysis, by utilizing a wiki-based approach.Today's enterprise wiki-systems provide numerous of services such as collaborative authoring, tagging, bookmarking, awareness, commenting, rating, linking, search, social networking, versioning, access control [1]. Furthermore, recent efforts aim to allow annotating semantic data within the wiki pages' content in enterprise wiki-Systems. How these functions can be applied for collaborative enterprise architecture (EA) modeling and documentation is explained by means of the following scenario. We illustrate how to model and describe the concepts shown in Figure 1 and corresponding instances in a wiki-based manner.

No abstract