2008
DOI: 10.1016/j.entcs.2008.06.020
|View full text |Cite
|
Sign up to set email alerts
|

A Model-Based Approach to the Verification and Adaptation of WF/.NET Components

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
30
0

Year Published

2009
2009
2016
2016

Publication Types

Select...
6
1
1

Relationship

7
1

Authors

Journals

citations
Cited by 30 publications
(30 citation statements)
references
References 7 publications
0
30
0
Order By: Relevance
“…We use as running example an online hardware supplier. This example was originally presented in [9] and both participants (a supplier and a buyer) were implemented using the Microsoft WF/.NET technology. Figure 1 presents the LTSs corresponding to both peers.…”
Section: Synchronous Adaptationmentioning
confidence: 99%
“…We use as running example an online hardware supplier. This example was originally presented in [9] and both participants (a supplier and a buyer) were implemented using the Microsoft WF/.NET technology. Figure 1 presents the LTSs corresponding to both peers.…”
Section: Synchronous Adaptationmentioning
confidence: 99%
“…S is a set of states, I ∈ S is the initial state, F ⊆ S are final states, and T : S × A → S is the transition function. Please refer to lines [15][16][17] in the BNF grammar presented in Figure 9 for the specific syntax of a VLTS.…”
Section: Definition 7 (Vlts) a Vector Lts Is A Tuplementioning
confidence: 99%
“…For the sake of conciseness, in the rest of this paper we will describe service interfaces only with their STS, making explicit argument types in STS labels. The STS formal model has been chosen because it is simple, graphical, and it can be easily derived from existing implementation languages (see for instance [12,13,14,15] where such abstractions for Web services were used for verification, composition or adaptation purposes). In particular, signature information can be obtained for our models using the information available in WSDL descriptions, whereas STS information is derived from the specification of a service expressed in a behavioural IDL such as Abstract BPEL or Abstract Windows Workflows (see Figure 6).…”
Section: Definition 3 (Sts)mentioning
confidence: 99%
See 1 more Smart Citation
“…Client and service protocols can be instantiated several times. At the user level, client and service interfaces can be specified using: (i) context information into XML files for context profiles, (ii) WSDL for signatures, and (iii) business processes defined in industrial platforms, such as Abstract BPEL (ABPEL) [2] or WF workflows (AWF) [12], for protocols. Here, we assume context information is inferred by means of the client requests (HTTP header of SOAP messages), and we consider processes (clients and services) implemented as business processes which provide the WSDL and protocol descriptions.…”
Section: Definition 1 (Ca-sts Label)mentioning
confidence: 99%