Evaluation Model for Web Service Change Management



Abstract-Today organizations in all industries are ever more dependent after IT and an extremely available network to meet their business objectives. As customer prospects and demands surge, and their needs is one of the prevailing problems encountered because of it enterprises at present, leading to increasingly intricate IT service management systems. Although there exists many change management issues and solutions, there is no proper support for successful change evaluation and monitoring. Present change management works are done only in the net service software such as WSDL Web Service Definition Language and there is no proper support for dynamic character in them. In order to provide a flexible environment for the business enterprise Analyst to execute the emergency changes within the service business reasoning without the need of IT personnel and to examine changes made, we propose a Finite Status Machine based Analysis Model for Web Service Runtime Change Management and also a set of change factors to evaluate runtime changes of web services. Among which we mainly give attention to the factor Business Coverage Enforcement which is used for checking whether there is certainly any insurance policy violation with respect to the changes made. We first determine the many change factors and produced solution is recognized as the change solution for individual change factor.

Keywords-Web Services, BL Analyzer, Dependency Analyzer, Change Factors, Business Coverage Supervisor, Runtime Change Management, Change Evaluation Report.


A web service is a piece of business logic that permits a paradigm move in business set ups permitting them to outsource required functionality from alternative party Web-based providers. As services aren't static, they undergo many changes throughout their life cycle because the IT service management system now is facing an extremely complex environment aroused by wide variety of requirements. This situation increases the probability of service interruption which causes business reduction. In cases like this, some changes are needed so that potential service interruptions can be averted. Something change is any addition, changes, or removal of approved, planned, or backed service or service part and its associated documentation. An average IT enterprise encounters considerable variety of changes each year. To take care of such changes, change management is necessary.

Change management is a couple of processes that are used to ensure that significant changes are put in place to a company process during its maintenance period. The purpose of the change management process is to ensure that: Business risk is managed and reduced; Standardized methods and techniques are used for reliable and prompt handling of all changes; all changes to service investments and settings items are documented in the settings management system; and all authorized changes support business needs and goals. Hence there arises the necessity for an efficient framework managing those changes without impacting on the business features. Here Change Management framework is proposed to make minor alterations to business logic but whose result is more pronounced to the success of the organization. Therefore the changes in business logic of the net service must be achieved very quickly within the given time constraint as the assistance consumed by the providers and clients must not be afflicted there by handling the changes at the runtime.

We give attention to creating environment for strong variations to the business enterprise logic such that it is possible to make regular modifications in something which aids provider and serves him to gratify clients' newfangled quests. Such environment is useful in the run-time management of web services also to exactly spot the perfect solution is to the service provider's maintenance element. There are numerous models that subsist for Business Process Management in which the process is recycled for the overall process changes. However, the situation with these solutions is that they only support the process level flexibility and not the application/service level versatility. On the other hand this Business Reasoning Management framework tries to append that service level flexibility. These changes are done at the Business analyst level rather than being done at the Developer level, which reduces the hierarchy level in change management and so implies a reduction in time and cost requirements.

A specific change in the reasoning, not only changes the operation concerned with it, but also the based mostly functions under the dependency group. Within the logic level, the set of guidelines form the finite says with functions as transitions. A rule is said to be reliant in this model, when there is a transition in one rule to another on receiving a function. The level of dependency analysis can be even long to the functions where in fact the parameters become the transition in one function to some other. Thus the rules and functions under logic form a dependency group which is examined and verified for each change initiated externally. Those dependency organizations assist in doing changes and brings about a highly effective change. Those changes that are made predicated on the dependency examination are measurable, complete and finite. Any change that is not based on the dependency examination is said to violate the discussed properties and may result in failing. Dependency analysis based on each factor is performed by the finite point out machine. By using finite express machine, it is possible that if a particular reasoning has been efficiently accepted then it would go to the halt condition. Alternatively, there exists a change from any point out to the exclusion status E, if the guideline or function encounters a fantastic type or parameter. By this way, the FSM simulates the pattern predicated on the action of the guidelines and functions, that can be easily verified and measured at each stage. This measure of change evaluation ensures that the business enterprise analyst has a direct control over the changes he makes and provides an environment that notifies the analyst about the outcome in a important way. We propose a couple of five change factors based on that your dependency existing between your business guidelines, functions and guidelines is examined. Among which we mainly focus on the factor Business Insurance plan Enforcement which is employed for checking out whether you can find any policy violation with regards to the changes made. These change factors are also involved in the change evaluation which makes the changes to be specified in an accurate and formal manner.


