Designing Paper Disasters: An Authoring Environment for Developing Training Exercises in Integrated Emergency Management

Discussion-based exercises are a prevalent form of training in emergency management, aimed at improving coordinative decision making between the various agencies involved in disaster response. In each exercise, small multi-agency groups of decision makers discuss potential courses of action within a fictitious disaster scenario presented as a textual narrative supported by visual materials. We present a cognitive engineering analysis of the problem of designing disaster scenarios for effective discussion-based exercises. The analysis was carried out through the development of a pilot authoring environment to establish and address the requirements of a training organisation in the UK. The pilot authoring environment embodies a simple theoretical model of the exercise process in which facts of a disaster scenario afford discussion of pertinent issues which are elicited by considerations fed to trainees. This representational scheme allows the authoring environment to complement and extend authors’ mental models of exercises, and thereby enhance five aspects of authoring: rationalisation; continuity of rationale; evolution; adaptability; and the integration of evaluation feedback.     

Linguistic Problems with Requirements and Knowledge Elicitation

Human and conversational aspects of requirements and knowledge identification are employed to show that requirements ‘engineering’ is not the same as civil engineering or scientific problem solving. Not only can requirements not be made fully explicit at the start of a project, they cannot be made fully explicit at all. A need is identified to enhance computer-based information systems (CBIS) development methods to accommodate: plurality of incommensurable perspectives, languages and agendas; dynamic representations of system features that can be experienced rather than abstracted and forced into an abstract paper-based representation; recognition that CBIS development is in general a continuous process where users changing their minds is a natural and necessary indication or organisational vitality.  It is suggested that prototyping and rapid application development go some way to addressing these requirements but that they require further development in the light of the theoretical light thrown on the nature of the problem.     

Effective Communication in Requirements Elicitation: A Comparison of Methodologies

The elicitation or communication of user requirements comprises an early and critical but highly error-prone stage in system development. Socially oriented methodologies provide more support for user involvement in design than the rigidity of more traditional methods, facilitating the degree of user–designer communication and the ‘capture’ of requirements. A more emergent and collaborative view of requirements elicitation and communication is required to encompass the user, contextual and organisational factors. From this accompanying literature in communication issues in requirements elicitation, a four-dimensional framework is outlined and used to appraise comparatively four different methodologies seeking to promote a closer working relationship between users and designers. The facilitation of communication between users and designers is subject to discussion of the ways in which communicative activities can be ‘optimised’ for successful requirements gathering, by making recommendations based on the four dimensions to provide fruitful considerations for system designers.     

Specifications in Context: Stakeholders, Systems and Modelling of Conflict

This paper looks from an ethnographic viewpoint at the case of two information systems in a multinational engineering consultancy. It proposes using the rich findings from ethnographic analysis during requirements discovery. The paper shows how context – organisational and social – can be taken into account during an information system development process. Socio-technical approaches are holistic in nature and provide opportunities to produce information systems utilising social science insights, computer science technical competence and psychological approaches. These approaches provide fact-finding methods that are appropriate to system participants’ and organisational stakeholders’ needs.  The paper recommends a method of modelling that results in a computerised information system data model that reflects the conflicting and competing data and multiple perspectives of participants and stakeholders, and that improves interactivity and conflict management.     

Scenario Analysis in an Automated Tool for Requirements Engineering

 This paper presents an automated tool for scenario-driven requirements engineering where scenario analysis plays the central role. It is shown that a scenario can be described by three views of data flow, entity relationship and state transition models by slight extensions of classic data flow, entity relationship and state transition diagrams. The notions of consistency and completeness of a set of scenarios are formally defined in graph theory terminology and automatically checked by the tool. The tool supports automatic validation of requirements definitions by analysing the consistency between a set of scenarios and requirements models. It also supports automatic synthesis of requirements models from a set of scenarios. Its utility and usefulness are demonstrated by a non-trivial example in the paper. Case studies of the tools are also presented.     

Socio-Technical and Soft Approaches to Information Requirements Elicitation in the Post-Methodology Era

