Reusable Web Services

Henderson, Peter B.; Yang, Jingtao

doi:10.1007/978-3-540-27799-6_15

Cited by 7 publications

(3 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Most earlier service-oriented research [8][9][10][11][12] are centered on this approach. In some literatures, it is termed control-centric [13], programmatic approach [14] or RPC-style.…”

Section: Method-centric Approachmentioning

confidence: 99%

A Comparative Study of Interface Design Approaches for Service-Oriented Software

Teo

Kadir

2006

2006 13th Asia Pacific Software Engineering Conference (APSEC'06)

View full text Add to dashboard Cite

In the service-oriented software environment, interactions between components are highly dependent on the exposed service interfaces. Therefore, designing an appropriate service interface is essential. In this paper, we aim to perform a comparative evaluation on three different approaches to service interface design, i.e. method-centric, message-centric and resourcecentric. The evaluation is peformed systematically based on a list of selected evaluation criteria. It is expected that the evaluation results may assist software architects to understand the differences between approaches and adopt the approaches wisely in the service interface design.

show abstract

“…Most earlier service-oriented research [8][9][10][11][12] are centered on this approach. In some literatures, it is termed control-centric [13], programmatic approach [14] or RPC-style.…”

Section: Method-centric Approachmentioning

confidence: 99%

A Comparative Study of Interface Design Approaches for Service-Oriented Software

Teo

Kadir

2006

2006 13th Asia Pacific Software Engineering Conference (APSEC'06)

View full text Add to dashboard Cite

show abstract

“…In a previous paper [5], we investigated the requirements for dynamic configurations for service-oriented systems, and argued that long-running interactions are necessarily asynchronous. A notation for describing such systems, called the Document Flow Model (DFM), was also introduced in loc.…”

Section: Motivationmentioning

confidence: 99%

“…In the following example, we use a Coordination Service to maintain the state of an interaction over stateless web services. In a previous example [5], all the services participating in an interaction were able to access the state-maintaining component, ContextStore. In this example, the Coordination Service is the only service accessing the ContextStore.…”

Section: An Examplementioning

confidence: 99%

Document Flow Model: A Formal Notation for Modelling Asynchronous Web Services Composition

Yang

Cîrstea

Henderson

2005

On the Move to Meaningful Internet Systems 2005: OTM 2005 Workshops

Self Cite

View full text Add to dashboard Cite

This paper presents a formal notation for modelling asynchronous web services composition, using context and coordination mechanisms. Our notation specifies the messages that can be handled by different web services, and describes a system of interrelated web services as the flow of documents between them. The notation allows the typical web services composition pattern, asynchronous messaging, and has the capability to deal with long-running service-to-service interactions and dynamic configuration behaviors.

show abstract

An Approach to Managing Feature Dependencies for Product Releasing in Software Product Lines

Lee

Yang

Zhu

et al. 2006

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Reusable Web Services

Cited by 7 publications

References 4 publications

A Comparative Study of Interface Design Approaches for Service-Oriented Software

A Comparative Study of Interface Design Approaches for Service-Oriented Software

Document Flow Model: A Formal Notation for Modelling Asynchronous Web Services Composition

An Approach to Managing Feature Dependencies for Product Releasing in Software Product Lines

Contact Info

Product

Resources

About