Web service interfaces

Beyer, Dirk; Chakrabarti, Arindam; Henzinger, Thomas A.

doi:10.1145/1060745.1060770

Cited by 100 publications

(64 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Thus, we consider order dependencies between messages but we do not look into the schema of these messages. Accordingly, we model the behaviour of a web service interface using Finite State Machines (FSM [5,16]). Our choice of FSMs is motivated by the following reasons:…”

Section: Modelling Behavioural Dimension Of Service Interfacesmentioning

confidence: 99%

See 1 more Smart Citation

Diagnosing and Measuring Incompatibilities between Pairs of Services

Aït-Bachir

Fauvet

2009

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. This text presents a tool, from its design to its implementation, which detects all behavioural incompatibilities between two service interfaces. Unlike prior work, the proposed solution does not simply check whether two services are incompatible or not, it rather provides detailed diagnosis, including the incompatibilities and for each one the location in the service interfaces where these incompatibilities occur. A measure of similarity between interfaces which considers outputs from the detection algorithm is proposed too. A visual report of the comparison analysis is also provided which pinpoints a set of incompatibilities that cause a behavioural interface not to simulate another one.

show abstract

Section: Modelling Behavioural Dimension Of Service Interfacesmentioning

confidence: 99%

“…Following [5,14], we adopt a simple yet effective approach to model service interface behaviour using Finite State Machines (FSMs). In the FSMs we consider, transitions are labelled with messages (to be sent or received).…”

Section: Modelling Behavioural Dimension Of Service Interfacesmentioning

confidence: 99%

Diagnosing and Measuring Incompatibilities between Pairs of Services

Aït-Bachir

Fauvet

2009

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…A different approach is proposed in [6] where compatibility is tested over the interfaces of services (not their implementations), which is simpler and more likely to be effective because a good interface should hide (complex) information that is not relevant for compatibility. A limitation of this approach is that it is based on a (synchronous) method-invocation model of interaction: as argued in [13], web-service composition languages such BPEL (the Business Process Execution Language [20]) rely on an (asynchronous) message-passing model, which is more adequate for interactions that need to run in a loosely-coupled operating environment.…”

Section: Introductionmentioning

confidence: 99%

“…In this respect, the notions of interface that are proposed in [6] do not clearly separate between interfaces for clients of the service and interfaces for providers of required external services, i.e., the approach is not formulated in the context of run-time service discovery and binding. Furthermore, [6] does not propose a model of composition of implementations (what is called a component algebra in [8]) so one has to assume that implementations of services with compatible interfaces, when composed, are 'consistent'.…”

Section: Introductionmentioning

confidence: 99%

Consistency of Service Composition

Fiadeiro

Lopes

2012

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. We address the problem of ensuring that, when an application executing a service binds to a service that matches required functional properties, both the application and the service can work together, i.e., their composition is consistent. Our approach is based on a component algebra for service-oriented computing in which the configurations of applications and of services are modelled as asynchronous relational nets typed with logical interfaces. The techniques that we propose allow for the consistency of composition to be guaranteed based on properties of service orchestrations (implementations) and interfaces that can be checked at design time, which is essential for supporting the levels of dynamicity required by run-time service binding.

show abstract

“…The SPIN model-checker is used for the behavior verification of the asynchronously communicating peers (bounded message queues). A language for specifying web service interfaces is presented in [38]. None of the above techniques uses automated abstraction-based verification and, thus, are less competitive in verification of large-scale web systems.…”

mentioning

confidence: 99%

Model Checking with Abstraction for Web Services

Sharygina

Kröning

Test and Analysis of Web Services

View full text Add to dashboard Cite

Abstract. Web services are highly distributed programs and, thus, are prone to concurrency-related errors. Model checking is a powerful technique to identify flaws in concurrent systems. However, the existing model checkers have only very limited support for the programming languages and communication mechanisms used by typical implementations of web services. This chapter presents a formalization of communication semantics geared for web services, and an automated way to extract formal models from programs implementing web services for automatic formal analysis. The formal models are analyzed by means of a symbolic model checker that implements automatic abstraction refinement. Our implementation takes one or more PHP5 programs as input, and is able to verify joint properties of these programs running concurrently. IntroductionWeb services are instantiations of service-oriented architectures, where a service is a function that is well defined, self-contained and does not depend on the context or state of other services [1]. They are designed to be published, accessed and used via intranet or Internet. The elements of the design are (1) a service provider, which offers some service; (2) a service broker who maintains a catalog of available services; and (3) service requesters which seek for a service from the service broker, and then attach to the service provider by composing the offered services with its own components. A web service offers an arbitrary complex functionality, which is described in a global system structure. Examples of web services include information systems such as map or travel services, e-commerce systems such as web shops, travel agencies, stock brokers, etc. Clearly, it is essential to enforce security and safety requirements in the development of such systems.Web services are typically implemented in a very distributed manner and, thus, are prone to errors caused by the distribution. They often involve multiple parties. As an example, consider an online shop that accepts charges to a credit card as form of payment. The parties involved are the users or 122 N. Sharygina and D. Kröning customers, the vendor itself, and back-office service providers, e.g., the payment clearing service. The authorization of the payment is given by a service company for credit card transactions, whereas the "shopping basket" and warehousing are implemented by the vendor. It is easy to imagine another party involved in a transaction, e.g., a company that performs the actual shipment.Each party typically employs a large set of machines for the purpose of load sharing. The safety and security requirements are often global, i.e., require reasoning about multiple parties and may involve more than one server at each party.A typical scenario is depicted in Fig. 5.1. A merchant is operating three hosts (e.g., for redundancy or load-balancing reasons). Two of these hosts ('Host 1' and 'Host 2') are used to run a web server, e.g., Apache. The web server itself is split up into multiple processes, T 1 , . . . , T 4 . T...

show abstract

Web service interfaces

Cited by 100 publications

References 20 publications

Diagnosing and Measuring Incompatibilities between Pairs of Services

Diagnosing and Measuring Incompatibilities between Pairs of Services

Consistency of Service Composition

Model Checking with Abstraction for Web Services

Contact Info

Product

Resources

About