The contributors to this special issue focus on socio-technical and soft approaches to information requirements elicitation and systems development. They represent a growing body of research and practice in this field. This review presents an overview and analysis of the salient themes within the papers encompassing their common underlying framework, the methodologies and tools and techniques presented, the organisational situations in which they are deployed and the issues they seek to address. It will be argued in the review that the contributions to this special edition exemplify the ‘post-methodological era’ and the ‘contingency approaches’ from which it is formed.     

The New Frontier Issues for Cognition Technology

Cognitive engineering has developed enormously over the last fifteen years. Yet, despite many excellent research projects and publications, its full potential has not been embraced into mainstream system design. This paper will examine the reasons for this failure and argue that the problem is not simply inertia or lack of education. There are strong organisational influences that cause resistance to this particular approach. The discipline itself has characteristics that make it fragile in the modern corporate structure. In addition, the cognitive engineers themselves are not blameless in the equation. They appear to have done exactly what they criticise the engineering community for doing: they have packaged their product in a manner that is not ‘user friendly’ to its target population, not structured to suit its application, and not output in the format required. Suggestions will be made to rectify the situation: a list of actions is proposed for practising cognitive engineers to make their product more likely to enjoy widespread uptake.     

Deriving Goals from a Use-Case Based Requirements Specification

Use cases and scenarios have emerged as prominent analysis tools during requirements engineering activities due to both their richness and informality. In some instances, for example when a project’s budget or schedule time is reduced at short notice, practitioners have been known to adopt a collection of use cases as a suitable substitute for a requirements specification. Given the challenges inherent in managing large collections of scenarios, this shortcut is cause for concern and deserves focused attention. We describe our experiences during a goal-driven requirements analysis effort for an electronic commerce application. In particular, we identify the specific risks incurred, focusing more on the challenges imposed due to traceability, inconsistent use of terminology, incompleteness and consistency, rather than on traditional software project management risks. We conclude by discussing the impact of the lessons learned for requirements engineering in the context of building quality systems during goal and scenario analysis.     

Goal-Oriented Requirements Engineering: A Unifying Framework

The study of contemporary requirements engineering (RE) methodologies indicates that modelling of organisational goals constitutes a central activity of the RE process. In particular, goals provide the rationale and drive the elaboration of the requirements that operationalise them. They also provide the criteria against which the completeness and correctness of the requirements specification is validated. In other words, requirements implement goals in the same way that programs implement design specifications. Despite the significance of goals in RE, research in the field is fragmented. No research has so far taken place in order to define the overall role that goals play in RE. This paper puts forward a unifying view of goal analysis in the context of RE. This allows the identification of similarities and differences between the different conceptions of goal used by different approaches and promotes the understanding of the overall role of goal analysis in RE. Based on this understanding the various approaches can be put together, thus leading to a stronger goal-driven RE framework that takes advantage of the contributions from the many streams of goal-oriented research.     

Toward overcoming culture, skill and situation hurdles in Human-Computer Interaction

This paper proposes a new effective strategy for designing and implementing interactive systems overcoming culture, skill and situation hurdles in Human-Computer Interaction (HCI). The strategy to identify and reduce these hurdles is developed in the framework of a methodology based on a recently introduced model of HCI, and exploits the technological innovations of XML (Extensible Markup Language). HCI is modelled as a cyclic process in which the user and the interactive system communicate by materializing and interpreting a sequence of messages. The interaction process is formalized by specifying both the physical message appearance and the computational aspect of the interaction. This formalization allows the adoption of notation traditionally adopted by users in their workplaces as the starting point of the interactive system design. In this way, the human–system interaction language takes into account the users’ culture. Moreover, the methodology permits user representatives to build a hierarchy of systems progressively adapted to users’ situations, skills and habits, according to the work organization in the domain considered. The strategy is proved to be effective by describing how to implement it using BANCO (Browsing Adaptive Network for Changing user Operativity), a feasibility prototype based on XML, which allows the hierarchy implementation and system adaptations. Several examples from an environmental case under study are used throughout the paper to illustrate the methodology and the effectiveness of the technology adopted. Published online: 4 June 2002     

