Change Management in Semantic Web Services

channelise Management in Semantic mesh functionChange Management in Semantic weave expediencys in Legal Domain using FSM XXMIntroductionWith the b argon-assed paradigm of proceeds Oriented Computing, m some(prenominal) enterprises attempt to utilize avails as fundamental elements for developing applications/solutions as an affixitive degree on flower of alive components. The weather vane Service Controller Architecture (WSCA) for renovation-based, enterprise-scaled communication channel solutions appropriates on the button this flexibility. The design, exposure and worry of serve fecal matter be accomplished through a Service Oriented Architecture (SOA) that supports the usage, composition and coordination of dish of processs in a uncloudedly coupled way. Web usefulnesss appear to be incisionicularly suitable for addressing these aspects of a SOA. Furthermore, composition languages such(prenominal) as BPEL add value by composing Web dos and facilitating the implementation of wrinkle processes. As the SOA paradigm brings this big behavior replace relying on loose coupling of gos it raises new questions in the argona of flip management. Change management is a central aspect in any package system design, but its complexity for Web table wait ons is increased by twain composition languages and loose coupling. The resulting advantages like composability, autonomy, message-based communication, and the avoidance of combined compilation and spine prove to be deficiencies in this context.In this paper we discuss these simple(a) challenges of commute management in the area of Web services (Web Service Change Management, WSCM). Currently there are no sound mechanisms and plan principles for ever-changing Web services and their related entities. Through analysis of a suitable scenario, limitedally looking at the enlarge of the Web service put upr and consumer roles, one can identify the various problems that exist in this dom ain. Therefore we pass on start our approach with the consideration of an application scenario from the trading domain of application and change management, the addition of Web services in private legal sector.An Overview of a WSCAA WSCA consists of several autonomous outsourced Web services, but acts as a virtually coherent entity. Business entities, in the form of Web services, are often geographically distributed and organizationally indep ratiocinationent. turn WSCA has a potential to introduce new business opportunities through dynamic alliances, the challenges of fully realizing a WSCA lie in managing changes during its lifecycle through Extreme X Machines (XXM).XXMIn this paper we explore the design changes as made to parcel projects by the useof a formal model known as Extreme X-Machines (XXM) 5,6, whichare based on the work of Eilenberg and Holcombe 7,8. An XXM model learns the availableity of the software without defining exactly how this availableity is achieved. This perspective allows an analysis of functional change whilst excluding specific implementation or requirements shortens.XXM are a landed e assert based model, they are intended to be employ by developers as a method acting to designtheir systems from at the top level but here, XXM are used as effectively to analyze and incorporate changes in, even addition of new wind vane services. Each model typically consists of a set of states which barrack to screens in the final system and functions which link the screens together. The functions are typically label with an enabling action such as click_ok which corresponds to a user clicking the OK button.Figure depicts the architecture of a WSCA. There are two cay components and two supporting components in this architecture. The key components include a WSCA precis and a WSCA instance. The two supporting components include ontology providers and Web service providers. WSCA schema A WSCA schema consists of a set of raise services and the relationships among these services. An abstract service specifies one type of functionality provided by the Web services. They are non bounded to any concrete services. They are defined in legal injury of service concepts in a Web service ontology.WSCA instance A WSCA instance is a composition of a set of concrete services, which instantiates a WSCA schema. It actually delivers the functionality and performance of a WSCA. Ontology providers The ontology provider manages and maintains a set of ontologies that describe the semantics of Web services. A WSCA outsources semantics from an ontology provider to build up its schema. Web service providers The Web service providers offer a set of Web services, which can be outsourced to form WSCA instances.The lifecycle of a WSCA is a series of stages through which it passes from its blood line to its termination. There are four levels in a WSCA lifecycle initiation, composition, service-orchestration and termination. The initiati on phase is the first stage, where the WSCA is described at a high level. It is initiated when the owner of the WSCA establishes a need for a business objective 53.The composition phase hand outs with integrating the selected Web services 42. After this, the selected Web services are orchestrate to provide the value-added service. The termination phase travel bys when the owner of the WSCA decides that the execution of the WSCA is no longstanding required.To materialize the concept of WSCA, the WSCA must automatically adapt to its dynamic environment, i.e., to deal with changes during its life clock. Because of the dynamic nature of Web service infrastructure, changes should be considered as the detect and managed in a structured and systematic way 52. Changes whitethorn be introduced by the occurrence of new market interests, new business regulation, or underlying service availability. Such changes require a corresponding accommodation of the WSCA structure with respect to th e functionality it provides and the performance it delivers.Once a change occurs, a WSCA must react in a reasonable time and realign itself to deal with the change. This alignment must be performed in an automatic manner considering the frequent occurrence of the changes to a WSCA. By doing this, the WSCA can not and deal with unanticipated changes to the underlying services and infrastructure, but also increase its market value, optimize functionality outsourcing, and maintain competitiveness.Problem FormulationThe problem with the existing system of legal decision qualification process is thatThere is no universal coalition body to unite the various modules of law in private sector likeA Public Interface to enquiry for a upshotOnline allotment of Advocates to usersJudgmentsUnion of India (to export Central Acts and Amendments) responsibility Acts (to export State Acts and Amendments)The whole system of legal enactment offset from user query, allotment of Advocate, and give earring fantasys is not under a single roof.imputable to inadequacy of getting the a la mode(p) and updated Acts or Amendments, roughlytimes old acts are cited which later cause problems when the geek is taken up in courts. This is a cause of embarrassment to the lawyer.In the existing System there is no spontaneous notification to the legal bodies regarding a change in the Acts. They themselves put one over to search for it on internet or find them in the in style(p) issues. The problem is that they are not notified about the change in Acts automatically.Proposed firmnessThe need is to have an automated Legal System in India, at least at the private level. And this automation should be done with the well-nigh contemporary and best suited group of technologies. The problem uncovers the major issue of incapability of notification of changed Acts or Amendments to the related bodies.The proposed WSCA model videlicet LegalCosmos functions to provide a comprehensive Legal Soluti on that outsources the functionality from various service providers, such as WS_IndianUnionAmmendments, WS_StateActAmmendments, WS_PublicInterface, WS_AdvocateAssociation, WS_Judgments (depicted in Figure 1.2).The user in need of a legal solution makes use of the web service WS_PublicInterface and submits his, here accused, expound and the details of the FIR filed by the complainant and forwards the FIR details like Case Crime No, Name, crime, date etc., to the WSCA which allots a Lawyer for the case with the help of WS_AdvocatesAssociation. An interested user (may be lawyer or a normal user) can find the details of the judgments through the WS_Judgments service. When a judgment is made the WS_Judgment web service provides the user with the copy of the order of the judgment.When these services are combined together as a WSCA, the WSCA will chew out the services on behalf of the user. There may potentially be some dependency relationship between them. These dependencies determine t he composition of the services. In the case of the LegalCosmos WSCA,users do not necessarily need to provide the information for distributively service. The input of some services can be derived from the dependency relationship. bid in WS_AdvocateAssociation selected advocate details are directly passed to the WS-Judgments.Fig. Change response for adding two new web services WS_UnionOfIndia, WS_StateActsWSCA Schema using exhaustible State MachineDefinition FSMis a mathematicalmodel of tallyused to design bothcomputer programsandsequential logiccircuits. It is conceived as anabstract machinethat can be in one of a finite number ofstates. The machine is in only one state at a time the state it is in at any given time is called thecurrent state. It can change from one state to another when initiated by a triggering event or condition this is called a passage. A particular FSM is defined by a list of its states, and the triggering condition for all(prenominal) transition.Fig. WSCA Schema (A simple XXM)Change Management in LegalCosmosThe change management in the proposed LegalCosmos WSCA primarily deals with the change in Acts in the form of Amendments. This change origins from the addition of two web services provided by the Union of India that produces amendments at the central level and the State Acts that produces amendments at the State level. Since these changes are initiated by the outsourced service providers and incorporate an alteration in web service. They form the part of bottom up changes.The bottom-up approach for managing changes is highly dependent on the services that compose the WSCA. Therefore, it is necessary to first define the changes that occur to Web services, and then map them onto the business level. These changes include Activation changes that occur at the service level and WSCA changes that are executed at the business level. Finally, we provide rules for mapping triggering changes to their respective reactive changes.In our work, we assume that activation changes occur asynchronously. For instance, the WS_PublicInterface service may not change its data types eyepatch the activation change of unavailability is being managed. Another assumption we make is that the service is associated with a set of states. We associate each change with a transition between two states precondition and postcondition.For example, a precondition for PIs unavailability is that it was previously available and the postcondition is that it has become unavailable. Activation changes and their respective preconditions and postconditions will later be used to model changes using FSM and XXM.Fig. Activation ChangesNon-Functional ChangesNon-functional changes counterbalance the dependableness, usability, and trust associated with a extremity service. This information may be stored by a third party, the WSCA, or fraction services. We assume the information is stored as attributes that are maintained by an independent third party ser vice provider. Changes to the trustworthiness of a Web service relate to the security, reputation, and privacy of a Web service. Changes in usability are dependent on the responsiveness and service cost. Finally, changes to dependability are associated with the availability and reliability of the Web service. Changes to service dependability are binary, because they represent two distinct states. For example, a service may either be available or unavailable. Alternatively, changes to service trust and usability are non-binary. Forinstance, service cost may assume more than two set during a phallus services lifetime. Therefore, we assume that a sceptre is set and maintained by the WSCA. This threshold declares the minimum and supreme intervals of a value accepted by the WSCA. For example, the WSCA has the threshold of minimum $5 and maximum $10 for any judgment service cost. Every time a change occurs to the cost of a member judgment service, it is compared with the threshold. On ly if the change exceeds the threshold, we consider that a triggering change has occurred. Note that the changes we have defined, such as changes to availability, are applicable to member services only. Once a member service is replaced, it is no longer part of the change management mechanism. For example, the e-Acts member service EA1 may become unavailable, and prompt the WSCA LegalCosmos to select an alternate e-Acts service EA2. After some time, EA1 may become available. However, since it is no longer a part of the LegalCosmos LCS, the LegalCosmos WSCA does not manage the change in EA1. Table 6.1.1.1 summarizes the non-functional changes in Web services.Non-Functional ChangesFig. Non-Functional ChangesFunctional ChangesUnlike non-functional changes, which are based on attributes, functional changes deal with changes to a services WSDL description 22. We represent functional changes as a combined execution of a remove followed by an add. We further classify functional changes int o structural and behavioral changes (Figure 6.1). Structural changes refer to the operational aspects of a Web service. For example, a structural change in a PI service can be caused by changing the operations offered to a user. Changes to the behavior of a Web service are indicated by changing its interaction with external entities. Functional changes to a member Web service occur when its WSDL description is modified. We assume these changes are initiated by the service provider.Fig. Functional ChangesXXM for Existing LegalCosmos WSCA, when Functional Changes are not introduced (before the removal of e-Acts web service)The key functional changes involved here are removal of e-Acts web service (E-Copy of acts) shown in dashed rectangle. It has to be removed as it gives only immutable acts and does not involve latest amendments done by the Bare Acts. This causes problems to the WSCA in maintaining latest updates of the amendments and sometimes leads to false application of acts.A n ew web service called WS_UnionOfIndia is added to the WSCA which supplies the latest acts and amendments to WSCA. The Union of India is responsible for making and amending acts on the Central level.A new web service called WS_StateActs is added to the WSCA which supplies the latest acts and amendments to WSCA. The State Acts is responsible for making and amending acts on the State level.XXM for WSCA when Functional Changes are introduced (after the removal of e-Acts web service and addition of two new web services, WS_UnionOfIndia and WS_StateActs)Fig.The above figure shows the two newly added web services namely WS_UnionOfIndia and WS_StateActs.WSCA ChangesEach activation change will initiate a WSCA change at the business layer. WSCA changes may occur at the composition and service orchestration levels of a WSCA. For instance, a Dt change in the PI service may trigger inconsistencies in the WSCA composition, such as incorrect controversy data types. Alternatively, a Da change may disrupt WSCA service orchestration. We divide the WSCA changes into composition and service orchestration.Fig. WSCA Changes at business level subprogram of ChangesA mapping specifies how changes in one layer correspond to changes in another layer 86. These mappings must remain consistent in the front end of frequent changes. When a change occurs at the service level, the business layer must react to manage the changes. Triggering changes have a reactive touch on the business layer of the WSCA.Our approach of mapping changes is based on mapping rules. These rules are based on the activation changes and their corresponding business level changes of WSCA. Some changes may have more than one rule associated with them. The rules are depicted in the matrix shown belowNon-Functional Changes Functional Changes spying of Activation Services Changes algorithmic rule 1 Change Detection Algorithm1 ChangeDetection (Input oldDesc, newDesc)2 while newDesc do3 Compare (oldDescFunctional, newDesc Functional)4 if oldDescFunctional= newDescFunctional then5 GenerateXXM (FunctionalXXM)6 end if7 Compare (oldDescNonFunctional, newDescNonFunctional)8 if oldDescNonFunctional = newDescNonFunctional then9 Threshold = CheckThreshold (oldDesc, newDesc)10 if Threshold then11 GenerateFSM(NonFunctionalFSM)12 end if13 end if14 end while15 ChangeReaction (FunctionalXXM, NonFunctionalFSM)Algorithm 2 Change Reaction Algorithm1 ChangeReaction (Input FunctionalXXM, NonFunctionalFSM)2 WSCAXXM = 3 while FunctionalXXM do4 WSCAXXM = Map (FunctionalXXM, WSCAXXM)5 end while6 while (NonFunctionalFSM) do7 WSCAXXM = Map (NonFunctionalFSM, WSCAXXM)8 end while9 while (NonFunctionalFSM) do10 if (WSCAXXM) then11 Execute (WSCAXXM)12 end if13 end whileAlgorithm 13 Change Management Algorithm1 ChangeManagement (Input executionTime, WSCA concrete service list)2 time = executionTime3 while time = 0 do4 for all each Web Service WSi in WSCA concrete service list do5 manoeuver alive message to WSi6 if not alive the n7 remove WSi from WSCA concrete service list8 call (serviceSelection (abstractService (WSi)))9 break10 end if11 globalDescription = WSi servicedescription from Registry12 if serviceDescription (WSi) not equals globalDescription then13 remove WSi from WSCA concre