Service Interoperability In Soa

Published Date: 02 Nov 2017

1 Research Scholar, Department of Computer Science & Engineering, Manonmaniam Sundaranar University, Thirunelveli, Tamil Nadu.

2Associate Professor, Department Of Banking Technology, Pondicherry University, Puducherry.

[email protected], [email protected]

Abstract: Nowadays sharing of information and services among the major enterprises plays a crucial role in distributed systems. For manipulating the services and their data, Service Oriented Architecture plays a major role in communicating various environments for their resource sharing. When integrating various enterprises, services and computing systems etc., interoperation among those systems plays a major role for an easy and error prone services. So for creating interoperable systems, Service Oriented Architectures and Web services are the major requirements. Generally the word Interoperability is defined as when more number of systems which are in different premises with their own set of inter-domain policies able to know how each other work, accessing their services by requisition but in the same time all the environments need to have some common infrastructure, same set of attributes for data transmission to provide a dependable connection with no errors or misunderstanding among them. In this paper we present a survey about Interoperability, its importance, its various specification in different environments and its various types in different scenario such that how we are using interoperation among various computing systems efficiently and meaningfully. In some enterprise applications it was defined and classified in various levels, such as technical, service, community, organization and business levels and its importance of interoperability problems, various factors involved in the context of interoperability, standards to follow before developing a service systems and take part in the distributed environment. When we are participating in the distributed environment what are the necessary quality factors must be involved in our own system to interoperate with other systems. The idea behind this survey is to create basic knowledge about services, Service Oriented Architecture, service interoperability in different contexts, security attributes when discussing about interoperability, role of interoperability in service interaction and various research opportunities and issues to enhance the standard interoperability factors between multiple SOA based environments. Because standardization of standard generic Interoperable framework is still in research.

Keywords- SOA, Service, Interoperability, Composability, Security, Web services.

INTRODUCTION

SOA is generally defined as decomposing the enterprise application functions into a set of interoperable services. It can be used and deployed through some application programming interface. In distributed environment, for describing the web based data manipulation, which was mainly based on request-response services. For doing this Service-oriented architecture is the best approach for both synchronous and asynchronous applications [1]. The functional part of any environment’s business logic are modularized and given as a solution for consumer/customer applications. It is generally called as collection of services and they communicate with each other to do various composite reusable functions. The operation involved in the communication may be in two ways simple transfer of date or it may involve two or more services combining for performing various tasks. SOA tells that how to integrate distributed applications in a Web-based environment and what are all the requirements needed for integrating multiple implementation platforms. The major feature involved in SOA was when we are considering various enterprises’ environment and data storage format which were different across various entities like operating systems, system software, and application infrastructure were integrated by understanding the specification of those entities and gives the result.

In case of very large enterprises they should quickly respond to business changes to address newer business requirements. So every time technology should be updated based on the user requirements. It was easily done through the service oriented Architecture because it was loosely coupled [10]. It easily allows the existing user to update the current services, adding new services to the existing one, to meet the business needs day to date. Figure 1 shows the basic representation of service Oriented Architecture and its basic entities.

Service Registry

Find Register

Service Consumer

Service Provider

Invokes

Fig.1. Service Oriented Architecture

The basis of a service-oriented architecture generally organized as loosely coupled services because every software components involved in the services can interact with other applications without knowing their procedural details. Basically SOA is constructed with three components.  

Service Consumer: The service consumer [2] will get the service from other component by requesting them and send request to service provider, which found in the registry for service execution.

Service Provider: The service provider [2] is a network-accessible application. This application provides a service to the consumer and this service publishes its contract to service registry and make itself available to the service consumers. 

Service Registry: A service registry [2] is a centralized network-accessible registry that receiving all the terms and conditions as service contracts from providers and makes them known to the service consumers.