Scenario Development and Practical Decision Making under Uncertainty: Application to Requirements Engineering

In this paper, we address the question of how flesh and blood decision makers manage the combinatorial explosion in scenario development for decision making under uncertainty. The first assumption is that the decision makers try to undertake ‘robust’ actions. For the decision maker a robust action is an action that has sufficiently good results whatever the events are. We examine the psychological as well as the theoretical problems raised by the notion of robustness. Finally, we address the false feeling of decision makers who talk of ‘risk control’. We argue that ‘risk control’ results from the thinking that one can postpone action after nature moves. This ‘action postponement’ amounts to changing look-ahead reasoning into diagnosis. We illustrate these ideas in the framework of software development and examine some possible implications for requirements analysis.     

Everyday Life as a Stage in Creating and Performing Scenarios for Wireless Devices

Scenarios in HCI are widely used and discussed as written or visual narratives. In this paper, we discuss fruitful conditions for the creation and performance of scenarios particularly for the concept design of mixed realities or wireless devices. Designers are attempting new ways of engaging people in design and experiencing ideas in early design phases. Examples range from exploring scenarios using mock-ups or Wizard-of-Oz techniques, to testing scenarios with prototypes. In our design projects, scenarios were created and performed with participants following them in their daily activities. Discussing these sessions, which we called SPES (Situated and Participative Enactment of Scenarios), we highlight as promising conditions to create scenarios: the everyday life as a stage and the opportunity for participants to exercise reflection-in-action.     

Exploring Context-aware Information Push

Despite much interest over recent years in the area of context-aware computing, there are still a number of significant gaps in our understanding of the HCI issues associated with such systems. One particular issue that remains relatively unexplored is how to design around the apparently conflicting goals of adapting to changes in context while at the same time adhering to the principle of predictability. In this paper, we describe our exploration into this issue through two alternative designs of an interactive context-aware tourist guide. One original design was based around information pull, i.e. the emphasis is on the user to decide when context-aware information is presented. Our second design incorporates the notion of information push whereby the actual presentation of context-aware information is triggered by contextual events, e.g. changes in the user’s location or changes to the opening times of attractions. Through the evaluation of these alternative designs we hope to gain a better understanding of the usability implications relating to push vs. pull in both this specific domain and in interactive context-aware systems in general.     

Using Reason’s Model of Organisational Accidents in Formalising Accident Reports

This paper proposes a method for analysing what are called organisational accidents. The first step of the method involves using Reason’s model of organisational failures. This provides heuristic guidance in identifying both the active and latent conditions that lead to major failures. The second step involves applying formal methods to support a detailed analysis of each latent and active condition. The method is demonstrated on a case study: the railway accident at Watford Junction in the United Kingdom. Analysis of the formal model helps to identify organisational factors that might have prevented the accident. It also helps to identify weaknesses in the report itself. In particular we argue that a signalling standard was misunderstood, the consequences of which could lead to another serious accident.     

Performance Management in Breast Screening: A Case Study of Professional Vision

As part of a programme to investigate the requirements for computer-based detection aids in the NHS breast screening programme, we have been studying how the work of mammogram reading is done within different screening centres. Our findings show how various interactional practices have been evolved in order to help maintain readers’ performance within acceptable levels. In this paper, we investigate one of these in detail, the use of annotations on screening reporting forms, and we consider their role in managing readers’ performance. Finally, we consider the implications of such practices for the design of computer-based systems and tools for breast screening.     

Co-ordinating Distributed Knowledge: A Study into the Use of an Organisational Memory

This paper presents an ethnographically informed investigation into the use of an organisational memory, focusing in particular on how information was used in the performance of work. We argue that understanding how people make use of distributed knowledge is crucial to the design of an organisational memory. However, we take the perspective that an ‘organisational memory’ is not technology dependent, but is an emergent property of group interaction. In this sense, the technology does not form the organisational memory, but provides a novel means of augmenting the co-ordination of collaborative action. The study examines the generation, development and maintenance of knowledge repositories and archives. The knowledge and information captured in the organisational memory enabled the team members to establish a common understanding of the design and to gain an appreciation of the issues and concerns of the other disciplines. The study demonstrates why technology should not be thought of in isolation from its contexts of use, but also how designers can make use of the creative flexibility that people employ in their everyday activities. The findings of the study are therefore of direct relevance to both the design of knowledge archives and to the management of this information within organisations.     

