2002
DOI: 10.1046/j.1365-2575.2003.00138.x
|View full text |Cite
|
Sign up to set email alerts
|

The user–developer communication process: a critical case study

Abstract: Abstract. Although user participation in systems development is widely believed to have positive impacts on user acceptance, it does not guarantee success and there is still much that we do not know about how and why user participation sometimes delivers positive benefits, but not always. Much of the prior research on user participation assumes that user–developer communication will ensure that the resulting system will be designed to meet users’ needs and will be accepted by them. The nature and quality of th… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

2
110
0
2

Year Published

2003
2003
2023
2023

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 132 publications
(114 citation statements)
references
References 48 publications
2
110
0
2
Order By: Relevance
“…[8], [7]). Barki and Hartwick [9] stress the need to identify users and user needs before an information system is designed and implemented.…”
Section: Importance Of User Involvementmentioning
confidence: 99%
See 1 more Smart Citation
“…[8], [7]). Barki and Hartwick [9] stress the need to identify users and user needs before an information system is designed and implemented.…”
Section: Importance Of User Involvementmentioning
confidence: 99%
“…Recent research has questioned the general assumption that user involvement leads to success [8]. Uncertainties on the real usefulness of user involvement add further arguments to an increased research focus on these issues.…”
Section: Importance Of User Involvementmentioning
confidence: 99%
“…According to Gallivan and Keil (2003) majority of prior researches investigating user involvement in software development will ensure clear requirements definitions, resulting in the system which meets user needs. However, Saiedian and Dale (2000) identified the following main difficulties in requirements elicitation: (1) poor communication, (2) resistance as a physical and emotional expression, (3) articulation of problems, and (4) different perspectives on problem to be solved.…”
Section: Related Workmentioning
confidence: 99%
“…Difficulties in identifying and involving relevant user groups (Gulliksen & Eriksson, 2006;Karlsson et al, 2012), and PD being time-consuming and lacking in formalisation (Gallivan & Keil, 2003;Wilson et al, 1997), are commonly reported. In IS development, frameworks and theories exist for identifying stakeholders and users, for example, stakeholder theory and the related developed frameworks (e.g.…”
Section: Participatory Design Of Information Systems In Erssmentioning
confidence: 99%