Agile requirements engineering practices and challenges: an empirical study

Information Systems Journal - Tập 20 Số 5 - Trang 449-480 - 2010
Balasubramaniam Ramesh1, Lan Cao2, Richard Baskerville3
1Computer Information Systems Department, Georgia State University, 35 Broad St. NW, Atlanta, GA 30302‐4015, USA, email: [email protected],
2Department of Information Technology and Decision Sciences, College of Business and Public Administration, Old Dominion University, Norfolk, VA 23529, USA, email: [email protected]
3email: [email protected], and

Tóm tắt

AbstractThis paper describes empirical research into agile requirements engineering (RE) practices. Based on an analysis of data collected in 16 US software development organizations, we identify six agile practices. We also identify seven challenges that are created by the use of these practices. We further analyse how this collection of practices helps mitigate some, while exacerbating other risks in RE. We provide a framework for evaluating the impact and appropriateness of agile RE practices by relating them to RE risks. Two risks that are intractable by agile RE practices emerge from the analysis. First, problems with customer inability and a lack of concurrence among customers significantly impact agile development. Second, risks associated with the neglecting non‐functional requirements such as security and scalability are a serious concern. Developers should carefully evaluate the risk factors in their project environment to understand whether the benefits of agile RE practices outweigh the costs imposed by the challenges.

Từ khóa


Tài liệu tham khảo

Abdel‐Hamid T., 1991, Software Project Dynamics: An Integrated Approach.

Agile Alliance.(2001) URLhttp://www.agilealliance.com/(last accessed 9 May 2006).

Araujo J.&Ribeiro J.C.(2005) Towards an aspect‐oriented agile requirements approach. Eighth International Workshop on Principles of Software Evolution.

Astels D., 2003, Test Driven Development: A Practical Guide.

10.1080/07421222.1993.11518006

Beck K., 2003, Test Driven Development: By Example.

10.1109/2.796139

10.1109/2.869384

Boehm B., 2003, Balancing Agility and Discipline: A Guide for the Perplexed.

Cao L. Mohan K. Xu P.&Ramesh B.(2004) How extreme does extreme programming have to be? Adapting XP practices to large‐scale projects. Proceedings of the 37th Annual Hawaii International Conference on System Sciences (HICSS'04) Hawaii HI USA.

Cockburn A.(2002)Agile software development.Addison‐Wesley Longman Boston MA USA.

10.1145/50087.50089

Cusumano M., 2000, Competing on Internet Time: Lessons from Netscape and Its Battle with Microsoft.

10.1147/sj.211.0004

10.1109/MS.2003.1231163

10.2307/258557

10.4018/jdm.2005100105

10.5381/jot.2004.3.8.c4

Fowler M., 1999, Refactoring: Improving the Design of Existing Programs.

Grünbacher P.&Hofer C.(2002) Complementing XP with requirements negotiation XP. Third International Conference on eXtreme Programming and Agile Software Process in Software Engineering Alghero Sarding Italy 26–29 May.

IEEE, 1998, IEEE recommended practice for software requirements specifications, IEEE Standard 830

Jepsen O.(2002) Time constrained requirement engineering – the cooperative way International Workshop on Time‐Constrained Requirements Engineering Essen Germany 9 September.

10.1145/203356.203363

10.1145/287831.287843

Kotonya G., 1998, Requirements Engineering: Process and Techniques.

10.1145/203330.203345

10.1109/52.965804

Lee M.(2002) Just‐in‐time requirements analysis – the engine that drives the planning game XP. Third International Conference on eXtreme Programming and Agile Software Process in Software Engineering Alghero Sarding Italy 26–29 May.

Levine L., 2002, Software

Lindvall M. Basili V. Boehm B. Costa P. Dangle K. Shull F.et al.(2002) Empirical findings in agile methods Second XP Universe and First Agile Universe Conference Chicago IL USA 4–7 August.

Lubars M. Potts C.&Richter C.(1993) A review of the state of the practice in requirements modeling. IEEE International Symposium on Requirements Engineering.

Mason J., 1996, Qualitative Researching.

10.4018/jdm.2005100103

Miles M.B., 1994, Qualitative Data Analysis: An Expanded Sourcebook.

Nawrocki J. Jasinski M. Walter B.&Wojciechowski A.(2002) Extreme programming modified: embrace requirements engineering practices. IEEE Joint International Conference on Requirements Engineering (RE′02) Essen Germany.

10.1287/isre.2.1.1

10.1109/MS.2004.1293075

Paetsch F.E.A.&Maurer F.(2003) Requirements engineering and agile software development.12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises.

Pinheiro F.A.C.(2002) Requirements honesty.12th IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises Fachhochschule Mannheim Germany.

10.1145/293411.293485

Schneider G., 1998, Applying Use Cases: A Practical Guide.

Sharp H.&Robinson H.(2003) Customer collaboration: challenges and successes in practice: an agile development 2003 technical exchange. Agile Development Conference Salt Lake UT USA.

Sillitti A. Ceschi M. Russo B.&Succi G.(2005) Managing uncertainty in requirements: a survey in documentation‐driven and agile companies. 11th IEEE International Symposium on Software Metrics.

Sommerville I., 1997, Requirements Engineering: A Good Practice Guide.

Strauss A., 1990, Basics of Qualitative Research. Grounded Theory Procedures and Techniques.

10.4018/jdm.2005100104

10.1145/163430.163447

Thông tin
Thông tin xuất bản

Information Systems Journal

Tập 20 Số 5

449-480

Thông tin tác giả