Workflow-oriented prototyping for the development of interactive software

Stary, Chris; Vidakis, Nectarios; Mohacsi, Stefan; Nagelholz, M.

doi:10.1109/cmpsac.1997.625063

Cited by 11 publications

(8 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It is generally understood to mean the actions undertaken by the end-user to achieve one step towards the goal. The time required to perform a specific task is still the most important factor to measure the value of an application in the work environment [60,59,61]. A specific task on handheld devices requires more time to complete the task than the same task on desktop computers (Fig.…”

Section: Participantsmentioning

confidence: 99%

Mobile computer Web-application design in medicine: some research based guidelines

Holzinger

Errath

2007

Univ Access Inf Soc

View full text Add to dashboard Cite

Designing Web-applications is considerably different for mobile computers (handhelds, Personal Digital Assistants) than for desktop computers. The screen size and system resources are more limited and end-users interact differently. Consequently, detecting handheld-browsers on the server side and delivering pages optimized for a small client form factor is inevitable. The authors discuss their experiences during the design and development of an application for medical research, which was designed for both mobile and personal desktop computers. The investigations presented in this paper highlight some ways in which Web content can be adapted to make it more accessible to mobile computing users. As a result, the authors summarize their experiences in design guidelines and provide an overview of those factors which have to be taken into consideration when designing software for mobile computers. ''The old computing is about what computers can do, the new computing is about what people can do'' (Leonardo's laptop: human needs and the new computing technologies, MIT Press, 2002).

show abstract

Section: Participantsmentioning

confidence: 99%

Mobile computer Web-application design in medicine: some research based guidelines

Holzinger

Errath

2007

Univ Access Inf Soc

View full text Add to dashboard Cite

show abstract

“…The TADEUS framework puts the following components into mutual context [19]: task model, user model, (problem domain) data model, and interaction (domain) model. For the sake of context-sensitivity all of them have to be related mutually, statically and dynamically (see also Figure 1).…”

Section: Contextual Development Using Tadeusmentioning

confidence: 99%

Contextual prototyping of user interfaces

Stary¹

2000

Proceedings of the 3rd Conference on Designing Interactive Systems: Processes, Practices, Methods, and Techniques

View full text Add to dashboard Cite

Contextual development differs from traditional user interface development in several ways: It focuses on the context of usage and the user population rather than on the technical features required for interaction. However, the latter come into play when transforming context specifications into user-interface code. Contextual development also considers design to be a non-linear process based on activities (re)engineering work processes rather than performing traditional software-engineering tasks. Consequently, contextual development requires usage-relevant (re)presentation and execution mechanisms. Although the specification of task-and user-knowledge has been recognized to be crucial for contextual user interface design, seamless development support is still lacking. The reported TA-DEUS (Task Analysis/Design/End User Systems) project targets toward an environment that allows contextual and seamless design and prototyping based on user and task knowledge. Due to its model-based nature TADEUS is open with respect to diagrammatic notations for specification, and different interaction platforms. As a result, different perspectives on the context, development process and its results can be kept consistent throughout development.

show abstract

“…The TADEUS (Task Analysis / Design / End User Systems) approach (Stary 1996a, Stary et al 1997a) provides a framework (in the sense of a global reference m odel, see ® gure 3) for representation, a methodology, and a corresponding environm ent for user interface developm ent. The inputs for the developm ent of the TA DEUS framework and representation scheme have been provided by techniques from work¯ow modeling as well as by user interface description language s. TADEUS aim s at integrating task-based and user-oriented developnent of interactive software, as these issues are m utually related (see the beginning of this section).…”

Section: Static and Dynam Ic User Mode Ling In Ta Deusmentioning

confidence: 99%

“…In order to speci® y the user interface, interaction features speci® ed in the interaction model have to be assigned to the tasks (presenting them to end users) as well as to the data that are going to be manipulated in the course of task accomplishment, for details see Stary et al (1997a ). In order to ® nalize the overall speci® cation of an application in TA D EUS, the OBD s of the involved interaction modalities have to be synchronized with task and data handling procedures that are represented in OBDs, too.…”

Section: Is-part-ofmentioning

confidence: 99%

Representation still matters: Cognitive engineering and user interface design

Stary¹,

Peschl²

1998

Behaviour & Information Technology

View full text Add to dashboard Cite

Abstract.With the increased utilization of cognitive models for designing user interfaces several disciplines started to contribute to acquiring and representing knowledge about users, artifacts, and tasks. Although a wealth of studies already exists on modeling mental processes, and although the goals of cognitive engineering have becom e quite clear over the last decade, essential epistemological and methodological issues in the context of developing user interfaces have remained untouched. However, recent challenging tasks, namely designing information spaces for distributed user comm unities, have led to a revival of well known problem s concerning the representation of knowledge and related issues, such as abstraction, navigation through information spaces, and visualization of abstract knowledge. All of these issues are associated with mental processes and thus, might becom e part of cognitive models. In this paper we reveal epistemological and methodological assumptions in the ® eld of cognitive modeling as well as their implications for user interface design. It turns out that in order to achieve the goal of developing hum an-oriented (in contrast to technology-driven) hum an-computer interfaces developers have to develop knowledge of the structure and the representational dynam ics of the cognitive systems which are interacting with the computer. We show that in a ® rst step it is necessary to study and investigate the diOE erent levels and forms of representation that are involved in the interaction processes between computers and human cognitive systems. We propose a hybrid user modeling approach as part of the task-based development procedure in TADEUS (Task Analysis/Design/End User Systems). The hybrid approach does not only enable the representation of functional roles end users have to perform, but also how end users perform these roles, i.e. the representation and re¯ection, if not prediction of their behavior. This way, holistic system developm ent that equally takes into account the organizational requirem ents and the end user reality at work places is facilitated.

show abstract

Workflow-oriented prototyping for the development of interactive software

Cited by 11 publications

References 4 publications

Mobile computer Web-application design in medicine: some research based guidelines

Mobile computer Web-application design in medicine: some research based guidelines

Contextual prototyping of user interfaces

Representation still matters: Cognitive engineering and user interface design

Contact Info

Product

Resources

About