The use of scenarios in design

Authors:
Bonnie A. Nardi
Affiliations:
-
Venue:
ACM SIGCHI Bulletin
Year:
1992

Citing 0
Cited 12

Software requirements and acceptance testing

Annals of Software Engineering
From conceptual modelling to requirements engineering

Annals of Software Engineering
Replicating the CREWS Use Case Authoring Guidelines Experiment

Empirical Software Engineering
An ethnographic approach to design

The human-computer interaction handbook
Automated Prototyping of User Interfaces Based on UML Scenarios

Automated Software Engineering
Controlling simulation games through rule-based scenarios

Proceedings of the 38th conference on Winter simulation
Automatic Synthesis Of Behavioral Object Specifications From Scenarios

Journal of Integrated Design & Process Science
From user needs to system specifications: Multi-disciplinary thematic seminars as a collaborative design method for development of health information systems

Journal of Biomedical Informatics
Reflections on a work-oriented design project

Human-Computer Interaction
Developing a Scenario Database for Product Innovation

HCD 09 Proceedings of the 1st International Conference on Human Centered Design: Held as Part of HCI International 2009
User interface prototyping based on UML scenarios and high-level Petri nets

ICATPN'00 Proceedings of the 21st international conference on Application and theory of petri nets
Reflections on 25 Years of Ethnography in CSCW

Computer Supported Cooperative Work

Quantified Score

Hi-index	0.00

Visualization

Abstract

A scenario is a description of a set of users, a work context, and a set of tasks that users perform or want to perform. A scenario sketches future technologies that will help users do the things they want to do. A scenario blends a carefully researched description of some set of real ongoing activities with an imaginative futuristic look at how technology could support those activities better.