A method for scenario-based requirements engineering is described. The method uses two types of scenario: structure models of " the system context and scripts of system usage. A modelling language is reported for describing scenarios, and heuristics are given to crosscheck dependencies between scenario models and the requirements specification. Heuristics are grouped into several anah,tic treatments that investigate correspondences between users' goals and system fimctions; input events and system processes to deal with them: system output and its destination in the scenario model, and acceptability anah,sis of system output for different stakehoMetw. The method is i/htstrated with a case study taken from the London Ambulance Service report. The prospects for scenario-based requirements engineering and related work are discussed.

Abstract: We propose an interface design process compatible with scenario-based design methods, but specifically intended to facilitate three primary goals: design knowledge reuse, comparison of design products, and long-term research growth within HCI. This effort describes a computer-aided design tool suite, LINK-UP, which supports the design process for specific genre of systems that cross many domains—notification systems. We describe the vision for LINK-UP, contrasting underlying concepts with typical task-based modeling approaches. To achieve its stated goals, the design process is organized and guided by critical parameters, presenting several challenges that we reflect on through the results of a design simulation study. The possibilities envisioned through this approach have important implications for the integration of reusable design knowledge, HCI processes, and design support tools.

The experience of preparing interface design knowledge to be reusable allows reflection on the process, potential, and general challenges of effectively and efficiently using this knowledge in design tasks. With an interest in crafting a catalog for design claims that would implement recent reuse theory in the human-computer interaction field, we developed and implemented a unique process of creating reusable content for notification systems---interfaces used for multitasking. This process, which we describe and illustrate, extends previous work on capturing metadata related to design claims. The data and metadata are stored in the catalog, which is intended to be accessible to other designers for reuse in other domains. The multitask nature of our catalog subject matter highlights a major challenges faced in reuse: the generalization specific and contextual information (claims). The challenge of balancing abstraction with specificity to ensure both meaningful and domainindependent data is also addressed. We believe that our approach can generalize to other reuse projects that strive for cross-domain knowledge application.

We elaborate a proposal for capturing, extending, and reusing design knowledge gleaned through usability testing. The proposal is specifically targeted to address interface design for notification systems, but its themes can be generalized to any constrained and well-defined genre of interactive system design. We reiterate arguments for and against using critical parameters to characterize user goals and usability artifacts. Responding to residual arguments, we suggest that clear advantages for research cohesion, design knowledge reuse, and HCI education are possible if several challenges are overcome. As a first step, we recommend a slight variation to the concept of a critical parameter, which would allow both abstract and concrete knowledge representation. With this concept, we demonstrate a feasible approach by introducing equations that elaborate and allow evolution of notification system critical parameters, which is made operational with a variety of usability evaluation instruments. A case study illustrates how one general instrument allowed system designs to be meaningfully compared and resulted in valuable inferences for interface reengineering. Broad implications and conclusions about this approach will be of interest to others concerned with using critical parameters in interface design, development of notification systems interfaces, or approaches to design rationale and knowledge reuse.

Jackson's Problem Frames provide a means of analysing and decomposing problems. They emphasise the world outside the computer helping the developer to focus on the problem domain instead of drifting into inventing solutions. The intention is to delay consideration of the solution space until a good understanding of the problem is gained.

Abstract. The main contribution of this paper is an initial method for automatically exploiting ontology design patterns with the aim of further automating the creation of enterprise ontologies in small-scale application contexts. The focus is so far on developing a fully automated construction method, thereby somewhat reducing the requirements on ontology customization and level of detail. In this paper we present an approach how to use knowledge (patterns) from other areas, like data modeling, knowledge reuse, software analysis and software design, to create ontology patterns. These design patterns are then used within our method for automatically matching and pruning them, in accordance with information extracted from existing knowledge sources within the company in question. Though the method still needs some fine-tuning, it has already been used when creating an enterprise ontology for a suppliercompany within the automotive industry. 1

patterns are an accepted way to facilitate and support reuse. This paper focuses on patterns in the field of Ontology Engineering and proposes a classification scheme for ontology patterns. The scheme divides ontology patterns into five levels: Application Patterns, Architecture Patterns, Design Patterns, Semantic Patterns, and Syntactic Patterns. Semantic and Syntactic Patterns are quite well-researched but the higher levels of pattern abstraction are so far almost unexplored. To illustrate the possibilities of patterns on these levels some examples are discussed, together with ideas of future work. 1

We discuss our research into the development and testing of a notification system claims library for assisting designers in interface development. Our research focuses on achieving consistent values among multiple users when adding and searching claims. We discuss the methods used for redesigning the application, techniques used for testing, and reengineering goals for the Claims Library. This work extends previous efforts on design knowledge reuse in the HCI research community, as such our methods and techniques should be reusable by others. We designed the interface to the library for users entering claims, ensuring usability and understandability. Since we noted problems with a particular feature (the IRC input method) through an internal round of testing, we conducted a lab-based test to isolate specific breakdowns. Our results validated portions of claim classification indices, suggest key reengineering changes that should inform ongoing and future development of the claims library—of broad interest of notification systems developers.

Based on extensive empirical observation of design activities that might be supported by a knowledge repository, we report conclusions from three case studies. Seeking to improve research infrastructure necessary to cultivate a “science of design ” within human-computer interaction, we focus on identifying essential activities that help proceduralize the key requirements of knowledge management within a software development effort. From related literature, we selected five focus points for our analyses, which in turn, guided development of our repository in terms of how design knowledge is used, reused, and harvested through system tools. The case studies successively validate potential activities, while exposing breakdowns in process or practice that show promise of being resolved with additional tool features highlighted in other cases. Emerging largely from our case studies, we present general guidelines and tradeoffs for developing a design knowledge repository, as well as directions for further empirical study. 1.

Interaction. Please do not cite or circulate without permission from the authors. A computer system does not itself express the motivations that initiated its design, the user requirements it was intended to address, the discussions, debates and negotiations that determined its organization, the reasons for its particular features, the reasons against features it does not have, the weighing of tradeoffs, and so forth. This information comprises the design rationale of the system. It can be critical to the many stakeholders in a design process: customers, users, service providers, and marketers, as well as designers who want to build upon the system and the ideas it embodies. Design rationale can contribute to theory development in HCI in three ways. First, it provides a foundation for ecological science in HCI by describing the decisions and implicit causal relationships embodied in HCI artifacts. Second, it provides a foundation for action science in HCI by integrating activities directed at description and understanding with those directed at design and development. Finally, it provides a framework for a synthetic science of HCI in which the insights and predictions of diverse technical theories can be integrated. The preceding chapters illustrated how theoretical concepts and methods from a variety of sciences are used to gain insight in the context of HCI design and evaluation. This chapter inverts that train of thought to some extent. It shows how reflective HCI design practices — involving design rationale documentation and analysis — can be used (1) to closely couple theoretical concepts and methods with the designed artifacts that instantiate them, (2) to more closely integrate theory application and theory development in design work, and (3) to more broadly integrate the insights of different technical theories. 1.