JOURNAL OF COMPUTING, VOLUME 2, ISSUE 12, DECEMBER 2010, ISSN 2151‐9617 

HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/  
WWW.JOURNALOFCOMPUTING.ORG     64 

Service Oriented Architecture –

Technologies, Approaches for Integration
and Automation of Legacy system in
Heterogeneous Environment using
Reusability technique
Latha S and Dr.Antony selvadoss Thanamani

Abstract— Legacy systems Integration in heterogeneous environment is one of the most pressing issues for organizations.
The continuous emergence of new technologies such as Service Oriented Architectures is robust, scalable, and maintainable.
Service Oriented Architecture (SOA) can be implemented using various technologies and approaches. For legacy integration
Web service is best suitable method for implementing Service Oriented Architecture. SOA legacy system modernization
projects have induced a lot of researchers to address the full modernization project life cycle starting from architecture
reconstruction, code analysis, modernization strategy selection etc. There are lot of challenges that legacy system has to
face during modernization. More over there are a lot of characteristics that has to be decided before framing the framework
for modernization. This theory helps us to understand the approaches and technologies available in SOA framework to come
up with a framework/architecture for modernizing the legacy system which is robust, scalable and secured.

Index Terms— Integration, Legacy System, Service Oriented Architecture, UDDI Registry, Web Service, WSDL, etc.,

——————————  ——————————
 Automated business processes.
1. INTRODUCTION  Multi-channel access to applications
 Reusability of existing application
Lot of complexity exist in the field of Information
Technology while developing new applications, replacing This paper focuses on Service Oriented Architecture and its
existing applications , maintenance of existing application components in enabling integration of legacy system,
and handling enhancement requests for a successfully allowing the synchronization of business processes and the
running applications. interoperability of information and operational systems.

In Distributed environment, applications use different
programming interfaces and interoperability protocol. If all
the applications have used same, it would be much simpler
and existing functionality and maintenance could be easier.
If same protocol and interfaces are used existing IT
infrastructure can be more easily replaced and modernized.
The emergence of Web services developments and
standards in support of automated business integration has
driven major technological advances in the integration
software space, most notably, the service-oriented
architecture (SOA).
This is the promise that service-oriented development
brings to the IT world, become the foundation for more
easily creating a variety of new strategic solutions,
including:
Legacy application transition to SOA environment can not
only utilize the secure data management ability in the
heterogeneous environment in the mainframe, which makes
SOA environment more secure, but also greatly reduce
operation costs of maintenance.
Service-oriented architecture for legacy system is about the
evolution of business processes, applications and services
from today's legacy-ridden and smooth integration of
disparate applications to a world of connected businesses,
accommodating rapid response to change and utilizing vast
degrees of business automation. It is a set of general design
principles that enables organizations to change business
processes on the wing and respond to the shifting demands
of the business in a manner that would be impractical or
cost-prohibitive using conventional application
development and resources allocation.

 Rapid application integration.

 
JOURNAL OF COMPUTING, VOLUME 2, ISSUE 12, DECEMBER 2010, ISSN 2151‐9617
HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/  
WWW.JOURNALOFCOMPUTING.ORG     65
This paper describes the methodology and results of a
survey targeting the distinct interpretations of the Service
Oriented Architecture for legacy modernization using
integration approach.
2. LEGACY SYSTEM
Legacy system is famous for its unique reliability, stability,
security, availability and massive data processing capacity.
Mainframe can provide excellent virtualization properties,
Quality of Service guarantee, highest application level
security and security load management.
2.1 INTRODUCTION
Legacy systems, like mainframes, which have evolved over
a period of more than four decades, are well known in the
IT industry for the Reliability-Availability-Scalability (RAS)
factor. These parameters are fine if the business model
doesn't change for 10-15 years or there are no new further
enhancements. This is impractical in today's dynamic and
competitive business environment.
Reliability of any enterprise platform will be much more
secure, if the applications developed on these legacy
systems are accessed from dumb terminals within the same
network in a centralized architecture. The costs associated
with legacy systems, like mainframes, are per-transaction,
so more transactions mean more cost incurred [3].
Mainframe systems are considered to be huge stores of
centralized computing and processing power. In dynamic
business environment to increase scalability, better
flexibility and better manageability for legacy system is
challenging.
Issues related to legacy systems, like aging of technologies
and platforms, high operational costs, increasing scarcity of
skills, and complex integration issues are key compulsions
to modernize these legacy systems [10].
2.2 LEGACY CRISIS
The crisis of legacy system is to make significant savings in
operating and maintaining legacy systems and its resources
for new business initiatives. In recent times, innovation in
the software industry has focused on the new applications
for distributed, open systems platforms (like Microsoft
Windows), using newer architecture and technology
paradigms [11].
The challenging crisis of legacy system
 Reusability
 Reduce maintenance cost
 Unified data access to heterogeneous data sources
