Abstract

This paper presents a set of tools supporting the development of interactive systems using two different notations. One of these notations, called ConcurTaskTrees (CTT), is used for task modelling. The other notation, called Interactive Cooperative Objects (ICO), is used for system modelling. Even though these two kinds of models represent two different views of the same world (users interacting with interactive systems), they are built by different people and used independently. The aim of this paper is to propose the use of scenarios as a bridge between these two views. On the task modelling side, scenarios are seen as possible traces of activities, while on the system side, they are viewed as traces of actions. This generic approach is presented in a case study in the domain of Air Traffic Control. Document type: Part of book or chapter of book

Abstract

This chapter describes RESCUE (Requirements Engineering with Scenarios for a User-centred Environment), a method for specifying requirements for complex sociotechnical systems that integrates human activity modeling, creative design workshops, system goal modeling using the i* notation, systematic scenario walkthroughs, and best practice in requirements management. This method has been, and is being applied in, specifying requirements for three separate systems in the domain of air traffic control. In this chapter we present examples showing how the method can be applied in the context of a case study involving the specification of requirements for Countdown, a system to provide bus passengers with information about expected bus arrival times. While this system shares some important similarities with systems used in air traffic control, we hope it is small and familiar enough to readers to provide meaningful insights into the application of the RESCUE process. Document type: Part of book or chapter of book