Fluid AOP : task-specific modularity

Most aspect-oriented programming technology used today uses a linguistic approach that enables programmers to write modular crosscutting code. Two limitations of these approaches are that there is only one decomposition present for a code-base and that they require developers to adopt a new (or...

Full description

Bibliographic Details
Main Author: Hon, Terry
Language:English
Published: University of British Columbia 2011
Online Access:http://hdl.handle.net/2429/32732
id ndltd-UBC-oai-circle.library.ubc.ca-2429-32732
record_format oai_dc
spelling ndltd-UBC-oai-circle.library.ubc.ca-2429-327322018-01-05T17:46:47Z Fluid AOP : task-specific modularity Hon, Terry Most aspect-oriented programming technology used today uses a linguistic approach that enables programmers to write modular crosscutting code. Two limitations of these approaches are that there is only one decomposition present for a code-base and that they require developers to adopt a new (or extended) programming language. We propose fluid AOP to modularize crosscutting concerns without these limitations. Fluid AOP provides mechanisms in the IDE for creating constructs that localize a software developer's interaction for a specific task. These constructs act as fluid aspects of the system. They are editable representations of the subset of the code-base that the developer needs to interact with to perform a task. We present three fluid AOP prototypes and provide comparisons between them; as well as comparisons between the fluid AOP, linguistic AOP, and non AOP approaches. Science, Faculty of Computer Science, Department of Graduate 2011-03-22T20:03:04Z 2011-03-22T20:03:04Z 2007 Text Thesis/Dissertation http://hdl.handle.net/2429/32732 eng For non-commercial purposes only, such as research, private study and education. Additional conditions apply, see Terms of Use https://open.library.ubc.ca/terms_of_use. University of British Columbia
collection NDLTD
language English
sources NDLTD
description Most aspect-oriented programming technology used today uses a linguistic approach that enables programmers to write modular crosscutting code. Two limitations of these approaches are that there is only one decomposition present for a code-base and that they require developers to adopt a new (or extended) programming language. We propose fluid AOP to modularize crosscutting concerns without these limitations. Fluid AOP provides mechanisms in the IDE for creating constructs that localize a software developer's interaction for a specific task. These constructs act as fluid aspects of the system. They are editable representations of the subset of the code-base that the developer needs to interact with to perform a task. We present three fluid AOP prototypes and provide comparisons between them; as well as comparisons between the fluid AOP, linguistic AOP, and non AOP approaches. === Science, Faculty of === Computer Science, Department of === Graduate
author Hon, Terry
spellingShingle Hon, Terry
Fluid AOP : task-specific modularity
author_facet Hon, Terry
author_sort Hon, Terry
title Fluid AOP : task-specific modularity
title_short Fluid AOP : task-specific modularity
title_full Fluid AOP : task-specific modularity
title_fullStr Fluid AOP : task-specific modularity
title_full_unstemmed Fluid AOP : task-specific modularity
title_sort fluid aop : task-specific modularity
publisher University of British Columbia
publishDate 2011
url http://hdl.handle.net/2429/32732
work_keys_str_mv AT honterry fluidaoptaskspecificmodularity
_version_ 1718594843095072768