Software requirements: analysis and specification
Software requirements: analysis and specification
Why is Software Late? An Empirical Study of Reasons for Delay in Software Development
IEEE Transactions on Software Engineering
Prioritizing software requirements in an industrial setting
ICSE '97 Proceedings of the 19th international conference on Software engineering
The use of goals to surface requirements for evolving systems
Proceedings of the 20th international conference on Software engineering
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
The Analytic Hierarchy Process--An Exposition
Operations Research
Supporting the Selection of Software Requirements
IWSSD '96 Proceedings of the 8th International Workshop on Software Specification and Design
Just Enough Requirements Management: Where Software Development Meets Marketing
Just Enough Requirements Management: Where Software Development Meets Marketing
Using an Agile Approach in a Large, Traditional Organization
AGILE '06 Proceedings of the conference on AGILE 2006
Evaluating the practical use of different measurement scales in requirements prioritisation
Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering
Supporting use case based requirements engineering
Information and Software Technology
Equality in cumulative voting: A systematic review with an improvement proposal
Information and Software Technology
| Hi-index | 0.00 |
Prioritisation is important in keeping a software project on track and ensuring that the stakeholder's needs are being fulfilled. In this paper four methods for goal prioritisation are examined. Using a case study as its basis, each method is evaluated on its ease of use for a stakeholder, the time it takes to complete and the amount of confidence they have that the method accurately reflects their priorities. The type of information yielded by each method is also described. The results show the techniques give a consistent priority. Grouping and ranking techniques are easier for stakeholders to perform and generally take less time than techniques showing magnitude of preference. There is also a strong correlation between the stakeholder's confidence in the technique and how easy they feel it was to perform.