Requirement change taxonomy and categorization in agile software development
Due to the rapid growth in software engineering technology and with advancements of agile methodology, software requirement change management is essentially concerned. Requirements are continuously changed in Agile Software Development (ASD) and need a careful change management method. Continuously...
Saved in:
| Main Authors: | , , |
|---|---|
| Format: | Conference or Workshop Item |
| Published: |
2017
|
| Subjects: | |
| Online Access: | http://repo.uum.edu.my/25539/ http://doi.org/10.1109/ICEEI.2017.8312441 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Institution: | Universiti Utara Malaysia |
| Summary: | Due to the rapid growth in software engineering technology and with advancements of agile methodology, software requirement change management is essentially concerned. Requirements are continuously changed in Agile Software Development (ASD) and need a careful change management method. Continuously change and poorly defined requirements may result in a requirement to become harmful that are both extremely risky and damaging, for the software project in ASD. In order to understand the issue, this paper reviewed several published research papers and identify the requirement change taxonomy. The main objective of this paper is to create requirement change taxonomy and further categorize the requirement change element on the basis of reason and origin of change, for a better understanding of change request. Change categorization will be referred to propose a model of requirement change management in ASD. Moreover, managing change request during requirement change management improves the chance of developing ASD project successfully by minimizing the risks associated with it. |
|---|