Cite Article

Case Study on Non-Functional Requirement Change Impact Traceability for Agile Software Development

Choose citation format

BibTeX

@article{IJASEIT10176,
   author = {Adila Firdaus Arbain and Dayang Norhayati Abang Jawawi and Wan Mohd Nasir bin Wan Kadir and Imran Ghani},
   title = {Case Study on Non-Functional Requirement Change Impact Traceability for Agile Software Development},
   journal = {International Journal on Advanced Science, Engineering and Information Technology},
   volume = {10},
   number = {1},
   year = {2020},
   pages = {34--40},
   keywords = {agile methodologies; scrum; feature driven development; traceability; non-functional requirement.},
   abstract = {Currently, it is crucial to develop a complex software on time. Agile software development methodologies provide methods to develop a system in term of time and cost-saving but it has been criticized for software quality management. In this paper, a case study is used to find out the need of NFR change impact traceability approach in most of Agile software methodology. This case study was conducted in an undergraduate course that trained the students on how to develop software using Agile process model.This case study has been conducted for 4 months in an undergraduate-level course, Application Development. The samples of this case study are among Year 3 undergraduate students. The case study shows the lack of traceability techniques in the existing Agile process model (SFDD- Secured Feature Driven Development) that result to non-awareness of NFR change impact during development. Based on the case study mentioned the main objective of the case study conducted in survey is to empirically test the theoretical constructs and the hypothesized relationships of the research issues that concern on the lack of change impact management towards NFR in Agile Software Methodology.  TANC (Traceability for Agile Non-Functional Requirement Change Impact) model offered techniques in tracing change impact during the agile development process. Therefore, the result of the case study, a traceability process model needs to design in order to tackle the NFR change impact issues in Agile software development.},
   issn = {2088-5334},
   publisher = {INSIGHT - Indonesian Society for Knowledge and Human Development},
   url = {http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10176},
   doi = {10.18517/ijaseit.10.1.10176}
}

EndNote

%A Arbain, Adila Firdaus
%A Abang Jawawi, Dayang Norhayati
%A Wan Kadir, Wan Mohd Nasir bin
%A Ghani, Imran
%D 2020
%T Case Study on Non-Functional Requirement Change Impact Traceability for Agile Software Development
%B 2020
%9 agile methodologies; scrum; feature driven development; traceability; non-functional requirement.
%! Case Study on Non-Functional Requirement Change Impact Traceability for Agile Software Development
%K agile methodologies; scrum; feature driven development; traceability; non-functional requirement.
%X Currently, it is crucial to develop a complex software on time. Agile software development methodologies provide methods to develop a system in term of time and cost-saving but it has been criticized for software quality management. In this paper, a case study is used to find out the need of NFR change impact traceability approach in most of Agile software methodology. This case study was conducted in an undergraduate course that trained the students on how to develop software using Agile process model.This case study has been conducted for 4 months in an undergraduate-level course, Application Development. The samples of this case study are among Year 3 undergraduate students. The case study shows the lack of traceability techniques in the existing Agile process model (SFDD- Secured Feature Driven Development) that result to non-awareness of NFR change impact during development. Based on the case study mentioned the main objective of the case study conducted in survey is to empirically test the theoretical constructs and the hypothesized relationships of the research issues that concern on the lack of change impact management towards NFR in Agile Software Methodology.  TANC (Traceability for Agile Non-Functional Requirement Change Impact) model offered techniques in tracing change impact during the agile development process. Therefore, the result of the case study, a traceability process model needs to design in order to tackle the NFR change impact issues in Agile software development.
%U http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10176
%R doi:10.18517/ijaseit.10.1.10176
%J International Journal on Advanced Science, Engineering and Information Technology
%V 10
%N 1
%@ 2088-5334

IEEE

