Show simple item record

dc.contributor.authorMedianero P, Xavier S
dc.contributor.authorCrespo, Sergio
dc.contributor.authorClunie, Clifton
dc.date.accessioned2017-07-28T15:38:20Z
dc.date.accessioned2017-07-28T15:38:20Z
dc.date.available2017-07-28T15:38:20Z
dc.date.available2017-07-28T15:38:20Z
dc.date.issued2014-07-04
dc.date.issued2014-07-04
dc.identifier.urihttp://ridda2.utp.ac.pa/handle/123456789/1842
dc.identifier.urihttp://ridda2.utp.ac.pa/handle/123456789/1842
dc.descriptionThe aspect-oriented programming has valuable advantages over other programming paradigms, but in turn it presents difficulties when applying the concepts within the stages of analysis and development to reduce the drawbacks of this paradigm. This paper proposes a methodology to reduce the drawbacks of the paradigm, at the same time provides steps that involve elements of common analysis in the Requirements Engineering with Aspects (basic unit of paradigm) in order to create the framework for a specific domain. The proposed methodology brings together some benefits methodologies, but it emphasizes the treatment of the first disadvantages of the programming aspects and the location and identification of aspects and elements; in addition, this article provides a tool that supports some methodology steps by generating part of the framework code base. In the process of treatment issues, the analysis is oriented to the specification of aspects using AspectJ, with rules to locate and determine aspects within its four Cyclical stages. Finally, it includes a case study which evaluates the steps in this methodology.en_US
dc.description.abstractThe aspect-oriented programming has valuable advantages over other programming paradigms, but in turn it presents difficulties when applying the concepts within the stages of analysis and development to reduce the drawbacks of this paradigm. This paper proposes a methodology to reduce the drawbacks of the paradigm, at the same time provides steps that involve elements of common analysis in the Requirements Engineering with Aspects (basic unit of paradigm) in order to create the framework for a specific domain. The proposed methodology brings together some benefits methodologies, but it emphasizes the treatment of the first disadvantages of the programming aspects and the location and identification of aspects and elements; in addition, this article provides a tool that supports some methodology steps by generating part of the framework code base. In the process of treatment issues, the analysis is oriented to the specification of aspects using AspectJ, with rules to locate and determine aspects within its four Cyclical stages. Finally, it includes a case study which evaluates the steps in this methodology.en_US
dc.formatapplication/pdf
dc.languageeng
dc.language.isoengen_US
dc.rightshttps://creativecommons.org/licenses/by-nc-sa/4.0/
dc.rightsinfo:eu-repo/semantics/openAccess
dc.subjectAspect Oriented Programmingen_US
dc.subjectMethodologyen_US
dc.subjectSoftware Engineeringen_US
dc.subjectRequirements Engineeringen_US
dc.subjectAspect Oriented Programming
dc.subjectMethodology
dc.subjectSoftware Engineering
dc.subjectRequirements Engineering
dc.titleAspect Oriented Programming Methodology to Support the Design of Specific Domain Frameworken_US
dc.typeinfo:eu-repo/semantics/article
dc.typeinfo:eu-repo/semantics/publishedVersion


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record