In this construction, the plan of action begins with problem of change request and the whole control of the get is conducted under the guidance of your analyst. A ChangeRequest can be an 'additional' expectation that theCustomerwants which is outside the current defined scope of the job which really is a change to an existing product. It really is first given by the analyst at length. This standards includes the change to be produced, brief explanation of the change to be produced, action to be produced, services, rules and the conditions under that your change must be made. The Question handler is in charge of finding the kind of the change and priority is assigned to point the order of importance of the demand and also establishes if the change can be put in place within the runtime. Site Variable Identifier discovers the website variables present in the request by simply tokenizing the question and looking whether any of tokens match against given domain variable set. After we are done with domain variable identification, we can determine the area to that your request identifies. The Domain Mapper discovers the corresponding website and services by making use of service repository which comprises a myriad of services and the effect to Business Reasoning Analyzer.

Fig1. Business insurance plan enforcement framework

The logic of all services in the service repository are decomposed into guidelines, functions and parameters along with associated business insurance policies are stored in the BL set in place with help of domain mapping. The BL analyzer identifies only the particular rule, functions, parameter and plan associated with it for every change require from BL place instead providing all the rules, functions, variables and regulations associated with it. The properties of interoperability, traceability, decidability, computability are maintained even after the alteration. These properties are assessed by property evaluator and the calculated properties are appended to the schema to create the ultimate schema. The house values assist the analyst to make a decision if to apply the alteration. Dependency Analyzer discovers dependencies with the ascertained guidelines and functions available logic through the discovered change requirements. The Policy Supervisor checks for policy violation in the guideline or function where change needs to be made and also in the dependent rules or functions. Since the change which is complete, finite and computable may also violate the associated insurance policies, it is also checked out by the insurance policy manager after evaluating the properties of the recognized change. Schema Generator is in charge of making and upholding BL schema at various periods. This BL schema is helpful in guiding the management folks who are not familiar in source code to make successful changes. The changes made in the schema will be kept up to date obviously in business logic. Same manner, when developers do some changes in logic, it gets updated in schema accurately. Run time manager is accountable for building and deploying the assistance after fruitful changes are done and and yes it helps to debug the exceptions in the service reasoning sophistically. Change evaluator evaluates the changes made by the analyst based on the change factors such as business coverage enforcement which can determine violation of policy in the discovered change criteria, code uniformity which checks whether the preconditions and post conditions remains frequent with regards to the changes made, essential measure which checks whether the requisite rule or function is not changed with regards to the changes made and mapping function which checks the consistency with respect to the logic and also on the non-functional factors such as service interruption time, response time, trustworthiness and service availability. The Change Evaluation Report includes result of the evaluation procedure for the change made i. e. the analysis procedures of the changes made by the analyst. By this platform, the analyst gets the advantages such versatility, works in a sophisticated environment without having much understanding of source code since they can put into action the changes at the schema level, knowledge copy since they can do the changes whatever comes in mind directly and can evaluate it easily, independency since no need for depending on development team therefore reducing enough time and cost.


Change factors are those that act as a criteria based on which the changes made can be evaluated. Any change available reasoning is governed by the following change factors. These factors influence changes either separately or in a group and make changes effective. And the change factors are the following
  • Business insurance plan enforcement
  • Requisite measure
  • Code consistency
  • Mapping function

A. Business Insurance plan Enforcement

In this newspaper, we mainly focus on the change factor business insurance policy enforcement which really is a way of measuring change which can determine violation of insurance plan in the identified change criteria. Here the primary role of business coverage enforcement is: coverage mapping which is only locating the appropriate policies which are associated with the rule or function where the change needs to be made and also with its dependent guidelines and functions; validation which pertains checking whether there is any insurance plan violation; and refinement which gives a host for the analyst to modify the coverage itself if necessary. In a very business logic L encompassing group of guidelines R, functions F, variables Pr, policy set in place P and dependency D, the change which is likely to be made can be examined based on the business plan enforcement factor which bank checks whether there exists any insurance plan violation with respect to the changes made. Whenever a change is specified, it is first analyzed for completeness, finiteness and computable. Once the guidelines, functions and guidelines in the change features are examined as complete, they may be mapped with the prevailing logic established L. Then your corresponding rules, functions, parameters, dependency collection and policy set in place are retrieved by which the change standards is examined whether it violates any insurance plan. If so, the analyst is informed as the change cannot be made because of the violation of policy. Normally the change is efficiently included in the existing logic place L.


The table within the next site shows the analysis results of some of the change requests implemented based on the business plan enforcement.



Change Request

Business Rule

Business Policy

Evaluation Result

Policy Partially Denied

Policy Completely Denied

Policy Accepted

Customers with armed service as occupation would like to do deal at any time till null balance for all his/her accounts

