2010 Fifth International Conference on Internet and Web Applications and Services 2010
DOI: 10.1109/iciw.2010.71
|View full text |Cite
|
Sign up to set email alerts
|

Top-Down Approach for Web Services Development

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
3
0
1

Year Published

2010
2010
2017
2017

Publication Types

Select...
3
3

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(4 citation statements)
references
References 4 publications
0
3
0
1
Order By: Relevance
“…This means that orchestration and choreography can be considered as two templates for coordination scenarios that manage sequence dependencies. Several researches define orchestration as a service composition in which a central coordinator -sometimes also referred to as the orchestrator (Busi, Gorrieri, Guidi, Lucchi & Zavattaro, 2005;Tabatabaei, Kadir & Ibrahim, 2008;ter Beek, Bucchiarone & Gnesi, 2006), the controller (Barker, Weissman & Hemert, 2009) or the choreographer (Mitra, Kumar & Basu, 2008) is responsible for coordinating the business process execution by invoking all component services in the right order (Busi et al, 2005;Barker et al, 2009;Tabatabaei et al, 2008;Malinova & Gocheva-Ilieva, 2008;ter Beek et al, 2006;Bellini, Prado & Zaina, 2010). This coordinator can be either one of the component services or another service (e.g.…”
Section: Orchestration and Choreography As Composition Stylesmentioning
confidence: 99%
See 1 more Smart Citation
“…This means that orchestration and choreography can be considered as two templates for coordination scenarios that manage sequence dependencies. Several researches define orchestration as a service composition in which a central coordinator -sometimes also referred to as the orchestrator (Busi, Gorrieri, Guidi, Lucchi & Zavattaro, 2005;Tabatabaei, Kadir & Ibrahim, 2008;ter Beek, Bucchiarone & Gnesi, 2006), the controller (Barker, Weissman & Hemert, 2009) or the choreographer (Mitra, Kumar & Basu, 2008) is responsible for coordinating the business process execution by invoking all component services in the right order (Busi et al, 2005;Barker et al, 2009;Tabatabaei et al, 2008;Malinova & Gocheva-Ilieva, 2008;ter Beek et al, 2006;Bellini, Prado & Zaina, 2010). This coordinator can be either one of the component services or another service (e.g.…”
Section: Orchestration and Choreography As Composition Stylesmentioning
confidence: 99%
“…In a choreography the component services are rather collaborating together. The business process is executed and coordinated by several peer-to-peer interactions among the collaborating services (Busi et al, 2005;Barker et al, 2009;Tabatabaei et al, 2008;Malinova & Gocheva-Ilieva, 2008;ter Beek et al, 2006;Bellini et al, 2010). The component services directly communicate with each other, and not through a central coordinator (Pedraza & Estublier, 2009;Pessoa et al, 2008).…”
Section: Orchestration and Choreography As Composition Stylesmentioning
confidence: 99%
“…While reviewing several previous studies concerning the field of Web Services, obviously it was necessary for all researchers to mention several main concepts, such as XML, UML, SOAP, XSD and also WSDL [13], which in turn are used to perform selections, descriptions, discovery, composition, and interaction with the Web Services [14]. All researches attempted to built a bridge between the Web Services providers and Web Services requesters to reach better comprehension for Web Service functionality from the Web Service requester to increase the exchangeability of information between heterogeneous applications.…”
Section: A Overviewmentioning
confidence: 99%
“…Assim, após o desenvolvimento desse novo levantamento bibliográfico, notou-se a existência de poucos trabalhos que propunham a geração automática de serviços a partir de modelos abstratos (KENZI et al, 2009;BENDER;BOZIC;KONDOV, 2014;BELLINI;PRADO;ZAINA, 2010). Notou-se também durante esse levantamento e durante a elaboração da AIRES que as principais operações demandadas pelos serviços a serem implementados eram do tipo CRUD (do inglês Create, Read, Update e Delete).…”
Section: Motivaçãounclassified