2005
DOI: 10.3127/ajis.v13i1.72
|View full text |Cite
|
Sign up to set email alerts
|

Consensus Making in Requirements Negotiation: the communication perspective

Abstract: When developing an Information System (IS), organizational goals of various stakeholders are commonly in direct conflict. Furthermore, individuals often rank their private objectives well over their management's directions. Recognising and reconciling all these diverse goals, and reaching agreement among the stakeholders, are prerequisite to establishing project cooperation and collaboration. This paper focuses, in particular, on the negotiation and consensus making during requirements elicitation -the earlies… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
7
0

Year Published

2006
2006
2017
2017

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 11 publications
(7 citation statements)
references
References 16 publications
0
7
0
Order By: Relevance
“…Various reasons exist for software system development failures. Such failures are often attributed to issues associated with human communication factors with respect to the determination of requirements (Alvarez, 2002;Price and Cybulski, 2007). Therefore, communication skills are considered in the present study.…”
Section: Stakeholders' Communication Skillsmentioning
confidence: 99%
See 1 more Smart Citation
“…Various reasons exist for software system development failures. Such failures are often attributed to issues associated with human communication factors with respect to the determination of requirements (Alvarez, 2002;Price and Cybulski, 2007). Therefore, communication skills are considered in the present study.…”
Section: Stakeholders' Communication Skillsmentioning
confidence: 99%
“…This phase directly impacts the quality and cost of the software. Ineffective elicitation process generally generates poor requirements and this leads to a lowquality system, a delay in the schedule and an increase in costs (Price and Cybulski, 2007). For a successful requirements elicitation process, active and appropriate stakeholder participation is required.…”
Section: Requirements Elicitationmentioning
confidence: 99%
“…Nguyen and Cybulski share this view and compare the RE process to an emergent constructivist learning process situated in a collaborative socio-organisational context, necessary to solve an ill-structured problem [22]. Price and Cybulski describe the consensus-building process in RE [23]. Fischer underlines the need for communities, rather than individuals, and for interdisciplinary teams in software design [24].…”
Section: Phase 1: Rq1 -Collaborative Creativity In Re Literaturementioning
confidence: 99%
“…The sorting is called prioritization. Interpersonal skills are important to ensure an effective RE process [14,15,16]. The skills therefore can be used as the final measures to qualify the selected stakeholders as the best possible participants.…”
Section: Related Workmentioning
confidence: 99%
“…The sorting is called prioritization. Interpersonal skills are important to ensure an effective requirement engineering process [14,15,16].…”
Section: Stakeholder Analysismentioning
confidence: 99%