2011 IEEE International Conference on Computer Science and Automation Engineering 2011
DOI: 10.1109/csae.2011.5952853
|View full text |Cite
|
Sign up to set email alerts
|

Requirements prioritization with respect to Geographically Distributed Stakeholders

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
8
0

Year Published

2013
2013
2022
2022

Publication Types

Select...
4
4
1

Relationship

0
9

Authors

Journals

citations
Cited by 24 publications
(8 citation statements)
references
References 7 publications
0
8
0
Order By: Relevance
“…Although, requirement prioritization techniques constitute a number of benefits, however; existing techniques have many limitations, including: interdependencies between requirements are not taken into account [47], [50], [53]- [58], error-prone [47]- [53], simple/informal ranking or grouping with no priority value of requirements [48], [52], [69]- [72], [61]- [68], for small number of stakeholders and could confuse stakeholders [57], [61], [64], [66]- [68], [70], [73], [74], complex [47], [54], [70], [76], [82]- [87], unscalable [55], [58], [61], [70], [76], [82], [87]- [94], timeconsuming [50], [51], [94], [54], [70], [78], [84], [88], [89], [92], [93], Unsuitable for large number of requirements [50],…”
Section: B: Requirement Prioritizationmentioning
confidence: 99%
“…Although, requirement prioritization techniques constitute a number of benefits, however; existing techniques have many limitations, including: interdependencies between requirements are not taken into account [47], [50], [53]- [58], error-prone [47]- [53], simple/informal ranking or grouping with no priority value of requirements [48], [52], [69]- [72], [61]- [68], for small number of stakeholders and could confuse stakeholders [57], [61], [64], [66]- [68], [70], [73], [74], complex [47], [54], [70], [76], [82]- [87], unscalable [55], [58], [61], [70], [76], [82], [87]- [94], timeconsuming [50], [51], [94], [54], [70], [78], [84], [88], [89], [92], [93], Unsuitable for large number of requirements [50],…”
Section: B: Requirement Prioritizationmentioning
confidence: 99%
“…The quality of software is directly proportional to the quality of requirement implementation. The more efforts in RE stage means more success of software development [6][7][8]. In most cases failure of software is due to RE failure [9].…”
Section: Introductionmentioning
confidence: 98%
“…RE is a systematic way of collecting requirements from user in a proper way by applying various elicitation techniques [1,2]. RE consist of four phases [17].…”
Section: Introductionmentioning
confidence: 99%