Nowadays SOA based applications are mainly focusing on defining and implementing of the individual business services. To Build an enterprise solutions we need to combine multiple existing enterprise/business services. These composite services can be further recursively composed with other services to form a higher level solution, and so on. This type of composition of business services is one of the main important features involved in SOA based environment. It also allows building new solutions based on the existing business services. Since the need for composition of individual business services increasing and growing day by day, it was very easier to implement new enterprise solutions.

1.2 DESIGN PRINCIPLES OF SOA

In the evolution of various programming language environment starting from monolithic application to distributed environment, one of major programming environment is object-oriented programming environment [2], it was filled with lots of needed requirements. As like object orientation, service-oriented architecture has become a unique design approach which introduces commonly accepted principles [3] that monitors the development and design of service based system.

Generally Services are:

Dynamically bound and discoverable.

Reusable.

Location-transparent.

Network-addressable interface.

Having own structure and logic.

Stress interoperability.

Stateless and standardized.

Coarse-grained interfaces.

Composite.

Loosely coupled.

Apart from this Design Principles, Interoperability plays a major role in creating enterprise business applications. Achieving interoperability among the various business environments helps to use the services of one enterprise by another one in need. This helps to increase time and efficiency. So to do this clear understanding among those environments should be made. For achieving this attributes and parameters used in the representation of enterprises and its various aspects must be noted and their characteristics should be analyzed. Interoperability can be defined in different contexts. In those, interoperability between security levels of different environments is still in research. In this paper, we try to classify some works related to service interoperability, importance of interoperability when we connect with other environment, various research opportunities and issues to enhance/improve the standard framework between multiple SOA environments. This paper is organized as follows: Section 2 presents the service interoperability and its importance, existing models involved to form interoperation and various kinds of interoperability. Section 3 discusses the related works done on service interoperability in various domains and applications and general interoperability requirements. Section 4 presents the various issues involved in handling interoperability and research opportunities to focus in various areas. Section 5 says about major challenges to focus on service interoperability. Finally in section 6 we present the conclusion of our survey by saying the importance of the service interoperability.

2. SERVICE INTEROPERABILITY

2.1 Concepts /Background of Interoperability

Interoperability [3] refers to the sharing of data or information. If the software programs are more interoperable then, it is easier for them to send and receive data. Software programs which are not having interoperable capability need to be integrated. In sharing of resources, data, information, integration among them plays a major role in make an interoperable system efficient. When we are communicating with various other environments, the problem is, each should know about other i.e. what the infrastructure, technical platform, syntactic knowledge, semantic knowledge, etc they are using. This should be efficiently done if both the environments should follow a common standard for interacting with each others. So it should acceptable among various criteria’s in which what both are needed and interoperating system is generated. A set of protocols which are platform, language, system independent are used by web services to interoperate between various systems or applications or services. These set of protocols helps the business partners to share important services by providing interoperability characteristics across firewalls.

Interoperability [4] generally in various perspectives, is capable of coordinating number of services in different environments and operates them in a reliable and understandable manner, such that information from the various environments transmits the data between those organization mutually understood by both even though there are differences in nature of language, programming interface and in any other entities.

When we are considering the interoperability between various computing environments, initially we have to create and support an open system model of interoperability. In continuation with this, the several entities of interoperable features involved in the process must be identified, checked and analyzed. The concepts involved in interoperability must be categorized based on the different requirement of enterprise computing. Based on the context we discussed, we need to identify the clean separation of functions involved in the particular environment is necessary, the reason behind is it is very tough to find out the entity requirements of interoperability. Interoperability is basically told in various layers in several enterprises. Each layer defines their part of interoperation in different context like business level, services level etc. Classification of interoperability is mainly based on previous works and related studies of interoperability [5] and on concepts of various enterprise environments [6].

2.2 Existing Models for Interoperability

Interoperability [9] was generally defined as ability of one or more heterogeneous systems accessing each other services and also using those services easily and effectively that provides meaningful sharing of services and data to achieve a desired solution. There are several models already existing for interoperability. They are

