A software requirements change source taxonomy

4th International Conference on Software Engineering Advances, ICSEA 2009, Includes SEDES 2009: Simposio para Estudantes de Doutoramento em Engenharia de Software

Volumn , Issue , 2009, Pages 51-58

  McGee, Sharon ^a   Greer, Des ^a  

^a QUEEN'S UNIVERSITY BELFAST   (United Kingdom)

Author keywords

Card sorting; Project management; Requirements change; Requirements management; Requirements uncertainty

Indexed keywords

CARD SORTING; EXPERT KNOWLEDGE; MULTIPLE PROJECTS; REQUIREMENTS CHANGE; REQUIREMENTS MANAGEMENT; SOFTWARE DEVELOPMENT; SOFTWARE REQUIREMENTS; SUPPORT REQUIREMENTS;

PROJECT MANAGEMENT; REQUIREMENTS ENGINEERING; SORTING; TAXONOMIES;

COMPUTER SOFTWARE;

EID: 70749140920     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSEA.2009.17     Document Type: Conference Paper

References (33)

1. N. Nurmuliani, D. Zowghi and S. P. Williams, "Requirements Volatility and Its Impact on Change Effort: Evidence-based Research in Software Development Projects", Australian Workshop on Requirements Engineering, Adelaide, 2006.
2. B. Williams, J. Carver and R. Vaughn, "Change Risk Assessment: Understanding Risks Involved in Changing Software Requirements", Proc. International Conference on Software Engineering Research and Practice, Las Vegas, Nevada, 2006.
3. D. Zowghi and N. Nurmuliani, "A study of the impact of requirements volatility on software project performance", Proc. Ninth Asia-Pacific Software Engineering Conference, 2002.
4. S. Ferreira, F. Collofello, D. Shunk, G. Mackulac and P. Wolfe, "Utilization of Process Modeling and Simulation in Understanding the Effects of Requirements Volatility in Software Development", International Workshop on Software Process Simulation and Modeling, Portland, Oregon, 2003.
5. T. Javed, M. Maqsood and Q. Durrani, "A study to investigate the impact of requirements instability on software defects", ACM Software Engineering Notes, 29, 3, 2004.
6. B. Boehm, "Industrial Software Metrics Top 10 List", IEEE Software, 4(5), 1987.
7. S. L. Pfleeger, "Software Metrics: Progress after 25 Years?", IEEE Software, 25(6), 2008.
8. K. Wiegers, Software Requirements, Microsoft Press, 2003.
9. N. Nurmuliani, D. Zowghi and S. P. Williams, "Using card sorting technique to classify requirements change", Proc. 12th IEEE International Conference on Requirements Engineering, Kyoto, Japan, 2004.
10. W. Lam, M. Loomes and V. Shankararaman, "Managing requirements change using metrics and action planning", Proc. 3rd European conference on Software Maintenance and Reengineering, Amsterdam, Netherlands, 1999.
11. W. Lam and V. Shankararaman, "Requirements change: a dissection of management issues", Proc 25th EUROMICRO Conference, Milan, Italy, 1999.
12. W. Lam and V. Shankararaman, "Managing change in software development using a process improvement approach", Proc. 24th Euromicro Conference, vol 2, Vasteras Sweden, 1998.
13. G. Stark, A. Skillicorn and R. Ameele, "An Examination of the Effects of Requirements Changes on Software Releases", CROSSTALK, The Journal of Defense Software Engineering, 1998.
14. S. D. P. Harker, K. D. Eason and J. E. Dobson, "The change and evolution of requirements as a challenge to the practice of software engineering", Proc. IEEE International Symposium on Requirements Engineering, San Diego, CA, USA, 1993.
15. I. Sommerville, Software Engineering, Personal Education Ltd, 2007.
16. N. Nurmuliani, D. Zowghi and S. Powell, "Analysis of requirements volatility during software development lifecycle", Proc. Australian Software Engineering Conference, Melbourne, 2004.
17. L. Mathiassen, T. Saarinen, T. Tuunanen and M. Rossi, "Managing Requirements Engineering Risks: Analysis and Synthesis of the Literature", Helsinki School of Economics Working Papers W-379, 2004.
18. D. Perry, A. Porter and L. Votta, "Empirical Studies of Software Engineering: A Roadmap", Proc. 22nd International Conference on Software Engineering, Limerick, Ireland, 2000.
19. D. I. K. Sjoberg, T. Dyba and M. Jorgensen, "The future of Empirical Methods in Software Engineering Research", Proc. Future of Software Engineering, Minneapolis, MN, 2007.
20. B. Nuseibeh and S. Easterbrook, "Requirements Engineering: A Roadmap", Proc 22nd International Conference on Software Engineering, Limerick, Ireland, 2000.
21. N. A. M. Maiden and G. Rugg. "ACRE: selecting methods for requirements acquisition", Software Engineering Journal, 11(3), 1996.
22. S. Fincher and J. Tenenberg, "Making sense of card sorting data", Expert Systems, 22(3), 2005.
23. Anonymous, Expert Systems Special Edition on Card Sorting, 22, 3, 2005.
24. M. Christel and K. Kang, "Issues in Requirements Elicitation", Technical Report No. CMU/SEI-92-TR-012 Software Engineering Institute, 1992.
25. B. Curtis, H. Krasner and N. Iscoe, "A field study of the software design process for large systems", Communications of the ACM, 31(11), 1988.
26. H. Barki, S. Rivard and J. Talbot, "Toward an assessment of software development risk", Journal of Managment Information Systems, 10(2), 1993.
27. B. Boehm, "Requirements that handle IKIWISI, COTS, and rapid change", Computer, 33(7), 2000.
28. A. Lamsweerde, Requirements Engineering : From System goals to UML models to software specifications, John Wiley & Sons Ltd, 2009.
29. R. Pressman, Software Engineering. A Practitioner's Approach, McGraw Hill, 2005.
30. T. Moynihan, "'Requirements-uncertainty': should it be a latent, aggregate or profile construct?" Proc. Australian Software Engineering Conference, Canberra, ACT, Australia, 2000.
31. T. Moynihan. "How experienced project managers assess risk", IEEE Software, 14(3), 1997.
32. A. M. Davis and K. V. Nori, "Requirements, Plato's Cave, and Perceptions of Reality", Proc. International Conference on Computer Software and Applications, Beijing, China, 2007.
33. C. Ebert and J. De Man, "Requirements uncertainty: influencing factors and concrete improvements", Proc. 27th International Conference on Software Engineering, ST Louis, Missouri, USA, 2005.