For all customers except customers with occupation as military, Minimal balance = 500

Customers with armed forces as job can be permitted to do transaction till null balance for only one account.




Any person in joint bill can remove the other persons posting the joint account at any time without their authorization and can create another account.

Two or more persons can share a joint accounts (i. e. several persons can have the same accounts name)

A person in joint bill can take away the extra person without his/ her authorization if the former is the only real owner.




Request to improve the minimum balance for all your accountholders

For all customers except customers with profession as military services,

Minimum balance = 400

Military accountholders must have minimum amount balance as null




Changing the utmost amount that may be moved between two accounts per day

Maximum amount moved should be 20000 per day

Maximum amount transferred should be greater than minimum balance.




certain amount of taxes must be put into all varieties of loans

tax ratio provided for each and every kind of loans

No tax must be payed for educational loans




V. Conclusion

Any company no subject its size will experience a sizable volume of changes in order to accommodate new business requirements, to correct faults in the infrastructure or the services, or for other reasons (such as legal requirements). This construction provides an environment for the business analyst to apply the changes at the advanced environment with no much understanding of the foundation code and measure the changes easily predicated on the proposed change factors where business coverage enforcement is principally focused. With the help of the algorithm produced for the business enterprise plan enforcement, a case study of banking domains is carried out. By this framework, analyst is able to implement whatever will come in his mind immediately without the help of producing team and to detect insurance plan violation and do the changes appropriately and also to refine the coverage itself if needed.


[1] Felix Cuadrado, Juan C. Duenas and Rodrigo Garc±ґa-Carmona, "An Autonomous Engine unit forServicesConfiguration and Deployment, " IEEE Trades on Software Engineering, Vol. 38, No. 3, May/June 2012.

[2] Xumin Liu, Athman Bouguettaya, Jemma Wu, and Li Zhou, "Ev-Lcs: SOMETHING For The Advancement Of Long-Term Composed Services, " IEEE Deals on Services Computing, Vol. PP, Concern 99, 2011.

[3] Dimitris Apostolou, Gregoris Mentzas, Ljiljana Stojanovic, Barbara Thoenssen, Toms Pariente Lobo, "A collaborative decision framework for taking care of changes in e-Government services, " Federal government Information Quarterly 28 (2011) 101-116, PUBLISHED @ ELSEVIER, 2011.

[4] Bruno Wassermann, Heiko Ludwig, Jim Laredo, Kamal Bhattacharya, Liliana Pasquale, "Distributed Cross-Domain Change Management, " 2009 IEEE International Seminar on Web, Services, 978-0-7695-3709-2/09, 2009 IEEE.

[5] Bassam Atieh Rajabi, Sai Peck Lee, "Change Management running a business Process Modeling Survey", 2009 International Seminar on Information Management and Engineering, 978-0-7695-1/09, 2009 IEEE.

[6] Bassam Atieh Rajabi, Sai Peck Lee, "Runtime Change Management Based on Object Oriented Petri Net, " 2009 International Seminar on Information Management and Executive, 978-0-7695-1/09, 2009 IEEE.

[7] Oliver Moser, Florian Rosenberg and Schahram Dustdar, "Domain-Specific Service Selection for Composite Services, " IEEE Deals on Software Engineering, VOL. 38, NO. 4, July/Aug. 2012

[8] Ruhi Sarikaya, Canturk Isci and Alper Buyuktosunoglu, "Runtime Software Behavior Prediction Utilizing a Statistical Metric Model, " IEEE Transactions on Computer systems, Vol. X, No. X, May 2011.

[9] Haochen Li, Zhiqiang Zhan, "Bussiness-Driven Automatic IT Change Management Based on Machine Learning, " 978-1-4673-0269-2/12, 2012 IEEE.

[10] Yanhua Du, Xitong Li, and PengCheng Xiong, "Petri Online Method of Mediation-Aided Composition of Web Services, " IEEE Tansactions on Automation Science and Anatomist, Vol. 9, No. 2, Apr. 2012.

[11] Marcello La Rosa, Arthur H. M. ter Hofstede, Petia Wohed, Hajo A. Reijers, Jan Mendling, and Wil M. P. truck der Aalst, "Managing Process Model Complexity via Concrete Syntax Changes, " IEEE Transactions on Industrial Informatics, Vol. 7, No. 2, May 2011.

Also We Can Offer!

Other services that we offer

If you don’t see the necessary subject, paper type, or topic in our list of available services and examples, don’t worry! We have a number of other academic disciplines to suit the needs of anyone who visits this website looking for help.

How to ...

We made your life easier with putting together a big number of articles and guidelines on how to plan and write different types of assignments (Essay, Research Paper, Dissertation etc)