scholarly journals Key Challenges in Agile Requirements Engineering

2017 ◽  
pp. 37-51 ◽  
Author(s):  
Eva-Maria Schön ◽  
Dominique Winter ◽  
María José Escalona ◽  
Jörg Thomaschewski
Keyword(s):  
Requirements Engineering ◽  
Agile Requirements

Communication patterns of agile requirements engineering

2011 ◽  
Author(s):  
Nik Nailah Binti Abdullah ◽  
Shinichi Honiden ◽  
Helen Sharp ◽  
Bashar Nuseibeh ◽  
David Notkin
Keyword(s):  
Requirements Engineering ◽  
Communication Patterns ◽  
Agile Requirements

A reflection on agile requirements engineering

2015 ◽  
Author(s):  
Irum Inayat ◽  
Lauriane Moraes ◽  
Maya Daneva ◽  
Siti Salwah Salim
Keyword(s):  
Requirements Engineering ◽  
Agile Requirements

scholarly journals A Metamodel for Agile Requirements Engineering

2019 ◽  
Vol 07 (02) ◽  
pp. 1-22 ◽  
Author(s):  
Eva-Maria Schön ◽  
Jorge Sedeño ◽  
Manuel Mejías ◽  
Jörg Thomaschewski ◽  
María José Escalona
Keyword(s):  
Requirements Engineering ◽  
Agile Requirements

scholarly journals Agile Requirements Engineering: An Empirical Analysis and Evidence from a Tertiary Education Context

10.28945/4286 ◽  
2019 ◽  
Vol 16 ◽  
pp. 097-112
Author(s):  
Meetu Thomas ◽  
Mali Senapathi
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Empirical Analysis ◽  
New Technologies ◽  
Resistance To Change ◽  
Tertiary Education ◽  
Future Research ◽  
Case Study Methodology ◽  
Face To Face ◽  
Agile Requirements

Aim/Purpose: The study describes empirical research into agile Requirements Engineering (RE) practices based on an analysis of data collected in a large higher education organization. Background: Requirements Engineering (RE) in agile development contexts is considerably different than in traditional software development. The field of agile RE is still nascent where there is a need to evaluate its impact in real-world settings. Methodology: Using a case study methodology, the study involved interviewing nine experienced software practitioners who reflected on the use and implementation of various agile RE practices in two software development projects of a student management system. Contribution: The primary contribution of the paper is the evaluation of agile RE practices in a large tertiary educational organization. Based on the analysis of the data, it provides valuable insights into the practice of agile RE in a specific context (i.e., education), but just as importantly, the ones that were omitted or replaced with others and why. Findings: While the evolutionary and iterative approach to defining requirements was followed in general, not all agile practices could be fully adhered to in the case organization. Although face-to-face communication with the customers has been recognized as one the most important agile RE practices, it was one of the most difficult practices to achieve with a large and diverse customer base. Addressing people issues (e.g., resistance to change, thinking, and mindset) was found to be a key driver to following the iterative RE process effectively. Contrary to the value-based approach advocated in the literature, the value-based approach was not strictly adhered to in requirements prioritization. Continuous integration was perceived to be a more beneficial practice than prototyping, as it allows frequent integration of code and facilitates delivering working software when necessary. Recommendations for Practitioners: Our study has important implications for practitioners. Based on our empirical analysis, we provide specific recommendations for effective implementation of agile RE practices. For example, our findings suggest that practitioners could address the challenges associated with limited face-to-face communication challenges by producing flexible, accessible, and electronic documentation to enable communication. Recommendations for Researchers: Researchers can use the identified agile RE practices and their variants to per-form in-depth investigations into agile requirements engineering in other educational contexts. Impact on Society: There are a number of new technologies that offer exciting new opportunities that can be explored to maximize the benefits of agile and other requirements techniques. Future Research: Future research could conduct case studies in different contexts and thus con-tribute to developing bundles or collections of practices to improve software development processes in specific contexts.

Best Practices Guidelines for Agile Requirements Engineering Practices

2010 ◽  
pp. 1-14
Author(s):  
Chetankumar Patel ◽  
Muthu Ramachandran
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Careful Analysis ◽  
Requirement Engineering ◽  
Functional Requirements ◽  
Knowledge Based ◽  
Development Methodology ◽  
Requirement Change ◽  
Engineering Practices ◽  
Agile Requirements

Developing software that meets the customers or stakeholders’ needs and expectation is the ultimate goal of the software development methodology. To meet their need we have to perform requirement engineering which helps to identify and structure requirements. In traditional software development methods end users or stakeholders predefined their requirements and sent to the development team to analysis and negotiation to produce requirement specification. In many cases it is risky or very difficult and not economical to produce a complete, verifiable set of requirements. Traditional software development has a problem to deal with requirement change after careful analysis and negotiation. This problem is well tackled by the Agile Practices as it’s recommends an on-site customer to represents their requirements through user stories on story cards. Generally customers have rarely a general picture of the requirements or system in their mind which leads problems related to requirements like requirements conflicts, missing requirements, and ambiguous requirements etc, and does not address non-functional requirements from exploration phase. This chapter introduces best knowledge based guidelines for agile requirements engineering to enhance the quality of requirements (story cards).

Best Practices Guidelines for Agile Requirements Engineering Practices

2012 ◽  
pp. 1403-1416
Author(s):  
Chetankumar Patel ◽  
Muthu Ramachandran
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Careful Analysis ◽  
Requirement Engineering ◽  
Functional Requirements ◽  
Knowledge Based ◽  
Development Methodology ◽  
Requirement Change ◽  
Engineering Practices ◽  
Agile Requirements

Developing software that meets the customers or stakeholders’ needs and expectation is the ultimate goal of the software development methodology. To meet their need we have to perform requirement engineering which helps to identify and structure requirements. In traditional software development methods end users or stakeholders predefined their requirements and sent to the development team to analysis and negotiation to produce requirement specification. In many cases it is risky or very difficult and not economical to produce a complete, verifiable set of requirements. Traditional software development has a problem to deal with requirement change after careful analysis and negotiation. This problem is well tackled by the Agile Practices as it’s recommends an on-site customer to represents their requirements through user stories on story cards. Generally customers have rarely a general picture of the requirements or system in their mind which leads problems related to requirements like requirements conflicts, missing requirements, and ambiguous requirements etc, and does not address non-functional requirements from exploration phase. This chapter introduces best knowledge based guidelines for agile requirements engineering to enhance the quality of requirements (story cards).

Sign in / Sign up

Export Citation Format

Share Document