Web Services Identification in Legacy Code

2,109 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,109
On SlideShare
0
From Embeds
0
Number of Embeds
34
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Web Services Identification in Legacy Code

  1. 1. Mining candidate web services from legacy code Lerina Aversano – RCOST Univ. Of Sannio, Italy Massimiliano Di Penta – RCOST Univ. Of Sannio, Italy Ciro Palumbo – Engineering Ingegneria Informatica S.p.A., Italy
  2. 2. Motivations and objective <ul><li>Service-oriented systems are becoming a reality </li></ul><ul><li>System integrators tend to build systems by composing services </li></ul><ul><li>However, lack of services available </li></ul><ul><li>But… </li></ul><ul><li>Features are just there, implemented in existing legacy systems </li></ul><ul><li>Objective of this work: </li></ul><ul><ul><li>Search for potential services inside existing legacy systems </li></ul></ul><ul><ul><li>Integrated approach: </li></ul></ul><ul><ul><ul><li>Combines IR tracing with structural matching of the goal WSDL onto existing methods </li></ul></ul></ul>
  3. 3. Related Work <ul><li>Stroulia, 2004: </li></ul><ul><ul><li>Uses Java2WSDL of AXIS to extract WSDL from legacy systems </li></ul></ul><ul><ul><ul><li>Flexible Interface Matching for Web-Service discovery </li></ul></ul></ul><ul><li>Kokash, 2006; </li></ul><ul><ul><li>Structural comparison of existing services </li></ul></ul><ul><ul><ul><li>A comparison of Web Service Interfaces Similarity Measures </li></ul></ul></ul>
  4. 4. Proposed Architecture
  5. 5. Matching Source-Target <ul><li>Based on Kokash’s algorithm </li></ul><ul><li>Combined matching Textual+Structural </li></ul><ul><li>Query expansion based on WordNet </li></ul><ul><li>Lucen: a text search engine library </li></ul><ul><li>XML schema of method parameter types are reversed from the source code </li></ul><ul><ul><li>Java library types handled through a library </li></ul></ul>
  6. 6. CLAROS – Structural Matching <ul><li>Objective: searching for a send mail service </li></ul><ul><li>Precision and recall vary for different threshold values </li></ul><ul><ul><li>Threshold is the maximum value for a range of scores </li></ul></ul>
  7. 7. CLAROS – Hybrid matching <ul><li>Textual + Structural </li></ul><ul><li>Improves the recall </li></ul><ul><li>Missing services due to lack of relationship concept-term </li></ul>
  8. 8. Work in progress <ul><li>Dealing with relationships terms concepts </li></ul><ul><ul><li>Use of ontologies </li></ul></ul><ul><ul><li>Latent Semantic Indexing </li></ul></ul><ul><li>Use of execution traces </li></ul><ul><li>Slicing of legacy code to extract the feature to be exported as a service </li></ul>
  9. 9. Questions?

×