PC-RE: a method for personal and contextual requirements engineering with some experience

  • Authors:

  • Alistair Sutcliffe;Stephen Fickas;McKay Moore Sohlberg

  • Affiliations:

  • Centre for HCI Design, School of Informatics, University of Manchester, P.O.Box 88, M60 1QD, Manchester, UK;Department of Computer & Information Science, University of Oregon, P.O.Box 88, 97403-1202, Eugene, OR, USA;Communication Disorders & Sciences, College of Education, 5251 University Of Oregon, P.O.Box 88, 97403-1202, Eugene, OR, USA

  • Venue:
  • Requirements Engineering
  • Year:
  • 2006

Quantified Score

Hi-index 0.00

Visualization

Abstract

A method for requirements analysis is proposed that accounts for individual and personal goals, and the effect of time and context on personal requirements. First a framework to analyse the issues inherent in requirements that change over time and location is proposed. The implications of the framework on system architecture are considered as three implementation pathways: functional specifications, development of customisable features and automatic adaptation by the system. These pathways imply the need to analyse system architecture requirements. A scenario-based analysis method is described for specifying requirements goals and their potential change. The method addresses goal setting for measurement and monitoring, and conflict resolution when requirements at different layers (group, individual) and from different sources (personal, advice from an external authority) conflict. The method links requirements analysis to design by modelling alternative solution pathways. Different implementation pathways have cost–benefit implications for stakeholders, so cost–benefit analysis techniques are proposed to assess trade-offs between goals and implementation strategies. The use of the framework is illustrated with two case studies in assistive technology domains: e-mail and a personalised navigation system. The first case study illustrates personal requirements to help cognitively disabled users communicate via e-mail, while the second addresses personal and mobile requirements to help disabled users make journeys on their own, assisted by a mobile PDA guide. In both case studies the experience from requirements analysis to implementation, requirements monitoring, and requirements evolution is reported.