Integrated Model: In this Model, the required knowledge for achieving interoperability was stored earlier into the computation process. It was classified into three categories as shown in the table 1.

TABLE I: CLASSIFICATION OF INTEGRATED MODEL

Tightly coupled Integration

Required knowledge needed for interoperation is injected into the business enterprises.

Cost- effective

Easy to implement

Software adaption

Interoperation knowledge was partially isolated from the application entities.

Knowledge is present in

Form of adapters and wrappers.

Use of common computing environments

Required knowledge is present in standard environment.

Middleware and interface description language was used.

Unified Model: In this, the required knowledge for interoperation can be achieved through standardization by shared meta-information functionality. It was classified into two categories as shown in the table 2.

TABLE II: CLASSIFICATION OF UNIFIED MODEL

Standard Meta Information

Formal specification for guaranteed interoperation implementation.

Explicitly shared meta-information

Knowledge can be defined using specific modeling language like UML

Federated Model [7]: In this model, each user has their own infrastructure for their business services. The required knowledge for achieving interoperation was shared Meta model. Here knowledge was assigned by negotiation process, verification models, and service behavior monitoring. It was classified in five levels as shown in the table 3. The various levels are mainly categorized on the aspects of parameters required for achieving the interoperation.

TABLE III: CLASSIFICATION OF FEDERATED MODEL

Technology

Service

Community

Organization

Business

The main goal of interoperability is to exchange useful information between simulation systems. In order to achieve this goal, it is essential to provide a way to exchange information and come to a common understanding of the information being exchanged. This common understanding result in a specification often standardized that provides a technical protocol to support the exchange of bits and bytes and a description framework to capture the information. The result is an agreement on how to exchange information and how to describe it. The information to be exchanged varies with respect to the available models and what information they can provide and/or consume.

2.2 Various Types of Interoperability

Based on the various research handled in various business environments and enterprise applications, Interoperability is classified into three categories.

Syntactic Interoperability

Semantic Interoperability

Pragmatic Interoperability

Syntactic Interoperability: Syntactic interoperability [14] is the basic entity involved in the interoperation. It involves the data transferred between the various enterprise organization are in understandable and well matched with the coordinating environment. To do the above concept the method followed here is message sending environment should encode the services using some cryptographic or algorithmic techniques already stored in the database in the form of rules and definitions. The message recipient environment receives the services from the sender and decodes the same by using the same algorithm technique or some other technique that they are following in their own enterprise. The issue occurred in this case of interoperation was when sender’s code or algorithm are incompatible with the recipient’s one, there was difficulties in understanding the message contents delivered.

Semantic Interoperability: Semantic interoperability [14] is other kind of interoperation involved in the systems. The role of semantic interoperability is mainly deals with data transferred between various organizations or between the sender and recipient should have the same meaning without considering the syntax and formats followed in their own environments. The main objective of interoperability was, user participating in the integrating environments does not know about the infrastructure, platforms, entities and knowledge of the recipient. But the data or message transferred, service requested, services received should be meaningful, error free and compatible with other systems. Here the different aspects of sender and receiver were identified and making a service level agreement among those systems was developed for communication. However one user does not know the subject knowledge of other users, they can only access the services that they are offering. The issue here was, so far there was no dynamic system for identifying the aspects of two or more systems in run time. The Semantic interoperable problems starts when both the sender and receiver having different subject knowledge and functional requirements [14] related to their enterprise. In order to solve the problems related to semantic interoperability, message sending environment and receiving environment should follow a common standard information transferring architecture to execute the entire message passing process smoothly and efficiently.

Pragmatic Interoperability: Pragmatic interoperability [14] is one of important aspects of web services particularly in information exchange systems. When there was continuous transmission of data, information etc among various platforms, the system should ensure that the entire receiving environment should follow a standard. When communication is happening, whenever the receiving system receives a particular message and stores the status of the data and sends an acknowledgement to the sender environment. Generally in many aspects, data delivered to particular environment should change the nature of the state, or priorly it should ask for the current status of the environment. So we conclude in the case of pragmatic interoperability that data services that are exchanged with some desired purpose for achieving the necessary functionalities. In conclusion that majority of the services the major functions of a particular data cannot be identified in a single data message. It can be done through identifying and verifying the number of service messages sent in the same order. The problem mainly occurred here is when the intended service messages differ from the actual meaning of the message.

