Cover Image

Crosscutting concern identification at requirements level

An unresolved problem faced by software developers is the failure to identify and modularize certain artefacts that compose the software. It is difficult to modularize these artefacts because they are dispersed among other artefacts in the software properties. Aspects Oriented Requirements Engineeri...

Full description

Saved in:
Bibliographic Details
Main Authors: Ali, B.S., Kasirun, Z.M.
Format: Article
Published: 2008
Subjects:
T Technology (General)
Online Access:http://eprints.um.edu.my/5093/
http://ejum.fsktm.um.edu.my/article/671.pdf
Tags: Add Tag
No Tags, Be the first to tag this record!
id my.um.eprints.5093
record_format eprints
spelling my.um.eprints.50932013-03-18T02:03:18Z http://eprints.um.edu.my/5093/ Crosscutting concern identification at requirements level Ali, B.S. Kasirun, Z.M. T Technology (General) An unresolved problem faced by software developers is the failure to identify and modularize certain artefacts that compose the software. It is difficult to modularize these artefacts because they are dispersed among other artefacts in the software properties. Aspects Oriented Requirements Engineering is showing encouraging results in improving identification, modularization and composition of crosscutting concerns. Identifying and documenting crosscutting concerns at the requirements-level is crucial. It avoids coupling between requirements, improves traceability among requirements, eases function modularization, reduces software complexity, enhances the correctness of the software design and most importantly it saves the cost. Although the research area is still in its infancy, several techniques for crosscutting concern identification have already been developed. However, all of the techniques reviewed are based on semi-automated way whereby human intervention is required to achieve the desired results. Therefore, in this paper, a fully automated technique based on Natural Language Processing (NLP) is proposed to identify crosscutting concern at the requirements level. 2008 Article PeerReviewed Ali, B.S. and Kasirun, Z.M. (2008) Crosscutting concern identification at requirements level. Malaysian Journal of Computer Science, 21 (2). pp. 78-87. ISSN 0127-9084 http://ejum.fsktm.um.edu.my/article/671.pdf
institution Universiti Malaya
building UM Library
collection Institutional Repository
continent Asia
country Malaysia
content_provider Universiti Malaya
content_source UM Research Repository
url_provider http://eprints.um.edu.my/
topic T Technology (General)
spellingShingle T Technology (General)
Ali, B.S.
Kasirun, Z.M.
Crosscutting concern identification at requirements level
description An unresolved problem faced by software developers is the failure to identify and modularize certain artefacts that compose the software. It is difficult to modularize these artefacts because they are dispersed among other artefacts in the software properties. Aspects Oriented Requirements Engineering is showing encouraging results in improving identification, modularization and composition of crosscutting concerns. Identifying and documenting crosscutting concerns at the requirements-level is crucial. It avoids coupling between requirements, improves traceability among requirements, eases function modularization, reduces software complexity, enhances the correctness of the software design and most importantly it saves the cost. Although the research area is still in its infancy, several techniques for crosscutting concern identification have already been developed. However, all of the techniques reviewed are based on semi-automated way whereby human intervention is required to achieve the desired results. Therefore, in this paper, a fully automated technique based on Natural Language Processing (NLP) is proposed to identify crosscutting concern at the requirements level.
format Article
author Ali, B.S.
Kasirun, Z.M.
author_facet Ali, B.S.
Kasirun, Z.M.
author_sort Ali, B.S.
title Crosscutting concern identification at requirements level
title_short Crosscutting concern identification at requirements level
title_full Crosscutting concern identification at requirements level
title_fullStr Crosscutting concern identification at requirements level
title_full_unstemmed Crosscutting concern identification at requirements level
title_sort crosscutting concern identification at requirements level
publishDate 2008
url http://eprints.um.edu.my/5093/
http://ejum.fsktm.um.edu.my/article/671.pdf
_version_ 1643687485894557696
score 13.211869

Similar Items