• Save
Web Services Identification in Legacy Code
Upcoming SlideShare
Loading in...5

Like this? Share it with your network


Web Services Identification in Legacy Code

Uploaded on


More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 13

http://www.linkedin.com 7
http://www.slideee.com 3
https://www.linkedin.com 2
http://www.lmodules.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


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