Several comprehensive User Centred Design methodologies have been published in the last decade, but while they all focus on users, they disagree on exactly what activities should take place during the User Needs Analysis, what the end products of a User Needs Analysis should cover, how User Needs Analysis findings should be presented, and how these should be documented and communicated. This paper highlights issues in different stages of the User Needs Analysis that appear to cause considerable confusion among researchers and practitioners. It is our hope that the User-Centred Design community may begin to address these issues systematically. A case study is presented reporting a User Needs Analysis methodology and process as well as the user interface design of an application supporting communication among first responders in a major disaster. It illustrates some of the differences between the User-Centred Design and the Requirements Engineering communities and shows how and where User-Centred Design and Requirements Engineering methodologies should be integrated, or at least aligned, to avoid some of the problems practitioners face during the User Needs Analysis.
Description
ScienceDirect - Interacting with Computers : User Needs Analysis and requirements engineering: Theory and practice
%0 Journal Article
%1 Lindgaard2006
%A Lindgaard, Gitte
%A Dillon, Richard
%A Trbovich, Patricia
%A White, Rachel
%A Fernandes, Gary
%A Lundahl, Sonny
%A Pinnamaneni, Anu
%D 2006
%J Interacting with Computers
%K analysis requirements requirementsengineering se softwareengineering usercentered
%N 1
%P 47 - 70
%R 10.1016/j.intcom.2005.06.003
%T User Needs Analysis and requirements engineering: Theory and practice
%U http://www.sciencedirect.com/science/article/pii/S0953543805000573
%V 18
%X Several comprehensive User Centred Design methodologies have been published in the last decade, but while they all focus on users, they disagree on exactly what activities should take place during the User Needs Analysis, what the end products of a User Needs Analysis should cover, how User Needs Analysis findings should be presented, and how these should be documented and communicated. This paper highlights issues in different stages of the User Needs Analysis that appear to cause considerable confusion among researchers and practitioners. It is our hope that the User-Centred Design community may begin to address these issues systematically. A case study is presented reporting a User Needs Analysis methodology and process as well as the user interface design of an application supporting communication among first responders in a major disaster. It illustrates some of the differences between the User-Centred Design and the Requirements Engineering communities and shows how and where User-Centred Design and Requirements Engineering methodologies should be integrated, or at least aligned, to avoid some of the problems practitioners face during the User Needs Analysis.
@article{Lindgaard2006,
abstract = {Several comprehensive User Centred Design methodologies have been published in the last decade, but while they all focus on users, they disagree on exactly what activities should take place during the User Needs Analysis, what the end products of a User Needs Analysis should cover, how User Needs Analysis findings should be presented, and how these should be documented and communicated. This paper highlights issues in different stages of the User Needs Analysis that appear to cause considerable confusion among researchers and practitioners. It is our hope that the User-Centred Design community may begin to address these issues systematically. A case study is presented reporting a User Needs Analysis methodology and process as well as the user interface design of an application supporting communication among first responders in a major disaster. It illustrates some of the differences between the User-Centred Design and the Requirements Engineering communities and shows how and where User-Centred Design and Requirements Engineering methodologies should be integrated, or at least aligned, to avoid some of the problems practitioners face during the User Needs Analysis.},
added-at = {2011-07-22T11:08:10.000+0200},
author = {Lindgaard, Gitte and Dillon, Richard and Trbovich, Patricia and White, Rachel and Fernandes, Gary and Lundahl, Sonny and Pinnamaneni, Anu},
biburl = {https://www.bibsonomy.org/bibtex/2290ea07c5d828faa08fcfbfd663fab10/enitsirhc},
description = {ScienceDirect - Interacting with Computers : User Needs Analysis and requirements engineering: Theory and practice},
doi = {10.1016/j.intcom.2005.06.003},
interhash = {ff379350848cee2ffe21b2fc3b1b0887},
intrahash = {290ea07c5d828faa08fcfbfd663fab10},
issn = {0953-5438},
journal = {Interacting with Computers},
keywords = {analysis requirements requirementsengineering se softwareengineering usercentered},
note = {Special Theme Papers from Special Editorial Board Members (Contains Regular Papers)},
number = 1,
pages = {47 - 70},
timestamp = {2011-07-22T11:08:10.000+0200},
title = {User Needs Analysis and requirements engineering: Theory and practice},
url = {http://www.sciencedirect.com/science/article/pii/S0953543805000573},
volume = 18,
year = 2006
}