A field study of the software design process for large systems
Communications of the ACM
Using scenarios in design meetings—a case study example
Taking software design seriously
Designing interaction
Getting around the task-artifact cycle: how to make claims and design by scenario
ACM Transactions on Information Systems (TOIS)
Test early, test often: a formative usability kit for writers
SIGDOC '92 Proceedings of the 10th annual international conference on Systems documentation
A reappraisal of structured analysis: design in an organizational context
ACM Transactions on Information Systems (TOIS)
Cognitive systems engineering
Scenario-based design: envisioning work and technology in system development
Scenario-based design: envisioning work and technology in system development
Scenarios in discount usability engineering
Scenario-based design
Scenario-based design
The use-case construct in object-oriented software engineering
Scenario-based design
Project work: the organisation of collaborative design and development in software engineering
Computer Supported Cooperative Work - Special issue on studies of cooperative design
Collaborative conceptual design: a large software project case study
Computer Supported Cooperative Work - Special issue on studies of cooperative design
Requirements Elicitation and Validation with Real World Scenes
IEEE Transactions on Software Engineering
Requirements Development in Scenario-Based Design
IEEE Transactions on Software Engineering
Making Use of Scenarios for Validating Analysis and Design
IEEE Transactions on Software Engineering
Software for use: a practical guide to the models and methods of usage-centered design
Software for use: a practical guide to the models and methods of usage-centered design
The unified software development process
The unified software development process
Making Use: Scenario-Based Design of Human-Computer Interactions
Making Use: Scenario-Based Design of Human-Computer Interactions
The New Review of Information Behaviour Research
Scenario-Based Analysis of Software Architecture
IEEE Software
Scenarios in System Development: Current Practice
IEEE Software
Scenarios-an industrial case study and hypermedia enhancements
RE '95 Proceedings of the Second IEEE International Symposium on Requirements Engineering
Small-Scale Classification Schemes: A Field Study of Requirements Engineering
Computer Supported Cooperative Work
Scenario-based prototyping for requirements identification
Proceedings of the workshop on Rapid prototyping
A design process based on a model combining scenarios with goals and functions
IEEE Transactions on Systems, Man, and Cybernetics, Part A: Systems and Humans
Relating context to interface: an evaluation of picture scenarios
OZCHI '05 Proceedings of the 17th Australia conference on Computer-Human Interaction: Citizens Online: Considerations for Today and the Future
Pastiche scenarios: Fiction as a resource for user centred design
Interacting with Computers
OZCHI '07 Proceedings of the 19th Australasian conference on Computer-Human Interaction: Entertaining User Interfaces
An Organizational View of Pervasive Computing
Social Science Computer Review
Scenario-based usability engineering techniques in agile development processes
CHI '08 Extended Abstracts on Human Factors in Computing Systems
On the Process of Software Design: Sources of Complexity and Reasons for Muddling through
Engineering Interactive Systems
Scenario-based design as an approach to enhance user involvement and innovation
UAHCI'07 Proceedings of the 4th international conference on Universal access in human computer interaction: coping with diversity
Use case evaluation (UCE): a method for early usability evaluation in software development
INTERACT'07 Proceedings of the 11th IFIP TC 13 international conference on Human-computer interaction
Scenario-Based design of ambient intelligence
UCS'06 Proceedings of the Third international conference on Ubiquitous Computing Systems
Scenario-based interactive UI design
Proceedings of the SIGCHI Conference on Human Factors in Computing Systems
PLANT: A pattern language for transforming scenarios into requirements models
International Journal of Human-Computer Studies
Hi-index | 0.00 |
Scenarios have gained acceptance in both research and practice as a way of grounding software-engineering projects in the users' work. However, the research on scenario-based design (SBD) includes very few studies of how scenarios are actually used by practising software engineers in real-world projects. Such studies are needed to evaluate current SBD approaches and advance our general understanding of what scenarios contribute to design. This longitudinal field study analyses the use of scenarios during the conceptual design of a large information system. The role of the scenarios is compared and contrasted with that of three other design artefacts: the requirements specification, the business model, and the user interface prototype. The distinguishing features of the scenarios were that they were task based and descriptive. By being task based the scenarios strung individual events and activities together m purposeful sequences and, thereby, provided an intermediate level of description that was both an instantiation of overall work objectives and a fairly persistent context for the gradual elaboration of subtasks. By being descriptive the scenarios preserved a real-world feel of the contents, flow, and dynamics of the users' work. The scenarios made the users' work recognizable to the software engineers as a complex but organized human activity. This way the scenarios attained a unifying role as mediator among both the design artefacts and the software engineers, whilst they were not used for communication with users. The scenarios were, however, discontinued before the completion of the conceptual design because their creation and management was dependent on a few software engineers who were also the driving forces of several other project activities. Finally, the software engineers valued the concreteness and coherence of the scenarios although that entailed a risk of missing some effective reconceptions of the users' work.