Abstract

In a business atmosphere changes are ever occurring incidents which are supported by Information Technologies and there should be proper management techniques to handle these changes effectively. Also business processes must be aligned to IT to ensure the proper functionality of their services even after changes are propagated. Services might be moved, or relocated and may undergo changes during their life cycle. Hence there should be an effective framework for managing these changes without affecting the business functionality. This work stresses mainly on handling these dynamic changes to a business entity as it should support at business logic level and a new architecture model is proposed based on finite state machine theory of automata. It aligns IT with the business entity by automatically adapting the corresponding execution environment in case a change in the business process occurs.

Highlights

  • A web service is a piece of business logic that enables a paradigm shift in business structures allowing them to outsource required functionality from third party Web-based providers

  • To accommodate the changes to be done to the business logic of the web service, a user interface has been designed for business analysts where they can specify the changes and implement by themselves

  • 7.3 Status after Changes done Once changes such as addition of business rules, deletion or modification has been done, the business logic of the web service will be regenerated wherever the new statements or modified statements exist in the Business Logic (BL) Schema (Business logic schema)

Read more

Summary

INTRODUCTION

A web service is a piece of business logic that enables a paradigm shift in business structures allowing them to outsource required functionality from third party Web-based providers. There should be an effective framework for managing these changes without affecting the business functionality. If Web service is exposed to changes the Web service clients on the customer’s side is neither part of the upgraded piece of software nor of the IT environment which is being upgraded. This probably results in erroneous behaviour whose real cause is located somewhere in the system. If this is not possible consumers should be notified about upcoming changes in advance. We propose a framework for managing changes that are propagated during run time using FSM based theory of automata

RELATED WORKS
FRAMEWORK FOR MANAGING RUN-TIME CHANGES
MOTIVATING EXAMPLE
ATAM Process
Scenario Interaction Conflicts
BL Schema loaded for Airline reservation service editing
CONCLUSIONS
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call