Non functional requirements (NFRs) traceability metamodel for agile development

Agile methodologies are well known for early and frequent releases. Besides, these methodologies also handle requirement changes well without causing delays. However, it has been noticed that the functional requirements changes can affect the non-functional requirements (NFRs) such as security and p...

Full description

Saved in:
Bibliographic Details
Main Authors: Firdaus, Adila, Ghani, Imran, Abg. Jawawi, Dayang Norhayati, Wan Kadir, Wan Mohd. Nasir
Format: Article
Language:English
Published: Penerbit UTM Press 2015
Subjects:
Online Access:http://eprints.utm.my/id/eprint/56156/1/ImranGhani2015_NonFunctionalRequirements%28NFRs%29Traceability.pdf
http://eprints.utm.my/id/eprint/56156/
http://dx.doi.org/10.11113/jt.v77.6191
Tags: Add Tag
No Tags, Be the first to tag this record!
Institution: Universiti Teknologi Malaysia
Language: English
id my.utm.56156
record_format eprints
spelling my.utm.561562017-11-01T04:16:43Z http://eprints.utm.my/id/eprint/56156/ Non functional requirements (NFRs) traceability metamodel for agile development Firdaus, Adila Ghani, Imran Abg. Jawawi, Dayang Norhayati Wan Kadir, Wan Mohd. Nasir QA75 Electronic computers. Computer science Agile methodologies are well known for early and frequent releases. Besides, these methodologies also handle requirement changes well without causing delays. However, it has been noticed that the functional requirements changes can affect the non-functional requirements (NFRs) such as security and performance. It is also possible that the agile team is not even aware of these effects causing dysfunctional system. This issue could be addressed by offering traceability mechanism that helps to trace the effect of functional requirement changes on the non-functional requirements. Unfortunately, a few researchers have conducted studies regarding this issue. Thus, this study attempts to present a Traceability Process Model (TPM) to tackle the issue of tracing NFR especially security and performance. However, to materialize a full scale TPM, a metamodel is necessary. Therefore in this paper, we present a metamodel by integrating two existing metamodels. Then we validate the newly built metamodel with precision and recall methods. Lastly, we also develop a traceability tool that is based on the proposed metamodel. Penerbit UTM Press 2015-10 Article PeerReviewed application/pdf en http://eprints.utm.my/id/eprint/56156/1/ImranGhani2015_NonFunctionalRequirements%28NFRs%29Traceability.pdf Firdaus, Adila and Ghani, Imran and Abg. Jawawi, Dayang Norhayati and Wan Kadir, Wan Mohd. Nasir (2015) Non functional requirements (NFRs) traceability metamodel for agile development. Jurnal Teknologi, 77 (9). pp. 115-125. ISSN 2180-3722 http://dx.doi.org/10.11113/jt.v77.6191 DOI:10.11113/jt.v77.6191
institution Universiti Teknologi Malaysia
building UTM Library
collection Institutional Repository
continent Asia
country Malaysia
content_provider Universiti Teknologi Malaysia
content_source UTM Institutional Repository
url_provider http://eprints.utm.my/
language English
topic QA75 Electronic computers. Computer science
spellingShingle QA75 Electronic computers. Computer science
Firdaus, Adila
Ghani, Imran
Abg. Jawawi, Dayang Norhayati
Wan Kadir, Wan Mohd. Nasir
Non functional requirements (NFRs) traceability metamodel for agile development
description Agile methodologies are well known for early and frequent releases. Besides, these methodologies also handle requirement changes well without causing delays. However, it has been noticed that the functional requirements changes can affect the non-functional requirements (NFRs) such as security and performance. It is also possible that the agile team is not even aware of these effects causing dysfunctional system. This issue could be addressed by offering traceability mechanism that helps to trace the effect of functional requirement changes on the non-functional requirements. Unfortunately, a few researchers have conducted studies regarding this issue. Thus, this study attempts to present a Traceability Process Model (TPM) to tackle the issue of tracing NFR especially security and performance. However, to materialize a full scale TPM, a metamodel is necessary. Therefore in this paper, we present a metamodel by integrating two existing metamodels. Then we validate the newly built metamodel with precision and recall methods. Lastly, we also develop a traceability tool that is based on the proposed metamodel.
format Article
author Firdaus, Adila
Ghani, Imran
Abg. Jawawi, Dayang Norhayati
Wan Kadir, Wan Mohd. Nasir
author_facet Firdaus, Adila
Ghani, Imran
Abg. Jawawi, Dayang Norhayati
Wan Kadir, Wan Mohd. Nasir
author_sort Firdaus, Adila
title Non functional requirements (NFRs) traceability metamodel for agile development
title_short Non functional requirements (NFRs) traceability metamodel for agile development
title_full Non functional requirements (NFRs) traceability metamodel for agile development
title_fullStr Non functional requirements (NFRs) traceability metamodel for agile development
title_full_unstemmed Non functional requirements (NFRs) traceability metamodel for agile development
title_sort non functional requirements (nfrs) traceability metamodel for agile development
publisher Penerbit UTM Press
publishDate 2015
url http://eprints.utm.my/id/eprint/56156/1/ImranGhani2015_NonFunctionalRequirements%28NFRs%29Traceability.pdf
http://eprints.utm.my/id/eprint/56156/
http://dx.doi.org/10.11113/jt.v77.6191
_version_ 1643654011766702080