Evolution of Requirements Engineering in Agile Methodology – Literature Review
Bibliographic record
Abstract
Requirements Agile approaches have transformed engineering. This paper shows how RE in Agile software development has evolved from documentation-heavy to collaborative, adaptable, and customer-focused. Agile was born in the mid-1990s when the industry realized it needed to respond to changing client needs and market volatility. This evolution includes iterative development, client interaction, and emphasizing communication above documentation, as discussed in the paper. By comparing conventional and Agile RE approaches, we demonstrate the benefits of adapting to change, working with customers, and delivering functional software faster. This analysis provides a persuasive description of Agile RE implementation methodologies and resources through a detailed literature review and real-world experiences. User stories and backlog refinement are notable techniques. The research finishes by exploring how these techniques affect team dynamics, project success, and customer satisfaction. RE's Agile difficulties and opportunities are also examined. The findings illuminate RE methods' successful adaptation to Agile projects' dynamic character. Software development is more responsive and effective due to this adaptation.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".