Legacy Modernization & its approaches
 
 
Technologies for modernizing legacy systems, replacement
of legacy systems is a not at all a straight forward process.
Switching off a thirty year old system and plugging the new
feature overnight is not a feasible solution There is an
increasing need to migrate legacy systems[4][1] to new
hardware and software development paradigm[5][6]. There
are three possible ways in which we can solve the legacy
problem [5][2]
Redevelopment: Redevelops the legacy system from scratch
using the new hardware platform and modern architecture,
tools and databases. Here the risk of failure is too high and
also expensive from the point of view of cost.
Wrapping: Wrapping surrounds the existing data,
individual program, application systems, and interfaces
with the new operations or the “new and improved” look.
The wrapped component act as the server performing some
functions required by an external client that does not need
to know the service is implemented.
Migration: When redevelopment is unacceptably risky and
wrapping is unsuitable, migrating is the alternative solution.
Migration moves the existing operational system to a new
platform, retaining the legacy system functionality and
causing as little disruption to the existing operational and
business environment as possible. The risk of failure is high
and time consuming factor.
From a detailed survey of the literature in this area there has
been no successful practical experience report from projects
using a comprehensive modernization approach. The use of
these approaches is still somewhat risky and advanced.
3. SERVICE ORIENTED ARCHITECTURE
3.1 INTRODUCTION
“A service-oriented architecture (SOA) is a paradigm for
organizing and utilizing distributed capabilities that may be
under the control of different ownership domains”[1]. Actually,
to enact a “plug and do business” [2], different technologies
have been adopted (e.g. SOA, Grid Computing, etc) and
innovative solutions and enabling integration of legacy
system, allowing the synchronization of business processes
and the interoperability of information and operational
systems have been developed.
Service Oriented Architecture can be viewed as a computing
methodology or approach to build IT systems in which
business services used to align IT systems with the needs of
the business. Earlier approaches used in building IT systems
focused on direct use of specific implementation
environments such as object orientation or procedure
orientation to solve business problems. These approaches
resulted in systems that are often tied to the features and
functions of a particular execution environment technology.
JOURNAL OF COMPUTING, VOLUME 2, ISSUE 12, DECEMBER 2010, ISSN 2151‐9617
HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/  
WWW.JOURNALOFCOMPUTING.ORG     66
Service Oriented Architecture is to address the requirements
of loosely coupled, standards-based, and protocol-
independent distributed computing, mapping enterprise
information systems (EIS) appropriately to the overall
business process flow.
In an SOA, software resources are packaged as “services”,
which are well defined, self-contained modules that provide
standard business functionality and are independent of the
state or context of other services.
A service-oriented architecture (SOA) is a collection of
network-accessible, loosely coupled services that are
assembled into composite applications to support the
requirements of software users. Services in a SOA are
discovered, described, and invoked via XML messages
typically using UDDI for discovery, WSDL for service
interface bindings, and SOAP or REST for message transport
[6].
Services are described in a standard definition language,
have a published interface, and communicate with each
other requesting execution of their operations in order to
collectively support a common business task or process [7].
Services that utilize Web services standards, e.g., Web
Services Description Language (WSDL), Simple Object
Access Protocol (SOAP), and Universal Description,
Discovery and Integration registry (UDDI), are the most
popular type of services available today.
From the above description of service-oriented architecture,
it shows clearly that service is a key component. A service
can be considered as a means by which the needs of a
consumer are brought together with the capabilities of the
service provider [5]. Services within an organizational
context can either be driven by the needs of the consumer,
user/business requirements and drilling down to the
system level (top down), or taking into account the system
capabilities of the service provider and building up services
that can be exposed to the higher layers in the architecture
(bottom up).
One of the primary goals of using Service-Oriented
Architecture (SOA), is reuse of services. This helps to avoid
duplication of code for enabling similar business functions
across multiple business processes, spanning one or more
lines of businesses [7]. Reuse of services also helps in
achieving business agility by quickly assembling new
business processes from existing services to meet dynamic
needs, and even creating new business processes with
having to create fewer new services from start. Therefore,
service reuse brings forward multiple business benefits -
from reduction in development cost, increased code
reliability for business processes with reuse of well tested
code, sharing of common infrastructure across multiple
business processes, to reduction in development time and
 
 
increased business agility [11]. It is therefore one of the key
motivational pillars of SOA.
Reusability of code has been a goal in IT-based solutions
from the start of computer programming [13]. It started with
the use of mnemonics representing op codes, use of
subroutines in structured programming as reusable
modules, to the concept of a group of related subroutines as
libraries, followed by more advanced concepts of reusable
software components and objects. The concept of reusability
in SOA goes further – not just reuse of a block of code but
code that represents (i.e., implements) a business service.
While sharing code and objects had some limited success,
reuse at this level is challenged from difficulty of
coordination in software development across independent
developers, as well as understanding, identification and
searching of existing codes. However, service orientation
with loose coupling of independently developed codes that
align with some business functions makes the challenges in
code reusability more amenable.
However, there exist many challenges in reusing services,
and without a proactive approach in governing SOA service
life-cycle and supporting certain core capabilities in both
development and runtime environment, this will remain an
elusive goal [8].
Next challenging thing in legacy system is Unified data
access to heterogeneous data sources.
Current data programming technologies are more or less
specific to data source types. In Service Oriented
Architecture environments and real-world applications,
however, data frequently comes from a variety of sources,
including relational databases, custom data access, Web
services, XML data stores, enterprise information systems,
etc.
The diversity of programming models needed to handle this
data heterogeneity poses a big challenge development
community. Service Data Object provides a common and
simple API that allows handling data from heterogeneous
data sources in a uniform way.
3.2 ROLE OF SERVICE IN SERVICES ORIENTED
ARCHITECTURE
A service-oriented architecture contains three basic
components:
JOURNAL OF COMPUTING, VOLUME 2, ISSUE 12, DECEMBER 2010, ISSN 2151‐9617
HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/  
WWW.JOURNALOFCOMPUTING.ORG     67
Fig.1 SOA Components 
A service provider creates a Web service and possibly
publishes to the service broker the information necessary to
access and interface with the Web service.
A service broker (known as a service registry) makes the
Web service access and interface information available to
any potential service requester.
A service requestor binds to the service provider in order to
invoke one of its Web services, having optionally placed
entries in the broker registry using various find operations.
Each component can also act as one of the two other
components. For example, if a service provider requires
information that it can only acquire from some other service,
it acts as a service requester while still serving the original
request [9].
The service provider creates a Web service and possibly
publishes its interface and access information to the service
broker. The service broker (also known as service registry) is
responsible for making the Web service interface and
implementation access information available to any
potential service requestor. The service requestor binds to
the service provider in order to invoke one of its Web
services, having optionally placed entries in the broker
registry using various find operations.
3.3 NEED FOR SERVICE ORIENTED ARCHITECTURE
Business organizations are dealing with two fundamental
concerns; the ability to quickly change to meet today’s
urgent demand for new level of agility, and the need to
reduce cost [5]. To remain competitive, businesses must
adapt quickly to internal factors such as acquisition and
restructuring, or external factors like competitive forces,
customer requirements or government regulations. Cost-
effective, flexible IT infrastructure is highly needed to
support the business. The concept of service oriented
architecture can help organizations succeed in the dynamic
business landscape of today. This can be achieved through
the primary characteristic of SOA which encourages the
reuse of business logic. SOA, when properly implemented,
makes reusability extremely cost- effective. The motivations
for different service oriented architecture initiatives include
 
 
a range of technical and business reasons. The most
common motivations are agility, flexibility, reusability, data
rationalization, integration, and reduced costs.
Leverage Existing Assets: SOA provides a layer of
abstraction that enables an organization to continue
leveraging its investment in IT by wrapping these existing
assets as services that provides business functions.
Organizations potentially can continue getting value out of
existing resources instead of having to rebuild a new system
from the scratch if they could employ an effective migration
path from the legacy systems to a service based system.
Easy Integration and Complexity Management
The integration point in Service Oriented Architecture is the
service specification and not the implementation. This
provides implementation transparency and minimizes the
impact when infrastructure and implementation changes
occur [5]. By providing a service specification in front of
existing resources and assets built on disparate systems,
integration becomes more manageable since complexities
are isolated. This becomes even more important as more
businesses work together to provide the value chain.
Responsively and Faster Time to Market: The ability to
compose new services out of existing ones provides a
distinct advantage to an organization that has to be agile to
respond to demanding business needs. Leveraging existing
components and services reduces the time needed to go
through the software development life cycle of gathering
requirements, performing design, development and testing.
This leads to rapid development of business services and
allows an organization to respond quickly to changes and
reduce its time-to-market.
Reduce Cost and Increased Reuse: With core business
services exposed in a loosely coupled manner, they can be
more easily used and combined based on business needs.
This means less duplication of resources, more potential for
reuse, and lower costs. Reuse seems to have been the holy
grail of software for decades [5]. With effective service-
based software reuse programs in place, IT delivery
organizations can build up libraries of business meaningful
functionality that are not attached to particular usage
settings, and are easily composable and re-composable to
meet new business requirements which can be hosted
remotely or locally. These libraries can help organizations to
reduce the investment required to address new business
software requirements, make delivery of new solutions
faster and more dependable. It will also improve the
accuracy and speed with which solutions can be altered.
Improved Flexibility: Flexibility concerns the ability of
solutions to be altered in the face of changing business and
technology requirements. This is boosted by the loosely-
coupled nature of services which are composed to meet
solution requirements in a SOA environment. Flexibility is a
JOURNAL OF COMPUTING, VOLUME 2, ISSUE 12, DECEMBER 2010, ISSN 2151‐9617
HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/  
WWW.JOURNALOFCOMPUTING.ORG     68
key to the change management element of IT-business
alignment. Since the business environment is highly
dynamic and volatile, SOAs allows businesses to be ready
for future challenges. Business processes which comprise of
a series of business services, can be more easily created,
changed and managed to meet the needs of the time. SOA
provides the flexibility and responsiveness that is critical to
businesses to survive and thrive.
Division of Responsibility
Service-oriented development aims to separate business
logic from the data thereby gives the ability to more easily
allow business people to concentrate on business issues,
technical people to concentrate on technical issues, and for
both to collaborate using the service contract.
4. WEB SERVICE
Web service is a software application identified by a URI,
whose interfaces and bindings are capable of being defined,
described, and discovered as XML artifacts. A Web service
supports direct interactions with other software agents
using XML-based messages exchanged via Internet-based
protocols [91].
The benefits of Web services include the decoupling of
service interfaces, the enablement of dynamic service
binding, and an increase in cross-language, cross platform
interoperability. These benefits derive from the standard
XML interface and access descriptions in WSDL.
Web services technology is an ideal technology choice for
implementing a service-oriented architecture since Web
services are standards based. Interoperability is a key
business advantage of web service.
Web services are widely supported across the industry. Web
services are platform and language neutral; there is no rule
for or against a particular hardware or software platform.
Web services can be implemented in any programming
language or toolset.
This technology provides a migration path to gradually
enable existing business functions as Web services are
required.
This technology supports synchronous and asynchronous,
RPC-based, and complex message-oriented exchange
patterns.
A Web service is a software system designed to support
interoperable machine-to-machine interaction over a
network [14]. It is described using a standard, formal data
centric XML notation, called its service description. It covers
all the details necessary to interact with the service,
including message formats, transport protocols and
locations. The most common service descriptions are:
• The Simple Object Access Protocol (SOAP) [15] that is the
fundamental messaging framework of web services. This
 
 
protocol provides extendable XML-based messaging
allowing data exchange between distributed applications
and may be used with different network transport protocols
(e.g., Hyper Text Transfer Protocol (HTTP), Simple Mail
Transfer Protocol (SMTP)).
• Web Service Description Language (WSDL) [16] is an
XML-based service description on how to communicate and
make a request to a Web service. WSDL is often used in
combination with SOAP and XML Schema to provide web
services over the internet. WSDL description is used to get
the syntactic information about the definition of each service
provided by a government agency. Each service must have a
WSDL document containing an XML description of the
functional aspects of the service, as well as the input and
output parameters for its operations. Communication
between service requester (citizen interface) and service
provider (agency) is carried through SOAP messages.
• Universal Description Discovery and Integration (UDDI)
[17] is the protocol used for the publishing of the Web
services information in order to find available Web services
on the Internet or an intranet. It is designed to be
interrogated by SOAP messages and to provide access to
WSDL documents describing the protocol bindings and
message formats required to interact with the Web services
listed in its directory.
A web service provides an access interface to a service. This
interface hides the implementation details of the service,
allowing it to be used independently of the hardware or
software platform on which this is implemented and of the
programming language in which this is written.
4.1 WEB SERVICES DESCRIPTION LANGUAGE
(WSDL)
Each web service has associated a WSDL document which
contains information about what messages go in and come
out from a service. This information is only syntactic or
structural but not semantic information.
A WSDL document has two parts: an abstract part and a
concert part [18]. The first one, describes what Web service
does in terms of messages it consumes and produces, and
the other one, defines how and where the service is offered.
JOURNAL OF COMPUTING, VOLUME 2, ISSUE 12, DECEMBER 2010, ISSN 2151‐9617
HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/  
WWW.JOURNALOFCOMPUTING.ORG     69
Fig. 2 Structure of WSDL 
Figure shows the syntactic structure of a WSDL document
sticking out the abstract part and concrete part. As
mentioned documentation provided by a WSDL file is XML-
based. It is formed by a set of definitions contained into a
<definitions> element. This element contains a target name
attribute who is the ownership of the set of definitions
inside the document, all the XML namespace needed (xmlns
attributes) and an optional name attribute related with the
name of the Web Service. A <definitions> element is
composed by the following elements:
• <type> element: It is used to indicate the data definitions
that web service will use later in the definition of the
messages that it will exchange.
• <message> element: It allows describing the messages
that web service will exchange. A message is composed by
one or more parts where a part is associated conceptually
with a parameter; its structure depends on how the binding
area of the WSDL is written. Each part has two attributes, its
name and the kind (element or type) which is associated
with the messaging style.
• <portType> element: It contains one attribute, the port
Type name, it is only an identifier. This element is the most
important part of a WSDL document essentially because it
structures the set of <operation>s that a Web service
provides and the group of inputs, outputs and faults
message that it will be required or produce.
The message exchange defined by a <operation> can be
One-way, Request-response, Solicit-response or
Notification
• <binding> element: While <portType> specify what
<operation>s can be carried out and the <messages>s define
the parameters types for the operations, the <binding>
elements describe how to format those messages to interact
in a protocol-depended manner.
• <service> element: It is the final part of a web service
description which contains one attribute, its name, and a
child element <port> which has two attributes, name and a
reference to a binging. A service can have several <port>
elements. Each <port> element describes where a single
portType is offered via a given binding.
 
 
4.2 SIMPLE OBJECT ACCESS PROTOCOL (SOAP)
Simple Object Access Protocol (SOAP) is a network,
transport, and programming language neutral protocol that
allow a service consumer to call a remote service provider.
The message format is XML.
SOAP is designed to be simple and extensible. It provides a
framework to describe message content and process
instructions.
All SOAP messages are encoded using XML. SOAP is
transport protocol independent. HTTP is one of the
supported transports. Hence, SOAP can be run over an
existing Internet infrastructure. SOAP is operating system
independent and not tied to any programming language or
component technology. It is object model neutral.
5. CONCLUSION
The existing mainframe systems also called legacy systems
are not capable of some of the mentioned benefits. For
example, the cost of maintenance of a legacy system is very
expensive and does not support critical business application
because business logic and data are not separate.
This paper presents various technological challenges of
legacy system including possibility of reusing existing logic
to support current business process, reusing existing process
to reduce costs, reusing existing system design to ensure
dependable and reliable solution, reusing existing system’
elements for faster deliver and challenges need to be dealt in
evolution of a legacy system over Intranet based
architectures and the concepts of using Service oriented
architecture to overcome the challenges.
6. ACKNOWLEDGEMENT
The authors would like to thank Dr. Antony Selvadoss
Thanamani, Head and Department of Computer Science, NGM
College for his guidance and constant encouragement and help
extended during this work.
The authors would also like to acknowledge and thank the
authors and publishers of referenced papers and textbooks, for
making available their invaluable work products which served
as excellent reference to this paper. All trademarks and
registered trademarks used in this paper are the properties of
their respective owners / companies.
7. REFERENCES
[1]. Bradley A., Gall N., Schulte R. W., Understanding and Applying
the Design Differences Between WS-* Based Architecture and
Web-Oriented Architecture, G00147780, 25 April, 2007.
[2]. Bacquet, J., Naccari, F. N. (2002). ‘Plug and Do Business’ and the
European R&D Programs, in:Camarinha-Matos, L. (ed.),
Collaborative Business Ecosystems and Virtual Enterprises.
Kluwer Publisher.
[3]. Eric Newcomer, Greg Lomow. Understanding SOA with Web
Services. Addison-Wesley, 2005
[4]. http://publib.boulder.ibm.com/infocenter/txformp/v6r0m0/ind
ex.jsp?topic=/com.ibm.cics.te.doc/erziaz0015.htm
JOURNAL OF COMPUTING, VOLUME 2, ISSUE 12, DECEMBER 2010, ISSN 2151‐9617 
HTTPS://SITES.GOOGLE.COM/SITE/JOURNALOFCOMPUTING/  
WWW.JOURNALOFCOMPUTING.ORG     70 
[5]. Michael Rosen. Adoption of Best Practices in Service Oriented
Architecture Development. Cutter Benchmark Review on Second Dr. Antony Selvadoss Thanamani, Ph.D., Head, Department
Analyzing IT Metrics for Informed Management Decision, Volume of Computer Science, NGM college , Pollachi. He has done his
6, Number 10 October 2006. research on e-learning and has published few technical research
[6]. Engelen, R.a., 2008. A framework for service-oriented computing papers in journals.
with C and C++ Web service components. ACM Transactions on
Internet Technology, 8(3), 1-25
[7]. Lopez, N., Casallas, R. & Villalobos, J., 2007. Challenges in
Creating Environments for SOA Learning. International Workshop
on Systems Development in SOA Environments (SDSOA'07: ICSE
Workshops 2007), 9-9.
[8]. Dan, A., Johnson, R.D. & Carrato, T., 2008. SOA service reuse by
design. Proceedings of the 2nd international workshop on Systems
development in SOA environments - SDSOA '08, 25.
[9]. J. Ang and M. Luo, "Front cover Patterns : Service- Oriented
Architecture and Web Services ces," Contract.
[10]. T. Jianfeng and Z. Xianing, "Mainframe Application Transition to
SOA Environment Using CICS Service Flow Feature," 2008
International Conference on Computer Science and Software
Engineering, 2008, pp. 404-408.
[11]. "Introduction to SOA with Web Services." – IBM Redbooks
[12]. Linthicum, Dave, October 2007, Core Value of a SOA is the Ability
to Reuse Services? Not a Chance, DOI=
http://www.infoworld.com/archives/emailPrint.jsp?R=printThi
s&A=http://weblog.infoworld.com/realworldsoa/archives/2007
/10/core_value_of_a.html
[13]. Mehul, J., July 2007, SOA Reusability: Shrinking the Lag between
Business and IT. java.net, DOI=
http://today.java.net/pub/a/today/2007/07/24/soa-reusability-
shrinking-lag-time.html
[14]. Graham, Steve., Simeonov, Simeon., Boubez, Toufic., Daniels,
Glen., Davis,Doug., Nakamura, Yuichi., and Neyama, Ryo.
Building Web Services with Java. Second Edition, 2005. Sams
publishing. 2005
[15]. Simon. W, Graham. M and Simon. P. Portal Replication for Web
Application Availability Via SOAP. The Eighth IEEE International
Workshop on Object-Oriented Real-Time Dependable Systems,
2003.
[16]. Christensen, E., Curbera, F., Meredith, G., and Weerawarana, S.
Web Services Description Language (WSDL) Version 1.1, W3C
Note, March 2001; www.w3.org/TR/wsdl.html.
[17]. UDDI Spec Technical Committee, UDDI Version 3.0.2, October
2004;
[18]. http://uddi.org/pubs/uddi-v3.0.2-20041019.htm
[19]. Weerawarana, S., Curbera, Francisco., Leymann, Frank., Storey,
Tony., and Ferguson, Donald F. Web Service Platform
Architecture. Prentice Hall, 2005
[20]. Paulson,Viktor. Web Service Interoperability Issues. Master of
Science Thesis Stockhol, Sweden 2005.
[21]. Stephenson, David. Tips for solving web service interoperability
problems. Hewlett-Packard, 2004
[22]. M. Clavreul, O. Barais, and J. Jézéquel, "Integrating legacy systems
with MDE," Proceedings of the 32nd ACM/IEEE International
Conference on Software Engineering - ICSE '10, 2010, p. 69.
[23]. C. Engelke and C. Fitzgerald, "Replacing legacy web services with
RESTful services," Proceedings of the First International Workshop on
RESTful Design - WS-REST '10, 2010, p. 27.
[24]. The Mendeley Support Team, Getting Started with Mendeley,
London: Mendeley Ltd., 2010.
[25]. A. Bertolino and A. Polini, "IEEE International Conference on
Software Testing Verification and Validation Workshops SOA Test
Governance : enabling service integration testing across
organization and technology borders," Governance An International
Journal Of Policy And Administration, 2009, pp. 277-286

First Latha S , Research scholar, NGM college has completed her

MCA ., MPhil in computer science in the year 2005. She has 12+ years
of experience in teaching.