Requirement-oriented aspect refactoring for early aspect formation and mapping in software maintenance

Modularity aims to increase the maintainability of a software program by fostering reusability, assist in reducing development cost and enhancing the quality of the software. Although modularity gaining popularity, yet it hard to be realized due to the existence of stakeholder interest in the primar...

Full description

Bibliographic Details
Main Author: Subramaniam, Hema
Format: Thesis
Language:English
Published: 2016
Subjects:
Online Access:http://psasir.upm.edu.my/id/eprint/69312/1/FSKTM%202016%203%20IR.pdf
_version_ 1825933695924568064
author Subramaniam, Hema
author_facet Subramaniam, Hema
author_sort Subramaniam, Hema
collection UPM
description Modularity aims to increase the maintainability of a software program by fostering reusability, assist in reducing development cost and enhancing the quality of the software. Although modularity gaining popularity, yet it hard to be realized due to the existence of stakeholder interest in the primary programs. Thus, maintainability became an unresolved issue. This issue may be compromised by isolating stakeholder interests, yet the system still contains interests which hard to be located. Therefore, an essential approach for managing and controlling those crosscutting stakeholder interests became tremendously important. Accordingly, Aspect-Oriented Approach (AOA) is employed the concept of crosscutting concern and aspect as the representation of those stakeholder interests. At the present time, the software practitioners have preferred to conduct crosscutting concern isolation at coding level, which have been resulting in ambiguous situation. Therefore, the crosscutting concern isolation process was transformed into requirement specifications. Since Early Aspect concept stay in line with new software development, the attempt to make existing application’s to be AOA compatible became the matter in question. For this reason, the refactoring effort which started at requirement specification has become absolutely necessary. In that case, this study seeks to address the issue by proposing a conceptual framework known as Requirement-Oriented Aspect Refactoring (ReqOAR). In order to view the issue comprehensively, the ReqOAR aims to handle concern at requirement level and to facilitate aspect candidate flow throughout existing software artefacts. To foster effective concern handler at requirement level, ReqOAR conceptual framework were included with the process components such as concern identification, concern isolation and aspect formation. Whereas, to ensure the flow of aspect candidate throughout the software artefacts, ReqOAR comprise of process called as concern mapping. Apart from process components, ReqOAR also contain techniques components which associated with aforementioned process components. For instance, Crosscutting Concern Domain Library Listing (CCDLL) and Concern Associated Terms Glossary (CATG) are among the ReqOAR proposed techniques. Furthermore, ReqOAR was validated using empirical evaluation. According to the evaluation, an optimum accuracy value was recorded from the treatment technique compared to control technique. These current findings would definitely empower the growing body of AOA in the context of restructuring the requirement specification.
first_indexed 2024-03-06T10:01:18Z
format Thesis
id upm.eprints-69312
institution Universiti Putra Malaysia
language English
last_indexed 2024-03-06T10:01:18Z
publishDate 2016
record_format dspace
spelling upm.eprints-693122019-06-28T08:12:03Z http://psasir.upm.edu.my/id/eprint/69312/ Requirement-oriented aspect refactoring for early aspect formation and mapping in software maintenance Subramaniam, Hema Modularity aims to increase the maintainability of a software program by fostering reusability, assist in reducing development cost and enhancing the quality of the software. Although modularity gaining popularity, yet it hard to be realized due to the existence of stakeholder interest in the primary programs. Thus, maintainability became an unresolved issue. This issue may be compromised by isolating stakeholder interests, yet the system still contains interests which hard to be located. Therefore, an essential approach for managing and controlling those crosscutting stakeholder interests became tremendously important. Accordingly, Aspect-Oriented Approach (AOA) is employed the concept of crosscutting concern and aspect as the representation of those stakeholder interests. At the present time, the software practitioners have preferred to conduct crosscutting concern isolation at coding level, which have been resulting in ambiguous situation. Therefore, the crosscutting concern isolation process was transformed into requirement specifications. Since Early Aspect concept stay in line with new software development, the attempt to make existing application’s to be AOA compatible became the matter in question. For this reason, the refactoring effort which started at requirement specification has become absolutely necessary. In that case, this study seeks to address the issue by proposing a conceptual framework known as Requirement-Oriented Aspect Refactoring (ReqOAR). In order to view the issue comprehensively, the ReqOAR aims to handle concern at requirement level and to facilitate aspect candidate flow throughout existing software artefacts. To foster effective concern handler at requirement level, ReqOAR conceptual framework were included with the process components such as concern identification, concern isolation and aspect formation. Whereas, to ensure the flow of aspect candidate throughout the software artefacts, ReqOAR comprise of process called as concern mapping. Apart from process components, ReqOAR also contain techniques components which associated with aforementioned process components. For instance, Crosscutting Concern Domain Library Listing (CCDLL) and Concern Associated Terms Glossary (CATG) are among the ReqOAR proposed techniques. Furthermore, ReqOAR was validated using empirical evaluation. According to the evaluation, an optimum accuracy value was recorded from the treatment technique compared to control technique. These current findings would definitely empower the growing body of AOA in the context of restructuring the requirement specification. 2016-01 Thesis NonPeerReviewed text en http://psasir.upm.edu.my/id/eprint/69312/1/FSKTM%202016%203%20IR.pdf Subramaniam, Hema (2016) Requirement-oriented aspect refactoring for early aspect formation and mapping in software maintenance. Doctoral thesis, Universiti Putra Malaysia. Aspect-oriented programming Software maintenance Computer software - Development
spellingShingle Aspect-oriented programming
Software maintenance
Computer software - Development
Subramaniam, Hema
Requirement-oriented aspect refactoring for early aspect formation and mapping in software maintenance
title Requirement-oriented aspect refactoring for early aspect formation and mapping in software maintenance
title_full Requirement-oriented aspect refactoring for early aspect formation and mapping in software maintenance
title_fullStr Requirement-oriented aspect refactoring for early aspect formation and mapping in software maintenance
title_full_unstemmed Requirement-oriented aspect refactoring for early aspect formation and mapping in software maintenance
title_short Requirement-oriented aspect refactoring for early aspect formation and mapping in software maintenance
title_sort requirement oriented aspect refactoring for early aspect formation and mapping in software maintenance
topic Aspect-oriented programming
Software maintenance
Computer software - Development
url http://psasir.upm.edu.my/id/eprint/69312/1/FSKTM%202016%203%20IR.pdf
work_keys_str_mv AT subramaniamhema requirementorientedaspectrefactoringforearlyaspectformationandmappinginsoftwaremaintenance