An architecture for flexible, evolvable process-driven user-guidance environments

  • Authors:

  • Timothy J. Sliski;Matthew P. Billmers;Lori A. Clarke;Leon J. Osterweil

  • Affiliations:

  • Laboratory for Advanced Software Engineering Research, Department of Computer Science, University of Massachusetts at Amherst, Amherst, MA;Laboratory for Advanced Software Engineering Research, Department of Computer Science, University of Massachusetts at Amherst, Amherst, MA;Laboratory for Advanced Software Engineering Research, Department of Computer Science, University of Massachusetts at Amherst, Amherst, MA;Laboratory for Advanced Software Engineering Research, Department of Computer Science, University of Massachusetts at Amherst, Amherst, MA

  • Venue:
  • Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
  • Year:
  • 2001

Quantified Score

Hi-index 0.00

Visualization

Abstract

Complex toolsets can be difficult to use. User interfaces can help by guiding users through the alternative choices that might be possible at any given time, but this tends to lock users into the fixed interaction models dictated by the user-interface designers. Alternatively, we propose an approach where the tool utilization model is specified by a process, written in a process definition langauge. Our approach incorporates a user-interface specification that describes how the user-interface is to respond to, or reflect, progress through the execution of the process definition. By not tightly binding the user-guidance process, the associated user-interfaces, and the toolset, it is easy to develop alternative processes that provide widely varying levels and styles of guidance and to be responsive to evolution in the processes, user interfaces, or toolset. In this paper, we describe this approach for developing process-driven user-guidance environments, a lossely coupled architecture for supporting this separation of concerns, and a generator for automatically binding the process and the user interface. We report on a case study using this approach. Although this case study used a specific process definition language and a specific toolset, the approach is applicable to other process definition languages and toolsets, provided they meet some basic, sound software engineering requirements.