1 / 17

In Support of an Aspect-oriented Approach to Migrating Distributed Applications

In Support of an Aspect-oriented Approach to Migrating Distributed Applications. Devon M. Simmonds Computer Science Department University of North Carolina, Wilmington simmondsd@uncw.edu. Distributed Systems. C. A. B. network. Middleware-based Communication

lela
Download Presentation

In Support of an Aspect-oriented Approach to Migrating Distributed Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. In Support of an Aspect-oriented Approach to Migrating Distributed Applications Devon M. Simmonds Computer Science Department University of North Carolina, Wilmington simmondsd@uncw.edu

  2. Distributed Systems C A B network • Middleware-based Communication • The Internet has helped make distributed systems pervasive.

  3. Distributed Systems Development Context C A • Heterogeneity • hardware platforms, operating systems, network protocols, programming languages. • Proliferation of middleware technologies • Continuous evolution of middleware • .Net, SOAP, EJB, CORBA, Jini, etc. B

  4. Distributed Systems Goals C A • Portability • Interoperability • Reusability • etc. B

  5. A Distributed Systems Problem Coupling of middleware artifacts and functional artifacts!

  6. Coupling: A Distributed Systems Problem Coupling makes the migration of applications difficult. In application migration the technology with which an application is developed is replaced by a different technology.

  7. How does coupling make migration difficult? PIM ClassC ClassA ClassC ClassB ClassA Eliminate Old Middleware Refactor Application ClassC ClassB ClassA ClassC ClassA Integrate New Middleware New Distributed Application ClassD ClassB ClassD ClassB Distributed Application

  8. Non Aspect-Oriented Migration of a Legacy Application

  9. Aspect-Oriented Software Development To The Rescue! Coupling’s call: Help! Help! Senor AOSD

  10. In AOSD crosscutting functionality is isolated in modular units called aspects. Crosscutting functionality logging in org.apache.tomcat

  11. Composition Specification Composition transformations transformations Aspect Oriented Model-driven Development Framework (AOMDF) Source Level Phase Develop source models Source primary model Source aspect models Develop primary Model mappings Develop aspect model mappings Transformation Specification Phase Aspect model mappings Primary model mappings Apply primary model mappings Apply aspect model mappings Target Level Phase Target aspect models Target primary model

  12. Complete AOMDF = Transformation + composition

  13. Complete AOMDF

  14. AOMDDF Instance Design Design

  15. Aspect-Oriented Development & Migration Middleware Change Non Aspect-Oriented Migration M1 to M2 Migration

  16. Summary & Conclusion C A • AO approach to development and migration makes quality attributes more achievable • Portability, Interoperability, Reusability • Further research needed to quantify the specific benefits. • Specifying metrics In Support of an Aspect-oriented Approach to Migrating Distributed Applications B

  17. Q u e s t i o n s ?

More Related