Web Services Overview

McGovern, James; Tyagi, Sameer; Stevens, Michael E.; Mathew, Sunil

doi:10.1016/b978-155860900-6/50004-x

Cited by 49 publications

(21 citation statements)

References 1 publication

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…SAML provides a standard, XML-based format to exchange security information between different security agents over the Internet. It allows services to exchange authentication, authorization, and attribute information without organizations and their partners having to modify their current security solutions [3]. XACML complements SAML by providing a language to specify role-based, access control rules in a declarative format.…”

Section: Securitymentioning

confidence: 99%

See 1 more Smart Citation

Quality Attributes for Service-Oriented Architectures

O’Brien

Merson

Bass

2007

International Workshop on Systems Development in SOA Environments (SDSOA'07: ICSE Workshops 2007)

126

View full text Add to dashboard Cite

show abstract

Section: Securitymentioning

confidence: 99%

“…That is possible because Web services define the interface format and communication protocols but do not restrict the implementation language or platform. Other SOA technologies-such as Jini and CORBAhave not yet produced enough of a following to become a universal standard for interoperability [3].…”

Section: Interoperabilitymentioning

confidence: 99%

Quality Attributes for Service-Oriented Architectures

O’Brien

Merson

Bass

2007

International Workshop on Systems Development in SOA Environments (SDSOA'07: ICSE Workshops 2007)

126

View full text Add to dashboard Cite

show abstract

“…To make use of the service, if the service consumer requests more information about the provider, the extent of coupling will be increased between them [2]. To gain a better appreciation of the extent to which coupling can become part of service design, we need to take a look at the common types of relationships that need to be created within and outside of the service boundary [3].…”

Section: Introductionmentioning

confidence: 99%

A metrics suite and fuzzy model for measuring coupling in Service Oriented Architecture

Karhikeyan¹,

Geetha

2012

2012 International Conference on Recent Advances in Computing and Software Systems

View full text Add to dashboard Cite

The paper proposes a suite of metrics for measuring coupling in service oriented architecture. The principle characteristic of Service Oriented Architecture is loose coupling. Coupling means that the existence and the extent of dependency between modules, components, or services consumers and providers. The coupling is an important aspect in the evaluation of reusability of components or services. In this paper we propose a suite of metrics for measuring the degree of coupling in services at the design phase. The dependencies between services cause coupling. Many coupling metrics have already been proposed but it is recognised that the dependencies they considered for measuring coupling are insufficient. This paper takes five kinds of dependencies viz. direct dependency, indirect dependency, IO dependency, and State dependency and Delayed Message dependency to evaluate the degree of coupling in a service. The paper also proposes a fuzzy logic model to measure the degree of coupling due to these dependencies.

show abstract

“…Unlike traditional transactions, web service transactions are usually complex, involve multiple parties, spanning over many organizations, and may last over a relatively long time [9]. Various advanced transaction models and architectures for web services have been proposed [40], and their middleware support [41]. An overview of service transaction behaviors is offered in [42], which is a superset of those used in this paper as requirements.…”

Section: Web Service Transactionsmentioning

confidence: 99%

Transaction Management in Service-Oriented Systems: Requirements and a Proposal

Sun

Khoury²,

Aiello³

2011

IEEE Trans. Serv. Comput.

View full text Add to dashboard Cite

Abstract-Service-Oriented Computing (SOC) is becoming the mainstream development paradigm of applications over the Internet, taking advantage of remote independent functionalities. The cornerstone of SOC's success lies in the potential advantage of composing services on the fly. When the control over the communication and the elements of the information system is low, developing solid systems is challenging. In particular, developing reliable web service compositions usually requires the integration of both composition languages, such as the Business Process Execution Language (BPEL), and of coordination protocols, such as WSAtomicTransaction and WS-BusinessActivity. Unfortunately, the composition and coordination of web services currently have separate languages and specifications. The goal of this paper is twofold. First, we identify the major requirements of transaction management in Service-oriented systems and survey the relevant standards. Second, we propose a semiautomatic approach to integrate BPEL specifications and web service coordination protocols, that is, implementing transaction management within service composition processes, and thus overcoming the limitations of current technologies.

show abstract

Web Services Overview

Cited by 49 publications

References 1 publication

Quality Attributes for Service-Oriented Architectures

Quality Attributes for Service-Oriented Architectures

A metrics suite and fuzzy model for measuring coupling in Service Oriented Architecture

Transaction Management in Service-Oriented Systems: Requirements and a Proposal

Contact Info

Product

Resources

About