Decision Making and Management of Dynamic Risk

Managing dynamic environments often requires decision making under uncertainty and risk. Two types of uncertainty are involved: uncertainty about the state and the evolution of the situation, and ‘openness’ of the possible actions to face possible consequences. In an experimental study on risk management in dynamic situations, two contrasted ‘ecological’ scenarios – transposed from effective situations of emergency management – were compared in order to identify the impact of their ‘openness’ in the subjects’ strategies for decision making. The ‘Lost Child’ scenario presented qualitative and irreversible consequences (child’s death) and high uncertainty; it exerted high demands both in risk assessment (risk representation) and action elaboration and choice. A less open situation (‘Hydrocarbon Fire’) required a main choice between two contrasted actions, with quantitative computable consequences. The strategies of ‘experimental subjects’ (university students) and ‘operative subjects’ (professional fire-fighter officers) were compared in order to evaluate the ecological validity of experimental research in this field, from the point of view of the subjects themselves. The two scenarios appeared to be independent, so that quite different models of decision making have to be hypothesised, differing by the importance of assessing risk and defining possible actions on the one hand, and by the process of choice on the other. ‘Experimental’ subjects dramatically differed from ‘operative’ subjects when confronted with the same scenario, particularly for the less technical but more demanding scenario. It is hypothesised that three components might account for the effect of the situations and for the differences between and within groups of subjects: importance of situation assessment, spatial abilities, and global orientation of activity in managing dynamic risk.     

Negotiating and Understanding Information Systems Requirements: The Use of Set Diagrams

A major contributor to the failure of information technology-based systems is the problem of understanding user or customer requirements in the initial analysis and requirements identification stage of development. This paper identifies and describes an approach to help overcome some of these problems, particularly the mismatch or understanding gap between the customer and the developer. The approach is intended to be used at the early stages of requirement determination and introduces techniques from operational research into the process. In particular set theory and Venn diagrams are used as a way of graphically representing the relationships and gaps in understanding that may exist. The benefit obtained from the use of the technique is partly in the graphical representations themselves but mainly in the dialogue and negotiation that result from the construction of the diagrams. The technique has been developed in a research study of retail organisations’ use of information technology in the UK and an example case study from the sector is used to illustrate and discuss the technique.     

Analysis and Classification of Human Driving Behaviour in an Urban Environment*

Intelligent vehicle systems have introduced the need for designers to consider user preferences so as to make several kinds of driving features as driver friendly as possible. This requirement raises the problem of how to suitably analyse human performance so they can be implemented in automatic driving tasks. The framework of the present work is an adaptive cruise control with stop and go features for use in an urban setting. In such a context, one of the main requirements is to be able to tune the control strategy to the driver’s style. In order to do this, a number of different drivers were studied through the statistical analysis of their behaviour while driving. The aim of this analysis is to decide whether it is possible to determine a driver’s behaviour, what signals are suitable for this task and which parameters can be used to describe a driver’s style. An assignment procedure is then introduced in order to classify a driver’s behaviour within the stop and go task being considered. Finally, the findings were analysed subjectively and compared with a statistically objective one.     

A Framework for Integrating Non-Functional Requirements into Conceptual Models

The development of complex information systems calls for conceptual models that describe aspects beyond entities and activities. In particular, recent research has pointed out that conceptual models need to model goals, in order to capture the intentions which underlie complex situations within an organisational context. This paper focuses on one class of goals, namely non-functional requirements (NFR), which need to be captured and analysed from the very early phases of the software development process. The paper presents a framework for integrating NFRs into the ER and OO models. This framework has been validated by two case studies, one of which is very large. The results of the case studies suggest that goal modelling during early phases can lead to a more productive and complete modelling activity.