Adila Firdaus Arbain,Dayang Norhayati Abang Jawawi,Wan Mohd Nasir bin Wan Kadir and Imran Ghani,"Case Study on Non-Functional Requirement Change Impact Traceability for Agile Software Development," International Journal on Advanced Science, Engineering and Information Technology, vol. 10, no. 1, pp. 34-40, 2020. [Online]. Available: http://dx.doi.org/10.18517/ijaseit.10.1.10176.

RefMan/ProCite (RIS)

TY  - JOUR
AU  - Arbain, Adila Firdaus
AU  - Abang Jawawi, Dayang Norhayati
AU  - Wan Kadir, Wan Mohd Nasir bin
AU  - Ghani, Imran
PY  - 2020
TI  - Case Study on Non-Functional Requirement Change Impact Traceability for Agile Software Development
JF  - International Journal on Advanced Science, Engineering and Information Technology; Vol. 10 (2020) No. 1
Y2  - 2020
SP  - 34
EP  - 40
SN  - 2088-5334
PB  - INSIGHT - Indonesian Society for Knowledge and Human Development
KW  - agile methodologies; scrum; feature driven development; traceability; non-functional requirement.
N2  - Currently, it is crucial to develop a complex software on time. Agile software development methodologies provide methods to develop a system in term of time and cost-saving but it has been criticized for software quality management. In this paper, a case study is used to find out the need of NFR change impact traceability approach in most of Agile software methodology. This case study was conducted in an undergraduate course that trained the students on how to develop software using Agile process model.This case study has been conducted for 4 months in an undergraduate-level course, Application Development. The samples of this case study are among Year 3 undergraduate students. The case study shows the lack of traceability techniques in the existing Agile process model (SFDD- Secured Feature Driven Development) that result to non-awareness of NFR change impact during development. Based on the case study mentioned the main objective of the case study conducted in survey is to empirically test the theoretical constructs and the hypothesized relationships of the research issues that concern on the lack of change impact management towards NFR in Agile Software Methodology.  TANC (Traceability for Agile Non-Functional Requirement Change Impact) model offered techniques in tracing change impact during the agile development process. Therefore, the result of the case study, a traceability process model needs to design in order to tackle the NFR change impact issues in Agile software development.
UR  - http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10176
DO  - 10.18517/ijaseit.10.1.10176

RefWorks

RT Journal Article
ID 10176
A1 Arbain, Adila Firdaus
A1 Abang Jawawi, Dayang Norhayati
A1 Wan Kadir, Wan Mohd Nasir bin
A1 Ghani, Imran
T1 Case Study on Non-Functional Requirement Change Impact Traceability for Agile Software Development
JF International Journal on Advanced Science, Engineering and Information Technology
VO 10
IS 1
YR 2020
SP 34
OP 40
SN 2088-5334
PB INSIGHT - Indonesian Society for Knowledge and Human Development
K1 agile methodologies; scrum; feature driven development; traceability; non-functional requirement.
AB Currently, it is crucial to develop a complex software on time. Agile software development methodologies provide methods to develop a system in term of time and cost-saving but it has been criticized for software quality management. In this paper, a case study is used to find out the need of NFR change impact traceability approach in most of Agile software methodology. This case study was conducted in an undergraduate course that trained the students on how to develop software using Agile process model.This case study has been conducted for 4 months in an undergraduate-level course, Application Development. The samples of this case study are among Year 3 undergraduate students. The case study shows the lack of traceability techniques in the existing Agile process model (SFDD- Secured Feature Driven Development) that result to non-awareness of NFR change impact during development. Based on the case study mentioned the main objective of the case study conducted in survey is to empirically test the theoretical constructs and the hypothesized relationships of the research issues that concern on the lack of change impact management towards NFR in Agile Software Methodology.  TANC (Traceability for Agile Non-Functional Requirement Change Impact) model offered techniques in tracing change impact during the agile development process. Therefore, the result of the case study, a traceability process model needs to design in order to tackle the NFR change impact issues in Agile software development.
LK http://ijaseit.insightsociety.org/index.php?option=com_content&view=article&id=9&Itemid=1&article_id=10176
DO  - 10.18517/ijaseit.10.1.10176