2007
DOI: 10.1007/978-3-540-73551-9_16
|View full text |Cite
|
Sign up to set email alerts
|

Soya: A Programming Model and Runtime Environment for Component Composition Using SSDL

Abstract: Abstract. The SOAP Service Description Language (SSDL) is a SOAPcentric language for describing Web Service contracts. SSDL focuses on message abstraction as the building block for creating service-oriented applications and provides an extensible range of protocol frameworks that can be used to describe and formally model component composition based on Web Service interactions. Given its novel approach, implementing support for SSDL contracts presents interesting challenges to middleware developers. At one end… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2012
2012
2018
2018

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(2 citation statements)
references
References 5 publications
0
2
0
Order By: Relevance
“…Requirements engineers in SOA usually use model driven approaches to specify the requirements of the services. Among the 24 service description methods found in the review, [7], [24], [25], [30], [26] use various model based approaches to describe services. There are modeling approaches like SMMA (Single Model Multiple Analysis) that can help even in generating codes from the models alone [15].…”
Section: Functional Vs Non Functional Requirements Description Methodsmentioning
confidence: 99%
See 1 more Smart Citation
“…Requirements engineers in SOA usually use model driven approaches to specify the requirements of the services. Among the 24 service description methods found in the review, [7], [24], [25], [30], [26] use various model based approaches to describe services. There are modeling approaches like SMMA (Single Model Multiple Analysis) that can help even in generating codes from the models alone [15].…”
Section: Functional Vs Non Functional Requirements Description Methodsmentioning
confidence: 99%
“…Table 2 shows the major problems discovered in the literature study. [4], [9], [14], [18][19][20][21][22][23][24][25][26] Gap between business oriented and IT oriented Service Realizations. [7], [16], [17], [27] Lack of dynamic adaptability and situation awareness [9], [14], [23], [28] Producer only centric approaches [29], [31] Imprecise Requirements Specification…”
Section: Rq2: Problem Faced In Describing Servicesmentioning
confidence: 99%