80 likes | 180 Views
Using scenarios to capture information requirements. Helene Fowkes Cardiff University. About my talk. The aim : to demonstrate the use of scenarios as a tool for: supporting end-users assisting the information professional The focus : the TRESTLE project 1999-2001
E N D
Using scenarios to capture information requirements Helene Fowkes Cardiff University
About my talk ... • The aim: to demonstrate the use of scenarios as a tool for: • supporting end-users • assisting the information professional • The focus: the TRESTLE project 1999-2001 • Depts of Information Studies and Computer Science, University of Sheffield • GlaxoSmithKline (GSK) • The topics covered: • concept of scenarios • information extraction; • techniques for eliciting user requirements • usability evaluation
Scenarios: What are they? • Scenarios are about creating a story with a logical plot • Characteristics of scenarios: • applied to any context • future-orientated • anticipate change and the implications of those changes • The TRESTLE project used scenarios to: • design and evaluate an information service
Developing scenarios: About the project • Project aims: to develop an information system to: • facilitate competitive intelligence at GSK • apply text extraction techniques to a popular industry-wide online current awareness newsletter called scrip • The Challenge: to deliver a high precision current awareness service to scrip users at GSK. • My Challenge: to define the information scenarios and redesign the scrip interface
Creating scenarios:defining user information requirements • The aim: tobuild up a picture of: • user population: who are scrip users? • purpose and patterns of use • context of use: information, task and work environment • The methods used: • questionnaire • observations and verbal protocols • semi-structured interviews and prototyping • The outcome: 4 scenarios emerged, 2 were implemented in the information system
Using scenarios as an evaluation tool • Creating scenarios added functionality to scrip and required user feedback on: • usability e.g flexibility, ease of navigation, simplicity • relevance/added value e.g compatibility, acceptability • Scenarios were constructed that represented typical user information needs. Example: • “imagine that you are working on a project that is developing a new drug for treating asthma. You are keen to find out if what stage in the drug development process one of your main competitors, AstraZeneca, is at.”
Scenarios: a useful tool for information professionals? • Possible applications of scenarios: • designing and evaluating the usability of the library website • resource allocation • anticipating the impact of new technologies on information services • The benefits: more tailored and responsive information services?