Requirements Engineering in Agile Software Development

Finding out, analyzing, documenting, and checking requirements are important activities in all development approaches, including agile development. This paper discusses problems concerned with the conduction of requirements engineering activities in agile software development processes and suggests some improvements to solve some challenges caused by agile requirements engineering practices in large projects, like properly handling and identifying sensitive (including non- functional) requirements, documenting and managing requirements documentation, keeping agile teams in contact with outside customers. The paper also discusses the requirements traceability problem in agile software development and the relationships between the traceability and refactoring processes and their impact on each other.

[1]  JaatunMartin Gilje,et al.  Agile Software Development , 2002, Comput. Sci. Educ..

[2]  Richard Baskerville,et al.  Agile requirements engineering practices and challenges: an empirical study , 2007, Inf. Syst. J..

[3]  Emil Vassev,et al.  Use Cases , 2010, Encyclopedia of Software Engineering.

[4]  David S. Janzen,et al.  Towards traceable test-driven development , 2009, 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering.

[5]  Serge Demeyer,et al.  Establishing Traceability Links between Unit Test Cases and Units under Test , 2009, 2009 13th European Conference on Software Maintenance and Reengineering.

[6]  Genny Tortora,et al.  Recovering traceability links in software artifact management systems using information retrieval methods , 2007, TSEM.

[7]  James D. Arthur,et al.  Determining the Applicability of Agile Practices to Mission and Life-Critical Systems , 2007, 31st IEEE Software Engineering Workshop (SEW 2007).

[8]  Lorena Delgadillo.  Story-Wall: Lightweight Requirements Management for Agile Software Development , 2007 .

[9]  Pekka Abrahamsson,et al.  Integrating agile software development and software process improvement: a longitudinal case study , 2005, 2005 International Symposium on Empirical Software Engineering, 2005..

[10]  Outi Salo.  Systematical Validation of Learning in Agile Software Development Environment , 2005, Wissensmanagement.

[11]  Alberto Sillitti,et al.  Requirements Engineering for Agile Methods , 2005 .

[12]  Mark T True,et al.  Software Requirements , 2005 .

[13]  Isaac Pentinmaki,et al.  Review of "Lean software development: an agile tookit" by Mary and Tom Poppendieck. Addison Wesley 2003. , 2004, SOEN.

[14]  A. Karimi,et al.  Master‟s thesis , 2011 .

[15]  Frank Maurer,et al.  Requirements engineering and agile software development , 2003, WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003..

[16]  Mary Poppendieck,et al.  Lean Software Development: An Agile Toolkit , 2003 .

[17]  A. Hanks.  Canada , 2002 .

[18]  Scott W. Ambler,et al.  Agile modeling: effective practices for extreme programming and the unified process , 2002 .

[19]  Jim Highsmith,et al.  Agile Software Development Ecosystems , 2002 .

[20]  Steve R. Palmer,et al.  A Practical Guide to Feature-Driven Development , 2002 .

[21]  K. Beck,et al.  Extreme Programming Explained , 2002 .

[22]  透明.  技术专题：Mastering EJB , 2002 .

[23]  Armin Eberlein.  Agile Requirements Definition: A View from Requirements Engineering , 2002 .

[24]  Rolf Goetz.  How Agile Processes Can Help in Time-Constrained Requirements Engineering , 2002 .

[25]  Ken Schwaber,et al.  Agile Software Development with SCRUM , 2001 .

[26]  Christopher McPhee.  Requirements engineering for projects with critical time-to-market , 2001 .

[27]  Martin Fowler,et al.  Planning Extreme Programming , 2000 .

[28]  J. Stapleton,et al.  DSDM: Dynamic Systems Development Method , 1999, Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275).

[29]  Kent L. Beck.  Extreme Programming , 1999, Proceedings Technology of Object-Oriented Languages and Systems. TOOLS 29 (Cat. No.PR00275).

[30]  Karl E. Wiegers,et al.  Software Requirements , 1999 .

[31]  Eric Lefebvre,et al.  Java modeling in color with UML: enterprise components and process , 1999 .

[32]  Jakob Nielsen,et al.  Interface: The Use and Misuse of Focus Groups , 1997, IEEE Softw..

[33]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[34]  Jonathan Rosenhead,et al.  Soft Systems Methodology in Action , 1991 .

[35]  A. Berztiss,et al.  Requirements Engineering , 2002, J. Object Technol..

[36]  James H. Cross,et al.  Reverse engineering and design recovery: a taxonomy , 1990, IEEE Software.

[37]  Barry W. Boehm,et al.  Verifying and Validating Software Requirements and Design Specifications , 1989, IEEE Software.

[38]  Oscar López Villegas,et al.  Requirements Reuse for Software Development , 2022 .