Agile Requirements Definition: A View from Requirements Engineering
Armin Eberlein
Abstract
Armin Eberlein
Abstract
Agile methods are an attractive alternative for those pressured to produce code fast. Many programmers like the hands-on strategy of these approaches which also help them avoid some of the less exciting tasks, such as specification. On the other hand, some people appear to welcome agile methods as an excuse to throw overboard everything that requirements engineering has been teaching. This position paper looks at numerous aspects of requirements engineering and argues about their suitability for agile approaches. The aim is to elicit lessons from requirements engineering that agile methods might consider, if quality is a major concern.
OpenAlex reports 75 citations for this work. Citation counts describe recorded attention and do not establish research quality.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
Agile methods are an attractive alternative for those pressured to produce code fast. Many programmers like the hands-on strategy of these approaches which also help them avoid some of the less exciting tasks, such as specification. On the other hand, some people appear to welcome agile methods as an excuse to throw overboard everything that requirements engineering has been teaching. This position paper looks at numerous aspects of requirements engineering and argues about their suitability for agile approaches. The aim is to elicit lessons from requirements engineering that agile methods might consider, if quality is a major concern.
Key concepts: Requirement, Agile software development, Requirements engineering, Agile usability engineering, Requirements analysis, Engineering, Agile Unified Process, Requirements elicitation