GENERAL INTEROPERABILITY

REQUIREMENTS IN SOA ENVIRONMENT

Interoperability can be occurred/should be focused in various Perspectives [15] when we are communicating with various other environments. They are

Description: It is general representation of the information involved in the service based enterprise, business applications, data in various levels and how to manipulate the data are defined in a standard format. For example: Every enterprise should describe their own data in their own prescribed format like objective of the system, Technical details involving hardware, software requirements and business details. Without knowing what the purpose of the service is, we are not going to access the service. Therefore interoperability starts to occur in basic description level.

Communication: It is defined as the process of exchanging messages or transferring information between organizations all over the world. It is also means as the flow of information from source to receiver. Messages should be in an understandable format so that it will be easy for the users to process the messages. (Example: When two or more systems communicate, interoperability should occur in understanding the message format, what type of protocol is used, interface mechanism which is used for understanding the information between sender and receiver.

Browse information: is defined as requirement specification with reference to an organization capacity to access and retrieve the information stored in the central database. For example, information which is published by other organizations is easily accessed by other organizations if interoperable parameters are satisfied between the organizations.

Message Format: Another important category where interoperability can be achieved is through message format. Generally messages are used to send information from source to destination over networks. So we use the standard message format that determines the structure of the message that is to be sent. Common standard of Message format helps various business enterprises to communicate their messages in the distributed environment. It is the predetermined arrangement of parts of the message in the form of header, data and footer and index to identify the particular message.

Connection: Connection between two sources or organization also plays as one part of interoperability requirements. Simply talking connection is referred as a link between two devices for sharing or transferring the data’s over the internet. It is otherwise known as path between source and destination. Here also it suggests that there is a need for common framework among the enterprises in communicating and message transfer.

Security: It was one of the main parameters in the requirements of interoperability. Because when different levels of security followed in different organizations, at one point of time, they have to cooperate and exchange information whenever it was required. So security parameters in each and every organization should be analyzed. There are several security aspects that should be addressed in case of interoperability. They are Confidentiality, Authentication, Auditing, Authorization, Assurance, quality of service, End-to End Security, Interoperability. As in conclusion, security is safety measure that is provided for each and every organization users to safeguard their confidential data’s and to compose with other organization by checking the security level parameters without knowing what is knowledge present in the other system.

Negotiation: Negotiation is a discussion among the people, various enterprise or various corporate sectors for making decisions and to manage the disputes that occurs within the organization. It also provides organization with some set of specifications to reach their goal in business.

Agreement: Agreement among the various communicating services following a common agreement with standard format to define the collaboration agreement between two parties. This contract specifies the details of the product, standards that they are using to represent their own logic, and the activities that the company is performing.

Semantics: It was one of the major requirements in integration of various services in a single environment. Because when we are integrating we need to define the context of interoperation between various business processes that are commonly called as interoperability, should be concentrated in semantic level. Generally semantics was defined as meaning of expressions or relationships that gives meaning to the data.

Availability: It is another kind of requirement in the interoperability perspective. It was defined as the aspects of quality attributes to be measured in which whether the required service was available in all time for immediate use. It also states the probability of the service that is accessible when the server is available and also the amount that a method, subsystem or a tool that is operable and it is in an executable state.

Learning: Learning is to understand the standards and qualities of the collaborating business process to address the functionalities and aspects involved in the learning process of participating environment. Learning implements some set of methods to refine the knowledge and it also denotes some changes in the system through which we can acquire the knowledge by building or modifying the representations.

Scalability: When more number of services is integrating in a dynamic environment, the environment is capable of handling the system in more number of requests in a capable manner without performance loss. It also refers to the capability of a system to increase total throughput under an increased load when adding additional resources.

Specifications: It involves relation between the user and the provider by providing necessary requirements by specifying how to decide the desired service and how to use exactly. Generally it acts as intermediate between the user and the providers.

Performance: In interoperability perspective, performance plays a major role because when communicating with other system, how effectively it does the system competence that carries out functionalities at desired level and also requires understanding of how effectively you can use the functionalities that satisfies your requirements. Based on Quality of Service (QOS) factors performance can be still enhanced and improved.

Generality: It was one of the requirements that were handled in the context of quality that was used in the application component. It is defined as a state that is not limited to a particular case and it collects a large amount of information and presents in a single description.

Reliability [7]: is the capability of a system or an element to perform and maintain its required functions in continuous processes with necessary constraints over a period of time. It was also been taken as metrics in the perspective of measuring the service quality and it also represents the number of failures per day, week, month, or year. It also guarantees the messages that are being sent and received.

Based on the list of requirements, it was very clear and fine to understand the concepts and requirements of interoperability for developing a SOA based environment. Generally the researchers those who are working on service based environment, proposing service oriented computation mechanism the above requirements are very well suited for their underlying environment and for the research in which they are targeting. In this survey we also discuss the requirements that are used in various approaches and which are the requirements are not applied in the interoperable framework to suit the interoperability requirements.

3.1 Importance of Security in Interoperability

Security was one of the main parameters in the requirements of interoperability. Because when different levels of security followed or combined in different organizations, at one point of time, they have to cooperate and exchange information whenever it was required. So security parameters in each and every organization should be analyzed. There are several security aspects that should be addressed in case of interoperability. They are Confidentiality, Authentication, Auditing, Authorization, Assurance, quality of service, End-to End Security, Interoperability. As in conclusion, security is safety measure that is provided for each and every organization users to safeguard their confidential data’s and to compose with other organization by checking the security level parameters without knowing what is knowledge present in the other system.

As concluded from various interoperability frameworks done on several environments it was necessary that service interoperability constitute a necessary role for sharing and communicating the services among heterogeneous SOA systems. Based on the survey there are several requirements needed for interoperation between multiple platforms/environments. Table IV shows the various interoperability frameworks, their platforms, merits and demerits and interoperable requirements not covered by using the numeric numbers.

Table IV: Summary of Service Interoperability requirements in Various Frameworks and their main features and demerits.

No

Interoperability Frameworks

Platform/Environment

Main Features/Merits

Demerits

Requirements Not Covered

1.

Ideas Interoperability Framework

Enterprise Modeling

Architecture & Platform

Ontology

Augmenting quality attributes

Co-ordination of Enterprise process

Integration of business process, Syntactic and Semantic application.

Seamless Interoperability

Too specific

7,8,11,13,15,16

2

E-health Interoperability Framework

Interoperability through health organizations

Link organizational, informational and technical aspects

Different point between framework layers

Specific and Incompatible with other frameworks

2,4,7,8,9,

14,15,16

3

European Interoperability Framework

Technical E-health system

Supports interoperability of services and system between public administration and public.

Seamlessness

Too Specific

7,8,11,14,15

4

Enterprise Interoperability Framework

Structures interoperability knowledge

Identifies and categorize the knowledge that removes both syntactic and semantic barriers in process level.

Framework is too specific and cannot be used for different SOA Frameworks.

Doesn’t provides metrics for all suggested attributes

4,6,7,8,11,14

5

CCA Interoperability Framework

Discussing on various categories of Interoperability

Standards, Interfaces & Protocols

Adoption for Translation and mapping

Proxy to span of each framework

Doesn’t provide clear architecture for relationship between components

4,6,7,8,9,11,12,13,14,15,16

6

Evaluative Interoperability Framework

Testing environments

Resolving interoperability issues in Testing environments

Specific only in Testing environments

1,2,3,4,7,8,9,11,13,14,15

7

TAHI Interoperability Framework

For smart homes

Addresses the need of having common message format.

3.2 Problems occurred during Interoperability

During SOA based implementation of business enterprises there exists various interoperable problems.

Incompatible with the different standards and specifications of the products used by the business process.

Insufficient support to broadcast errors from one level to another level in SOA.

XML schema constraints occurred in the products is inconsistent.

Treating user requirements as an intermediate process is lagging.

Providing Negotiation aid in the business level.

Automatic composition of service components and reliable software systems

Products support asynchronous web service communication using proprietary standards.

To explicitly address the different levels from business processes to the programming level.

To directly connect business functionality and feature sets with pricing of the solution.

To explicitly include business interoperability in the model of the business functionality.

To provide an integrated view of the problem, leading to a consistent behavior suited to the needs of the customer.

RESEARCH OPPORTUNITIES & DIRECTIONS

Service interoperability is a major obstacle in realizing the SOA vision. Interoperability is the capability of multiple, autonomous and heterogeneous systems to use each other’s services effectively without misunderstanding.

Seamlessness: Ability to communicate without boundaries. Communicating by crossing boundaries. Authors also describe their experiences showing that without the appropriate settings and non-functional requirements seamless interoperability cannot be achieved.

The finding is that some of those frameworks are domain specific and some are general and not specific for one particular domain. Many research works have been conducted to solve different interoperability issues for specific domains such as resource management, enterprise system and healthcare sector.

Based on the lack of various interoperable awareness, motivates researchers to focus on seamlessness attributes of web services and SOA in various different perspectives. Researchers are going on in various categories such that some looking at a particular perspective while others have attempted to integrate several specifications such as enterprise coordination, business process integration, semantic applications, syntactical applications and physical integration etc.

So it is advantageous to develop a generic framework for seamlessness interoperability in service oriented environments based on fulfilling the various interoperability requirements which supports multi SOA environment.

Performance: Ability to carry out functionalities at desired level. Performance of the interoperability is defined in terms of system efficiency, where efficiency is the amount of computing resources required by system to perform its function. So increasing the performance of an integrated system in various levels when more number of systems is integrated.

Scalability: Ability of a system to grow without sacrificing performance.

Security: Availability of Security mechanisms that control or protect integrity of system. In case of security parameter every service based environment having distinct security policies based on their requirements. The research finding is that to develop a generic security framework that interoperates various distinct security policies of individual service oriented systems.

Reliability: Ability of the system to be able to perform its intended functions with required precision. Reliability also includes fault-tolerance, availability and stability of the system.

Synchronization: Synchronization is the process of establishing consistency among data on different data sources. In many of the services there are multiple participants, a single data may have multiple copies each of which is kept in one location and dealt with by different participants. If one copy is changed (e.g., new information are filled in or original data are modified), other copies should be informed punctually to keep synchronization between them. We call such issue as synchronization oriented interoperability. The finding is that synchronization among data plays a major role in service interoperability.

Quality of Service: When various service resources together to form new value-added services. It is not always possible when any of the resources may be composed together, quality of service between those services are same. There might be some QoS conflicts between them. We call it QoS interoperability between services. The finding is that QoS may differ based on their requirements and needs.

Research are also focusing more on the interoperability requirements in many systems and their works can be divided into three categories which are Individual applications, Domain specifications, Conceptual frameworks.

MAJOR CHALLENGES

Increasing the performance of an integrated system in various levels when more number of systems is integrated & defining the Quality model to evaluate the efficiency of SOA based integrated systems. One of the major challenges for industry-wide adoption of the service-oriented approach deals with integration of systems. When integrating the systems interoperability plays a major role. Here interoperability can be achieved through loose coupling of various components and composition of services. And also quality becomes necessary for this integrated system. Enhancing the quality of services creates lot of difficulties. There is no proper mechanism for devising the quality of services in both atomic and composite services.

Develop a generic framework for seamlessness interoperability in service oriented environments based on fulfilling the various interoperability requirements which supports multi SOA environment. The finding is that some of those interoperability frameworks are domain specific and some are general and not specific for one particular domain. The major challenge is to develop a generic framework for seamlessness interoperability of SOA based on the different interoperability requirements which support seamlessness for multi SOA platform.

Developing a dynamic and adaptive service oriented middleware architecture for effective integration and Reusability.

Developing an interoperable internet based on heterogeneity among various services: The major challenge in developing this is because in future the internet will be heterogeneous in many dimensions, related to physical objects, networks, services and data, which present a significant challenge for sustaining in the future internet. To ensure that appropriate semantic technologies, shared standards and mediations are required to assure interoperability of heterogeneous entities such as things, sensors and networks.

Developing a dynamic secure framework in integration of service oriented systems. Next The Major challenge in integrating various real world subjects, integration of the products of other vendors more users, more information and more services in the internet intensifies the necessity for safety and security because it is a major threat in today’s internet.

Developing a model for dynamic transparent interoperability between legacy systems. One of the major challenges in dealing with interoperability is dealing among various models. Despite a number of approaches dealing with interoperability between coordination models, provided solutions are in general ad hoc and concern specific cases. The challenge is to provide an overall solution to this issue is required, based on appropriate modeling abstractions and transformation mappings between models. Moreover, a precise evaluation of such mappings with respect to the preservation of semantics is needed.

Developing an integrated model for interoperating web services by considering semantic information in services. Service Oriented Architectures and Web services are important for creating interoperable information systems. However, these technologies lack of semantics. To overcome this limitation, semantic Web services are necessary. The possible semantic heterogeneities delay the interoperability. To overcome this problem, it is necessary to integrate and to make inter-operate Web services by mechanisms allowing their publication, discovery, selection and mediation at semantic level.

Security impact and quality of service: There are several directions for future work to further improve an end-to-end secured and agile environment to establish collaborative Business Processes. Research will focus on the way these security requirements impact the global QoS and how QoS and QoP requirements can be mixed to improve service selection.

A Framework for efficient interoperability by exploring metrics: To prove an efficiency of interfaces between different systems and to evaluate the capability of such interoperability, specifications of the interfaces i.e. inter-connection need to be identified. It is also necessary to explore some metrics or requirements to measure and evaluate interoperability frameworks [10]. In the context of SOA interoperability issues for the heterogeneous systems, seamless interoperability framework would be a best approach to be considered.

Technical Level of Interoperability: Its is relative to the communication and information technologies concerning the norms for presenting, stocking, exchanging, processing and communicating the data by means of computer material.

Standard Framework for describing Service Combinations: There are no standardized ways to describe service combinations, and there are no pricing models for these services available, so every service request from a customer is resulting in a tedious and expensive calculation for the complex service needed by the customer. The decisions of choosing and combining services, which are presented here, have a simple, but powerful model. This model is based on some common methodologies widely used in economics and business. This kind of aiding system is needed to provide a solution to the issue of identifying and combining services.

CONCLUSION

In developing a complete integrated architecture we have to choose a middleware architecture that satisfies the necessary interoperable requirements that are specific in their models or environment. Based on the studies from various resources, the finding is that developing a generic framework for seamless interoperability with needed parameters such as dynamic security, dynamic transparent interoperability, functional and non- functional requirements and finally the quality attribute requirements are all important for the success of a system. Nonetheless, the requirements that will shape the architecture design possessing all the necessary requirements. Nowadays SOA is becoming a popular solution to distributed systems. To create successful designs, it is important to understand how an SOA supports different standards, compatible with interoperable requirements, how the security features are varied in various services and how it satisfies different quality attributes involved in them. Determining business value and translating that to quality attributes is an area where mature processes are still lacking. Defining the overall governance for SOA lifecycle management is also an area that is still maturing. There are many open issues and research challenges in how quality attributes are dealt with in the overall lifecycle management of an SOA-based system.