Change Management in Semantic Web Services

Change Management in Semantic Web Services in Legal Area using FSM & XXM

Introduction

With the new paradigm of Service Oriented Computing, many enterprises try to utilize services as fundamental elements for developing applications/solutions as an additive part on top of existing components. The Web Service Controller Structures (WSCA) for service-based, enterprise-scaled business alternatives provides exactly this flexibility. The design, exposure and management of services can be accomplished through something Oriented Structures (SOA) that supports the usage, structure and coordination of services in a loosely coupled manner. Web services seem to be particularly suitable for addressing these aspects of a SOA. Furthermore, composition dialects such as BPEL add value by composing Web services and facilitating the execution of business processes. As the SOA paradigm brings this big tendencies change relying on loose coupling of services it increases new questions in the area of change management. Change management is a central aspect in virtually any software design, but its complexity for Web services is increased by both structure languages and loose coupling. The ensuing advantages like composability, autonomy, message-based communication, and the avoidance of merged compilation and binding prove to be zero this context.

In this paper we discuss these elementary challenges of change management in the area of Web services (Web Service Change Management, WSCM). Currently there are no sound mechanisms and executive key points for changing Web services and their related entities. Through analysis of a suitable scenario, specifically looking at the details of the Web company and consumer functions, one can identify the many problems that can be found in this domain name. Therefore we begins our strategy with the factor of an application scenario from the business enterprise domain of request and change management, the addition of Web services in private legal sector.

An Overview of a WSCA

A WSCA includes several autonomous outsourced Web services, but serves as a almost coherent entity. Business entities, by means of Web services, are often geographically distributed and organizationally 3rd party. While WSCA has a potential to introduce home based business opportunities through vibrant alliances, the problems of fully realizing a WSCA lay in managing changes during its lifecycle through Extreme X Machines (XXM).

XXM:

In this newspaper we explore the look changes as made to software projects by the use of a formal model known as Extreme X-Machines (XXM) [5, 6], which are based on the work of Eilenberg and Holcombe [7, 8]. An XXM model describes the operation of the program without defining exactly how this functionality is achieved. This perspective allows an examination of useful change whilst excluding specific execution or requirements issues.

XXM are circumstances based model, they are really designed to be utilized by developers as a method to design their systems from at the very top level but here, XXM are used as effectively to investigate and incorporate changes in, even addition of new web services. Each model typically consists of a couple of states which match screens in the final system and functions which web page link the screens together. The functions are usually tagged with an permitting action such as "click_ok" which corresponds to a user clicking the OK button.

Figure depicts the structures of the WSCA. A couple of two key components and two encouraging components in this architecture. The main element components add a WSCA schema and a WSCA instance. The two supporting components include ontology providers and Web service providers.

WSCA schema: A WSCA schema includes a set of abstract services and the relationships among these services. An abstract service specifies one type of functionality provided by the net services. They are not bounded to any concrete services. They are simply defined in terms of service concepts in an online service ontology.

WSCA instance: A WSCA example is a structure of a set of concrete services, which instantiates a WSCA schema. It actually delivers the efficiency and performance of any WSCA.

Ontology providers: The ontology professional manages and keeps a set of ontologies that explain the semantics of Web services. A WSCA outsources semantics from an ontology professional to develop its schema.

Web service providers: The Web service providers provide a set of Web