Choosing the "right" prioritisation method

Proceedings of the Australian Software Engineering Conference, ASWEC

Volumn , Issue , 2008, Pages 517-526

  Hatton, Sarah ^a  

^a UNIVERSITY OF WESTERN AUSTRALIA   (Australia)

Author keywords

[No Author keywords available]

Indexed keywords

AMOUNT OF INFORMATION; AUSTRALIAN SOFTWARE ENGINEERING CONFERENCE; PROJECT DEVELOPMENT; SOFTWARE REQUIREMENTS;

SOFTWARE ENGINEERING; TECHNOLOGY;

STAGES;

EID: 50249090422     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ASWEC.2008.4483241     Document Type: Conference Paper

References (30)

1. The Standish Group, "The High Cost of Chaos," from Computerworld, "Few IS Projects Come in on Time. on Budget," Dec. 12 1994, p. 20.
2. A., Ngo-The, and G., Ruhe, "Decision Support in Requirements Engineering", in Engineering and Managing Software Requirements, ed. Aurum, A., and Wohlin, C., Springer Verlag, Berlin, Germany, 2005, pp. 267-286.
3. I., Sommerville and P. Sawyer, Requirements Engineering: A Good Practice Guide. John Wiley & Sons. 1997.
4. M. van Genuchten, "Why is Software Late? An Empirical Study of Reasons for Delay in Software Development". IEEE Transactions of Software Engineering, 1991. 17(6): pp. 582-590.
5. A. Davis, Software Requirements: Analysis and Specification. Second Edition ed., Englewood Cliffs, NJ, USA: Prentice-Hall. 1993
6. K. Wiegers, Software Requirements, 2nd Edition, Microsoft Press, Redmond, WA., 2003.
7. S. Hatton, "Early Prioritisation of Goals " In Hainaut, J.-L.; Rundensteiner, E.A.; Kirchberg, M.; Bertolotto, M.; Brochhausen, M.; Chen, P.; Sisaid Cherji, S.; Doerr, M.; Han, H.; Hartmann, S.; Parsons, J.; Poels, G.; Rolland, C.; Trujillo, J.; Yu, E.; Zimlanyi, E. (Eds.) Advances in Conceptual Modeling - Foundations and Applications. Lecture Notes in Computer Science Vol 4802 Springer-Verlag, Berlin Heidelberg New York, 2007, pp 235-244.
8. C.J. Neill and P.A. Laplante, "Requirements Engineering: The State of the Practice," IEEE Software, Vol. 20, No. 6, November-December 2003. pp. 40-45.
9. P.A. Laplante and C.J. Neill, "The Demise of the Waterfall Model is Imminent" and other Urban Myths of Software Engineering" ACM Queue, Vol.1, No. 10, February 2004. pp. 10-15.
10. K. Beck, Extreme Programming Explained: Embrace Change, Addison-Wesley Professional, USA, 1999.
11. The DSDM Consortium: "DSDM public version 4.2" online; available www.dsdm.org last accessed 22/01/07.
12. S. R. Palmer, and J. M. Felsing, A Practical Guide to Feature-Driven Development, Prentice Hall PTR, 2002.
13. L. Rising, and N. S. Janoff, "The Scrum Software Development Process for Small Teams", IEEE Software, July/ August 2000.
14. D. Astels, Test Driven Development: A Practical Guide Prentice Hall PTR, 2003.
15. J. Highsmith, Agile Software Development Ecosystems. Addison Wesley Professional 2002.
16. A. AhI, An Experimental Comparison of Five Prioritisation Techniques - Investigating Ease of Use, Accuracy, and Scalability, Master Thesis No. MSE-2005-11, School of Engineering, Blekinge Institute of Technology 2005.
17. J. Karlsson, C. Wohlin, and B. Regnell, "An Evaluation of Methods for Prioritising Software Requirements", Information and Software Technology 39(14-15), 998, pp. 939-947.
18. L. Karlsson, P. Berander, B. Regnell, and C. Wohlin, "Simple Is Better? - An Experiment on Requirements Prioritisation" In proc. Third Conference on Software Engineering Research and Practice in Sweden (SERPS '03), Lund, Sweden, 2003.
19. L. Karlsson, M. Host, and B. Regnell "Evaluating the practical use of different measurement scales in requirements prioritisation." In Proceedings of the 2006 ACM/IEEE international Symposium on Empirical Software Engineering. ISESE '06. ACM Press, New York, NY, 326-335, 2006.
20. G.A. Miller, "The Magical Number Seven, Plus or Minus Two: Some Limits on Our Capacity for Processing Information" The Psychological Review, vol. 63, pp. 81-97 1956.
21. D. Tudor, and G. A. Walter, "Using an Agile Approach in a Large, Traditional Organisation" Proceedings of AGILE 2006 Conference (AGILE'06). pp 367 -373. 2006.
22. E.H. Forman, and S. I. Gass, "The Analytic Hierarchy Process - and Exposition" in Operations Research Vol 49 No 4 July-August 2001 pp469-486, 2001.
23. M. A. Mustafa and J. F. Al-Bahar, "Project Risk Assessment Using the Analytic Hierarchy Process" in IEEE Transactions on Engineering Management Vol 38 Issue 1 Feb 1991 pp 46-52. 1991.
24. T. L. Saaty, The Analytic Hierarchy Process, Planning, Priority Setting, Resource Allocation, McGraw-Hill, USA 1980.
25. A. M. Davis, Just Enough Requirement Management, Where Software Development Meets Marketing Dorset House Publishing Company Incorporated New York USA, 2005.
26. Y. Bao, T. Wu, Y. He, and X. Ge, "An Improved AHP method in Performance Assessment" in Fifth World Congress on Intelligent Control and Automation pp 177-180 2004.
27. th International Conference on Software Engineering pp 564-565. 1997.
28. M. Host, B. Regnell, & C. Wohlin, Using Students as Subjects - A Comparative Study of Students and Professionals in Lead-Time Impact Assessment. Empirical Software Engineering, Vol. 5, No. 3, pp. 201-214, 2000.
29. P. Berander, 2004. "Using Students as Subjects in Requirements Prioritisation." In Proceedings of the 2004 international Symposium on Empirical Software Engineering (August 19 - 20, 2004). International Symposium on Empirical Software Engineering. IEEE Computer Society, Washington, DC, 167-176.
30. Anton, A., Potts, C.: "The Use of Goals to Surface Requirements for Evolving Systems". In Proceedings of 20th international Conference on Software Engineering (ICSE 98). 1998. Kyoto, Japan. 1998.