Weaving a social fabric into existing software

Li, Cheng; Patterson, John; Rohall, Steven L.; Hupfer, Susanne; Ross, Steven

doi:10.1145/1052898.1052911

Cited by 17 publications

(7 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…An idea of a program modification utilizing AOP was used in [7]. Authors of the paper are using aspects to incorporate new, collaborative features into existing applications.…”

Section: Related Workmentioning

confidence: 99%

Evolving Metamodels in Aspect-Oriented Manner

Vagac¹,

Kollár²,

Chodarev³

2011

Acta Electrotechnica Et Informatica

View full text Add to dashboard Cite

Multi-layered software architecture allows to allocate different responsibilities to different layers. When such a responsibility is to react about other part of the system, we can speak about a metalevel architecture. Such an architecture consists of at least two levels-a base level and a metalevel, where the metalevel reasons about the base level. A causal connection associates the base level objects with the metalevel objects and guarantees that changes to the metalevel are reflected into corresponding changes to the base level and vice-versa [14]. This paper presents an innovative approach to handle casual connections in metalevel architectures. The base level is represented by a legacy application. The metalevel contains a metamodel. The metamodel represents certain feature of the base level application. Aspect-oriented techniques are used to add a new code to the base level application. This code manages casual connection between the base level and the metamodel at the metalevel.

show abstract

“…An idea of a program modification utilizing AOP was used in [7]. Authors of the paper are using aspects to incorporate new, collaborative features into existing applications.…”

Section: Related Workmentioning

confidence: 99%

Evolving Metamodels in Aspect-Oriented Manner

Vagac¹,

Kollár²,

Chodarev³

2011

Acta Electrotechnica Et Informatica

View full text Add to dashboard Cite

show abstract

“…This approach is known but not widely used. An example of aspect modification in graphical interface of a program can be found in [9]. Aspects can be woven into a program treated as a "black box".…”

Section: Aspects Modificationsmentioning

confidence: 99%

“…Aspects oriented approach were used in program tracing [5,6,7,8] but the goal of tracing was different than in our approach. In [9] an example of adding new functionalities by aspects can be found.…”

Section: Introductionmentioning

confidence: 99%

Aspects in the Maintenance of Compiled Programs

Bluemke

Billewicz

2008

2008 Third International Conference on Dependability of Computer Systems DepCoS-RELCOMEX

View full text Add to dashboard Cite

We propose a new approach to the maintenance of programs with unavailable source code and documentation i.e. aspects oriented programming [2,3,4]. Aspects are used to trace the program execution and identify points, in which aspects implementing new functionalities may be applied. A special tool [1,10] for aspect oriented program tracing was designed and implemented. This tool is necessary to use the proposed approach. A modification of GIU interface of a compiled program without source code and documentation is presented. Advantages and disadvantages of described concepts are pointed out.

show abstract

“…The present research suggests that performance ilities o f distributed applications (e.g., maintainability, serviceability, accountability, security, scalability and durability) can be easily improved by incorporating design patterns as aspects, without polluting the appli cations. There are also other case studies available in AO literature [11], [26] to reinforce the fact that non-functional features as aspects can be readily woven into software sys tems. Weaving concurrency patterns as aspects provide several advantages.…”

Section: Discussionmentioning

confidence: 98%

“…In [12], refac toring a CORBA [2] middle-ware implementation, using aspects, is analyzed. Weaving contextual collaboration as aspects into a legacy application such as an address book has been explored in [26], In [18] and [32], aspects are used at the model level. Aspect-Oriented Programming (AOP) can be considered as a further enhancement o f the OOP.…”

Section: Proposed Solutionmentioning

confidence: 99%

Aspect-oriented refactoring to patterns

Nagappan¹

View full text Add to dashboard Cite

R ep ro d u ced with p erm ission o f th e copyright ow ner. Further reproduction prohibited w ithout perm ission. 1*1 Library and Archives Canada Published Heritage Branch 395 Wellington Street Ottawa ON K1A 0N 4 C anada i * i Canada R ep ro d u ced with p erm ission o f th e copyright ow ner. Further reproduction prohibited w ithout perm ission. Abstract When new commercial software systems are developed, or existing ones are enhanced, non-functional features (such as logging and security) are typically added to the system as an after-thought. To meet market pressure, initial versions o f the system are deliber ately kept simple and primarily focused on functional requirements. In subsequent ver sions, non-functional features identified for system enhancement are added to it. The drawback o f such an approach is that it makes the initial simple version increasingly more complex, and thus more difficult to support and maintain. The aspect-oriented ap proach has been proposed to add such non-functional features (commonly referred as "ilities" in the field o f computer engineering) to software systems without polluting or af fecting the integrity o f the original code. In other words, non-functional features imple mented in the form o f aspects stand isolated without interfering with the simplicity, read ability and integrity o f the original system. This research brings together solutions to non functional requirements using patterns and refactoring to patterns in an aspect-oriented approach.The proposed solution has been tested by adding non-functional ilities to an existing RMI-based instant messaging system using patterns and aspect-oriented ap proach. The proposed solution is also tested to refactor an existing non-functional feature.The main proposal o f this research is that aspects are a vehicle for adding refactor ing/patterns to a system. Re-usable aspect libraries that are designed and implemented as part o f this research could be directly integrated into real world applications. ii R ep ro d u ced with p erm ission o f th e copyright ow ner. Further reproduction prohibited w ithout perm ission.

show abstract

Weaving a social fabric into existing software

Cited by 17 publications

References 10 publications

Evolving Metamodels in Aspect-Oriented Manner

Evolving Metamodels in Aspect-Oriented Manner

Aspects in the Maintenance of Compiled Programs

Aspect-oriented refactoring to patterns

Contact Info

Product

Resources

About