Figure 1 - uploaded by Dirk Draheim
Content may be subject to copyright.
Source publication
The representation of GUIs as documents is a technological trend that has been present for some years, but is only now about to significantly change the way in which most user interfaces are developed. This paper examines this change, explains the reasons behind it and the concepts involved. It compares the old fashioned way of programming user int...
Context in source publication
Context 1
... mitigate the necessity of programming in the process of GUI creation, there exist many visual tools for editing GUIs. These tools usually let a user compose a GUI in a more or less WYSIWIG-style and then generate program code for that GUI which can be integrated into the application being developed. In Fig. 1, for example, we see the Visual Studio IDE showing a GUI design on the left and the corresponding generated code on the right side. ...
Similar publications
one convenient and yet power full way for teaching protective relaying design and application, is to model and simulation techniques. Therefore, this paper presents designing a Graphical User Interface (GUI) mode for digital differential relay, to protected power transformer based on MATLAB software, where the GUI can help the end users to run simu...
Recently security problems in the Graphic User Interface (GUI) of applications have become a serious threat for system security. Because much of security experts don't design the GUI from end user's point of view, users have problems to practice security. The aim of Human & Computer Interaction (HCI) and Security (HCI-Sec) is to improve the usabili...
The vision of Pervasive and Ubiquitous Computing promises that our future environments will be furnished with an increasing number of computationally augmented artifacts. Consequently new services and applications, which will come up, should fit into the lifestyle and life-patterns of very different individuals unobtrusively. In this paper we prese...
The starting point of this thesis is to deal with the difficulties encountered in the TEL community for designing educational applications exploiting geographic information. Ultimately, it is to provide a new framework allowing for the operational design of geographic Web applications for experts in the domain (and particularly for teachers). The s...
This paper presents a platform, named MultiCom, for the design and the evaluation of user interfaces and more generally of interactive systems or products dedicated to the end user. MultiCom is a kind of "usability lab" which contains various distributed resources on network and dedicated software to capture and analyse the human working with a com...
Citations
... Various definitions of electronic documents exist, each coming with different intentions: from the domain of libraries (ISO 2709, MARC , Dublin Core etc.) over technical exchange formats (ODF, PDF etc.) to enterprise computing (ISO 10244, Moreq etc.), compare also with [37][38][39][40][41]. In this paper, we use digital document (ii) as the name of a communication mode. ...
Our aim is to understand technological and socio-economic barriers to blockchain solutions that are intrinsic in the blockchain technology stack itself (permissionless as well as permissioned). On the basis of that, we want to understand the future potentioal impact of blockchain technology. We provide an argumentation against the theoretical background of Williamson's instutional analysis framework, and triangulate the insights with results from four design science research efforts. We (i) characterize cryptocurrency as one-tiered collateralized money. We (ii) review potential blockchain solutions against defined essential modes of communications. We review (iii) well-known scalability issues and potential denial-of-service attacks through a new probabilistic model. We (iv) characterize a typical neglection of physical network infrastructure in blockchain technology discussions. We (v) describe four successful blockchain solutions and explain their design. There is (vi) no evidence that the proclaimed ``blockchain revolution'' can disrupt our institutional stack; instead, it can only happen in the boundaries of the current institutional stack. Nevertheless, it is possible to (vii) design useful blockchain solutions. The findings of this research enable policy makers, decision makers and information systems architects alike to make informed decisions about blockchain technology and its application. Given its theoretic foundation in new institutional economics, triangulated with comprehensive results from design science efforts, this study is the first of its kind in the area of blockchain technology research. <br
... Building on the growing interest in AUI descriptions, Draheim et al. introduced the concept of ''GUIs as documents'' [17]. The authors provide a detailed comparison of four GUI development paradigms, proposing a documentoriented GUI paradigm where editing of the graphical user interface can take place at application runtime. ...
... The distinction of these two types is not sufficient to accurately describe the possible ways in which sighted and blind users may collaborate. Proximity between users 16 does not actually impact collaboration much as long as an adequate communication channel 17 is available. The ability to interact directly with the computer system that the users collaborate about can certainly be a benefit, and this can often be accomplished both locally and by means of remote connectivity. ...
... Sighted users often tend to depend on a visual focal point when collaborating about the interaction with a system or an application. 17 The main requirement for the communication channel is that it provides for sufficient bandwidth to enable efficient and specific exchange of information. A phone connection is often much more constructive to collaboration than, for example, an online chat session. ...
While providing non-visual access to graphical user interfaces has been a topic of research for over 20 years, blind users still face many obstacles when using computer systems. Furthermore, daily life has become more and more infused with devices that feature some kind of visual interface. Existing solutions for providing multimodal user interfaces that ensure accessibility are largely based on either graphical toolkit hooks, queries to the application and environment, scripting, model-driven user interface development or runtime adaptation. Parallel User Interface Rendering (PUIR) is a novel approach based on past and current research into accessibility, promoting the use of abstract user interface descriptions. Based on a single consistent conceptual model, PUIR provides a mechanism to render a user interface simultaneously in multiple modalities. Each representation of the UI provides equivalent semantics to ensure that collaboration between users of different modalities is facilitated. The possible application of this novel technique goes well beyond the realm of accessibility, as multimodal interfaces become more popular and even needed. The design presented here has been implemented as a prototype for testing and further research in this fascinating area of HCI.
... Within recent years, we have seen the emergence of GUI representation being implemented using documents instead of code [18]. Using this approach, GUI representation is implemented in a more declarative fashion, commonly in markup based languages [25]. ...
... By using a document-oriented approach, there are many advantages discussed in [18] including separation of concerns, compatibility, editibility, non-universality and abstraction. Also, with many development platforms, What You See Is What You Get (WYSI-WYG) editors are included for the GUI documents, allowing developers to preview their GUI without the need for compilation and testing. ...
Dynamic Software Product Line (DSPL) Engineering has gained interest through its promise of being able to unify software adaptation whereby software adaptation can be realised at compile time and runtime. While previous work has enabled program logic adaptation by the use of language extensions and platform support, little attention has been placed on Graphical User Interface (GUI) variability. Different design patterns including the Model View Controller are commonly used in GUI implementation, with GUI documents being used for declaring the GUI. To handle dynamic GUI variability currently, the developer needs to implement GUI refinements using multiple techniques. This paper proposes a solution for dealing with GUI document variability, statically and dynamically, in a unified way. In our approach, we currently use a compile time method for producing GUI variants, and code transformations to handle these variants within the application at runtime. To avoid GUI duplicates, only GUI variants that are unique, and related to a valid product configuration, are produced. To validate our approach, we implemented tool support to enable this for Android based applications.
... Going further in the transformational document approach, the document-oriented GUI enables users the edit directly documents on the web, considering that the Graphical User Interface is also a document (Draheim, Lutteroth & Weber, 2006). Coupled with XML technologies and composite hypermedia item structure, this technique enables addressing item authoring as a layered edition of embedded documents describing different components or aspects of the item. ...
This chapter reviews the contribution of new information-communication technologies to the advancement of educational assessment. Improvements can be described in terms of precision in detecting the actual values of the observed variables, efficiency in collecting and processing information, and speed and frequency of feedback given to the participants and stakeholders. The chapter reviews previous research and development in two ways, describing the main tendencies in four continents (Asia, Australia, Europe and the US) as well as summarizing research on how technology advances assessment in certain crucial dimensions (assessment of established constructs, extension of assessment domains, assessment of new constructs and in dynamic situations). As there is a great variety of applications of assessment in education, each one requiring different technological solutions, the chapter classifies assessment domains, purposes and contexts and identifies the technological needs and solutions for each. The chapter reviews the contribution of technology to the advancement of the entire educational evaluation process, from authoring and automatic generation and storage of items, through delivery methods (Internet-based, local server, removable media, mini-computer labs) to forms of task presentation made possible with technology for response capture, scoring and automated feedback and reporting. Finally, the chapter identifies areas for which further research and development is needed (migration strategies, security, availability, accessibility, comparability, framework and instrument compliance) and lists themes for research projects feasible for inclusion in the Assessment and Teaching of Twenty-first Century Skills project. © 2012 Springer Science+Business Media B.V. All rights reserved.
... Womöglich wäre es in solch einem Fall einfacher die Oberfläche mit einem moderneren Framework neu zu gestalten, als den Quelltext mit einem eigenen Parser zu lesen und versuchen zu interpretieren. Weitere Nachteile, die Dialoge in Quelltextform mit sich bringen, sind in [Draheim, et al., 2006] beschrieben. ...
... Womöglich wäre es in solch einem Fall einfacher die Oberfläche mit einem moderneren Framework neu zu gestalten, als den Quelltext mit einem eigenen Parser zu lesen und versuchen zu interpretieren. Weitere Nachteile, die Dialoge in Quelltextform mit sich bringen, sind in [Draheim, et al., 2006] beschrieben. ...
Berührungsempfindliche Bildschirme wurden in den letzten Jahren immer günstiger und beliebter. Die grafischen Benutzeroberflächen von Anwendungen für Desktop- und Laptopcomputer sind jedoch für eine solche Eingabeart nicht ausgelegt und neue Programmversionen ändern diesen Umstand auch kaum. In dieser Diplomarbeit wird daher eine Methode vorgestellt, um Entwicklern die Möglichkeit zu geben, ihre Dialoge automatisch auf die Benutzung für Touch anzupassen. Dafür wurde ein Prototyp entwickelt, der die automatische Transformation von Dialogen in der Dialogbeschreibungssprache XAML erlaubt. Die Migration der Dialoge wird durch eine parametrisierbare Transformationsvorschrift in XSLT durchgeführt. Zusätzlich kann mit einer beliebigen .NET Sprache in den Migrationsprozess eingegriffen werden. Um die Funktionsfähigkeit der beschriebenen Transformation zu zeigen, wurde im Rahmen dieser Diplomarbeit eine Studie auf einem berührungsempfindlichen Bildschirm durchgeführt. Dazu wurden zwei Dialoge mehrmals transformiert, indem die Steuerelemente automatisch verändert und ersetzt wurden. Außerdem wurden einige Steuerelemente für die Studie analysiert und entsprechend von Gestaltungsregeln für die Benutzung mit den Fingern angepasst, um in der Studie bewertet zu werden.
... However, for a particular project, a level of detail should be fixed by a style guide, at least for the most concrete system descriptions in the hierarchy, but at best for all the levels in the hierarchy. For example, with form-oriented analysis [89,82,83,95,94,96,97,105,106,92,87,107] we have proposed a style guide for the level of system dialogue specification. Here, the formcharts have only two kinds of entities that are wired, i.e., the reports that are shown to the user at the computer screen and the server actions that appear as interaction capabilities for the user in the realm of a report. ...
... The typed workflow chart is an extension of the formchart that addresses the needs of workflow definition. Similarly, typed business process analysis is a generalization of form-oriented analysis [89,82,83,95,94,96,97,105,106,92,87,107] that addresses the needs of business process specification. The framework of typed business process analysis is also amenable to the integration of business process modeling in general and workflow definition in particular as we will detail in Sect. ...
The purpose of this chapter is to characterize workflow-intensive systems from a human-computer interaction viewpoint, i.e.,
it explains how a typical ITapplication is experienced by a user. It explains how a typical IT application structures the
work of its user. Therefore the notion of worklist is explained and how current workflow technology orchestrates applications
and programs that implement system dialogues on the basis of a worklist paradigm. As an important by-product the chapter contributes
to the understanding of the gap between workflow definition and application programming. The chapter also discusses how workflow
technologies can support the assignment of actors to tasks. Again, we try to conduct the discussion as product-independent
as possible. What interests us are the basic concepts behind concrete role models found in today’s workflow technologies.
... However, for a particular project, a level of detail should be fixed by a style guide, at least for the most concrete system descriptions in the hierarchy, but at best for all the levels in the hierarchy. For example, with form-oriented analysis [89,82,83,95,94,96,97,105,106,92,87,107] we have proposed a style guide for the level of system dialogue specification. Here, the formcharts have only two kinds of entities that are wired, i.e., the reports that are shown to the user at the computer screen and the server actions that appear as interaction capabilities for the user in the realm of a report. ...
... The typed workflow chart is an extension of the formchart that addresses the needs of workflow definition. Similarly, typed business process analysis is a generalization of form-oriented analysis [89,82,83,95,94,96,97,105,106,92,87,107] that addresses the needs of business process specification. The framework of typed business process analysis is also amenable to the integration of business process modeling in general and workflow definition in particular as we will detail in Sect. ...
Isn’t it compelling to apply the structured programming arguments to the field of business process modeling? Our answer to
this question is ‘no’.
... The document-oriented approach views a GUI as a structured document analogous to forms that can be created in office applications (Draheim et al. 2006). ...
... In this paper we describe how GUI customization can be improved by supporting transclusion of GUI specification parts. We describe a document-oriented GUI customization system (Draheim et al. 2006), the Auckland Interface Model (AIM) (Lutteroth & Weber 2008), which has been implemented on the Java, .NET, and Haiku platforms. Document orientation means that GUIs can be treated like documents, i.e. they can be modified, saved and loaded at runtime. ...
... The main benefit of using separate languages to specify GUIs is the separation of concerns (Draheim et al. 2006). Separating the specification of the GUI from the program logic makes the structure of an application clearer, and allows developers to edit the GUI without navigating the program logic. ...
Usually the possibilities for end users to customize GUIs to their requirements are limited. We present a GUI specification and customization system, the Auckland Interface Model (AIM), that represents GUIs as documents that can be loaded, saved and changed by the end user during runtime. GUI layout and GUI content can be customized independently, and GUIs can be decomposed using transclusion. In this paper, we explain why transclusion is an important feature for GUI customization that does not only facilitate the maintenance of a GUI, but also supports its consistency and clarity. Transclusion makes it easier to reuse GUI specifications, and support different customization scopes. AIM was implemented on several platforms and evaluated using the cognitive dimensions framework.
... Layout of GUI elements is a necessary component of GUI design, independent of many of the technological changes. This holds true even in the current shift from programmatically specified GUI descriptions to document-based descriptions such as XUL, which we observed early on and which we accompanied with theoretical considerations [6]. It is surprising that in many object-oriented GUI frameworks, their most sophisticated layout managers, namely the Grid-bag Layout managers, do not offer modelbased abstractions. ...
Many major programming platforms support layout managers in Grid-bag style, where GUI elements can be placed on a rectangular grid. In Grid-bag layout mangers, cells of the underlying grid can be merged in order to create more complex layouts. In this work we classify software engineering issues with Grid-bag layout managers - chiefly bad coupling and a low level of abstraction - into several levels of severity of these issues. In the past we have presented the Auckland Layout Model, which is based on tabstops instead of gridlines. The Auckland Layout Model provides several layers of abstraction and avoids the bad coupling phenomena encountered in Grid-bag Layout. In this work we report on a platform-independent reduction of Grid-bag Layout to Auckland Layout, thus establishing that Grid-bag Layout can be implemented on top of Auckland Layout Model. The reduction of Grid-bag Layout to Auckland Layout presented here is based on an abstract datatype called a Grid-bag analyzer.
